RFC 6838: Media Type Specifications and Registration Procedures

This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo…

Read RFC 6838 on the RFC Editor

Outgoing relationships (20 related RFCs)

Obsoletes, Informative reference — RFC 4288: Media Type Specifications and Registration Procedures
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Normative reference — RFC 3023: XML Media Types
Normative reference — RFC 4855: Media Type Registration of RTP Payload Formats
Normative reference — RFC 3979: Intellectual Property Rights in IETF Technology
Normative reference — RFC 6532: Internationalized Email Headers
Normative reference — RFC 2978: IANA Charset Registration Procedures
Normative reference — RFC 5378: Rights Contributors Provide to the IETF Trust
Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 2026: The Internet Standards Process -- Revision 3
Informative reference — RFC 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
Informative reference — RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Informative reference — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Informative reference — RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols

Incoming relationships (78 related RFCs)

Showing 50 of 78 related RFCs.

Updated by — RFC 9694: Guidelines for the Definition of New Top-Level Media Types
Normatively referenced by — RFC 7030: Enrollment over Secure Transport
Normatively referenced by — RFC 8225: PASSporT: Personal Assertion Token
Normatively referenced by — RFC 6920: Naming Things with Hashes
Normatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Normatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Normatively referenced by — RFC 7741: RTP Payload Format for VP8 Video
Normatively referenced by — RFC 8840: A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)
Normatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Normatively referenced by — RFC 7587: RTP Payload Format for the Opus Speech and Audio Codec
Normatively referenced by — RFC 9068: JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
Normatively referenced by — RFC 9205: Building Protocols with HTTP
Normatively referenced by — RFC 8081: The "font" Top-Level Media Type
Normatively referenced by — RFC 8091: A Media Type Structured Syntax Suffix for JSON Text Sequences
Normatively referenced by — RFC 9458: Oblivious HTTP
Normatively referenced by — RFC 9535: JSONPath: Query Expressions for JSON
Normatively referenced by — RFC 9557: Date and Time on the Internet: Timestamps with Additional Information
Normatively referenced by — RFC 9628: RTP Payload Format for VP9 Video
Normatively referenced by — RFC 9782: Entity Attestation Token (EAT) Media Types
Normatively referenced by — RFC 7193: The application/cms Media Type
Normatively referenced by — RFC 7320: URI Design and Ownership
Normatively referenced by — RFC 7763: The text/markdown Media Type
Normatively referenced by — RFC 8147: Next-Generation Pan-European eCall
Normatively referenced by — RFC 8148: Next-Generation Vehicle-Initiated Emergency Calls
Normatively referenced by — RFC 8894: Simple Certificate Enrolment Protocol
Normatively referenced by — RFC 9264: Linkset: Media Types and a Link Relation Type for Link Sets
Normatively referenced by — RFC 9559: Matroska Media Container Format Specification
Normatively referenced by — RFC 6922: The application/sql Media Type
Normatively referenced by — RFC 7351: A Media Type for XML Patch Operations
Normatively referenced by — RFC 7655: RTP Payload Format for G.711.0
Normatively referenced by — RFC 8255: Multiple Language Content Type
Normatively referenced by — RFC 8292: Voluntary Application Server Identification (VAPID) for Web Push
Normatively referenced by — RFC 8331: RTP Payload for Society of Motion Picture and Television Engineers (SMPTE) ST 291-1 Ancillary Data
Normatively referenced by — RFC 8817: RTP Payload Format for Tactical Secure Voice Cryptographic Interoperability Specification (TSVCIS) Codec
Normatively referenced by — RFC 9134: RTP Payload Format for ISO/IEC 21122 (JPEG XS)
Normatively referenced by — RFC 9237: An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9512: YAML Media Type
Normatively referenced by — RFC 9636: The Time Zone Information Format (TZif)
Normatively referenced by — RFC 9649: WebP Image Format
Normatively referenced by — RFC 9701: JSON Web Token (JWT) Response for OAuth Token Introspection
Normatively referenced by — RFC 9770: Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) Framework
Normatively referenced by — RFC 9901: Selective Disclosure for JSON Web Tokens
Normatively referenced by — RFC 9943: An Architecture for Trustworthy and Transparent Digital Supply Chains
Normatively referenced by — RFC 9996: Media Types for Protocol Buffers
Normatively referenced by — RFC 9999: Remote ATtestation procedureS (RATS) Conceptual Message Wrapper (CMW)
Informatively referenced by — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Informatively referenced by — RFC 7519: JSON Web Token (JWT)
Informatively referenced by — RFC 7515: JSON Web Signature (JWS)
Informatively referenced by — RFC 8949: Concise Binary Object Representation (CBOR)