Mapping between X.400(1988) / ISO 10021 and RFC 822

Abstract

Mapping between X.400(1988) / ISO 10021 and RFC 822 Status of this Memo This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. Distribution of this memo is unlimited. This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 (1988) Recommendations on Message Handling Systems / ISO IEC 10021 Message Oriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems using the RFC 822 mail protocol [Crocker82a] or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings. The mappings should not require any changes to end systems. Kille [Page 2] RFC 1138 Mapping X.400(88) and 822 December 1989 (MOTIS). This ISO/CCITT standard is referred to in this document as "X.400", which is a convenient shorthand. Any reference to the 1984 CCITT Recommendations will be explicit. X.400 defines an Interpersonal Messaging System (IPMS), making use of a store and forward Message Transfer System. This document relates to the IPMS, and not to wider application of X.400. It is expected that X.400 will be implemented very widely. 1.2. RFC 822 RFC 822 is the current specification of the messaging standard on the Internet. This standard evolved with the evolution of the network from the ARPANET (created by the Defense Advanced Research Projects Agency) to the Internet, which now involves over 1000 networks and is sponsored by DARPA, NSF, DOE, NASA, and NIH. It specifies an end to end message format. It is used in conjunction with a number of different message transfer protocol environments. SMTP Networks On the Internet and other TCP/IP networks, RFC 822 is used in conjunction with two other standards: RFC 821, also known as Simple Mail Transfer Protocol (SMTP) [Postel82a], and RFC 1034 which is a Specification for domains and a distributed name service [Mockapetris87a]. UUCP Networks UUCP is the UNIX to UNIX CoPy protocol, which is usually used over dialup telephone networks to provide a simple message transfer mechanism. There are some extensions to RFC 822, particularly in the addressing. They use domains which conform to RFC 1034, but not the corresponding domain nameservers [Horton86a]. Csnet Some portions of Csnet follow the Internet protocols. The dialup portion of Csnet uses the Phonenet protocols as a replacement for RFC 821. This portion uses domains which conform to RFC 1034, but not the corresponding domain nameservers. Bitnet Some parts of Bitnet and related networks use RFC 822 related protocols, with EBCDIC encoding. Kille [Page 3] RFC 1138 Mapping X.400(88) and 822 December 1989 JNT Mail Networks A number of X.25 networks, particularly those associated with the UK Academic Community, use the JNT (Joint Network Team) Mail Protocol, also known as Greybook [Kille84a]. This is used with domains and name service specified ...

MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME

“…These are RFCs 987, 1026RFCs 987, , 1138RFCs 987, , 1148RFCs 987, and 1327. This document is a revision of RFC 1327 [21]. As far as possible, changes have been made in a compatible fashion.…”

Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses

“…The "table 3" mapping defined in RFC 1327 [2] is provided by the associatedX400Gateway attribute. This value may identify multiple possible associated gateways.…”

X.400(1988) for the Academic and Research Community in Europe

“…-In order to maintain the widest connectivity with the highest possible functionality, gateways should be installed that gateway between X.400(1988) and RFC 822/MIME. These gateways should follow the specifications of RFC 1327 [1] and RFC 1494 et al [4]. Experience with these gateways should be fed back into the appropriate RARE and IETF Working Groups to improve the standards.…”