metasystema.org
UpdatedBEST CURRENT PRACTICEIETF streamBCP13

RFC 6838: Media Type Specifications and Registration Procedures

Still current, but amended. Parts of this document are changed or extended by RFC 9694. Read both.

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 HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.

Document record

Document ID
RFC6838
Published
January 2013
Authors
N. Freed; J. Klensin; T. Hansen
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
art
Pages
32
Also known as
BCP13
Obsoletes:
RFC 4288
Updated by:
RFC 9694

Standards lineage

This document is one revision in a chain of 13 RFCs, each formally replacing the one before it.

  1. RFC 1341 (1992)
  2. RFC 1342 (1992)
  3. RFC 1521 (1993)
  4. RFC 1522 (1993)
  5. RFC 1590 (1994)
  6. RFC 2045 (1996)
  7. RFC 2046 (1996)
  8. RFC 2047 (1996)
  9. RFC 2048 (1996)
  10. RFC 2049 (1996)
  11. RFC 4288 (2005)
  12. RFC 4289 (2005)
  13. 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.

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?

canonical URL: /rfc/6838-media-type-specifications-and-registration-procedures