Title: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Author(s): N. Freed, N. Borenstein.
Status: DRAFT STANDARD
Date: Nov 1996
Length: 72932
Obsoletes: RFC1521, RFC1522, RFC1590
Updated by: RFC2184, RFC2231
STD 11, RFC822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for
(1) textual message bodies in character sets other than
US-ASCII,
(2) an extensible set of different formats for non-textual
message bodies,
(3) multi-part message bodies, and
(4) textual header information in character sets other than
US-ASCII.
These documents are based on earlier work documented in RFC934, STD 11, and RFC1049, but extends and revises them. Because RFC822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC822.
This initial document specifies the various headers used to describe the structure of MIME messages. The second document, RFC2046, defines the general structure of the MIME media typing system and defines an initial set of media types. The third document, RFC2047, describes extensions to RFC822 to allow non-US-ASCII text data in Internet mail header fields. The fourth document, RFC2048, specifies various IANA registration procedures for MIME-related facilities. The fifth and final document, RFC2049, describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography.
These documents are revisions of RFCs 1521, 1522, and 1590, which themselves were revisions of RFC1341 and RFC1341. An appendix in RFC2049 describes differences and changes from previous versions.
[sh-index] Back to list of manuals
|
| |
