Frame Marking RTP Header Extension
draft-berger-avtext-framemarking-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Espen Berger , Suhas Nandakumar , Mo Zanaty | ||
| Last updated | 2015-07-06 | ||
| Replaced by | draft-ietf-avtext-framemarking | ||
| 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-avtext-framemarking | |
| 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 describes a Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted, and essential when the middlebox or node has no access to the media encryption keys. It is also useful for codec-agnostic processing of encrypted or unencrypted media, while it also supports extensions for codec-specific information.
Authors
Espen Berger
Suhas Nandakumar
Mo Zanaty
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)