A General Mechanism for RTP Header Extensions
RFC 8285, “A General Mechanism for RTP Header Extensions”, is a Proposed Standard document published in October 2017 by D. Singer, H. Desineni, R. Even. It obsoletes RFC 5285. The canonical text is published by the RFC Editor.
Abstract
This document provides a general mechanism to use the header extension feature of RTP (the Real-time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is decentralized. The actual extensions in use in a session are signaled in the setup information for that session. This document obsoletes RFC 5285.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8285 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8284 Lightweight Directory Access Protocol Schema for Supporting the Extensible Messaging and Presence Protocol in White Pages
- RFC 8286 RTP/RTCP Extension for RTP Splicing Notification
- RFC 8283 An Architecture for Use of PCE and the PCE Communication Protocol in a Network with Central Control
- RFC 8287 Label Switched Path Ping/Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers with MPLS Data Planes
- RFC 8282 Extensions to the Path Computation Element Communication Protocol for Inter-Layer MPLS and GMPLS Traffic Engineering
- RFC 8288 Web Linking
- RFC 8281 Path Computation Element Communication Protocol Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
- RFC 8280 Research into Human Rights Protocol Considerations