idnits 2.17.1 draft-ietf-payload-vp9-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 7, 2020) is 1389 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-16) exists of draft-ietf-avtext-framemarking-10 ** Downref: Normative reference to an Experimental draft: draft-ietf-avtext-framemarking (ref. 'I-D.ietf-avtext-framemarking') ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) -- Possible downref: Non-RFC (?) normative reference: ref. 'VP9-BITSTREAM' Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 AVTCore Working Group J. Uberti 3 Internet-Draft S. Holmer 4 Intended status: Standards Track M. Flodman 5 Expires: January 8, 2021 D. Hong 6 Google 7 J. Lennox 8 8x8 / Jitsi 9 July 7, 2020 11 RTP Payload Format for VP9 Video 12 draft-ietf-payload-vp9-10 14 Abstract 16 This memo describes an RTP payload format for the VP9 video codec. 17 The payload format has wide applicability, as it supports 18 applications from low bit-rate peer-to-peer usage, to high bit-rate 19 video conferences. It includes provisions for temporal and spatial 20 scalability. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 8, 2021. 39 Copyright Notice 41 Copyright (c) 2020 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions, Definitions and Acronyms . . . . . . . . . . . . 3 58 3. Media Format Description . . . . . . . . . . . . . . . . . . 3 59 4. Payload Format . . . . . . . . . . . . . . . . . . . . . . . 5 60 4.1. RTP Header Usage . . . . . . . . . . . . . . . . . . . . 5 61 4.2. VP9 Payload Descriptor . . . . . . . . . . . . . . . . . 6 62 4.2.1. Scalability Structure (SS): . . . . . . . . . . . . . 11 63 4.3. Frame Fragmentation . . . . . . . . . . . . . . . . . . . 13 64 4.4. Scalable encoding considerations . . . . . . . . . . . . 13 65 4.5. Examples of VP9 RTP Stream . . . . . . . . . . . . . . . 14 66 4.5.1. Reference picture use for scalable structure . . . . 14 67 5. Feedback Messages and Header Extensions . . . . . . . . . . . 14 68 5.1. Reference Picture Selection Indication (RPSI) . . . . . . 15 69 5.2. Full Intra Request (FIR) . . . . . . . . . . . . . . . . 15 70 5.3. Layer Refresh Request (LRR) . . . . . . . . . . . . . . . 15 71 5.4. Frame Marking . . . . . . . . . . . . . . . . . . . . . . 16 72 6. Payload Format Parameters . . . . . . . . . . . . . . . . . . 17 73 6.1. Media Type Definition . . . . . . . . . . . . . . . . . . 17 74 6.2. SDP Parameters . . . . . . . . . . . . . . . . . . . . . 19 75 6.2.1. Mapping of Media Subtype Parameters to SDP . . . . . 19 76 6.2.2. Offer/Answer Considerations . . . . . . . . . . . . . 20 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 78 8. Congestion Control . . . . . . . . . . . . . . . . . . . . . 21 79 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 80 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 81 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 82 11.1. Normative References . . . . . . . . . . . . . . . . . . 21 83 11.2. Informative References . . . . . . . . . . . . . . . . . 23 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 86 1. Introduction 88 This memo describes an RTP payload specification applicable to the 89 transmission of video streams encoded using the VP9 video codec 90 [VP9-BITSTREAM]. The format described in this document can be used 91 both in peer-to-peer and video conferencing applications. 93 The VP9 video codec was developed by Google, and is the successor to 94 its earlier VP8 [RFC6386] codec. Above the compression improvements 95 and other general enhancements above VP8, VP9 is also designed in a 96 way that allows spatially-scalable video encoding. 98 2. Conventions, Definitions and Acronyms 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 3. Media Format Description 106 The VP9 codec can maintain up to eight reference frames, of which up 107 to three can be referenced by any new frame. 109 VP9 also allows a frame to use another frame of a different 110 resolution as a reference frame. (Specifically, a frame may use any 111 references whose width and height are between 1/16th that of the 112 current frame and twice that of the current frame, inclusive.) This 113 allows internal resolution changes without requiring the use of key 114 frames. 116 These features together enable an encoder to implement various forms 117 of coarse-grained scalability, including temporal, spatial and 118 quality scalability modes, as well as combinations of these, without 119 the need for explicit scalable coding tools. 121 Temporal layers define different frame rates of video; spatial and 122 quality layers define different and possibly dependent 123 representations of a single input frame. Spatial layers allow a 124 frame to be encoded at different resolutions, whereas quality layers 125 allow a frame to be encoded at the same resolution but at different 126 qualities (and thus with different amounts of coding error). VP9 127 supports quality layers as spatial layers without any resolution 128 changes; hereinafter, the term "spatial layer" is used to represent 129 both spatial and quality layers. 131 This payload format specification defines how such temporal and 132 spatial scalability layers can be described and communicated. 134 Temporal and spatial scalability layers are associated with non- 135 negative integer IDs. The lowest layer of either type has an ID of 136 0, and is sometimes referred to as the "base" temporal or spatial 137 layer. 139 Layers are designed (and MUST be encoded) such that if any layer, and 140 all higher layers, are removed from the bitstream along either of the 141 two dimensions, the remaining bitstream is still correctly decodable. 143 For terminology, this document uses the term "frame" to refer to a 144 single encoded VP9 frame for a particular resolution/quality, and 145 "picture" to refer to all the representations (frames) at a single 146 instant in time. A picture thus consists of one or more frames, 147 encoding different spatial layers. 149 Within a picture, a frame with spatial layer ID equal to SID, where 150 SID > 0, can depend on a frame of the same picture with a lower 151 spatial layer ID. This "inter-layer" dependency can result in 152 additional coding gain compared to the case where only traditional 153 "inter-picture" dependency is used, where a frame depends on 154 previously coded frame in time. For simplicity, this payload format 155 assumes that, within a picture and if inter-layer dependency is used, 156 a spatial layer SID frame can depend only on the immediately previous 157 spatial layer SID-1 frame, when S > 0. Additionally, if inter- 158 picture dependency is used, a spatial layer SID frame is assumed to 159 only depend on a previously coded spatial layer SID frame. 161 Given above simplifications for inter-layer and inter-picture 162 dependencies, a flag (the D bit described below) is used to indicate 163 whether a spatial layer SID frame depends on the spatial layer SID-1 164 frame. Given the D bit, a receiver only needs to additionally know 165 the inter-picture dependency structure for a given spatial layer 166 frame in order to determine its decodability. Two modes of 167 describing the inter-picture dependency structure are possible: 168 "flexible mode" and "non-flexible mode". An encoder can only switch 169 between the two on the first packet of a key frame with temporal 170 layer ID equal to 0. 172 In flexible mode, each packet can contain up to 3 reference indices, 173 which identify all frames referenced by the frame transmitted in the 174 current packet for inter-picture prediction. This (along with the D 175 bit) enables a receiver to identify if a frame is decodable or not 176 and helps it understand the temporal layer structure. Since this is 177 signaled in each packet it makes it possible to have very flexible 178 temporal layer hierarchies and patterns which are changing 179 dynamically. 181 In non-flexible mode, the inter-picture dependency (the reference 182 indices) of a Picture Group (PG) MUST be pre-specified as part of the 183 scalability structure (SS) data. In this mode, each packet has an 184 index to refer to one of the described pictures in the PG, from which 185 the pictures referenced by the picture transmitted in the current 186 packet for inter-picture prediction can be identified. 188 (Editor's Note: A "Picture Group", as used in this document, is not 189 the same thing as a the term "Group of Pictures" as it is 190 traditionally used in video coding, i.e. to mean an independently- 191 decoadable run of pictures beginning with a keyframe. Suggestions 192 for better terminology are welcome.) 193 The SS data can also be used to specify the resolution of each 194 spatial layer present in the VP9 stream for both flexible and non- 195 flexible modes. 197 4. Payload Format 199 This section describes how the encoded VP9 bitstream is encapsulated 200 in RTP. To handle network losses usage of RTP/AVPF [RFC4585] is 201 RECOMMENDED. All integer fields in the specifications are encoded as 202 unsigned integers in network octet order. 204 4.1. RTP Header Usage 206 The general RTP payload format for VP9 is depicted below. 208 0 1 2 3 209 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 |V=2|P|X| CC |M| PT | sequence number | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | timestamp | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | synchronization source (SSRC) identifier | 216 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 217 | contributing source (CSRC) identifiers | 218 | .... | 219 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 220 | VP9 payload descriptor (integer #octets) | 221 : : 222 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | : VP9 pyld hdr | | 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 225 | | 226 + | 227 : Bytes 2..N of VP9 payload : 228 | | 229 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 | : OPTIONAL RTP padding | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 The VP9 payload descriptor will be described in Section 4.2; the VP9 234 payload header is described in [VP9-BITSTREAM]. OPTIONAL RTP padding 235 MUST NOT be included unless the P bit is set. The figure 236 specifically shows the format for the first packet in a frame. 237 Subsequent packets will not contain the VP9 payload header, and will 238 have later octets in the frame payload. 240 Figure 1 242 Marker bit (M): MUST be set to 1 for the final packet of the highest 243 spatial layer frame (the final packet of the picture), and 0 244 otherwise. Unless spatial scalability is in use for this picture, 245 this will have the same value as the E bit described below. Note 246 this bit MUST be set to 1 for the target spatial layer frame if a 247 stream is being rewritten to remove higher spatial layers. 249 Payload Type (PT): In line with the policy in Section 3 of 250 [RFC3551], applications using the VP9 RTP payload profile MUST 251 assign a dynamic payload type number to be used in each RTP 252 session and provide a mechanism to indicate the mapping. See 253 Section 6.2 for the mechanism to be used with the Session 254 Description Protocol (SDP) [RFC4566]. 256 Timestamp: The RTP timestamp indicates the time when the input frame 257 was sampled, at a clock rate of 90 kHz. If the input picture is 258 encoded with multiple layer frames, all of the frames of the 259 picture MUST have the same timestamp. 261 If a frame has the VP9 show_frame field set to 0 (i.e., it is 262 meant only to populate a reference buffer, without being output) 263 its timestamp MAY alternately be set to be the same as the 264 subsequent frame with show_frame equal to 1. (This will be 265 convenient for playing out pre-encoded content packaged with VP9 266 "superframes", which typically bundle show_frame==0 frames with a 267 subsequent show_frame==1 frame.) Every frame with show_frame==1, 268 however, MUST have a unique timestamp modulo the 2^32 wrap of the 269 field. 271 The remaining RTP Fixed Header Fields (V, P, X, CC, sequence number, 272 SSRC and CSRC identifiers) are used as specified in Section 5.1 of 273 [RFC3550]. 275 4.2. VP9 Payload Descriptor 276 In flexible mode (with the F bit below set to 1), The first octets 277 after the RTP header are the VP9 payload descriptor, with the 278 following structure. 280 0 1 2 3 4 5 6 7 281 +-+-+-+-+-+-+-+-+ 282 |I|P|L|F|B|E|V|Z| (REQUIRED) 283 +-+-+-+-+-+-+-+-+ 284 I: |M| PICTURE ID | (REQUIRED) 285 +-+-+-+-+-+-+-+-+ 286 M: | EXTENDED PID | (RECOMMENDED) 287 +-+-+-+-+-+-+-+-+ 288 L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED) 289 +-+-+-+-+-+-+-+-+ -\ 290 P,F: | P_DIFF |N| (CONDITIONALLY REQUIRED) - up to 3 times 291 +-+-+-+-+-+-+-+-+ -/ 292 V: | SS | 293 | .. | 294 +-+-+-+-+-+-+-+-+ 296 Figure 2 298 In non-flexible mode (with the F bit below set to 0), The first 299 octets after the RTP header are the VP9 payload descriptor, with the 300 following structure. 302 0 1 2 3 4 5 6 7 303 +-+-+-+-+-+-+-+-+ 304 |I|P|L|F|B|E|V|Z| (REQUIRED) 305 +-+-+-+-+-+-+-+-+ 306 I: |M| PICTURE ID | (RECOMMENDED) 307 +-+-+-+-+-+-+-+-+ 308 M: | EXTENDED PID | (RECOMMENDED) 309 +-+-+-+-+-+-+-+-+ 310 L: | TID |U| SID |D| (CONDITIONALLY RECOMMENDED) 311 +-+-+-+-+-+-+-+-+ 312 | TL0PICIDX | (CONDITIONALLY REQUIRED) 313 +-+-+-+-+-+-+-+-+ 314 V: | SS | 315 | .. | 316 +-+-+-+-+-+-+-+-+ 318 Figure 3 320 I: Picture ID (PID) present. When set to one, the OPTIONAL PID MUST 321 be present after the mandatory first octet and specified as below. 323 Otherwise, PID MUST NOT be present. If the SS field was present 324 in the stream's most recent start of a keyframe (i.e., non- 325 flexible scalability mode is in use), then the PID MUST also be 326 present in every packet. 328 P: Inter-picture predicted frame. When set to zero, the frame does 329 not utilize inter-picture prediction. In this case, up-switching 330 to a current spatial layer's frame is possible from directly lower 331 spatial layer frame. P SHOULD also be set to zero when encoding a 332 layer synchronization frame in response to an LRR 333 [I-D.ietf-avtext-lrr] message (see Section 5.3). When P is set to 334 zero, the TID field (described below) MUST also be set to 0 (if 335 present). Note that the P bit does not forbid intra-picture, 336 inter-layer prediction from earlier frames of the same picture, if 337 any. 339 L: Layer indices present. When set to one, the one or two octets 340 following the mandatory first octet and the PID (if present) is as 341 described by "Layer indices" below. If the F bit (described 342 below) is set to 1 (indicating flexible mode), then only one octet 343 is present for the layer indices. Otherwise if the F bit is set 344 to 0 (indicating non-flexible mode), then two octets are present 345 for the layer indices. 347 F: Flexible mode. F set to one indicates flexible mode and if the P 348 bit is also set to one, then the octets following the mandatory 349 first octet, the PID, and layer indices (if present) are as 350 described by "Reference indices" below. This MUST only be set to 351 1 if the I bit is also set to one; if the I bit is set to zero, 352 then this MUST also be set to zero and ignored by receivers. The 353 value of this F bit MUST only change on the first packet of a key 354 picture. A key picture is a picture whose base spatial layer 355 frame is a key frame, and which thus completely resets the encoder 356 state. This packet will have its P bit equal to zero, SID or D 357 bit (described below) equal to zero, and B bit (described below) 358 equal to 1. 360 B: Start of a frame. MUST be set to 1 if the first payload octet of 361 the RTP packet is the beginning of a new VP9 frame, and MUST NOT 362 be 1 otherwise. Note that this frame might not be the first frame 363 of a picture. 365 E: End of a frame. MUST be set to 1 for the final RTP packet of a 366 VP9 frame, and 0 otherwise. This enables a decoder to finish 367 decoding the frame, where it otherwise may need to wait for the 368 next packet to explicitly know that the frame is complete. Note 369 that, if spatial scalability is in use, more frames from the same 370 picture may follow; see the description of the M bit above. 372 V: Scalability structure (SS) data present. When set to one, the 373 OPTIONAL SS data MUST be present in the payload descriptor. 374 Otherwise, the SS data MUST NOT be present. 376 Z: Not a reference frame for upper spatial layers. If set to 1, 377 indicates that frames with higher spatial layers SID+1 of the 378 current and following pictures do not depend on the current 379 spatial layer SID frame. This enables a decoder which is 380 targeting a higher spatial layer to know that it can safely 381 discard this packet's frame without processing it, without having 382 to wait for the "D" bit in the higher-layer frame (see below). 384 The mandatory first octet is followed by the extension data fields 385 that are enabled: 387 M: The most significant bit of the first octet is an extension flag. 388 The field MUST be present if the I bit is equal to one. If set, 389 the PID field MUST contain 15 bits; otherwise, it MUST contain 7 390 bits. See PID below. 392 Picture ID (PID): Picture ID represented in 7 or 15 bits, depending 393 on the M bit. This is a running index of the pictures. The field 394 MUST be present if the I bit is equal to one. If M is set to 395 zero, 7 bits carry the PID; else if M is set to one, 15 bits carry 396 the PID in network byte order. The sender may choose between a 7- 397 or 15-bit index. The PID SHOULD start on a random number, and 398 MUST wrap after reaching the maximum ID. The receiver MUST NOT 399 assume that the number of bits in PID stay the same through the 400 session. 402 In the non-flexible mode (when the F bit is set to 0), this PID is 403 used as an index to the picture group (PG) specified in the SS 404 data below. In this mode, the PID of the key frame corresponds to 405 the first specified frame in the PG. Then subsequent PIDs are 406 mapped to subsequently specified frames in the PG (modulo N_G, 407 specified in the SS data below), respectively. 409 All frames of the same picture MUST have the same PID value. 411 Frames (and their corresponding pictures) with the VP9 show_frame 412 field equal to 0 MUST have distinct PID values from subsequent 413 pictures with show_frame equal to 1. Thus, a Picture as defined 414 in this specification is different than a VP9 Superframe. 416 All frames of the same picture MUST have the same value for 417 show_frame. 419 Layer indices: This information is optional but recommended whenever 420 encoding with layers. For both flexible and non-flexible modes, 421 one octet is used to specify a layer frame's temporal layer ID 422 (TID) and spatial layer ID (SID) as shown both in Figure 2 and 423 Figure 3. Additionally, a bit (U) is used to indicate that the 424 current frame is a "switching up point" frame. Another bit (D) is 425 used to indicate whether inter-layer prediction is used for the 426 current frame. 428 In the non-flexible mode (when the F bit is set to 0), another 429 octet is used to represent temporal layer 0 index (TL0PICIDX), as 430 depicted in Figure 3. The TL0PICIDX is present so that all 431 minimally required frames - the base temporal layer frames - can 432 be tracked. 434 The TID and SID fields indicate the temporal and spatial layers 435 and can help middleboxes and and endpoints quickly identify which 436 layer a packet belongs to. 438 TID: The temporal layer ID of current frame. In the case of non- 439 flexible mode, if PID is mapped to a picture in a specified PG, 440 then the value of TID MUST match the corresponding TID value of 441 the mapped picture in the PG. 443 U: Switching up point. If this bit is set to 1 for the current 444 picture with temporal layer ID equal to TID, then "switch up" 445 to a higher frame rate is possible as subsequent higher 446 temporal layer pictures will not depend on any picture before 447 the current picture (in coding order) with temporal layer ID 448 greater than TID. 450 SID: The spatial layer ID of current frame. Note that frames 451 with spatial layer SDI > 0 may be dependent on decoded spatial 452 layer SID-1 frame within the same picture. Different frames of 453 the same picture MUST have distinct spatial layer IDs, and 454 frames' spatial layers MUST appear in increasing order within 455 the frame. 457 D: Inter-layer dependency used. MUST be set to one if current 458 spatial layer SID frame depends on spatial layer SID-1 frame of 459 the same picture. MUST only be set to zero if current spatial 460 layer SID frame does not depend on spatial layer SID-1 frame of 461 the same picture. For the base layer frame (with SID equal to 462 0), this D bit MUST be set to zero. 464 TL0PICIDX: 8 bits temporal layer zero index. TL0PICIDX is only 465 present in the non-flexible mode (F = 0). This is a running 466 index for the temporal base layer pictures, i.e., the pictures 467 with TID set to 0. If TID is larger than 0, TL0PICIDX 468 indicates which temporal base layer picture the current picture 469 depends on. TL0PICIDX MUST be incremented when TID is equal to 470 0. The index SHOULD start on a random number, and MUST restart 471 at 0 after reaching the maximum number 255. 473 Reference indices: When P and F are both set to one, indicating a 474 non-key frame in flexible mode, then at least one reference index 475 has to be specified as below. Additional reference indices (total 476 of up to 3 reference indices are allowed) may be specified using 477 the N bit below. When either P or F is set to zero, then no 478 reference index is specified. 480 P_DIFF: The reference index (in 7 bits) specified as the relative 481 PID from the current picture. For example, when P_DIFF=3 on a 482 packet containing the picture with PID 112 means that the 483 picture refers back to the picture with PID 109. This 484 calculation is done modulo the size of the PID field, i.e., 485 either 7 or 15 bits. 487 N: 1 if there is additional P_DIFF following the current P_DIFF. 489 4.2.1. Scalability Structure (SS): 491 The scalability structure (SS) data describes the resolution of each 492 frame within a picture as well as the inter-picture dependencies for 493 a picture group (PG). If the VP9 payload descriptor's "V" bit is 494 set, the SS data is present in the position indicated in Figure 2 and 495 Figure 3. 497 +-+-+-+-+-+-+-+-+ 498 V: | N_S |Y|G|-|-|-| 499 +-+-+-+-+-+-+-+-+ -\ 500 Y: | WIDTH | (OPTIONAL) . 501 + + . 502 | | (OPTIONAL) . 503 +-+-+-+-+-+-+-+-+ . - N_S + 1 times 504 | HEIGHT | (OPTIONAL) . 505 + + . 506 | | (OPTIONAL) . 507 +-+-+-+-+-+-+-+-+ -/ 508 G: | N_G | (OPTIONAL) 509 +-+-+-+-+-+-+-+-+ -\ 510 N_G: | TID |U| R |-|-| (OPTIONAL) . 511 +-+-+-+-+-+-+-+-+ -\ . - N_G times 512 | P_DIFF | (OPTIONAL) . - R times . 513 +-+-+-+-+-+-+-+-+ -/ -/ 515 Figure 4 517 N_S: N_S + 1 indicates the number of spatial layers present in the 518 VP9 stream. 520 Y: Each spatial layer's frame resolution present. When set to one, 521 the OPTIONAL WIDTH (2 octets) and HEIGHT (2 octets) MUST be 522 present for each layer frame. Otherwise, the resolution MUST NOT 523 be present. 525 G: PG description present flag. 527 -: Bit reserved for future use. MUST be set to zero and MUST be 528 ignored by the receiver. 530 N_G: N_G indicates the number of pictures in a Picture Group (PG). 531 If N_G is greater than 0, then the SS data allows the inter- 532 picture dependency structure of the VP9 stream to be pre-declared, 533 rather than indicating it on the fly with every packet. If N_G is 534 greater than 0, then for N_G pictures in the PG, each picture's 535 temporal layer ID (TID), switch up point (U), and the R reference 536 indices (P_DIFFs) are specified. 538 The first picture specified in the PG MUST have TID set to 0. 540 G set to 0 or N_G set to 0 indicates that either there is only one 541 temporal layer or no fixed inter-picture dependency information is 542 present going forward in the bitstream. 544 Note that for a given picture, all frames follow the same inter- 545 picture dependency structure. However, the frame rate of each 546 spatial layer can be different from each other and this can be 547 controlled with the use of the D bit described above. The 548 specified dependency structure in the SS data MUST be for the 549 highest frame rate layer. 551 In a scalable stream sent with a fixed pattern, the SS data SHOULD be 552 included in the first packet of every key frame. This is a packet 553 with P bit equal to zero, SID or D bit equal to zero, and B bit equal 554 to 1. The SS data MUST only be changed on the picture that 555 corresponds to the first picture specified in the previous SS data's 556 PG (if the previous SS data's N_G was greater than 0). 558 4.3. Frame Fragmentation 560 VP9 frames are fragmented into packets, in RTP sequence number order, 561 beginning with a packet with the B bit set, and ending with a packet 562 with the E bit set. There is no mechanism for finer-grained access 563 to parts of a VP9 frame. 565 4.4. Scalable encoding considerations 567 In addition to the use of reference frames, VP9 has several 568 additional forms of inter-frame dependencies, largely involving 569 probability tables for the entropy and tree encoders. In VP9 syntax, 570 the syntax element "error_resilient_mode" resets this additional 571 inter-frame data, allowing a frame's syntax to be decoded 572 independently. 574 Due to the requirements of scalable streams, a VP9 encoder producing 575 a scalable stream needs to ensure that a frame does not depend on a 576 previous frame (of the same or a previous picture) that can 577 legitimately be removed from the stream. Thus, a frame that follows 578 a removable frame (in full decode order) MUST be encoded with 579 "error_resilient_mode" set to true. 581 For spatially-scalable streams, this means that 582 "error_resilient_mode" needs to be turned on for the base spatial 583 layer; it can however be turned off for higher spatial layers, 584 assuming they are sent with inter-layer dependency (i.e. with the "D" 585 bit set). For streams that are only temporally-scalable without 586 spatial scalability, "error_resilient_mode" can additionally be 587 turned off for any picture that immediately follows a temporal layer 588 0 frame. 590 4.5. Examples of VP9 RTP Stream 592 4.5.1. Reference picture use for scalable structure 594 As discussed in Section 3, the VP9 codec can maintain up to eight 595 reference frames, of which up to three can be referenced or updated 596 by any new frame. This section illustrates one way that a scalable 597 structure (with three spatial layers and three temporal layers) can 598 be constructed using these reference frames. 600 +----------+---------+------------+---------+ 601 | Temporal | Spatial | References | Updates | 602 +----------+---------+------------+---------+ 603 | 0 | 0 | 0 | 0 | 604 | | | | | 605 | 0 | 1 | 0,1 | 1 | 606 | | | | | 607 | 0 | 2 | 1,2 | 2 | 608 | | | | | 609 | 2 | 0 | 0 | 6 | 610 | | | | | 611 | 2 | 1 | 1,6 | 7 | 612 | | | | | 613 | 2 | 2 | 2,7 | - | 614 | | | | | 615 | 1 | 0 | 0 | 3 | 616 | | | | | 617 | 1 | 1 | 1,3 | 4 | 618 | | | | | 619 | 1 | 2 | 2,4 | 5 | 620 | | | | | 621 | 2 | 0 | 3 | 6 | 622 | | | | | 623 | 2 | 1 | 4,6 | 7 | 624 | | | | | 625 | 2 | 2 | 5,7 | - | 626 +----------+---------+------------+---------+ 628 Example scalability structure 630 This structure is constructed such that the "U" bit can always be 631 set. 633 5. Feedback Messages and Header Extensions 634 5.1. Reference Picture Selection Indication (RPSI) 636 The reference picture selection index is a payload-specific feedback 637 message defined within the RTCP-based feedback format. The RPSI 638 message is generated by a receiver and can be used in two ways. 639 Either it can signal a preferred reference picture when a loss has 640 been detected by the decoder -- preferably then a reference that the 641 decoder knows is perfect -- or, it can be used as positive feedback 642 information to acknowledge correct decoding of certain reference 643 pictures. The positive feedback method is useful for VP9 used for 644 point to point (unicast) communication. The use of RPSI for VP9 is 645 preferably combined with a special update pattern of the codec's two 646 special reference frames -- the golden frame and the altref frame -- 647 in which they are updated in an alternating leapfrog fashion. When a 648 receiver has received and correctly decoded a golden or altref frame, 649 and that frame had a PictureID in the payload descriptor, the 650 receiver can acknowledge this simply by sending an RPSI message back 651 to the sender. The message body (i.e., the "native RPSI bit string" 652 in [RFC4585]) is simply the PictureID of the received frame. 654 Note: because all frames of the same picture must have the same 655 inter-picture reference structure, there is no need for a message to 656 specify which frame is being selected. 658 5.2. Full Intra Request (FIR) 660 The Full Intra Request (FIR) [RFC5104] RTCP feedback message allows a 661 receiver to request a full state refresh of an encoded stream. 663 Upon receipt of an FIR request, a VP9 sender MUST send a picture with 664 a keyframe for its spatial layer 0 layer frame, and then send frames 665 without inter-picture prediction (P=0) for any higher layer frames. 667 5.3. Layer Refresh Request (LRR) 669 The Layer Refresh Request [I-D.ietf-avtext-lrr] allows a receiver to 670 request a single layer of a spatially or temporally encoded stream to 671 be refreshed, without necessarily affecting the stream's other 672 layers. 674 +---------------+---------------+ 675 |0|1|2|3|4|5|6|7|0|1|2|3|4|5|6|7| 676 +---------------+---------+-----+ 677 | RES | TID | RES | SID | 678 +---------------+---------+-----+ 680 Figure 5 682 Figure 5 shows the format of LRR's layer index fields for VP9 683 streams. The two "RES" fields MUST be set to 0 on transmission and 684 ingnored on reception. See Section 4.2 for details on the TID and 685 SID fields. 687 Identification of a layer refresh frame can be derived from the 688 reference IDs of each frame by backtracking the dependency chain 689 until reaching a point where only decodable frames are being 690 referenced. Therefore it's recommended for both the flexible and the 691 non-flexible mode that, when upgrade frames are being encoded in 692 response to a LRR, those packets should contain layer indices and the 693 reference fields so that the decoder or an MCU can make this 694 derivation. 696 Example: 698 LRR {1,0}, {2,1} is sent by an MCU when it is currently relaying 699 {1,0} to a receiver and which wants to upgrade to {2,1}. In response 700 the encoder should encode the next frames in layers {1,1} and {2,1} 701 by only referring to frames in {1,0}, or {0,0}. 703 In the non-flexible mode, periodic upgrade frames can be defined by 704 the layer structure of the SS, thus periodic upgrade frames can be 705 automatically identified by the picture ID. 707 5.4. Frame Marking 709 The Frame Marking RTP header extension [I-D.ietf-avtext-framemarking] 710 is a mechanism to provide information about frames of video streams 711 in a largely codec-independent manner. However, for its extension 712 for scalable codecs, the specific manner in which codec layers are 713 identified needs to be specified specifically for each codec. This 714 section defines how frame marking is used with VP9. 716 0 1 2 3 717 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 719 | ID=2 | L=2 |S|E|I|D|B| TID |0|0|0|0|0| SID | TL0PICIDX | 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 722 Figure 6 724 When this header extension is used with VP9, the TID and SID fields 725 MUST match the values in the packet which the header extension is 726 attached to; see Section 4.2 for details on these fields. 728 See [I-D.ietf-avtext-framemarking] for explanations of the other 729 fields, which are generic. 731 6. Payload Format Parameters 733 This payload format has two optional parameters. 735 6.1. Media Type Definition 737 This registration is done using the template defined in [RFC6838] and 738 following [RFC4855]. 740 Type name: video 742 Subtype name: VP9 744 Required parameters: None. 746 Optional parameters: 747 These parameters are used to signal the capabilities of a receiver 748 implementation. If the implementation is willing to receive 749 media, both parameters MUST be provided. These parameters MUST 750 NOT be used for any other purpose. 752 max-fr: The value of max-fr is an integer indicating the maximum 753 frame rate in units of frames per second that the decoder is 754 capable of decoding. 756 max-fs: The value of max-fs is an integer indicating the maximum 757 frame size in units of macroblocks that the decoder is capable 758 of decoding. 760 The decoder is capable of decoding this frame size as long as 761 the width and height of the frame in macroblocks are less than 762 int(sqrt(max-fs * 8)) - for instance, a max-fs of 1200 (capable 763 of supporting 640x480 resolution) will support widths and 764 heights up to 1552 pixels (97 macroblocks). 766 profile-id: The value of profile-id is an integer indicating the 767 default coding profile, the subset of coding tools that may 768 have been used to generate the stream or that the receiver 769 supports). Table 1 lists all of the profiles defined in 770 section 7.2 of [VP9-BITSTREAM] and the corresponding integer 771 values to be used. 773 If no profile-id is present, Profile 0 MUST be inferred. 775 Informative note: See Table 2 for capabilities of coding 776 profiles defined in section 7.2 of [VP9-BITSTREAM]. 778 Encoding considerations: 780 This media type is framed in RTP and contains binary data; see 781 Section 4.8 of [RFC6838]. 783 Security considerations: See Section 7 of RFC xxxx. 784 [RFC Editor: Upon publication as an RFC, please replace "XXXX" 785 with the number assigned to this document and remove this note.] 787 Interoperability considerations: None. 789 Published specification: VP9 bitstream format [VP9-BITSTREAM] and 790 RFC XXXX. 791 [RFC Editor: Upon publication as an RFC, please replace "XXXX" 792 with the number assigned to this document and remove this note.] 794 Applications which use this media type: 795 For example: Video over IP, video conferencing. 797 Fragment identifier considerations: N/A. 799 Additional information: None. 801 Person & email address to contact for further information: 802 Jonathan Lennox 804 Intended usage: COMMON 806 Restrictions on usage: 807 This media type depends on RTP framing, and hence is only defined 808 for transfer via RTP [RFC3550]. 810 Author: Jonathan Lennox 812 Change controller: 813 IETF AVTCore Working Group delegated from the IESG. 815 +---------+------------+ 816 | Profile | profile-id | 817 +---------+------------+ 818 | 0 | 0 | 819 | | | 820 | 1 | 1 | 821 | | | 822 | 2 | 2 | 823 | | | 824 | 3 | 3 | 825 +---------+------------+ 827 Table 1: Table 1. Table of profile-id integer values representing 828 the VP9 profile corresponding to the set of coding tools supported. 830 +---------+-----------+-----------------+--------------------------+ 831 | Profile | Bit Depth | SRGB Colorspace | Chroma Subsampling | 832 +---------+-----------+-----------------+--------------------------+ 833 | 0 | 8 | No | YUV 4:2:0 | 834 | | | | | 835 | 1 | 8 | Yes | YUV 4:2:0,4:4:0 or 4:4:4 | 836 | | | | | 837 | 2 | 10 or 12 | No | YUV 4:2:0 | 838 | | | | | 839 | 3 | 10 or 12 | Yes | YUV 4:2:0,4:4:0 or 4:4:4 | 840 +---------+-----------+-----------------+--------------------------+ 842 Table 2: Table 2. Table of profile capabilities. 844 6.2. SDP Parameters 846 The receiver MUST ignore any fmtp parameter unspecified in this memo. 848 6.2.1. Mapping of Media Subtype Parameters to SDP 850 The media type video/VP9 string is mapped to fields in the Session 851 Description Protocol (SDP) [RFC4566] as follows: 853 o The media name in the "m=" line of SDP MUST be video. 855 o The encoding name in the "a=rtpmap" line of SDP MUST be VP9 (the 856 media subtype). 858 o The clock rate in the "a=rtpmap" line MUST be 90000. 860 o The parameters "max-fs", and "max-fr", MUST be included in the 861 "a=fmtp" line of SDP if SDP is used to declare receiver 862 capabilities. These parameters are expressed as a media subtype 863 string, in the form of a semicolon separated list of 864 parameter=value pairs. 866 o The OPTIONAL parameter profile-id, when present, SHOULD be 867 included in the "a=fmtp" line of SDP. This parameter is expressed 868 as a media subtype string, in the form of a parameter=value pair. 869 When the parameter is not present, a value of 0 MUST be used for 870 profile-id. 872 6.2.1.1. Example 874 An example of media representation in SDP is as follows: 876 m=video 49170 RTP/AVPF 98 877 a=rtpmap:98 VP9/90000 878 a=fmtp:98 max-fr=30; max-fs=3600; profile-id=0; 880 6.2.2. Offer/Answer Considerations 882 When VP9 is offered over RTP using SDP in an Offer/Answer model 883 [RFC3264] for negotiation for unicast usage, the following 884 limitations and rules apply: 886 o The parameter identifying a media format configuration for VP9 is 887 profile-id. This media format configuration parameter MUST be 888 used symmetrically; that is, the answerer MUST either maintain all 889 configuration parameters or remove the media format (payload type) 890 completely if one or more of the parameter values are not 891 supported. 893 o To simplify the handling and matching of these configurations, the 894 same RTP payload type number used in the offer SHOULD also be used 895 in the answer, as specified in [RFC3264]. An answer MUST NOT 896 contain the payload type number used in the offer unless the 897 configuration is exactly the same as in the offer. 899 7. Security Considerations 901 RTP packets using the payload format defined in this specification 902 are subject to the security considerations discussed in the RTP 903 specification [RFC3550], and in any applicable RTP profile such as 904 RTP/AVP [RFC3551], RTP/AVPF [RFC4585], RTP/SAVP [RFC3711], or RTP/ 905 SAVPF [RFC5124]. SAVPF [RFC5124]. However, as "Securing the RTP 906 Protocol Framework: Why RTP Does Not Mandate a Single Media Security 907 Solution" [RFC7202] discusses, it is not an RTP payload format's 908 responsibility to discuss or mandate what solutions are used to meet 909 the basic security goals like confidentiality, integrity and source 910 authenticity for RTP in general. This responsibility lays on anyone 911 using RTP in an application. They can find guidance on available 912 security mechanisms in Options for Securing RTP Sessions [RFC7201]. 913 Applications SHOULD use one or more appropriate strong security 914 mechanisms. The rest of this security consideration section 915 discusses the security impacting properties of the payload format 916 itself. 918 This RTP payload format and its media decoder do not exhibit any 919 significant non-uniformity in the receiver-side computational 920 complexity for packet processing, and thus are unlikely to pose a 921 denial-of-service threat due to the receipt of pathological data. 922 Nor does the RTP payload format contain any active content. 924 8. Congestion Control 926 Congestion control for RTP SHALL be used in accordance with RFC 3550 927 [RFC3550], and with any applicable RTP profile; e.g., RFC 3551 928 [RFC3551]. The congestion control mechanism can, in a real-time 929 encoding scenario, adapt the transmission rate by instructing the 930 encoder to encode at a certain target rate. Media aware network 931 elements MAY use the information in the VP9 payload descriptor in 932 Section 4.2 to identify non-reference frames and discard them in 933 order to reduce network congestion. Note that discarding of non- 934 reference frames cannot be done if the stream is encrypted (because 935 the non-reference marker is encrypted). 937 9. IANA Considerations 939 The IANA is requested to register the media type registration "video/ 940 vp9" as specified in Section 6.1. The media type is also requested 941 to be added to the IANA registry for "RTP Payload Format MIME types" 942 . 944 10. Acknowledgments 946 Alex Eleftheriadis, Yuki Ito, Won Kap Jang, Sergio Garcia Murillo, 947 Roi Sasson, Timothy Terriberry, Emircan Uysaler, and Thomas Volkert 948 commented on the development of this document and provided helpful 949 comments and feedback. 951 11. References 953 11.1. Normative References 955 [I-D.ietf-avtext-framemarking] 956 Zanaty, M., Berger, E., and S. Nandakumar, "Frame Marking 957 RTP Header Extension", draft-ietf-avtext-framemarking-10 958 (work in progress), November 2019. 960 [I-D.ietf-avtext-lrr] 961 Lennox, J., Hong, D., Uberti, J., Holmer, S., and M. 962 Flodman, "The Layer Refresh Request (LRR) RTCP Feedback 963 Message", draft-ietf-avtext-lrr-07 (work in progress), 964 July 2017. 966 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 967 Requirement Levels", BCP 14, RFC 2119, 968 DOI 10.17487/RFC2119, March 1997, 969 . 971 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 972 with Session Description Protocol (SDP)", RFC 3264, 973 DOI 10.17487/RFC3264, June 2002, 974 . 976 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 977 Jacobson, "RTP: A Transport Protocol for Real-Time 978 Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, 979 July 2003, . 981 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 982 Description Protocol", RFC 4566, DOI 10.17487/RFC4566, 983 July 2006, . 985 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 986 "Extended RTP Profile for Real-time Transport Control 987 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, 988 DOI 10.17487/RFC4585, July 2006, 989 . 991 [RFC4855] Casner, S., "Media Type Registration of RTP Payload 992 Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007, 993 . 995 [RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman, 996 "Codec Control Messages in the RTP Audio-Visual Profile 997 with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104, 998 February 2008, . 1000 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 1001 Specifications and Registration Procedures", BCP 13, 1002 RFC 6838, DOI 10.17487/RFC6838, January 2013, 1003 . 1005 [VP9-BITSTREAM] 1006 Grange, A., de Rivaz, P., and J. Hunt, "VP9 Bitstream & 1007 Decoding Process Specification", Version 0.6, March 2016, 1008 . 1012 11.2. Informative References 1014 [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and 1015 Video Conferences with Minimal Control", STD 65, RFC 3551, 1016 DOI 10.17487/RFC3551, July 2003, 1017 . 1019 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 1020 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 1021 RFC 3711, DOI 10.17487/RFC3711, March 2004, 1022 . 1024 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 1025 Real-time Transport Control Protocol (RTCP)-Based Feedback 1026 (RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February 1027 2008, . 1029 [RFC6386] Bankoski, J., Koleszar, J., Quillio, L., Salonen, J., 1030 Wilkins, P., and Y. Xu, "VP8 Data Format and Decoding 1031 Guide", RFC 6386, DOI 10.17487/RFC6386, November 2011, 1032 . 1034 [RFC7201] Westerlund, M. and C. Perkins, "Options for Securing RTP 1035 Sessions", RFC 7201, DOI 10.17487/RFC7201, April 2014, 1036 . 1038 [RFC7202] Perkins, C. and M. Westerlund, "Securing the RTP 1039 Framework: Why RTP Does Not Mandate a Single Media 1040 Security Solution", RFC 7202, DOI 10.17487/RFC7202, April 1041 2014, . 1043 Authors' Addresses 1045 Justin Uberti 1046 Google, Inc. 1047 747 6th Street South 1048 Kirkland, WA 98033 1049 USA 1051 Email: justin@uberti.name 1052 Stefan Holmer 1053 Google, Inc. 1054 Kungsbron 2 1055 Stockholm 111 22 1056 Sweden 1058 Email: holmer@google.com 1060 Magnus Flodman 1061 Google, Inc. 1062 Kungsbron 2 1063 Stockholm 111 22 1064 Sweden 1066 Email: mflodman@google.com 1068 Danny Hong 1069 Google, Inc. 1070 1585 Charleston Road 1071 Mountain View, CA 94043 1072 US 1074 Email: dannyhong@google.com 1076 Jonathan Lennox 1077 8x8, Inc. / Jitsi 1078 1350 Broadway 1079 New York, NY 10018 1080 US 1082 Email: jonathan.lennox@8x8.com