This repository has been archived by the owner on Jan 14, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.html
2426 lines (2006 loc) · 143 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<link href="webrtc.css" rel="stylesheet">
<title>RTP Payload Format For AV1</title>
<!--
<link rel="stylesheet" href="assets/css/bootstrap.min.css">
-->
<link rel="stylesheet" href="assets/css/av1-rtp-spec.css">
<link rel="stylesheet" href="assets/css/syntax-tango.css">
<link rel="apple-touch-icon" sizes="57x57" href="assets/images/icons/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="assets/images/icons/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="assets/images/icons/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="assets/images/icons/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="assets/images/icons/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="assets/images/icons/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="assets/images/icons/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="assets/images/icons/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="assets/images/icons/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="assets/images/icons/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="assets/images/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="assets/images/icons/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="assets/images/icons/favicon-16x16.png">
<link rel="manifest" href="/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="assets/images/icons/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<script src="respec-w3c.js" class="remove">
// // keep this comment //
</script>
<script class="remove" src="webrtc.js" type="text/javascript">
// // keep this comment //
</script>
</head>
<body>
<div class="container">
<div class="row">
<div class="col-md-10 col-md-offset-1">
<section>
<h1 class="no_toc" id="rtp-payload-format-for-av1-v10">RTP Payload Format For AV1 (v1.0)</h1>
<p><strong>Authors:</strong> The Alliance for Open Media AV1 Real-Time Communications Subgroup</p>
<p><strong>Status:</strong> This document is a draft of a proposed specification.</p>
<section>
<h2 class="no_toc" id="abstract">Abstract</h2>
<p>This document describes an RTP payload format for the <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1 video codec</a>. The payload format has wide applicability, from low bit-rate peer-to-peer usage, to high bit-rate multi-party video conferences. It includes provisions for temporal and spatial scalability.</p>
</section>
<section>
<h2 class="no_toc" id="contents">Contents</h2>
<ul id="markdown-toc">
<li><a href="#introduction" id="markdown-toc-introduction">1 Introduction</a></li>
<li><a href="#conventions-definitions-and-acronyms" id="markdown-toc-conventions-definitions-and-acronyms">2 Conventions, Definitions and Acronyms</a></li>
<li><a href="#media-format-description" id="markdown-toc-media-format-description">3 Media Format Description</a></li>
<li><a href="#payload-format" id="markdown-toc-payload-format">4 Payload Format</a> <ul>
<li><a href="#rtp-header-usage" id="markdown-toc-rtp-header-usage">4.1 RTP Header Usage</a></li>
<li><a href="#rtp-header-marker-bit-m" id="markdown-toc-rtp-header-marker-bit-m">4.2 RTP Header Marker Bit (M)</a></li>
<li><a href="#dependency-descriptor-rtp-header-extension" id="markdown-toc-dependency-descriptor-rtp-header-extension">4.3 Dependency Descriptor RTP Header Extension</a></li>
<li><a href="#av1-aggregation-header" id="markdown-toc-av1-aggregation-header">4.4 AV1 Aggregation Header</a></li>
<li><a href="#payload-structure" id="markdown-toc-payload-structure">4.5 Payload Structure</a></li>
</ul>
</li>
<li><a href="#packetization-rules" id="markdown-toc-packetization-rules">5 Packetization Rules</a> <ul>
<li><a href="#examples" id="markdown-toc-examples">5.1 Examples</a></li>
</ul>
</li>
<li><a href="#mane-and-sfm-behavior" id="markdown-toc-mane-and-sfm-behavior">6 MANE and SFM Behavior</a> <ul>
<li><a href="#simulcast" id="markdown-toc-simulcast">6.1 Simulcast</a></li>
<li><a href="#example" id="markdown-toc-example">6.1.1 Example</a></li>
</ul>
</li>
<li><a href="#payload-format-parameters" id="markdown-toc-payload-format-parameters">7 Payload Format Parameters</a> <ul>
<li><a href="#media-type-definition" id="markdown-toc-media-type-definition">7.1 Media Type Definition</a></li>
<li><a href="#sdp-parameters" id="markdown-toc-sdp-parameters">7.2 SDP Parameters</a> <ul>
<li><a href="#mapping-of-media-subtype-parameters-to-sdp" id="markdown-toc-mapping-of-media-subtype-parameters-to-sdp">7.2.1 Mapping of Media Subtype Parameters to SDP</a></li>
</ul>
</li>
<li><a href="#rid-restrictions-mapping-for-av1" id="markdown-toc-rid-restrictions-mapping-for-av1">7.2.2 RID Restrictions Mapping for AV1</a> <ul>
<li><a href="#usage-with-the-sdp-offeranswer-model" id="markdown-toc-usage-with-the-sdp-offeranswer-model">7.2.3 Usage with the SDP Offer/Answer Model</a></li>
<li><a href="#usage-in-declarative-session-descriptions" id="markdown-toc-usage-in-declarative-session-descriptions">7.2.4 Usage in Declarative Session Descriptions</a></li>
</ul>
</li>
<li><a href="#examples-1" id="markdown-toc-examples-1">7.3 Examples</a> <ul>
<li><a href="#level-upgrading" id="markdown-toc-level-upgrading">7.3.1 Level upgrading</a></li>
<li><a href="#simulcast-with-payload-multiplexing" id="markdown-toc-simulcast-with-payload-multiplexing">7.3.2 Simulcast with Payload Multiplexing</a></li>
<li><a href="#simulcast-with-ssrc-multiplexing" id="markdown-toc-simulcast-with-ssrc-multiplexing">7.3.3 Simulcast with SSRC Multiplexing</a></li>
<li><a href="#single-stream-simulcast" id="markdown-toc-single-stream-simulcast">7.3.4 Single Stream Simulcast</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#feedback-messages" id="markdown-toc-feedback-messages">8 Feedback Messages</a></li>
<li><a href="#full-intra-request-fir" id="markdown-toc-full-intra-request-fir">8.1 Full Intra Request (FIR)</a></li>
<li><a href="#layer-refresh-request-lrr" id="markdown-toc-layer-refresh-request-lrr">8.2 Layer Refresh Request (LRR)</a></li>
<li><a href="#iana-considerations" id="markdown-toc-iana-considerations">9 IANA Considerations</a></li>
<li><a href="#security-considerations" id="markdown-toc-security-considerations">10 Security Considerations</a></li>
<li><a href="#references" id="markdown-toc-references">11 References</a> <ul>
<li><a href="#normative-references" id="markdown-toc-normative-references">11.1 Normative References</a></li>
<li><a href="#informative-references" id="markdown-toc-informative-references">11.2 Informative References</a></li>
</ul>
</li>
<li><a href="#appendix" id="markdown-toc-appendix">Appendix</a> <ul>
<li><a href="#dependency-descriptor-rtp-header-extension-1" id="markdown-toc-dependency-descriptor-rtp-header-extension-1">Dependency Descriptor RTP Header Extension</a> <ul>
<li><a href="#a1-introduction" id="markdown-toc-a1-introduction">A.1 Introduction</a></li>
<li><a href="#a2-conventions-definitions-and-acronyms" id="markdown-toc-a2-conventions-definitions-and-acronyms">A.2 Conventions, Definitions and Acronyms</a></li>
<li><a href="#a3-media-stream-requirements" id="markdown-toc-a3-media-stream-requirements">A.3 Media Stream Requirements</a></li>
<li><a href="#a4-active-decode-targets" id="markdown-toc-a4-active-decode-targets">A.4 Active Decode Targets</a></li>
<li><a href="#a5-chains" id="markdown-toc-a5-chains">A.5 Chains</a></li>
<li><a href="#a6-usage-of-chains-after-packet-loss" id="markdown-toc-a6-usage-of-chains-after-packet-loss">A.6 Usage of Chains After Packet Loss</a></li>
<li><a href="#a7-switching" id="markdown-toc-a7-switching">A.7 Switching</a></li>
<li><a href="#a8-dependency-descriptor-format" id="markdown-toc-a8-dependency-descriptor-format">A.8 Dependency Descriptor Format</a> <ul>
<li><a href="#a81-templates" id="markdown-toc-a81-templates">A.8.1 Templates</a></li>
<li><a href="#a82-syntax" id="markdown-toc-a82-syntax">A.8.2 Syntax</a></li>
<li><a href="#a83-semantics" id="markdown-toc-a83-semantics">A.8.3 Semantics</a></li>
</ul>
</li>
<li><a href="#a9-signaling-sdp-information" id="markdown-toc-a9-signaling-sdp-information">A.9 Signaling (SDP) Information</a></li>
<li><a href="#a10-examples" id="markdown-toc-a10-examples">A.10 Examples</a></li>
<li><a href="#a101-scenarios" id="markdown-toc-a101-scenarios">A.10.1 Scenarios</a> <ul>
<li><a href="#a1011-decode-targets-decode-target-indications-and-chains" id="markdown-toc-a1011-decode-targets-decode-target-indications-and-chains">A.10.1.1 Decode targets, Decode Target Indications, and Chains</a></li>
<li><a href="#a1012-spatial-upswitch" id="markdown-toc-a1012-spatial-upswitch">A.10.1.2 Spatial Upswitch</a></li>
<li><a href="#a1013-dynamic-prediction-structure" id="markdown-toc-a1013-dynamic-prediction-structure">A.10.1.3 Dynamic Prediction Structure</a></li>
</ul>
</li>
<li><a href="#a102-scalability-structure-examples" id="markdown-toc-a102-scalability-structure-examples">A.10.2 Scalability structure examples</a> <ul>
<li><a href="#a1021-l1t3-single-spatial-layer-with-3-temporal-layers" id="markdown-toc-a1021-l1t3-single-spatial-layer-with-3-temporal-layers">A.10.2.1 L1T3 Single Spatial Layer with 3 Temporal Layers</a></li>
<li><a href="#a1022-l3t3-full-svc" id="markdown-toc-a1022-l3t3-full-svc">A.10.2.2 L3T3 Full SVC</a></li>
<li><a href="#a1023-l3t3-k-svc-with-temporal-shift" id="markdown-toc-a1023-l3t3-k-svc-with-temporal-shift">A.10.2.3 L3T3 K-SVC with Temporal Shift</a></li>
</ul>
</li>
<li><a href="#a11-references" id="markdown-toc-a11-references">A.11 References</a> <ul>
<li><a href="#a111-normative-references" id="markdown-toc-a111-normative-references">A.11.1 Normative References</a></li>
<li><a href="#a112-informative-references" id="markdown-toc-a112-informative-references">A.11.2 Informative References</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</section>
<section>
<h2 id="introduction">1 Introduction</h2>
<p>This document describes an RTP payload specification applicable to the transmission of video streams encoded using the <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1 video codec</a>. In AV1, the smallest individual video encoder entity presented for transport is the Open Bitstream Unit (OBU). This specification allows both for fragmentation and aggregation of OBUs in the same RTP packet, but explicitly disallows doing so across frame boundaries.</p>
<p>Appendix A of this document describes the Dependency Descriptor (DD) RTP Header extension, which conveys information about individual video frames and the dependencies between them. This allows forwarding of video frames in situations where an intermediary does not wish to examine the RTP payload or does not have access to it, such as when the RTP payload is encrypted end-to-end. While the DD RTP Header extension was designed for use with AV1, it may prove useful for other codecs as well.</p>
<p>This specification also provides several mechanisms through which scalability structures are described. AV1 uses the concept of predefined scalability structures. These are a set of commonly used picture prediction structures that can be referenced simply via an indicator value (scalability_mode_idc, residing in the sequence header). For cases that do not fall in any of the predefined cases, there is a mechanism for describing the scalability structure. These bitstream parameters greatly simplify the organization of the corresponding data at the RTP payload format level.</p>
</section>
<section>
<h2 id="conventions-definitions-and-acronyms">2 Conventions, Definitions and Acronyms</h2>
<p>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in <a href="https://tools.ietf.org/html/rfc2119">RFC2119</a>.</p>
<dl>
<dt>Coded frame</dt>
<dd>The representation of one frame before the decoding process.</dd>
<dt>Frame</dt>
<dd>A frame in this document is synonymous to a Coded frame.</dd>
</dl>
<p class="alert alert-info"><strong>Note:</strong> In contrast, in AV1, Frame is defined as the representation of video signals in the spatial domain.</p>
<p class="alert alert-info"><strong>Note:</strong> Multiple frames may be present at the same instant in time.</p>
<dl>
<dt>Media-Aware Network Element (MANE)</dt>
<dd>A middlebox that relays streams among transmitting and receiving clients by selectively forwarding packets and which may have access to the media (<a href="https://tools.ietf.org/html/rfc6184">RFC6184</a>).</dd>
<dt>OBU element</dt>
<dd>An OBU, or a fragment of an OBU, contained in an RTP packet.</dd>
<dt>Open Bitstream Unit (OBU)</dt>
<dd>The smallest bitstream data framing unit in AV1. All AV1 bitstream structures are packetized in OBUs.</dd>
<dt>“S” Mode</dt>
<dd>A scalability mode in which multiple encodings are sent on the same SSRC. This includes the S2T1, S2T1h, S2T2, S2T2h, S2T3, S2T3h, S3T1, S3T1h, S3T2, S3T2h, S3T3 and S3T3h scalability modes defined in Section 6.7.5 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</dd>
<dt>Selective Forwarding Middlebox (SFM)</dt>
<dd>A middlebox that relays streams among transmitting and receiving clients by selectively forwarding packets without accessing the media (<a href="https://tools.ietf.org/html/rfc7667">RFC7667</a>).</dd>
<dt>Temporal unit</dt>
<dd>Defined by the AV1 specification: A temporal unit consists of all the OBUs that are associated with a specific, distinct time instant.</dd>
</dl>
</section>
<section>
<h2 id="media-format-description">3 Media Format Description</h2>
<p>The AV1 codec can maintain up to eight reference frames, of which up to seven can be referenced by any new frame. AV1 also allows a frame to use another frame of a different spatial resolution as a reference frame. This allows internal resolution changes without requiring the use of key frames. These features together enable an AV1 encoder to implement various forms of coarse-grained scalability, including temporal, spatial, and quality scalability modes, as well as combinations of these, without the need for explicit scalable coding tools.</p>
<p>Spatial and quality layers define different and possibly dependent representations of a single input frame. For a given spatial layer, temporal layers define different frame rates of video. Spatial layers allow a frame to be encoded at different spatial resolutions, whereas quality layers allow a frame to be encoded at the same spatial resolution but at different qualities (and thus with different amounts of coding error). AV1 supports quality layers as spatial layers without any resolution changes; hereinafter, the term “spatial layer” is used to represent both spatial and quality layers.</p>
<p>This payload format specification provides for specific mechanisms through which such temporal and spatial scalability layers can be described and communicated.</p>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/video_coding/codecs/av1/scalability_structure_unittest.cc?q=TemplatesAreSortedByLayerId">Temporal and spatial scalability layers are associated with non-negative integer IDs. The lowest layer of either type has an ID equal to 0.</p>
<p class="alert alert-info" data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/video_coding/codecs/av1/scalability_structure_unittest.cc?q=FrameDependsOnSameOrLowerLayer"><strong>Note:</strong> Layer dependencies are constrained by the AV1 specification such that a temporal layer with temporal_id T and spatial layer with spatial_id S are only allowed to reference previously coded video data having temporal_id T’ and spatial_id S’, where T’ <= T and S’ <= S.</p>
</section>
<section>
<h2 id="payload-format">4 Payload Format</h2>
<p>This section describes how the encoded AV1 bitstream is encapsulated in RTP.</p>
<section>
<h3 id="rtp-header-usage">4.1 RTP Header Usage</h3>
<p>The general RTP payload format follows the RTP header format <a href="https://tools.ietf.org/html/rfc3550">RFC3550</a> and generic RTP header extensions <a href="https://tools.ietf.org/html/rfc8285">RFC8285</a>, and is shown below.</p>
<p>The Dependency Descriptor and AV1 aggregation header are described in this document. The payload itself is a series of OBU elements, preceded by length information as detailed later in this document. An OBU element is either an entire OBU or an OBU fragment.</p>
<pre><code>
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=2|P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers |
| .... |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| 0x100 | 0x0 | extensions length |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| ID | hdr_length | |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ |
| |
| dependency descriptor (hdr_length #bytes) |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | Other rtp header extensions...|
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| AV1 aggr hdr | |
+-+-+-+-+-+-+-+-+ |
| |
| Bytes 2..N of AV1 payload |
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : OPTIONAL RTP padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</code></pre>
<p class="alert alert-info"><strong>Note:</strong> The ID used to identify the Dependency Descriptor is signaled as defined in Section A.7 of this specification. Some examples are provided in Sections 7.2 and 7.3.</p>
</section>
<section>
<h3 id="rtp-header-marker-bit-m">4.2 RTP Header Marker Bit (M)</h3>
<p data-tests="https://bugs.chromium.org/p/webrtc/issues/detail?id=12167">The RTP header Marker bit MUST be set equal to 0 if the packet is not the last packet of the temporal unit, it SHOULD be set equal to 1 otherwise.</p>
<p class="alert alert-info"><strong>Note:</strong> It is possible for a receiver to receive the last packet of a temporal unit without the marker bit being set equal to 1, and a receiver should be able to handle this case. The last packet of a temporal unit is also indicated by the next packet, in RTP sequence number order, having an incremented timestamp.</p>
</section>
<section>
<h3 id="dependency-descriptor-rtp-header-extension">4.3 Dependency Descriptor RTP Header Extension</h3>
<p>To facilitate the work of selectively forwarding portions of a scalable video bitstream, as is done by a Selective Forwarding Middlebox (SFM), certain information needs to be provided for each packet. Appendix A of this specification defines how this information is communicated.</p>
</section>
<section>
<h3 id="av1-aggregation-header">4.4 AV1 Aggregation Header</h3>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=AssembleFrameFromOnePacketWithOneObu">The aggregation header is carried in the first byte of the RTP payload and is used to indicate if the first and/or last OBU element in the payload is a fragment of an OBU. The aggregation header is not part of the AV1 bitstream and MUST NOT be presented to an AV1 decoder.</p>
<p>The structure is as follows.</p>
<pre><code>
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|Z|Y| W |N|-|-|-|
+-+-+-+-+-+-+-+-+
</code></pre>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseTreatsContinuationFlagAsNotBeginningOfFrame, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseTreatsNoContinuationFlagAsBeginningOfFrame">Z: MUST be set to 1 if the first OBU element is an OBU fragment that is a continuation of an OBU fragment from the previous packet, and MUST be set to 0 otherwise.</p>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseTreatsWillContinueFlagAsNotEndOfFrame, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseTreatsNoWillContinueFlagAsEndOfFrame">Y: MUST be set to 1 if the last OBU element is an OBU fragment that will continue in the next packet, and MUST be set to 0 otherwise.</p>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=UseSizeForAllObusWhenFourObusFitsIntoThePacket, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=AssembleFrameSetsOBUPayloadSizeWhenAbsent, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=AssembleFrameSetsOBUPayloadSizeWhenPresent">W: two bit field that describes the number of OBU elements in the packet. This field MUST be set equal to 0 or equal to the number of OBU elements contained in the packet. If set to 0, each OBU element MUST be preceded by a length field. If not set to 0 (i.e., W = 1, 2 or 3) the last OBU element MUST NOT be preceded by a length field. Instead, the length of the last OBU element contained in the packet can be calculated as follows:</p>
<pre data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=OmitsSizeForLastObuWhenThreeObusFitsIntoThePacket"><code>
Length of the last OBU element =
length of the RTP payload
- length of aggregation header
- length of previous OBU elements including length fields
</code></pre>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=SetsNbitAtTheFirstPacketOfAKeyFrameWithSequenceHeader, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=DoesntSetNbitAtThePacketsOfAKeyFrameWithoutSequenceHeader, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=DoesntSetNbitAtThePacketsOfADeltaFrame, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseUsesNewCodedVideoSequenceBitAsKeyFrameIndidcator, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseUsesUnsetNewCodedVideoSequenceBitAsDeltaFrameIndidcator">N: MUST be set to 1 if the packet is the first packet of a coded video sequence, and MUST be set to 0 otherwise.</p>
<p class="alert alert-info" data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/video_rtp_depacketizer_av1_unittest.cc?q=ParseRejectsPacketWithNewCVSAndContinuationFlagsBothSet"><strong>Note:</strong> if N equals 1 then Z must equal 0.</p>
</section>
<section>
<h3 id="payload-structure">4.5 Payload Structure</h3>
<p>The smallest high-level syntax unit in AV1 is the OBU. All AV1 bitstream structures are packetized in OBUs. Each OBU has a header, which provides identifying information for the contained data (payload).</p>
<p>The payload contains a series of one or more OBU elements. The design allows for a combination of aggregation and fragmentation of OBUs, i.e., a set of OBU elements in which the first and/or last element is a fragment of an OBU.</p>
<p>The length field is encoded using leb128. Leb128 is defined in the AV1 specification, and provides for a variable-sized, byte-oriented encoding of non-negative integers where the first bit of each (little-endian) byte indicates whether or not additional bytes are used in the representation (AV1, Section 4.10.5).</p>
<p class="untestable">Whether or not the first and/or last OBU element is a fragment of an OBU is signaled in the aggregation header. Fragmentation may occur regardless of how the W field is set.</p>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=PacketizeOneObuWithoutSizeAndExtension, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=PacketizeOneObuWithoutSizeWithExtension, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=RemovesObuSizeFieldWithoutExtension, https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=RemovesObuSizeFieldWithExtension">The AV1 specification allows OBUs to have an optional size field called obu_size (also leb128 encoded), signaled by the obu_has_size_field flag in the OBU header. To minimize overhead, the obu_has_size_field flag SHOULD be set to zero in all OBUs.</p>
<p>The following figure shows an example payload where the length field is shown as taking two bytes for the first and second OBU elements and one byte for the last (N) OBU element.</p>
<pre><code>
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Z|Y|0 0|N|-|-|-| OBU element 1 size (leb128) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
: :
: OBU element 1 data :
: :
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | OBU element 2 size (leb128) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: OBU element 2 data :
: :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: :
: ... :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OBU e... N size| |
+-+-+-+-+-+-+-+-+ OBU element N data +-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</code></pre>
<p>The following figure shows an example payload containing two OBU elements where the last OBU element omits the length field (and the W field is set to 2). The size of the last OBU element can be calculated given the formula described in Section 4.4.</p>
<pre><code>
OBU element example size calculation:
Total RTP payload size = 303 bytes
AV1 aggregation header = 1 byte
OBU element 1 size = 2 bytes
OBU element 1 data = 200 bytes
OBU element 2 data = 303 - 1 - (2 + 200) = 100 bytes
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Z|Y|1 0|N|-|-|-| OBU element 1 size (leb128) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
: :
: OBU element 1 data :
: :
| |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
: :
: OBU element 2 data :
: :
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</code></pre>
</section>
</section>
<section>
<h2 id="packetization-rules">5 Packetization Rules</h2>
<p class="untestable">Each RTP packet MUST NOT contain OBUs that belong to different temporal units.</p>
<p data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/rtp_rtcp/source/rtp_packetizer_av1_unittest.cc?q=DiscardsTemporalDelimiterAndTileListObu">The temporal delimiter OBU, if present, SHOULD be removed when transmitting, and MUST be ignored by receivers. Tile list OBUs are not supported. They SHOULD be removed when transmitted, and MUST be ignored by receivers.</p>
<p class="untestable">If a sequence header OBU is present in an RTP packet and operating_points_cnt_minus_1 > 0 then for any number i where 0 <= i < operating_points_cnt_minus_1 the following MUST be true: (operating_point_idc[i] & operating_point_idc[i+1]) == operating_point_idc[i+1].</p>
<p class="untestable">A sender MAY produce a sequence header with operating_points_cnt_minus_1 = 0 and operating_point_idc[0] = 0xFFF and seq_level_idx[0] = 0. In such case, seq_level_idx[0] does not reflect the level of the operating point.</p>
<p class="alert alert-info"><strong>Note:</strong> The intent is to disable OBU dropping in the AV1 decoder. To ensure a decoder’s capabilities are not exceeded, OBU filtering should instead be implemented at the system level (e.g., in a MANE).</p>
<p class="untestable">If more than one OBU contained in an RTP packet has an OBU extension header, then the values of the temporal_id and spatial_id MUST be the same in all such OBUs in the RTP packet.</p>
<p class="untestable">If a sequence header OBU is present in an RTP packet, then it SHOULD be the first OBU in the packet. OBUs that are not associated with a particular layer (and thus do not have an OBU extension header) SHOULD be in the beginning of a packet, following the sequence header OBU if present.</p>
<p class="untestable">A sequence header OBU SHOULD be included in the base layer when scalable encoding is used. When simulcast encodings are transported on the same SSRC (an “S” mode), a sequence header OBU SHOULD be aggregated with each spatial layer. This ensures that if an intermediary removes simulcast encodings from the bitstream before forwarding, the modified bitstream will still be decodable.</p>
<section>
<h3 id="examples">5.1 Examples</h3>
<p>The following are example packetizations of OBU sequences. A two-letter notation is used to identify the OBU type: FH - frame header, TG - tile group, FR - frame, SH - sequence header, TD - temporal delimitered, MD - metadata. Parentheses after the type indicate the temporal_id and spatial_id combination. For example “TG(0,1)” indicates a tile group OBU with temporal_id equal to 0 and spatial_id equal to 1.</p>
<p>The following is an example coded video sequence:</p>
<pre><code>
TD SH MD MD(0,0) FH(0,0) TG0(0,0) MD(0,1) FH(0,1) TG(0,1)
</code></pre>
<p>This sequence could be packetized as follows. First, the TD OBU is dropped. Then, the following packetization grouping (indicated using square brackets) may be used:</p>
<pre><code>
[ SH MD MD(0,0) FH(0,0) TG(0,0) ] [ MD(0,1) FH(0,1) TG(0,1) ]
</code></pre>
<p>It is also possible to send each OBU in its own RTP packet:</p>
<pre><code>
[ SH ] [ MD ] [ MD(0,0) ] [ FH(0,0) ] [ TG(0,0) ] ...
</code></pre>
<p>The following packetization grouping would not be allowed, since it combines data from different spatial layers in the same packet:</p>
<pre><code>
[ SH MD MD(0,0) FH(0,0) TG(0,0) MD(0,1) FH(0,1) TG(0,1) ]
</code></pre>
</section>
</section>
<section>
<h2 id="mane-and-sfm-behavior">6 MANE and SFM Behavior</h2>
<p>If a packet contains an OBU with an OBU extension header then the entire packet is considered associated with the layer identified by the temporal_id and spatial_id combination that are indicated in the extension header. If a packet does not contain any OBU with an OBU extension header, then it is considered to be associated with all operating points.</p>
<p>The general function of a MANE or SFM is to selectively forward packets to receivers. To make forwarding decisions a MANE may inspect the media payload, so that it may need to be able to parse the AV1 bitstream and if so, cannot function when end-to-end encryption is enabled. An SFM does not parse the AV1 bitstream and therefore needs to obtain the information relevant to selective forwarding by other means, such as the Dependency Descriptor described in Appendix A. In addition to enabling bitstream-independent forwarding and support for end-to-end encryption, the Dependency Descriptor also enables forwarding where the metadata OBU provided in the AV1 bitstream is not sufficient to express the structure of the stream.</p>
<section>
<h3 id="simulcast">6.1 Simulcast</h3>
<p class="needs-tests">The RTP payload defined in this specification supports two distinct modes for transport of simulcast encodings. In either mode, simulcast transport MUST only be used to convey multiple encodings from the same source. Also, in either mode, a sequence header OBU SHOULD be aggregated with each spatial layer. Both modes MUST be supported by implementations of this specification.</p>
<p class="needs-tests">When simulcast encodings are transported each on a separate RTP stream, each simulcast encoding utilizes a distinct bitstream containing its own distinct Sequence Header and Scalability Metadata OBUs. This mode utilizes distinct SSRCs and Restriction Identifiers (RIDs) for each encoding as described in <a href="https://tools.ietf.org/html/rfc8852">RFC8852</a> and, as a result, RTCP feedback can be provided for each simulcast encoding. This mode of simulcast transport, which MUST be supported by SFMs, utilizes Session Description Protocol (SDP) signaling as described in <a href="https://tools.ietf.org/html/rfc8851">RFC8851</a> and <a href="https://tools.ietf.org/html/rfc8853">RFC8853</a>.</p>
<p class="untestable">When simulcast encodings are transported on a single RTP stream, RIDs are not used and the Sequence Header and Scalability Metadata OBUs (utilizing an ‘S’ mode) convey information relating to all encodings. This simulcast transport mode is possible since AV1 enables multiple simulcast encodings to be provided within a single bitstream. However, in this mode, RTCP feedback cannot be provided for each simulcast encoding, but only for the aggregate, since only a single SSRC is used. This mode of simulcast transport MAY be supported by SFMs.</p>
</section>
<section>
<h3 id="example">6.1.1 Example</h3>
<p>In this example, it is desired to send three simulcast encodings, each containing three temporal layers. When sending all encodings on a single SSRC, scalability mode ‘S3T3’ would be indicated within the scalability metadata OBU, and the Dependency Descriptor describes the dependency structure of all encodings.</p>
<p>When sending each simulcast encoding on a distinct SSRC, the scalability mode ‘L1T3’ would be indicated within the scalability metadata OBU of each bitstream, and the Dependency Descriptor in each stream describes only the dependency structure for that individual encoding. A distinct spatial_id (e.g. 0, 1, 2) could be used for each stream (if a single AV1 encoder is used to produce the three simulcast encodings), but if distinct AV1 encoders are used, the spatial_id values may not be distinct.</p>
</section>
</section>
<section>
<h2 id="payload-format-parameters">7 Payload Format Parameters</h2>
<p>This section specifies the parameters that MAY be used to select optional features of the payload format and certain features of the bitstream.</p>
<section>
<h3 id="media-type-definition">7.1 Media Type Definition</h3>
<p>The AV1 media type used for signaling the transfer of AV1 via RTP is registered at https://www.iana.org/assignments/media-types/video/AV1.</p>
</section>
<section>
<h3 id="sdp-parameters">7.2 SDP Parameters</h3>
<p>The parameters for AV1 are <strong>profile</strong>, <strong>level-idx</strong>, and <strong>tier</strong>. These parameters indicate the profile, level, and tier of the bitstream carried by the RTP stream, or a specific set of the profile, level, and tier that the receiver supports.</p>
<p class="untestable">The <strong>profile</strong> parameter is an integer indicating the highest AV1 profile that may have been used to generate the bitstream or that the receiver supports. The range of possible values is identical to the <strong>seq_profile</strong> syntax element specified in <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>. If the parameter is not present, it MUST be inferred to be 0 (“Main” profile).</p>
<p class="untestable">The <strong>level-idx</strong> parameter is an integer indicating the highest AV1 level that may have been used to generate the bitstream or that the receiver supports. The range of possible values is identical to the <strong>seq_level_idx</strong> syntax element specified in <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>. If the parameter is not present, it MUST be inferred to be 5 (level 3.1).</p>
<p class="untestable">The <strong>tier</strong> parameter is an integer indicating the highest tier that may have been used to generate the bitstream or that the receiver supports. The range of possible values is identical to the <strong>seq_tier</strong> syntax element specified in <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>. If the parameter is not present, the tier MUST be inferred to be 0.</p>
<section>
<h4 id="mapping-of-media-subtype-parameters-to-sdp">7.2.1 Mapping of Media Subtype Parameters to SDP</h4>
<p>The media type video/AV1 string is mapped to fields in the Session Description Protocol (SDP) per <a href="https://tools.ietf.org/html/rfc4566">RFC4566</a> as follows:</p>
<ul data-tests="https://github.com/medooze/semantic-sdp-js/blob/master/lib/SDPInfo.js">
<li>The media name in the “m=” line of SDP MUST be video.</li>
</ul>
<ul data-tests="https://github.com/medooze/semantic-sdp-js/blob/master/lib/SDPInfo.js">
<li>The encoding name in the “a=rtpmap” line of SDP MUST be AV1 (the media subtype).</li>
</ul>
<ul data-tests="https://github.com/medooze/semantic-sdp-js/blob/master/lib/SDPInfo.js">
<li>The clock rate in the “a=rtpmap” line MUST be 90000.</li>
</ul>
<ul class="untestable">
<li>The parameters “<strong>profile</strong>”, “<strong>level-idx</strong>”, and “<strong>tier</strong>” MAY be included in the “a=fmtp” line of SDP. These parameters are expressed as a media subtype string, in the form of a semicolon separated list of parameter=value pairs.</li>
</ul>
<p data-tests="https://github.com/medooze/semantic-sdp-js/blob/master/lib/SDPInfo.js">The receiver MUST ignore any fmtp parameter not specified in this document.</p>
</section>
</section>
<section>
<h3 id="rid-restrictions-mapping-for-av1">7.2.2 RID Restrictions Mapping for AV1</h3>
<p>The RID specification declares the set of codec-agnostic restrictions for media streams. All the restrictions are optional and are subject to negotiation based on the SDP Offer/Answer rules described in Section 6 in <a href="https://tools.ietf.org/html/rfc8851">RFC8851</a>. When these restrictions are applied to the AV1 codec, they MUST have the following interpretation:</p>
<ul class="untestable">
<li><strong>max-width</strong>, maximum width of the frame in units of samples. The meaning of the restriction is the same as variable <strong>MaxHSize</strong> of the levels table from Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</li>
</ul>
<ul class="untestable">
<li><strong>max-height</strong>, maximum height of the frame in units of samples. The meaning of the restriction is the same as variable <strong>MaxVSize</strong> of the levels table from Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</li>
</ul>
<ul class="untestable">
<li><strong>max-fps</strong>, maximum number of temporal units per second.</li>
</ul>
<ul class="untestable">
<li><strong>max-fs</strong>, maximum size of the frame in units of samples. The meaning of the restriction is the same as variable <strong>MaxPicSize</strong> of the levels table from Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</li>
</ul>
<ul class="untestable">
<li><strong>max-br</strong>, maximum bit rate in units bits per second. The meaning of the restriction is the same as variable <strong>MaxBitrate</strong> defined in Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</li>
</ul>
<ul class="untestable">
<li><strong>max-pps</strong>, maximum decode rate in units of samples per second. The meaning of the restriction is the same as variable <strong>MaxDecodeRate</strong> of the levels table from Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>.</li>
</ul>
<ul class="untestable">
<li><strong>max-bpp</strong>, maximum number of bits per pixel of any given coded frame, calculated as a ratio between <strong>CompressedSize</strong> variable defined Section A.3 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a> and expressed in bits, and number of samples in frame.</li>
</ul>
<p class="untestable">If during the SDP negotiation process both parties acknowledge restrictions, then the transported media stream MUST have at least one operating point with the negotiated restrictions.</p>
<section>
<h4 id="usage-with-the-sdp-offeranswer-model">7.2.3 Usage with the SDP Offer/Answer Model</h4>
<p>When AV1 is offered over RTP using SDP in an Offer/Answer model as described in <a href="https://tools.ietf.org/html/rfc3264">RFC3264</a> for negotiation for unicast usage, the following limitations and rules apply:</p>
<ul data-tests="https://webrtc-review.googlesource.com/c/src/+/198782">
<li>The media format configuration is identified by <strong>level-idx</strong>, <strong>profile</strong> and <strong>tier</strong>. These media configuration parameters are asymmetrical and the answerer MAY declare its own media configuration if the answerer receiving capabilities are different from the offerer.</li>
</ul>
<ul data-tests="https://webrtc-review.googlesource.com/c/src/+/198782">
<li>The AV1 stream sent by either the offerer or the answerer MUST be encoded with a profile, level and tier, lesser or equal to the values of the <strong>level-idx</strong>, <strong>profile</strong> and <strong>tier</strong> declared in the SDP by the receiving agent.</li>
</ul>
</section>
<section>
<h4 id="usage-in-declarative-session-descriptions">7.2.4 Usage in Declarative Session Descriptions</h4>
<p>When AV1 over RTP is offered with SDP in a declarative style, as in Real Time Streaming Protocol (RTSP) <a href="https://tools.ietf.org/html/rfc2326">RFC2326</a> or Session Announcement Protocol (SAP) <a href="https://tools.ietf.org/html/rfc2974">RFC2974</a>, the following considerations apply.</p>
<ul class="untestable">
<li>All parameters capable of indicating both stream properties and receiver capabilities are used to indicate only stream properties. In this case, the parameters <strong>profile</strong>, <strong>level-idx</strong> and <strong>tier</strong> declare only the values used by the stream, not the capabilities for receiving streams.</li>
</ul>
<ul class="untestable">
<li>A receiver of the SDP is required to support all parameters and values of the parameters provided; otherwise, the receiver MUST reject (RTSP) or not participate in (SAP) the session. It falls on the creator of the session to use values that are expected to be supported by the receiving application.</li>
</ul>
</section>
</section>
<section>
<h3 id="examples-1">7.3 Examples</h3>
<p>An example of media representation in SDP is as follows:</p>
<ul>
<li>m=video 49170 RTP/AVPF 98</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
</ul>
<section>
<h4 id="level-upgrading">7.3.1 Level upgrading</h4>
<p>In the following example the offer is accepted with level upgrading. The level to use in the offerer-to-answerer direction is Level 2.0, and the level to use in the answerer-to-offerer direction is Level 3.0/Tier 1. The answerer is allowed to send at any level up to and including Level 2.0, and the offerer is allowed to send at any level up to and including Level 3.0/Tier 1:</p>
<p>Offer SDP:</p>
<ul>
<li>m=video 49170 RTP/AVPF 98</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=0; level-idx=0;</li>
</ul>
<p>Answer SDP:</p>
<ul>
<li>m=video 49170 RTP/AVPF 98</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=0; level-idx=4; tier=1;</li>
</ul>
</section>
<section>
<h4 id="simulcast-with-payload-multiplexing">7.3.2 Simulcast with Payload Multiplexing</h4>
<p>In the following example an offer is made by a conferencing server to receive 3 simulcast streams with payload multiplexing. The answerer agrees to send 3 simulcast streams at different resolutions.</p>
<p>Offer SDP:</p>
<ul>
<li>m=video 49170 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:2 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=rtpmap:99 AV1/90000</li>
<li>a=rtpmap:100 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=fmtp:99 profile=2; level-idx=8; tier=1;</li>
<li>a=fmtp:100 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
<li>a=rtcp-fb:99 ccm fir</li>
<li>a=rtcp-fb:99 nack</li>
<li>a=rtcp-fb:99 nack pli</li>
<li>a=rtcp-fb:100 ccm fir</li>
<li>a=rtcp-fb:100 nack</li>
<li>a=rtcp-fb:100 nack pli</li>
<li>a=rid:q recv pt=98;max-width=640;max-height=480</li>
<li>a=rid:h recv pt=99;max-width=1280;max-height=720</li>
<li>a=rid:f recv pt=100;max-width=1920;max-height=1080</li>
<li>a=simulcast:recv q;h;f</li>
</ul>
<p>Answer SDP:</p>
<ul>
<li>m=video 48120 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:2 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=fmtp:99 profile=2; level-idx=8; tier=1;</li>
<li>a=fmtp:100 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
<li>a=rtcp-fb:99 ccm fir</li>
<li>a=rtcp-fb:99 nack</li>
<li>a=rtcp-fb:99 nack pli</li>
<li>a=rtcp-fb:100 ccm fir</li>
<li>a=rtcp-fb:100 nack</li>
<li>a=rtcp-fb:100 nack pli</li>
<li>a=rid:q send pt=98;max-width=640;max-height=480</li>
<li>a=rid:h send pt=99;max-width=1280;max-height=720</li>
<li>a=rid:f send pt=100;max-width=1920;max-height=1080</li>
<li>a=simulcast:send q;h;f</li>
</ul>
</section>
<section>
<h4 id="simulcast-with-ssrc-multiplexing">7.3.3 Simulcast with SSRC Multiplexing</h4>
<p>In the following example an offer is made by a conferencing server to receive 3 simulcast streams with SSRC multiplexing. The answerer agrees to send 3 simulcast streams at different resolutions.</p>
<p>Offer SDP:</p>
<ul>
<li>m=video 49170 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:2 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
<li>a=rid:q recv</li>
<li>a=rid:h recv</li>
<li>a=rid:f recv</li>
<li>a=simulcast:recv q;h;f</li>
</ul>
<p>Answer SDP:</p>
<ul>
<li>m=video 48120 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:2 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
<li>a=rid:q send</li>
<li>a=rid:h send</li>
<li>a=rid:f send</li>
<li>a=simulcast:send q;h;f</li>
</ul>
</section>
<section>
<h4 id="single-stream-simulcast">7.3.4 Single Stream Simulcast</h4>
<p>In the following example an offer is made to send a single RTP stream to a conferencing server. This single stream might include any AV1 dependency structure, including “S” scalability modes.</p>
<p>Offer SDP:</p>
<ul>
<li>m=video 49170 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
</ul>
<p>Answer SDP:</p>
<ul>
<li>m=video 48120 UDP/TLS/RTP/SAVPF 98</li>
<li>a=mid:0</li>
<li>a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid</li>
<li>a=extmap:3 urn:3gpp:video-orientation</li>
<li>a=extmap:4 https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension</li>
<li>a=sendrecv</li>
<li>a=rtcp-mux</li>
<li>a=rtcp-rsize</li>
<li>a=rtpmap:98 AV1/90000</li>
<li>a=fmtp:98 profile=2; level-idx=8; tier=1;</li>
<li>a=rtcp-fb:98 ccm fir</li>
<li>a=rtcp-fb:98 nack</li>
<li>a=rtcp-fb:98 nack pli</li>
</ul>
</section>
</section>
</section>
<section>
<h2 id="feedback-messages">8 Feedback Messages</h2>
</section>
<section>
<h2 id="full-intra-request-fir">8.1 Full Intra Request (FIR)</h2>
<p>The Full Intra Request (FIR) RTCP feedback message defined in <a href="https://tools.ietf.org/html/rfc5104">RFC5104</a> allows a
receiver to request a Decoder Refresh Point of an encoded stream.
Section 3 of <a href="https://tools.ietf.org/html/rfc8082">RFC8082</a> updates the definition of the Decoder Refresh
Point.</p>
<p class="untestable">Upon reception of an FIR, for every SSRC indicated in the FIR message,
the AV1 sender MUST send a new coded video sequence as soon as possible.
See section 7.5 of the <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1 video codec</a> for the definition
of a new coded video sequence.</p>
<p class="untestable">If simulcast encodings of the same source are transported on distinct SSRCs,
then in addition to sending a new coded video sequence for each encoding
corresponding to an SSRC in the FIR message, the AV1 sender MAY also send
new coded video sequences for other encodings from the same source(s).</p>
</section>
<section>
<h2 id="layer-refresh-request-lrr">8.2 Layer Refresh Request (LRR)</h2>
<p>The Layer Refresh Request specified in <a href="https://tools.ietf.org/html/draft-ietf-avtext-lrr-07">I-D.ietf-avtext-lrr</a> is designed to allow a receiver of a layered media stream to request that one or more of its substreams be refreshed, such that it can then be decoded by an endpoint which previously was not receiving those layers, without requiring that the entire stream be refreshed (as it would be if the receiver sent a Full Intra Request (FIR) per <a href="https://tools.ietf.org/html/rfc5104">RFC5104</a>).</p>
<pre><code> +---------------+---------------+
|0|1|2|3|4|5|6|7|0|1|2|3|4|5|6|7|
+---------------+---------+-+---+
| RES | TID | RES |0|SID|
+---------------+---------+-+---+
Figure 4
</code></pre>
<p class="untestable">AV1 streams MUST use the Layer Refresh Request format defined for VP9 in Section 5.3 of <a href="https://tools.ietf.org/html/draft-ietf-payload-vp9">I-D.ietf-payload-vp9</a>, with the high order bit of its three-bit SID field set to 0. Figure 4 shows the format for AV1 streams. Notice that SID here is two bits. SID is associated with AV1’s spatial_id and TID is associated with AV1’s temporal_id. See Sections 2, 5.3.3, and 6.2.3 of the AV1 bitstream specification <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a> for details on the temporal_id and spatial_id fields.</p>
<p class="untestable">Identification of a layer refresh frame may be performed by examining the coding dependency structure of the coded video sequence it belongs to. This may be provided by the scalability metadata (Sections 5.8.5 and 6.7.5 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>), either in the form of a pre-defined scalability mode or through a scalability structure (Sections 5.8.6 and 6.7.6 of <a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a>). Alternatively, the Dependency Descriptor RTP header extension that is specified in Appendix A of this document may be used.</p>
</section>
<section>
<h2 id="iana-considerations">9 IANA Considerations</h2>
<p>The AV1 media type is registered with IANA for signaling the transfer of AV1 via RTP at https://www.iana.org/assignments/media-types/video/AV1.</p>
</section>
<section>
<h2 id="security-considerations">10 Security Considerations</h2>
<p>RTP packets using the payload format defined in this document are subject to the security considerations discussed in the RTP specification <a href="https://tools.ietf.org/html/rfc3550">RFC3550</a> and in any appropriate RTP profile. This implies that confidentiality of the media streams is achieved by encryption, for example, through the application of SRTP <a href="https://tools.ietf.org/html/rfc3711">RFC3711</a>. A potential denial-of-service threat exists for data encodings using compression techniques that have non-uniform receiver-end computational load. The attacker can inject pathological datagrams into the stream that are complex to decode and that cause the receiver to be overloaded. Therefore, the usage of data origin authentication and data integrity protection of at least the RTP packet is RECOMMENDED, for example, with SRTP <a href="https://tools.ietf.org/html/rfc3711">RFC3711</a>. Encryption of RTP Header Extensions such as the Dependency Descriptor is also RECOMMENDED, using techniques such as <a href="https://tools.ietf.org/html/rfc6904">RFC6904</a> or successor specifications.</p>
<p>Note that the appropriate mechanism to ensure confidentiality and integrity of RTP packets and their payloads is very dependent on the application and on the transport and signaling protocols employed. Thus, although SRTP is given as an example above, other possible choices exist. See <a href="https://tools.ietf.org/html/rfc7202">RFC7202</a>.</p>
<p class="untestable">Decoders MUST discard reserved OBU types and reserved metadata OBU types, and SHOULD filter out temporal delimiter and tile list OBUs carried within the RTP payload. Middle boxes SHOULD NOT parse OBUs they do not support.</p>
<p>End-to-end security services such as authentication, integrity, or confidentiality protection could prevent an SFM or MANE from performing media-aware operations other than discarding complete packets. For example, repacketization requires that the MANE have access to the cleartext media payload. The Dependency Descriptor RTP extension described in Appendix A allows discarding of packets in a media-aware way even when confidentiality protection is used.</p>
</section>
<section>
<h2 id="references">11 References</h2>
<section>
<h3 id="normative-references">11.1 Normative References</h3>
<ul>
<li>
<p><a href="https://aomediacodec.github.io/av1-spec/av1-spec.pdf">AV1</a> <strong>AV1 Bitstream & Decoding Process Specification, Version 1.0.0 with Errata 1</strong>, January 2019.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc3550">RFC3550</a> <strong>RTP: A Transport Protocol for Real-Time Applications</strong>, H. Schulzrinne, S. Casner, R. Frederick, and V. Jacobson, July 2003.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc5104">RFC5104</a> <strong>Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)</strong>, S. Wenger, U. Chandra, M. Westerlund, and B. Burman, February 2008.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc6904">RFC6904</a> <strong>Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)</strong>, J. Lennox, April 2013.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc7667">RFC7667</a> <strong>RTP Topologies</strong>, M. Westerlund and S. Wenger, November 2015.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc8285">RFC8285</a> <strong>A General Mechanism for RTP Header Extensions for generic RTP header extensions</strong>, D. Singer, H. Desineni, and R. Even, October 2017.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc8851">RFC8851</a> <strong>RTP Payload Format Restrictions</strong>, A. Roach, January 2021.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc8852">RFC8852</a> <strong>RTP Stream Identifier Source Description (SDES)</strong>, A. Roach, S. Nandakumar and P. Thatcher, January 2021.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc8853">RFC8853</a> <strong>Using Simulcast in SDP and RTP Sessions</strong>, B. Burman, M. Westerlund, S. Nandakumar and M. Zanaty, January 2021.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/draft-ietf-avtext-lrr-07">I-D.ietf-avtext-lrr</a> <strong>The Layer Refresh Request (LRR) RTCP Feedback Message</strong>, J. Lennox, D. Hong, J. Uberti, S. Holmer, and M. Flodman, June 29, 2017.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/draft-ietf-payload-vp9">I-D.ietf-payload-vp9</a> <strong>RTP Payload Format for VP9 Video</strong>, J. Uberti, S. Holmer, M. Flodman, D. Hong, and J. Lennox, February 2021.</p>
</li>
</ul>
</section>
<section>
<h3 id="informative-references">11.2 Informative References</h3>
<ul>
<li>
<p><a href="https://tools.ietf.org/html/rfc3711">RFC3711</a> <strong>The Secure Real-time Transport Protocol (SRTP)</strong>, M. Baugher, D. McGrew, M. Naslund, E. Carrara, and K. Norrman, March 2004.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc7202">RFC7202</a> <strong>Securing the RTP Framework: Why RTP Does Not Mandate a Single Security Solution</strong>, C. Perkins and M. Westerlund, April 2014.</p>
</li>
<li>
<p><a href="https://tools.ietf.org/html/rfc8082">RFC8082</a> <strong>Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs</strong>, S. Wenger, J. Lennox, B. Burman, and M. Westerlund, March 2017.</p>
</li>
</ul>
</section>
</section>
<section>
<h2 id="appendix">Appendix</h2>
<section>
<h3 id="dependency-descriptor-rtp-header-extension-1">Dependency Descriptor RTP Header Extension</h3>
<section>
<h4 id="a1-introduction">A.1 Introduction</h4>
<p>This appendix describes the Dependency Descriptor (DD) RTP Header extension. The DD is used for conveying dependency information about individual video frames in a scalable video stream. The DD includes provisions for both temporal and spatial scalability.</p>
<p>In the DD, the smallest unit for which dependencies are described is an RTP frame. An RTP frame contains one complete coded video frame and may also contain additional information (e.g., metadata). Each RTP frame is identified by a frame_number. When spatial scalability is used, there may be multiple RTP frames produced for the same time instant. Further, this specification allows for the transmission of an RTP frame over multiple packets. RTP frame aggregation is explicitly disallowed. Hereinafter, RTP frame will be referred to as frame.</p>
<p>The DD uses the concept of Decode targets, each of which represents a subset of a scalable video stream necessary to decode the stream at a certain temporal and spatial fidelity. A frame may be associated with several Decode targets. This concept is used to facilitate selective forwarding, as is done by a Selective Forwarding Middlebox (SFM). Typically an SFM would select one Decode target for each endpoint, and forward all frames associated with that target.</p>
<p>The DD also uses the concept of Instantaneous Decidability or Decodability (IDD). The IDD property is the ability to decide immediately whether a received or missed packet is needed to decode a received bitstream. This property allows an SFM to determine whether it has to forward a packet to one or more downstream endpoints or attempt to recover essential missed packets.</p>
<p>The property is satisfied when the receiver is able to determine whether:</p>
<ul>
<li>The packet belongs to a frame which is required for the endpoint’s Decode target. This is determined from the Decode Target Indication (DTI) values (see Section A.4).</li>
<li>All frames referenced by the current frame have been forwarded to the endpoint. This is determined from the frame difference values (see Section A.8.3).</li>
<li>Upon receiving the very first packet after an RTP sequence number gap, if any of the missed packets are required for the Decode target to remain decodable. This is determined from the Chain information (see Section A.6).</li>
</ul>
<p>To reduce overhead, the DD uses templates to avoid sending repetitive information. Subsequent packets refer to a template containing predefined information, which may be overridden with custom dependencies. In this way, the typical DD payload requires three bytes. Dynamic structures whose information is not known in advance can be described using additional bytes.</p>
</section>
<section>
<h4 id="a2-conventions-definitions-and-acronyms">A.2 Conventions, Definitions and Acronyms</h4>
<p>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in <a href="https://tools.ietf.org/html/rfc2119">RFC2119</a>.</p>
<dl class="no-test-needed">
<dt>Chain</dt>
<dd>A sequence of frames for which it can be determined instantly if a frame from that sequence has been lost.</dd>
<dt>Decode target</dt>
<dd>The set of frames needed to decode a coded video sequence at a given spatial and temporal fidelity.</dd>
</dl>
<dl data-tests="https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L17">
<dt>Decode Target Indication (DTI)</dt>
<dd>Describes the relationship of a frame to a Decode target. The DTI indicates four distinct relationships: ‘not present’, ‘discardable’, ‘switch’, and ‘required’.</dd>
</dl>
<dl data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/video_coding/codecs/av1/scalability_structure_unittest.cc?q=NoFrameDependsOnDiscardableOrNotPresent">
<dt>Discardable indication</dt>
<dd>An indication for a frame, associated with a given Decode target, that it will not be a Referred frame for any frame belonging to that Decode target.</dd>
</dl>
<p class="alert alert-info"><strong>Note:</strong> A frame belonging to more than one Decode target may be discardable for one Decode target and not for another.</p>
<dl class="no-test-needed">
<dt>Frame dependency structure</dt>
<dd>Describes frame dependency information for the coded video sequence. The structure includes the number of DTIs, an ordered list of Frame dependency templates, and a mapping between Chains and Decode targets.</dd>
</dl>
<dl data-tests="https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L222, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L310, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L426, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L556">
<dt>Frame dependency template</dt>
<dd>Contains frame description information that many frames have in common. Includes values for spatial ID, temporal ID, DTIs, frame dependencies, and Chain information.</dd>
</dl>
<dl data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/video_coding/codecs/av1/scalability_structure_unittest.cc?q=NoFrameDependsOnDiscardableOrNotPresent">
<dt>Not present indication</dt>
<dd>An indication for a frame, that it is not associated with a given Decode target.</dd>
</dl>
<dl class="no-test-needed">
<dt>Referred frame</dt>
<dd>A frame on which the current frame depends.</dd>
</dl>
<dl data-tests="https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L17">
<dt>Required indication</dt>
<dd>An indication for a frame, associated with a given Decode target, that it belongs to the Decode target and has neither a Discardable indication nor a Switch indication.</dd>
</dl>
<p class="alert alert-info"><strong>Note:</strong> A frame belonging to more than one Decode target may be required for one Decode target and not required (either discardable or switch) for another.</p>
<dl data-tests="https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/modules/video_coding/codecs/av1/scalability_structure_unittest.cc?q=NoFrameDependsThroughSwitchIndication">
<dt>Switch indication</dt>
<dd>An indication associated with a specific Decode target that all subsequent frames for that Decode target will be decodable if the frame containing the indication is decodable.</dd>
</dl>
</section>
<section>
<h4 id="a3-media-stream-requirements">A.3 Media Stream Requirements</h4>
<p>A bitstream conformant to this extension must adhere to the following statement(s).</p>
<p data-tests="https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L222, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L310, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L426, https://github.com/medooze/media-server/blob/9d32f5511673e9098f1ed1d03149aae767613a03/test/ddls.cpp#L556">A frame for which all Referred frames are decodable MUST itself be decodable.</p>