RFC 4289: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
In plain English — editorial summary, not part of the RFC
This document specifies IANA registration procedures for MIME external body access types and content-transfer-encodings. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4289
- Published
- December 2005
- Authors
- N. Freed; J. Klensin
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- BCP13
- Obsoletes:
- RFC 2048
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 2045Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesUpdated
November 1996
- RFC 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 1820Multimedia E-mail (MIME) User Agent ChecklistObsoleted
August 1995
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 3803Content Duration MIME Header DefinitionCurrent
June 2004
- RFC 3579RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)Updated
September 2003
- RFC 3525Gateway Control Protocol Version 1Obsoleted
June 2003
- RFC 5092IMAP URL SchemeUpdated
November 2007
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?