RFC 1138:Mapping between X.400(1988) / ISO 10021 a...
RFC-Ref

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


1. Chapter 1 -- Overview
1.1. X.400
1.2. RFC 822
1.3. The need for conversion
1.4. General approach
1.5. Gatewaying Model
1.5.1. X.400
1.5.2. RFC 822
1.5.3. The Gateway
1.5.4. Repeated Mappings
1.6. RFC 987
1.7. Aspects not covered
1.8. Subsetting
1.9. Document Structure
1.10. Acknowledgements
2. Chapter 2 -- Service Elements
2.1. The Notion of Service Across a Gateway
2.1.1. Origination of Messages
2.1.2. Reception of Messages
2.2. RFC 822
2.2.1. Origination in RFC 822
2.2.2. Reception by RFC 822
2.3. X.400
2.3.1. Origination in X.400
2.3.1.1. Basic Interpersonal Messaging Service
2.3.1.2. IPM Service Optional User Facilities
2.3.2. Reception by X.400
2.3.2.1. Standard Mandatory Services
2.3.2.2. Standard Optional Services
2.3.2.3. New Services
3. Chapter 3 -- Basic Mappings
3.1. Notation
3.1.1. RFC 822
3.1.2. ASN.1
3.2. ASCII and IA5
3.3. Standard Types
3.3.1. Boolean
3.3.2. NumericString
3.3.3. PrintableString
3.3.4. T.61String
3.3.5. UTCTime
3.3.6. Integer
3.3.7. Object Identifier
3.4. Encoding ASCII in Printable String
4. Chapter 4 -- Addressing
4.1. A textual representation of MTS.ORAddress
4.2. Basic Representation
4.2.1. Encoding of Personal Name
4.2.2. Standard Encoding of MTS.ORAddress
4.3. EBNF.822-address <-> MTS.ORAddress
4.3.1. X.400 encoded in RFC 822
4.3.2. RFC 822 encoded in X.400
4.3.3. Component Ordering
4.3.4. RFC 822 -> X.400
4.3.5. X.400 -> RFC 822
4.4. Repeated Mappings
4.5. Directory Names
4.6. MTS Mappings
4.6.1. RFC 822 -> X.400
4.6.2. X.400 -> RFC 822
4.6.2.1. MTS Mappings
4.6.2.2. Generation of RFC 822 Headers
4.6.2.3. Delivery Report Generation
4.6.3. Message IDs (MTS)
4.7. IPMS Mappings
4.7.1. RFC 822 -> X.400
4.7.2. X.400 -> RFC 822
4.7.3. IP Message IDs
4.7.3.1. msg-id represented in X.400
4.7.3.2. IPMS.IPMIdentifier represented in RFC 822
4.7.3.3. msg-id -> IPMS.IPMIdentifier
4.7.3.4. IPMS.IPMIdentifier -> 822.msg-id
4.7.3.5. Phrase form
4.7.3.6. RFC 987 backwards compatibility
5. Chapter 5 -- Detailed Mappings
5.1. RFC 822 -> X.400
5.1.1. Basic Approach
5.1.2. X.400 Extension Field
5.1.3. Generating the IPM
5.1.4. Mappings to the MTS Abstract Service
5.1.5. Mappings to the MTA Abstract Service
5.1.6. Mapping New Fields
5.2. Return of Contents
5.3. X.400 -> RFC 822
5.3.1. Basic Approach
5.3.2. RFC 822 Settings
5.3.3. Basic Mappings
5.3.3.1. Encoded Information Types
5.3.3.2. Global Domain Identifier
5.3.4. Mappings from the IP Message
5.3.5. Mappings from an IP Notification
5.3.6. Mappings from the MTS Abstract Service
5.3.7. Mappings from the MTA Abstract Service
5.3.8. Mappings from Report Delivery
5.3.8.1. MTS Mappings
5.3.8.2. MTA Mappings
5.3.8.3. Example Delivery Report
5.3.9. Probe
6. Appendix A - Differences with RFC 987
7. Appendix B - Mappings specific to the JNT Mail
8. Appendix C - Mappings specific to UUCP Mail
9. Appendix D - Object Identifier Assignment
10. Appendix E - BNF Summary
11. Appendix F - Format of address mapping tables
12. References
13. Security Considerations
14. Author's Address

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org