RFC 8285

A General Mechanism for RTP Header Extensions, October 2017

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Obsoletes:
RFC 5285
Authors:
D. Singer
H. Desineni
R. Even, Ed.
Stream:
IETF
Source:
avtcore (wit)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8285

Discuss this RFC: Send questions or comments to the mailing list avt@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8285


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search