RFC 9751: Closing the RTP Payload Format Media Types Registry
In plain English — editorial summary, not part of the RFC
The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA "RTP Payload Format Media Types" registry as recommended by RFC 8088. To simplify the process and rely only on the "Media Types" registry, this document closes the RTP payload- specific registry. In addition, it updates the instruction in RFC 8088 to reflect this change.
Document record
- Document ID
- RFC9751
- Published
- March 2025
- Authors
- M. Westerlund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 8088
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9754Extensions for Opening and Delegating Files in NFSv4.2Current
March 2025
- RFC 9745The Deprecation HTTP Response Header FieldCurrent
March 2025
- RFC 9743Specifying New Congestion Control AlgorithmsCurrent
March 2025
- RFC 9737Reporting Errors in NFSv4.2 via LAYOUTRETURNCurrent
February 2025
- RFC 9766Extensions for Weak Cache Consistency in NFSv4.2's Flexible File LayoutCurrent
April 2025
- RFC 9768More Accurate Explicit Congestion Notification (AccECN) Feedback in TCPCurrent
April 2026
- RFC 9729The Concealed HTTP Authentication SchemeCurrent
February 2025
- RFC 9727api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIsCurrent
June 2025
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?