draft-ietf-payload-vp9-09.txt   draft-ietf-payload-vp9-10.txt 
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: January 8, 2021 D. Hong
Google Google
J. Lennox J. Lennox
8x8 / Jitsi 8x8 / Jitsi
January 13, 2020 July 7, 2020
RTP Payload Format for VP9 Video RTP Payload Format for VP9 Video
draft-ietf-payload-vp9-09 draft-ietf-payload-vp9-10
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 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 16, 2020. This Internet-Draft will expire on January 8, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions, Definitions and Acronyms . . . . . . . . . . . . 3 2. Conventions, Definitions and Acronyms . . . . . . . . . . . . 3
3. Media Format Description . . . . . . . . . . . . . . . . . . 3 3. Media Format Description . . . . . . . . . . . . . . . . . . 3
4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . 5 4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. RTP Header Usage . . . . . . . . . . . . . . . . . . . . 5 4.1. RTP Header Usage . . . . . . . . . . . . . . . . . . . . 5
4.2. VP9 Payload Descriptor . . . . . . . . . . . . . . . . . 6 4.2. VP9 Payload Descriptor . . . . . . . . . . . . . . . . . 6
4.2.1. Scalability Structure (SS): . . . . . . . . . . . . . 11 4.2.1. Scalability Structure (SS): . . . . . . . . . . . . . 11
4.3. Frame Fragmentation . . . . . . . . . . . . . . . . . . . 12 4.3. Frame Fragmentation . . . . . . . . . . . . . . . . . . . 13
4.4. Scalable encoding considerations . . . . . . . . . . . . 13 4.4. Scalable encoding considerations . . . . . . . . . . . . 13
4.5. Examples of VP9 RTP Stream . . . . . . . . . . . . . . . 13 4.5. Examples of VP9 RTP Stream . . . . . . . . . . . . . . . 14
4.5.1. Reference picture use for scalable structure . . . . 13 4.5.1. Reference picture use for scalable structure . . . . 14
5. Feedback Messages and Header Extensions . . . . . . . . . . . 14 5. Feedback Messages and Header Extensions . . . . . . . . . . . 14
5.1. Reference Picture Selection Indication (RPSI) . . . . . . 14 5.1. Reference Picture Selection Indication (RPSI) . . . . . . 15
5.2. Full Intra Request (FIR) . . . . . . . . . . . . . . . . 15 5.2. Full Intra Request (FIR) . . . . . . . . . . . . . . . . 15
5.3. Layer Refresh Request (LRR) . . . . . . . . . . . . . . . 15 5.3. Layer Refresh Request (LRR) . . . . . . . . . . . . . . . 15
5.4. Frame Marking . . . . . . . . . . . . . . . . . . . . . . 16 5.4. Frame Marking . . . . . . . . . . . . . . . . . . . . . . 16
6. Payload Format Parameters . . . . . . . . . . . . . . . . . . 16 6. Payload Format Parameters . . . . . . . . . . . . . . . . . . 17
6.1. Media Type Definition . . . . . . . . . . . . . . . . . . 16 6.1. Media Type Definition . . . . . . . . . . . . . . . . . . 17
6.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . 19 6.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . 19
6.2.1. Mapping of Media Subtype Parameters to SDP . . . . . 19 6.2.1. Mapping of Media Subtype Parameters to SDP . . . . . 19
6.2.2. Offer/Answer Considerations . . . . . . . . . . . . . 20 6.2.2. Offer/Answer Considerations . . . . . . . . . . . . . 20
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. Congestion Control . . . . . . . . . . . . . . . . . . . . . 21 8. Congestion Control . . . . . . . . . . . . . . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
11.1. Normative References . . . . . . . . . . . . . . . . . . 21 11.1. Normative References . . . . . . . . . . . . . . . . . . 21
11.2. Informative References . . . . . . . . . . . . . . . . . 22 11.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
This memo describes an RTP payload specification applicable to the This memo describes an RTP payload specification applicable to the
transmission of video streams encoded using the VP9 video codec transmission of video streams encoded using the VP9 video codec
[VP9-BITSTREAM]. The format described in this document can be used [VP9-BITSTREAM]. The format described in this document can be used
both in peer-to-peer and video conferencing applications. both in peer-to-peer and video conferencing applications.
The VP9 video codec was developed by Google, and is the successor to The VP9 video codec was developed by Google, and is the successor to
skipping to change at page 7, line 10 skipping to change at page 7, line 10
SSRC and CSRC identifiers) are used as specified in Section 5.1 of SSRC and CSRC identifiers) are used as specified in Section 5.1 of
[RFC3550]. [RFC3550].
4.2. VP9 Payload Descriptor 4.2. VP9 Payload Descriptor
In flexible mode (with the F bit below set to 1), The first octets In flexible mode (with the F bit below set to 1), The first octets
after the RTP header are the VP9 payload descriptor, with the after the RTP header are the VP9 payload descriptor, with the
following structure. following structure.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|I|P|L|F|B|E|V|-| (REQUIRED) |I|P|L|F|B|E|V|Z| (REQUIRED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
I: |M| PICTURE ID | (REQUIRED) I: |M| PICTURE ID | (REQUIRED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
M: | EXTENDED PID | (RECOMMENDED) M: | EXTENDED PID | (RECOMMENDED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED) L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED)
+-+-+-+-+-+-+-+-+ -\ +-+-+-+-+-+-+-+-+ -\
P,F: | P_DIFF |N| (CONDITIONALLY REQUIRED) - up to 3 times P,F: | P_DIFF |N| (CONDITIONALLY REQUIRED) - up to 3 times
+-+-+-+-+-+-+-+-+ -/ +-+-+-+-+-+-+-+-+ -/
V: | SS | V: | SS |
skipping to change at page 7, line 32 skipping to change at page 7, line 32
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 2 Figure 2
In non-flexible mode (with the F bit below set to 0), The first In non-flexible mode (with the F bit below set to 0), The first
octets after the RTP header are the VP9 payload descriptor, with the octets after the RTP header are the VP9 payload descriptor, with the
following structure. following structure.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|I|P|L|F|B|E|V|-| (REQUIRED) |I|P|L|F|B|E|V|Z| (REQUIRED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
I: |M| PICTURE ID | (RECOMMENDED) I: |M| PICTURE ID | (RECOMMENDED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
M: | EXTENDED PID | (RECOMMENDED) M: | EXTENDED PID | (RECOMMENDED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED) L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| TL0PICIDX | (CONDITIONALLY REQUIRED) | TL0PICIDX | (CONDITIONALLY REQUIRED)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
V: | SS | V: | SS |
skipping to change at page 9, line 9 skipping to change at page 9, line 9
VP9 frame, and 0 otherwise. This enables a decoder to finish VP9 frame, and 0 otherwise. This enables a decoder to finish
decoding the frame, where it otherwise may need to wait for the decoding the frame, where it otherwise may need to wait for the
next packet to explicitly know that the frame is complete. Note next packet to explicitly know that the frame is complete. Note
that, if spatial scalability is in use, more frames from the same that, if spatial scalability is in use, more frames from the same
picture may follow; see the description of the M bit above. picture may follow; see the description of the M bit above.
V: Scalability structure (SS) data present. When set to one, the V: Scalability structure (SS) data present. When set to one, the
OPTIONAL SS data MUST be present in the payload descriptor. OPTIONAL SS data MUST be present in the payload descriptor.
Otherwise, the SS data MUST NOT be present. Otherwise, the SS data MUST NOT be present.
-: Bit reserved for future use. MUST be set to zero and MUST be Z: Not a reference frame for upper spatial layers. If set to 1,
ignored by the receiver. indicates that frames with higher spatial layers SID+1 of the
current and following pictures do not depend on the current
spatial layer SID frame. This enables a decoder which is
targeting a higher spatial layer to know that it can safely
discard this packet's frame without processing it, without having
to wait for the "D" bit in the higher-layer frame (see below).
The mandatory first octet is followed by the extension data fields The mandatory first octet is followed by the extension data fields
that are enabled: that are enabled:
M: The most significant bit of the first octet is an extension flag. M: The most significant bit of the first octet is an extension flag.
The field MUST be present if the I bit is equal to one. If set, The field MUST be present if the I bit is equal to one. If set,
the PID field MUST contain 15 bits; otherwise, it MUST contain 7 the PID field MUST contain 15 bits; otherwise, it MUST contain 7
bits. See PID below. bits. See PID below.
Picture ID (PID): Picture ID represented in 7 or 15 bits, depending Picture ID (PID): Picture ID represented in 7 or 15 bits, depending
 End of changes. 12 change blocks. 
15 lines changed or deleted 20 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/