A General Mechanism for RTP Header Extensions

Document Type Replaced Internet-Draft (individual)
Authors Roni Even  , David Singer  , HariKishan Desineni 
Last updated 2015-10-08
Replaced by RFC 8285
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-avtcore-rfc5285-bis
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Roni Even (roni.even@mail01.huawei.com)
David Singer (singer@apple.com)
HariKishan Desineni (hd@qualcomm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)