A General Mechanism for RTP Header Extensions
RFC 5285, “A General Mechanism for RTP Header Extensions”, is a Proposed Standard document published in July 2008 by D. Singer, H. Desineni. It has been obsoleted by RFC 8285 — refer to the newer document for the authoritative version. 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 de-centralized. The actual extensions in use in a session are signaled in the setup information for that session. [STANDARDS-TRACK]
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 5285 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5284 User-Defined Errors for RSVP
- RFC 5286 Basic Specification for IP Fast Reroute: Loop-Free Alternates
- RFC 5283 LDP Extension for Inter-Area Label Switched Paths
- RFC 5287 Control Protocol Extensions for the Setup of Time-Division Multiplexing Pseudowires in MPLS Networks
- RFC 5282 Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 Protocol
- RFC 5288 AES Galois Counter Mode Cipher Suites for TLS
- RFC 5281 Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0
- RFC 5289 TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode