RFC 1590: Media Type Registration Procedure
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049.
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
Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content-type/subtypes). It also generalizes the scope of use of these Media Types to make it appropriate to use the same registrations and specifications with other applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1590
- Published
- March 1994
- Authors
- J. Postel
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 1521
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 2045Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message BodiesUpdated
November 1996
- RFC 2046Multipurpose Internet Mail Extensions (MIME) Part Two: Media TypesUpdated
November 1996
- RFC 2047MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII TextUpdated
November 1996
- RFC 2048Multipurpose Internet Mail Extensions (MIME) Part Four: Registration ProceduresObsoleted
November 1996
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1344Implications of MIME for Internet Mail GatewaysCurrent
June 1992
- RFC 1343A User Agent Configuration Mechanism for Multimedia Mail Format InformationCurrent
June 1992
- RFC 2183Communicating Presentation Information in Internet Messages: The Content-Disposition Header FieldUpdated
August 1997
- RFC 2184MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsObsoleted
August 1997
- RFC 2231MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and ContinuationsCurrent
November 1997
- RFC 1341MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message BodiesObsoleted
June 1992
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 1615Migrating from X.400(84) to X.400(88)Current
May 1994
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?