A General Mechanism for RTP Header Extensions
draft-even-avtcore-rfc5285-bis-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Roni Even , David Singer , HariKishan Desineni | ||
| Last updated | 2015-10-08 | ||
| Replaced by | draft-ietf-avtcore-rfc5285-bis | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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:
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.
Authors
Roni Even
David Singer
HariKishan Desineni
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)