RFC 1494: Equivalences between 1988 X.400 and RFC-822 Message Bodies
In plain English — editorial summary, not part of the RFC
This document describes the content of the "IANA MHS/MIME Equivalence table", and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1494
- Published
- August 1993
- Authors
- H. Alvestrand; S. Thompson
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1495Mapping between X.400 and RFC-822 Message BodiesObsoleted
August 1993
- RFC 1496Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messagesCurrent
August 1993
- RFC 1502X.400 Use of Extended Character SetsCurrent
August 1993
- RFC 1523The text/enriched MIME Content-typeObsoleted
September 1993
- RFC 1428Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIMECurrent
February 1993
- RFC 1427SMTP Service Extension for Message Size DeclarationObsoleted
February 1993
- RFC 1426SMTP Service Extension for 8bit-MIMEtransportObsoleted
February 1993
- RFC 1425SMTP Service ExtensionsObsoleted
February 1993
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?