RFC 5285

A General Mechanism for RTP Header Extensions, July 2008

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Obsoleted by:
RFC 8285
Authors:
D. Singer
H. Desineni
Stream:
IETF
Source:
avt (rai)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC5285

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

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.