RFC 9694: Guidelines for the Definition of New Top-Level Media Types
In plain English — editorial summary, not part of the RFC
This document defines best practices for defining new top-level media types. It also introduces a registry for top-level media types, and contains a short history of top-level media types. It updates RFC 6838.
Document record
- Document ID
- RFC9694
- Published
- March 2025
- Authors
- M.J. Dürst
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- art
- Pages
- 10
- Also known as
- BCP13
- Updates:
- RFC 6838
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9996Media Types for Protocol BuffersCurrent
July 2026
- RFC 6839Additional Media Type Structured Syntax SuffixesUpdated
January 2013
- RFC 9782Entity Attestation Token (EAT) Media TypesCurrent
May 2025
- RFC 9193Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-FormatCurrent
June 2022
- RFC 4735Example Media Types for Use in DocumentationCurrent
October 2006
- RFC 4027Domain Name System Media TypesCurrent
May 2005
- RFC 3676The Text/Plain Format and DelSp ParametersCurrent
February 2004
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 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?