RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
In plain English — editorial summary, not part of the RFC
This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fifth and final document describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2049
- Published
- November 1996
- Authors
- N. Freed; N. Borenstein
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.
- RFC 1341 (1992)
- RFC 1342 (1992)
- RFC 1521 (1993)
- RFC 1522 (1993)
- RFC 1590 (1994)
- RFC 2045 (1996)
- RFC 2046 (1996)
- RFC 2047 (1996)
- RFC 2048 (1996)
- RFC 2049 (1996)
- RFC 4288 (2005)
- RFC 4289 (2005)
- RFC 6838 (2013) ✓
Read the full history of Media Type Specifications and Registration Procedures →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- RFC 2653CIP Transport ProtocolsCurrent
August 1999
- RFC 2362Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol SpecificationObsoleted
June 1998
- RFC 4601Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)Obsoleted
August 2006
- RFC 2048Multipurpose Internet Mail Extensions (MIME) Part Four: Registration ProceduresObsoleted
November 1996
- RFC 2045Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesUpdated
November 1996
- RFC 2077The Model Primary Content Type for Multipurpose Internet Mail ExtensionsUpdated
January 1997
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?