Debian Codegraph @

rfc2161.html

raw
1 <pre>Network Working Group H. Alvestrand
2 Request for Comments: 2161 UNINETT
3 Category: Experimental January 1998
4
5
6 <span class="h1">A MIME Body Part for ODA</span>
7
8 Status of this Memo
9
10 This memo defines an Experimental Protocol for the Internet
11 community. It does not specify an Internet standard of any kind.
12 Discussion and suggestions for improvement are requested.
13 Distribution of this memo is unlimited.
14
15 Copyright Notice
16
17 Copyright (C) The Internet Society (1998). All Rights Reserved.
18
19 Table of Contents
20
21 Status of this Memo ........................................ <a href="#page-1">1</a>
22 <a href="#section-1">1</a> Introduction .............................................. <a href="#page-1">1</a>
23 <a href="#section-1.1">1.1</a> The Application/ODA MIME content-type ................... <a href="#page-1">1</a>
24 <a href="#section-1.2">1.2</a> ODA - application/oda ................................... <a href="#page-2">2</a>
25 <a href="#section-2">2</a> Security Considerations ................................... <a href="#page-3">3</a>
26 <a href="#section-3">3</a> References ................................................ <a href="#page-4">4</a>
27 <a href="#section-4">4</a> Author's Address .......................................... <a href="#page-4">4</a>
28 <a href="#section-5">5</a> Full Copyright Statement .................................. <a href="#page-5">5</a>
29
30 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
31
32 This document contains the definitions, originally contained in <a href="./rfc1495">RFC</a>
33 <a href="./rfc1495">1495</a> and <a href="./rfc1341">RFC 1341</a>, on how to carry ODA in MIME, and how to translate
34 it to its X.400 representation.
35
36 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. The Application/ODA MIME content-type</span>
37
38 The "ODA" subtype of application is used to indicate that a body
39 contains information encoded according to the Office Document
40 Architecture [ODA] standards, using the ODIF representation
41 format. For application/oda, the Content-Type line should also
42 specify an attribute/value pair that indicates the document
43 application profile (DAP), using the key word "profile", and the
44 document class, using the keyword "class".
45
46 For the keyword "class", the values "formatted", "processable" and
47 "formatted-processable" are legal values.
48
49
50
51
52 <span class="grey">Alvestrand Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2161">RFC 2161</a> A MIME Body Part for ODA January 1998</span>
55
56
57 Thus an appropriate header field might look like this:
58
59 Content-Type: application/oda; profile=Q112; class=formatted
60
61 Consult the ODA standard [<a href="#ref-T.411">T.411</a>] for further information.
62
63 The Base64 content-transfer-encoding is appropriate for carrying ODA.
64
65
66 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. ODA - application/oda</span>
67
68 X.400 Body Part: ODA
69 MIME Content-Type: application/oda
70 Conversion: None
71 Comments:
72
73 The ODA body part is defined in the CCITT document T.411 [<a href="#ref-T.411">T.411</a>],
74 <a href="#appendix-E">appendix E</a>, section E.2, "ODA identification in the P2 protocol of
75 MHS"
76
77 An abbreviated version of its ASN.1 definition is:
78
79 oda-body-part EXTENDED-BODY-PART-TYPE
80 PARAMETERS OdaBodyPartParameters
81 DATA OdaData
82 ::= id-et-oda
83
84 OdaBodyPartParameters ::= SET {
85 document-application-profile [0] OBJECT IDENTIFIER
86 document-architecture-class [1] INTEGER {
87 formatted (0)
88 processable (1)
89 formatted-processable(2)}}
90
91 id-et-oda OBJECT IDENTIFIER ::= { 2 8 1 0 1 }
92
93 Mapping from X.400 to MIME, the following is done:
94
95 The Parameters.document-application-profile is mapped onto the MIME
96 parameter "profile" according to the table below.
97
98 Profile OBJECT IDENTIFIER
99
100 Q112 { iso (1) identified-organization (3) ewos (16)
101 eg (2) oda (6) profile (0) q112 (1) }
102
103
104
105
106
107
108 <span class="grey">Alvestrand Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2161">RFC 2161</a> A MIME Body Part for ODA January 1998</span>
111
112
113 The Parameters.document-architecture-class is mapped onto the MIME
114 parameter "class" according to the table below.
115
116 String Integer
117
118 formatted formatted(0)
119 processable processable(1)
120 formatted-processable formatted-processable(2)
121
122 NOTE: This parameter is not defined in <a href="./rfc1341">RFC 1341</a>.
123
124 The body of the MIME content-type is the Data part of the ODA body
125 part.
126
127 When mapping from MIME to X.400, the following steps are done:
128
129 The Parameters.document-application-profile and Parameters.document-
130 architecture-class are set from the tables above. If any of the
131 parameters are missing, the values for Q112 and formatted-processable
132 are used.
133
134 It is an option for the gateway implementor to try to access them
135 from inside the document, where they are defined as
136
137 document-profile.document-characteristics.document-architecture-class
138
139 document-profile.document-characteristics.document-application-
140 profile
141
142 Gateways are NOT required to do this, since the document-
143 characteristics are optional parameters. If a gateway does not, it
144 simply uses the defaulting rules defined above.
145
146 The OBJECT IDENTIFIERs for the document application profile and for
147 ODA {2 8 0 0} must be added to the Encoded Information Types
148 parameter of the message envelope.
149
150 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
151
152 ODA body parts have the natural propensity of complex structures that
153 it is hard to find out what the parts are capable of.
154
155 Moreover, ODA is an extensible architecture, where new content
156 portions may be added at any time, so that the threats posed by this
157 body part may change over time.
158
159 However, no security risks related to ODA are known at this time.
160
161
162
163
164 <span class="grey">Alvestrand Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2161">RFC 2161</a> A MIME Body Part for ODA January 1998</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. References</span>
170
171 [<a id="ref-MIME">MIME</a>]
172 Freed, N., and N. Borenstein, "Multipurpose
173 Internet Mail Extensions (MIME) Part One: Format of Internet Message
174 Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.
175
176 [<a id="ref-T.411">T.411</a>]
177 CCITT Recommendation T.411 (1988), Open Document Architecture
178 (ODA) and Interchange Format, Introduction and General
179 Principles.
180
181 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Author's Address</span>
182
183 Harald Tveit Alvestrand
184 UNINETT
185 Postboks 6883 Elgeseter
186 N-7002 TRONDHEIM
187
188 Phone: +47 73 59 70 94
189 EMail: [email protected]
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Alvestrand Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2161">RFC 2161</a> A MIME Body Part for ODA January 1998</span>
223
224
225 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Full Copyright Statement</span>
226
227 Copyright (C) The Internet Society (1998). All Rights Reserved.
228
229 This document and translations of it may be copied and furnished to
230 others, and derivative works that comment on or otherwise explain it
231 or assist in its implementation may be prepared, copied, published
232 and distributed, in whole or in part, without restriction of any
233 kind, provided that the above copyright notice and this paragraph are
234 included on all such copies and derivative works. However, this
235 document itself may not be modified in any way, such as by removing
236 the copyright notice or references to the Internet Society or other
237 Internet organizations, except as needed for the purpose of
238 developing Internet standards in which case the procedures for
239 copyrights defined in the Internet Standards process must be
240 followed, or as required to translate it into languages other than
241 English.
242
243 The limited permissions granted above are perpetual and will not be
244 revoked by the Internet Society or its successors or assigns.
245
246 This document and the information contained herein is provided on an
247 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
248 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
249 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
250 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
251 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 Alvestrand Experimental [Page 5]
277 </pre>