| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 04:52:01 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f6a5df4fb8c179-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9694 » RFC Editor
Search RFCs
- File formats:
- Also available: XML file for editing
- Status:
- BEST CURRENT PRACTICE
- Updates:
- RFC 6838
- Author:
- M.J. Dürst
- Stream:
- IETF
- Source:
- mediaman (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9694
Discuss this RFC: Send questions or comments to the mailing list media-types@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9694
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us