RFC 4288: Media Type Specifications and Registration Procedures
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6838.
Current document in this lineage: RFC 2045 — Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies; RFC 2046 — Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types; RFC 2047 — MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text; RFC 2049 — Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples; RFC 4289 — Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures; RFC 6838 — Media Type Specifications and Registration Procedures
In plain English — editorial summary, not part of the RFC
This document defines procedures for the specification and registration of media types for use in MIME and other Internet protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4288
- Published
- December 2005
- Authors
- N. Freed; J. Klensin
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- 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 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3870application/rdf+xml Media Type RegistrationCurrent
September 2004
- RFC 3855Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400Current
July 2004
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current
April 2004
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
- RFC 3464An Extensible Message Format for Delivery Status NotificationsUpdated
January 2003
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?