draft-ietf-payload-vp9-08.txt   draft-ietf-payload-vp9-09.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
AVTCore Working Group J. Uberti AVTCore Working Group J. Uberti
Internet-Draft S. Holmer Internet-Draft S. Holmer
Intended status: Standards Track M. Flodman Intended status: Standards Track M. Flodman
Expires: July 16, 2020 D. Hong Expires: July 16, 2020 D. Hong
Google Google
J. Lennox J. Lennox
8x8 / Jitsi 8x8 / Jitsi
January 13, 2020 January 13, 2020
RTP Payload Format for VP9 Video RTP Payload Format for VP9 Video
draft-ietf-payload-vp9-08 draft-ietf-payload-vp9-09
Abstract Abstract
This memo describes an RTP payload format for the VP9 video codec. This memo describes an RTP payload format for the VP9 video codec.
The payload format has wide applicability, as it supports The payload format has wide applicability, as it supports
applications from low bit-rate peer-to-peer usage, to high bit-rate applications from low bit-rate peer-to-peer usage, to high bit-rate
video conferences. It includes provisions for temporal and spatial video conferences. It includes provisions for temporal and spatial
scalability. scalability.
Status of This Memo Status of This Memo
skipping to change at page 13, line 19 skipping to change at page 13, line 19
probability tables for the entropy and tree encoders. In VP9 syntax, probability tables for the entropy and tree encoders. In VP9 syntax,
the syntax element "error_resilient_mode" resets this additional the syntax element "error_resilient_mode" resets this additional
inter-frame data, allowing a frame's syntax to be decoded inter-frame data, allowing a frame's syntax to be decoded
independently. independently.
Due to the requirements of scalable streams, a VP9 encoder producing Due to the requirements of scalable streams, a VP9 encoder producing
a scalable stream needs to ensure that a frame does not depend on a a scalable stream needs to ensure that a frame does not depend on a
previous frame (of the same or a previous picture) that can previous frame (of the same or a previous picture) that can
legitimately be removed from the stream. Thus, a frame that follows legitimately be removed from the stream. Thus, a frame that follows
a removable frame (in full decode order) MUST be encoded with a removable frame (in full decode order) MUST be encoded with
"error_resilient_mode" to true. "error_resilient_mode" set to true.
For spatially-scalable streams, this means that For spatially-scalable streams, this means that
"error_resilient_mode" needs to be turned on for the base spatial "error_resilient_mode" needs to be turned on for the base spatial
layer; it can however be turned off for higher spatial layers, layer; it can however be turned off for higher spatial layers,
assuming they are sent with inter-layer dependency (i.e. with the "D" assuming they are sent with inter-layer dependency (i.e. with the "D"
bit set). For streams that are only temporally-scalable without bit set). For streams that are only temporally-scalable without
spatial scalability, "error_resilient_mode" can additionally be spatial scalability, "error_resilient_mode" can additionally be
turned off for any picture that immediately follows a temporal layer turned off for any picture that immediately follows a temporal layer
0 frame. 0 frame.
skipping to change at page 18, line 13 skipping to change at page 18, line 13
with the number assigned to this document and remove this note.] with the number assigned to this document and remove this note.]
Applications which use this media type: Applications which use this media type:
For example: Video over IP, video conferencing. For example: Video over IP, video conferencing.
Fragment identifier considerations: N/A. Fragment identifier considerations: N/A.
Additional information: None. Additional information: None.
Person & email address to contact for further information: Person & email address to contact for further information:
Jonathan Lennox %lt;jonathan.lennox@8x8.com%gt; Jonathan Lennox <jonathan.lennox@8x8.com&gt;
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
This media type depends on RTP framing, and hence is only defined This media type depends on RTP framing, and hence is only defined
for transfer via RTP [RFC3550]. for transfer via RTP [RFC3550].
Author: Jonathan Lennox %lt;jonathan.lennox@8x8.com%gt; Author: Jonathan Lennox <jonathan.lennox@8x8.com&gt;
Change controller: Change controller:
IETF AVTCore Working Group delegated from the IESG. IETF AVTCore Working Group delegated from the IESG.
+---------+------------+ +---------+------------+
| Profile | profile-id | | Profile | profile-id |
+---------+------------+ +---------+------------+
| 0 | 0 | | 0 | 0 |
| | | | | |
| 1 | 1 | | 1 | 1 |
 End of changes. 4 change blocks. 
4 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/