As per Relevance of the word experimental, we have this rfc below:
Network Working Group H.
Request for Comments: 2161
Category: Experimental January 1998
A MIME Body Part for
Status of this
This memo defines an Experimental Protocol for the
community. It does not specify an Internet standard of any kind
Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
Table of
Status of this Memo ........................................ 1
1 Introduction .............................................. 1
1.1 The Application/ODA MIME content-type ................... 1
1.2 ODA - application/oda ................................... 2
2 Security Considerations ................................... 3
3 References ................................................ 4
4 Author's Address .......................................... 4
5 Full Copyright Statement .................................. 5
1.
This document contains the definitions, originally contained in
1495 and RFC 1341, on how to carry ODA in MIME, and how to
it to its X.400 representation
1.1. The Application/ODA MIME content-
The "ODA" subtype of application is used to indicate that a
contains information encoded according to the Office
Architecture [ODA] standards, using the ODIF
format. For application/oda, the Content-Type line should
specify an attribute/value pair that indicates the
application profile (DAP), using the key word "profile", and
document class, using the keyword "class".
For the keyword "class", the values "formatted", "processable"
"formatted-processable" are legal values
Alvestrand Experimental [Page 1]
RFC 2161 A MIME Body Part for ODA January 1998
Thus an appropriate header field might look like this
Content-Type: application/oda; profile=Q112; class=
Consult the ODA standard [T.411] for further information
The Base64 content-transfer-encoding is appropriate for carrying ODA
1.2. ODA - application/
X.400 Body Part:
MIME Content-Type: application/
Conversion:
Comments
The ODA body part is defined in the CCITT document T.411 [T.411],
appendix E, section E.2, "ODA identification in the P2 protocol
MHS
An abbreviated version of its ASN.1 definition is
oda-body-part EXTENDED-BODY-PART-
PARAMETERS
DATA
::= id-et-
OdaBodyPartParameters ::= SET {
document-application-profile [0] OBJECT
document-architecture-class [1] INTEGER {
formatted (0)
processable (1)
formatted-processable(2)}}
id-et-oda OBJECT IDENTIFIER ::= { 2 8 1 0 1 }
Mapping from X.400 to MIME, the following is done
The Parameters.document-application-profile is mapped onto the
parameter "profile" according to the table below
Profile OBJECT
Q112 { iso (1) identified-organization (3) ewos (16)
eg (2) oda (6) profile (0) q112 (1) }
Alvestrand Experimental [Page 2]
RFC 2161 A MIME Body Part for ODA January 1998
The Parameters.document-architecture-class is mapped onto the
parameter "class" according to the table below
String
formatted formatted(0)
processable processable(1)
formatted-processable formatted-processable(2)
NOTE: This parameter is not defined in RFC 1341.
The body of the MIME content-type is the Data part of the ODA
part
When mapping from MIME to X.400, the following steps are done
The Parameters.document-application-profile and Parameters.document
architecture-class are set from the tables above. If any of
parameters are missing, the values for Q112 and formatted-
are used
It is an option for the gateway implementor to try to access
from inside the document, where they are defined
document-profile.document-characteristics.document-architecture-
document-profile.document-characteristics.document-application
Gateways are NOT required to do this, since the document
characteristics are optional parameters. If a gateway does not,
simply uses the defaulting rules defined above
The OBJECT IDENTIFIERs for the document application profile and
ODA {2 8 0 0} must be added to the Encoded Information
parameter of the message envelope
2. Security
ODA body parts have the natural propensity of complex structures
it is hard to find out what the parts are capable of
Moreover, ODA is an extensible architecture, where new
portions may be added at any time, so that the threats posed by
body part may change over time
However, no security risks related to ODA are known at this time
Alvestrand Experimental [Page 3]
RFC 2161 A MIME Body Part for ODA January 1998
3.
[MIME
Freed, N., and N. Borenstein, "
Internet Mail Extensions (MIME) Part One: Format of Internet
Bodies", RFC 2045, November 1996.
[T.411]
CCITT Recommendation T.411 (1988), Open Document
(ODA) and Interchange Format, Introduction and
Principles
4. Author's
Harald Tveit
Postboks 6883
N-7002
Phone: +47 73 59 70 94
EMail: Harald.T.Alvestrand@uninett.
Alvestrand Experimental [Page 4]
RFC 2161 A MIME Body Part for ODA January 1998
5. Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Alvestrand Experimental [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
