1496
HISTORIC
Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
Authors: H. Alvestrand, J. Romaguera, K. Jordan
Date: August 1993
Area: app
Working Group: mimemhs
Stream: IETF
Abstract
This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK]
RFC 1496
HISTORIC
Network Working Group H. Alvestrand
Request for Comments: 1496 SINTEF DELAB
Updates: <a href="./rfc1328">1328</a> J. Romaguera
NetConsult AG
K. Jordan
Control Data Systems, Inc.
August 1993
<span class="h1">Rules for Downgrading Messages from X.400/88 to X.400/84 When</span>
<span class="h1">MIME Content-Types are Present in the Messages</span>
Status of this Memo
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
Table of Contents
<a href="#section-1">1</a>. Introduction ............................................... <a href="#page-1">1</a>
<a href="#section-2">2</a>. Basic approach ............................................. <a href="#page-2">2</a>
<a href="#section-3">3</a>. Conversion rules ........................................... <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a> EBP conversions to Basic .................................. <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a> Encapsulation format ...................................... <a href="#page-3">3</a>
<a href="#section-4">4</a>. Implications ............................................... <a href="#page-4">4</a>
<a href="#section-5">5</a>. Security Considerations .................................... <a href="#page-4">4</a>
<a href="#section-6">6</a>. Authors' Addresses ......................................... <a href="#page-4">4</a>
<a href="#section-7">7</a>. References ................................................. <a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Interworking between X.400(88) and MIME is achieved by [<a href="#ref-4" title=""Mapping between X.400 and RFC-822 Message Bodies"">4</a>], which
complements <a href="./rfc1327">RFC-1327</a> [<a href="#ref-2" title=""Mapping between X.400(1988) / ISO 10021 and RFC-822"">2</a>], which in turn specifies the interworking
between X.400(88) and <a href="./rfc822">RFC-822</a> based mail.
Interworking between X.400(88) and X.400 (84) is achieved by <a href="./rfc1328">RFC-1328</a>
[<a href="#ref-3" title=""X.400 1988 to 1984 downgrading"">3</a>]. That document does not describe what to do in the case where
body parts arrive at the gateway that cannot be adequately
represented in the X.400(84) system.
This document describes how <a href="./rfc1328">RFC-1328</a> must be modified in order to
provide adequate support for the scenarios:
SMTP(MIME) -> X.400(84)
X.400(84) -> SMTP(MIME)
<span class="grey">Alvestrand, Romaguera & Jordan [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc1496">RFC 1496</a> HARPOON August 1993</span>
It replaces chapter 6 of <a href="./rfc1328">RFC-1328</a>. The rest of <a href="./rfc1328">RFC-1328</a> is NOT
obsoleted.
NOTE: A desireable side-effect of HARPOON is that a standardized
method for the identification and transmission of multimedia and
binary data (like spreadsheets) between X.400/84 UAs is achieved.
While this method is not compatible with current proprietary
approaches, we believe that it requires less invasive changes to
current UAs than other possible methods.
This memo updates <a href="./rfc1328">RFC 1328</a>. HARPOON is a pure name, and has no
meaning. Please send comments to the MIME-MHS mailing list
<mime-mhs@surnet.nl>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Basic approach</span>
The approach is to imagine that the connection X.400(84) <->
SMTP(MIME) never happens. This, of course, is an illusion, but can be
a very useful illusion.
All mail will therefore go on one of the paths
X.400(84) -> X.400(88) -> SMTP(MIME)
SMTP(MIME) -> X.400(88) -> X.400(84)
when it goes between a MIME user and an X.400(84) user.
The approach at the interface between X.400(88) and X.400(84) is:
o Convert what you can
o Encapsulate what you have to
o Never drop a message
Of course, for X.400/88 body parts that are already defined in
X.400/84, no downgrading should be done. In particular, multi-body
messages should remain multi-body messages, IA5 messages including
IA5 messages encoded as Extended Body Parts) should remain IA5
messages, and G3Fax messages should remain G3Fax messages.
<span class="grey">Alvestrand, Romaguera & Jordan [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc1496">RFC 1496</a> HARPOON August 1993</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Conversion rules</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. EBP conversions to Basic</span>
Some body parts are defined by X.400(88) as having both a Basic form
and an Extended form. These are listed in Annex B of X.420.
For all of these, the transformation from the Extended Body Part to
the Basic Body Part takes the form of putting the PARAMETERS and the
DATA members together in a SEQUENCE.
This transformation should be applied by the gateway in order to
allow (for example) X.400(88) systems that use the Extended form of
the IA5 body part to communicate with X.400(84) systems.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Encapsulation format</span>
For any body part that cannot be used directly in X.400(84), the
following IA5Text body part is made:
- Content = IA5String
- First bytes of content: (the description is in USASCII, with C
escape sequences used to represent control characters):
MIME-version: <version>\r\n
Content-type: <the proper MIME content type>\r\n
Content-transfer-encoding: <quoted-printable or base64>\r\n
<Possibly other Content headings here, terminated by\r\n>
\r\n
<Here follows the bytes of the content, as per [<a href="#ref-4" title=""Mapping between X.400 and RFC-822 Message Bodies"">4</a>], encoded in the
proper encoding>
All implementations MUST place the MIME-version: header first in the
body part. Headers that are placed by [<a href="#ref-2" title=""Mapping between X.400(1988) / ISO 10021 and RFC-822"">2</a>] and [<a href="#ref-4" title=""Mapping between X.400 and RFC-822 Message Bodies"">4</a>] into other parts of
the message MUST NOT be placed in the MIME body part.
This includes <a href="./rfc822">RFC-822</a> headings carried as heading-extensions, which
must be placed in a new IA5 body part starting with the string "<a href="./rfc822">RFC-</a>
<a href="./rfc822">822</a>-HEADERS", as specified in [<a href="#ref-2" title=""Mapping between X.400(1988) / ISO 10021 and RFC-822"">2</a>], <a href="#appendix-G">Appendix G</a>.
Other heading-extensions are still handled as described in chapter 5
of <a href="./rfc1328">RFC 1328</a>: They are dropped.
Since all X.400(88) body parts can be represented in MIME by using
the x400-bp MIME content-type, this conversion will never fail.
<span class="grey">Alvestrand, Romaguera & Jordan [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc1496">RFC 1496</a> HARPOON August 1993</span>
In the reverse direction, any IA5 body part that starts with the
token "MIME-Version:" will be subjected to conversion according to
[<a href="#ref-4" title=""Mapping between X.400 and RFC-822 Message Bodies"">4</a>] before including the body part into an X.400(88) message.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Implications</span>
The implications are several:
- People with X.400(84) readers who have the ability to save messages
to file will now be able to save MIME multimedia messages
- People who can use features like the "Mailcaps" file to identify
what to do about a bodypart can now grab implementations of MIME
that can run as subprograms and achieve at least some multimedia
functionality
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
The security considerations in [<a href="#ref-1" title=""MIME: Mechanisms for Specifying and Describing the Format of Internet Message Bodies"">1</a>] and [<a href="#ref-4" title=""Mapping between X.400 and RFC-822 Message Bodies"">4</a>] (beware of trojans that
can hit you if your UA automagically starts programs for you) are now
relevant also for X.400(84) systems.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Authors' Addresses</span>
Harald Tveit Alvestrand
SINTEF DELAB
N-7034 Trondheim
NORWAY
EMail: [email protected]
Kevin E. Jordan, ARH215
Control Data Systems, Inc.
4201 Lexington Avenue N
Arden Hills, MN 55126
USA
EMail: [email protected]
James A. Romaguera
NetConsult AG
Mettlendwaldweg 20a
3037 Herrenschwanden
Switzerland
EMail: [email protected]
<span class="grey">Alvestrand, Romaguera & Jordan [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc1496">RFC 1496</a> HARPOON August 1993</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
[<a id="ref-1">1</a>] Borenstein, N, and N. Freed, "MIME: Mechanisms for Specifying
and Describing the Format of Internet Message Bodies", <a href="./rfc1341">RFC 1341</a>,
Bellcore, Innosoft, June 1992.
[<a id="ref-2">2</a>] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021
and <a href="./rfc822">RFC-822</a>", <a href="./rfc1327">RFC 1327</a>, University College London, May 1992.
[<a id="ref-3">3</a>] Hardcastle-Kille, S., "X.400 1988 to 1984 downgrading", <a href="./rfc1328">RFC</a>
<a href="./rfc1328">1328</a>, University College London, May 1992.
[<a id="ref-4">4</a>] Alvestrand, H., Kille, S., Miles, R., Rose, M., and S. Thompson,
"Mapping between X.400 and <a href="./rfc822">RFC-822</a> Message Bodies", <a href="./rfc1494">RFC 1494</a>,
SINTEF DELAB, ISODE Consortium, Soft*Switch, Inc, Dover Beach
Consulting, Inc., Soft*Switch, Inc., August 1993.
Alvestrand, Romaguera & Jordan [Page 5]
Annotations
Select text to annotate