Frame Marking RTP Header Extension
draft-ietf-avtext-framemarking-11
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Mo Zanaty , Espen Berger , Suhas Nandakumar | ||
Last updated | 2021-02-05 (Latest revision 2020-08-04) | ||
Replaces | draft-berger-avtext-framemarking | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
ARTART Last Call review
(of
-13)
by Martin Thomson
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Waiting for WG Chair Go-Ahead | |
Associated WG milestone |
|
||
Document shepherd | Jonathan Lennox | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Jonathan Lennox <jonathan.lennox@8x8.com> |
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 decryption keys. It is also useful for codec-agnostic processing of encrypted or unencrypted media, while it also supports extensions for codec-specific information.
Authors
Mo Zanaty
Espen Berger
Suhas Nandakumar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)