Skip to main content

A General Mechanism for RTP Header Extensions

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Roni Even , David Singer , HariKishan Desineni
Last updated 2015-10-08
Replaced by RFC 8285
RFC stream (None)
Intended RFC status (None)
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 (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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
David Singer
HariKishan Desineni

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