RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
In plain English — editorial summary, not part of the RFC
RFC 2046 defines MIME media types — the type/subtype strings such as text/html and application/json that tell software how to interpret a body of bytes — along with multipart message structure.
Original abstract from the RFC
This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2046
- Published
- November 1996
- Authors
- N. Freed; N. Borenstein
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 44
- 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 →
Referenced by
5 later RFCs formally update or obsolete part of this document.
- RFC 2646The Text/Plain Format ParameterObsoleted
August 1999
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 5147URI Fragment Identifiers for the text/plain Media TypeCurrent
April 2008
- RFC 6657Update to MIME regarding "charset" Parameter Handling in Textual Media TypesCurrent
July 2012
- RFC 8098Message Disposition NotificationCurrent
February 2017
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2045Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesUpdated
November 1996
- RFC 1609Charting Networks in the X.500 DirectoryCurrent
March 1994
- RFC 1608Representing IP Information in the X.500 DirectoryCurrent
March 1994
- RFC 2562Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)Current
April 1999
- RFC 3406Uniform Resource Names (URN) Namespace Definition MechanismsObsoleted
October 2002
- RFC 1698Octet Sequences for Upper-Layer OSI to Support Basic Communications ApplicationsCurrent
October 1994
- RFC 3470Guidelines for the Use of Extensible Markup Language (XML) within IETF ProtocolsUpdated
January 2003
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
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?