Mapping between X.400(1988) / ISO 10021 and RFC 822
RFC 1327
| Document | Type |
RFC - Proposed Standard
(May 1992; No errata)
Obsoleted by RFC 2156
Updated by RFC 1495
Updates RFC 822
Was draft-ietf-kille-x_400mapping (individual)
|
|
|---|---|---|---|
| Authors | |||
| Last updated | 2013-03-02 | ||
| Stream | Legacy stream | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Stream | Legacy state | (None) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | RFC 1327 (Proposed Standard) | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
Network Working Group S. Hardcastle-Kille
Request for Comments: 1327 University College London
Obsoletes: RFCs 987, 1026, 1138, 1148 May 1992
Updates: RFC 822
Mapping between X.400(1988) / ISO 10021 and RFC 822
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.
Abstract
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. This
document is a revision based on RFCs 987, 1026, 1138, and 1148
[Kille86a,Kille87a] which it obsoletes.
This document specifies a mapping between two protocols. This
specification should be used when this mapping is performed on the
DARPA Internet or in the UK Academic Community. This specification
may be modified in the light of implementation experience, but no
substantial changes are expected.
Table of Contents
1 - Overview ...................................... 3
1.1 - X.400 ......................................... 3
1.2 - RFC 822 ....................................... 3
1.3 - The need for conversion ....................... 4
1.4 - General approach .............................. 4
1.5 - Gatewaying Model .............................. 5
1.6 - X.400 (1984) .................................. 8
1.7 - Compatibility with previous versions .......... 8
1.8 - Aspects not covered ........................... 8
1.9 - Subsetting .................................... 9
1.10 - Document Structure ............................ 9
Hardcastle-Kille [Page 1]
RFC 1327 Mapping between X.400(1988) and RFC 822 May 1992
1.11 - Acknowledgements .............................. 9
2 - Service Elements .............................. 10
2.1 - The Notion of Service Across a Gateway ........ 10
2.2 - RFC 822 ....................................... 11
2.3 - X.400 ......................................... 15
3 - Basic Mappings ................................ 24
3.1 - Notation ...................................... 24
3.2 - ASCII and IA5 ................................. 26
3.3 - Standard Types ................................ 26
3.4 - Encoding ASCII in Printable String ............ 28
4 - Addressing .................................... 30
4.1 - A textual representation of MTS.ORAddress ..... 30
4.2 - Basic Representation .......................... 31
4.3 - EBNF.822-address <-> MTS.ORAddress ............ 36
4.4 - Repeated Mappings ............................. 48
4.5 - Directory Names ............................... 50
4.6 - MTS Mappings .................................. 50
4.7 - IPMS Mappings ................................. 55
5 - Detailed Mappings ............................. 59
5.1 - RFC 822 -> X.400 .............................. 59
5.2 - Return of Contents ............................ 67
5.3 - X.400 -> RFC 822 .............................. 67
Appendix A - Mappings Specific to SMTP ..................... 91
Appendix B - Mappings specific to the JNT Mail ............. 91
1 - Introduction .................................. 91
2 - Domain Ordering ............................... 91
3 - Addressing .................................... 91
4 - Acknowledge-To: .............................. 91
5 - Trace ......................................... 92
6 - Timezone specification ........................ 92
7 - Lack of 822-MTS originator specification ...... 92
Appendix C - Mappings specific to UUCP Mail ................ 93
Appendix D - Object Identifier Assignment .................. 94
Appendix E - BNF Summary ................................... 94
Appendix F - Format of address mapping tables .............. 101
1 - Global Mapping Information .................... 101
Show full document text