RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
In plain English — editorial summary, not part of the RFC
This particular document is the third document in the series. It describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2047
- Published
- November 1996
- Authors
- K. Moore
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 15
- 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
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
- 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
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 2503MIME Types for Use with the ISO ILL ProtocolCurrent
February 1999
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?