Mapping between X.400 and RFC-822 Message Bodies
RFC 1495, “Mapping between X.400 and RFC-822 Message Bodies”, is a Proposed Standard document published in August 1993 by H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson. It updates RFC 1327. It has been obsoleted by RFC 2156 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 1495 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 1494 Equivalences between 1988 X.400 and RFC-822 Message Bodies
- RFC 1496 Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
- RFC 1493 Definitions of Managed Objects for Bridges
- RFC 1497 BOOTP Vendor Information Extensions
- RFC 1492 An Access Control Protocol, Sometimes Called TACACS
- RFC 1498 On the Naming and Binding of Network Destinations
- RFC 1491 A Survey of Advanced Usages of X.500
- RFC 1490 Multiprotocol Interconnect over Frame Relay