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
|
<pre>Internet Engineering Task Force (IETF) V. Singh
Request for Comments: 8015 callstats.io
Category: Standards Track C. Perkins
ISSN: 2070-1721 University of Glasgow
A. Clark
Telchemy
R. Huang
Huawei
November 2016
<span class="h1">RTP Control Protocol (RTCP) Extended Report (XR) Block</span>
<span class="h1">for Independent Reporting of Burst/Gap Discard Metrics</span>
Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of burst/gap discard metrics
independently of the burst/gap loss metrics for use in a range of RTP
applications.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc8015">http://www.rfc-editor.org/info/rfc8015</a>.
<span class="grey">Singh, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Independent Burst/Gap Discard Metrics Block . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. RTCP and RTCP Extended Reports . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-1.3">1.3</a>. Performance Metrics Framework . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-1.4">1.4</a>. Applicability . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Independent Burst/Gap Discard Metrics Block . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Report Block Structure . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
3.2. Definition of Fields in the Independent Burst/Gap Discard
Metrics Block . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3">3.3</a>. Derived Metrics Based on the Reported Metrics . . . . . . <a href="#page-8">8</a>
<a href="#section-4">4</a>. Considerations for Voice-over-IP Applications . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5">5</a>. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-5.2">5.2</a>. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.1">6.1</a>. New RTCP XR Block Type Value . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.2">6.2</a>. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.3">6.3</a>. Contact Information for Registrations . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#appendix-A">Appendix A</a>. Metrics Represented Using the Template from <a href="./rfc6390">RFC 6390</a> 13
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<span class="grey">Singh, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Independent Burst/Gap Discard Metrics Block</span>
This document defines a new block type that extends the metrics
defined in [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>]. The new block type reports the proportion of
packets discarded in a burst by the de-jitter buffer at the receiver.
The number of packets discarded depends on the de-jitter buffer
algorithm implemented by the endpoint.
The new report block defined in this document is different from the
one defined in [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>]. The metrics in [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>] depend on the
metrics in the burst/gap loss metric defined in [<a href="./rfc6958" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Loss Metric Reporting"">RFC6958</a>].
Consequently, an endpoint that sends a Burst/Gap Discard Metrics
Block [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>] also needs to send a Burst/Gap Loss Metrics Block
[<a href="./rfc6958" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Loss Metric Reporting"">RFC6958</a>]. The combined usage is useful when an endpoint observes
correlated packet losses and discard. However, when the burst of
packet losses and discards do not occur simultaneously, the
application could prefer to send a concise report block that just
reports the burst/gap of discarded packets. The report block in this
document provides the complete information and does not require
additional report blocks. That is, this block reports the total
number of packets discarded, the total burst duration, and the total
number of bursts. All of these metrics are missing in [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>].
This block provides information on transient network issues. Burst/
gap metrics are typically used in cumulative reports; however, they
can also be used in interval reports (see the Interval Metric flag in
<a href="#section-3.2">Section 3.2</a>). The variation in the number of packet discards in a
burst affects the user experience. Based on the metrics reported in
the block, the sending endpoint can change the packetization
interval, vary the bitrate, etc. The report can additionally be used
for diagnostics [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>]. The metric belongs to the class of
transport-related end-system metrics defined in [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>].
The definitions of "burst", "gap", "loss", and "discard" are
consistent with the definitions in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]. To accommodate a range
of de-jitter buffer algorithms and packet discard logic that can be
used by implementers, the method used to distinguish between bursts
and gaps uses an equivalent method to that defined in <a href="./rfc3611#section-4.7.2">Section 4.7.2
of [RFC3611]</a>. Note that reporting the specific de-jitter buffer
algorithm and/or the packet discard logic is out of the scope of this
document.
<span class="grey">Singh, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. RTCP and RTCP Extended Reports</span>
The use of RTCP for reporting is defined in [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>]. [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]
defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for
use with [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>] and [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Performance Metrics Framework</span>
The Performance Metrics Framework [<a href="./rfc6390" title=""Guidelines for Considering New Performance Metric Development"">RFC6390</a>] provides guidance on the
definition and specification of performance metrics. The RTP
Monitoring Framework [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>] provides guidelines for reporting the
block format using RTCP XR. The metrics block described in this
document is in accordance with the guidelines in [<a href="./rfc6390" title=""Guidelines for Considering New Performance Metric Development"">RFC6390</a>] and
[<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>].
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Applicability</span>
These metrics are applicable to a range of RTP applications that
contain de-jitter buffers at the receiver to smooth variation in
packet-arrival time and don't use stream repair means, e.g., Forward
Error Correction (FEC) [<a href="#ref-FLEX_FEC">FLEX_FEC</a>] and/or retransmission [<a href="./rfc4588" title=""RTP Retransmission Payload Format"">RFC4588</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
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="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
In addition, the following terms are defined:
Received, Lost, and Discarded
A packet is regarded as "lost" if it fails to arrive within an
implementation-specific time window. A packet that arrives within
this time window but is too early to be played out, too late to be
played out, or thrown away before playout due to packet
duplication or redundancy is be recorded as "discarded". A packet
SHALL NOT be regarded as "discarded" if it arrives within this
time window but is dropped during decoding by some higher-layer
decoder, e.g., due to a decoding error. Each packet is classified
as one of "received" (or "OK"), "discarded", or "lost". The
metric "cumulative number of packets lost" defined in [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>]
reports a count of packets lost from the media stream (single
synchronization source (SSRC) within a single RTP session).
Similarly, the metric "number of packets discarded" defined in
[<a href="./rfc7002" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count Metric Reporting"">RFC7002</a>] reports a count of packets discarded from the media
stream (single SSRC within a single RTP session) arriving at the
<span class="grey">Singh, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
receiver. Another metric, defined in [<a href="./rfc5725" title=""Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)"">RFC5725</a>], is available to
report on packets that are not recovered by any repair techniques
that are in use. Note that the term "discard" defined here builds
on the "discard" definition in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] but extends the concept
to take into account packet duplication and reports different
types of discard counts [<a href="./rfc7002" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count Metric Reporting"">RFC7002</a>].
Bursts and Gaps
The terms "burst" and "gap" are used in a manner consistent with
that of RTCP XR [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]. RTCP XR views an RTP stream as being
divided into bursts, which are periods during which the discard
rate is high enough to cause noticeable quality degradation
(generally a discard rate over 5 percent), and gaps, which are
periods during which discarded packets are infrequent, and hence
quality is generally acceptable.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Independent Burst/Gap Discard Metrics Block</span>
Metrics in this block report on burst/gap discard in the stream
arriving at the RTP system. Measurements of these metrics are made
at the receiving end of the RTP stream. Instances of this metrics
block use the synchronization source (SSRC) to refer to the separate
auxiliary Measurement Information Block [<a href="./rfc6776" title=""Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block"">RFC6776</a>], which describes
measurement periods in use (see <a href="./rfc6776#section-4.2">[RFC6776], Section 4.2</a>).
This metrics block relies on the measurement period in the
Measurement Information Block indicating the span of the report.
Senders MUST send this block in the same compound RTCP packet as the
Measurement Information Block. Receivers MUST verify that the
measurement period is received in the same compound RTCP packet as
this metrics block. If not, this metrics block MUST be discarded.
<span class="grey">Singh, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Report Block Structure</span>
The structure of the Independent Burst/Gap Discard Metrics Block is
as follows.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=35 | I | resv | Block Length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Sum of Burst Durations (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Discarded in Bursts | Number of |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bursts | Total Packets Expected in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Definition of Fields in the Independent Burst/Gap Discard Metrics</span>
<span class="h3"> Block</span>
Block Type (BT): 8 bits
An Independent Burst/Gap Discard Metrics Block is identified by
the constant 35.
Interval Metric flag (I): 2 bits
This field is used to indicate whether the burst/gap discard
metrics are Sampled, Interval, or Cumulative metrics [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>]:
I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive
metrics reports.
I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements.
In this document, burst/gap discard metrics can only be measured
over definite intervals and cannot be sampled. Also, the value
I=00 is reserved for future use. Senders MUST NOT use the values
I=00 or I=01. If a block is received with I=00 or I=01, the
receiver MUST discard the block.
<span class="grey">Singh, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
Reserved (resv): 6 bits
These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (see <a href="./rfc6709#section-4.2">[RFC6709], Section 4.2</a>).
Block Length: 16 bits
The length of this report block in 32-bit words, minus one. For
the Independent Burst/Gap Discard Metrics Block, the block length
is equal to 5. The block MUST be discarded if the block length is
set to a different value.
SSRC of Source: 32 bits
As defined in <a href="./rfc3611#section-4">Section 4 of [RFC3611]</a>.
Threshold: 8 bits
The Threshold is equivalent to Gmin in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>], i.e., the number
of successive packets that have to be received prior to, and
following, a discarded packet in order for that discarded packet
to be regarded as part of a gap. Note that the Threshold is set
in accordance with the Gmin calculation defined in <a href="./rfc3611#section-4.7.2">Section 4.7.2
of [RFC3611]</a>.
Sum of Burst Durations (ms): 24 bits
The total duration of bursts of discarded packets in the period of
the report (Interval or Cumulative).
The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
an over-range measurement. If the measurement is unavailable, the
value 0xFFFFFF MUST be reported.
Packets Discarded in Bursts: 24 bits
The total number of packets discarded during discard bursts, as
defined in <a href="./rfc7002#section-3.2">Section 3.2 of [RFC7002]</a>.
<span class="grey">Singh, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
Number of Bursts: 16 bits
The number of discard bursts in the period of the report (Interval
or Cumulative).
The measured value is an unsigned value. If the measured value
exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFF MUST be reported.
Total Packets Expected in Bursts: 24 bits
The total number of packets expected during the discard bursts
(that is, the sum of received packets and lost packets). The
metric is defined in [<a href="./rfc7003" title=""RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>].
Discard Count: 32 bits
Number of packets discarded over the period (Interval or
Cumulative) covered by this report, as defined in <a href="./rfc7002#section-3.2">Section 3.2 of
[RFC7002]</a>.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Derived Metrics Based on the Reported Metrics</span>
The metrics described here are intended to be used in conjunction
with information from the Measurement Information Block [<a href="./rfc6776" title=""Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block"">RFC6776</a>].
These metrics provide the following information relevant to
statistical parameters (depending on cumulative of interval
measures), for example:
o The average discarded burst size, which can be calculated by
dividing the metric "Packets Discarded in Bursts" by the "Number
of Bursts".
o The average burst duration, which can be calculated by dividing
the metric "Sum of Burst Durations (ms)" by the "Number of
Bursts".
<span class="grey">Singh, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Considerations for Voice-over-IP Applications</span>
This metrics block is applicable to a broad range of RTP
applications. Where the metric is used with a Voice-over-IP (VoIP)
application and the stream repair means is not available, the
following considerations apply.
RTCP XR views a call as being divided into bursts, which are periods
during which the discard rate is high enough to cause noticeable call
quality degradation (generally a discard rate over 5 percent) and
gaps, which are periods during which discarded packets are
infrequent, and hence call quality is generally acceptable.
If voice activity detection is used, the burst/gap duration is
determined as if silence packets had been sent, i.e., a period of
silence in excess of Gmin packets will terminate a burst condition.
The RECOMMENDED value for the threshold Gmin in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] results in
a burst being a period of time during which the call quality is
degraded to a similar extent to a typical pulse code modulation (PCM)
severely errored second.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. SDP Signaling</span>
[<a id="ref-RFC3611">RFC3611</a>] defines the use of SDP (Session Description Protocol)
[<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] for signaling the use of XR blocks. XR blocks can be used
without prior signaling.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. SDP rtcp-xr Attribute Extension</span>
This section augments the SDP [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] attribute "rtcp-xr" defined
in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. The
ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>] syntax is as follows.
xr-format =/ xr-ind-bgd-block
xr-ind-bgd-block = "ind-burst-gap-discard"
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Offer/Answer Usage</span>
When SDP is used in Offer/Answer context, the SDP Offer/Answer usage
defined in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral
parameters, refer to <a href="./rfc3611#section-5.2">Section 5.2 of [RFC3611]</a>.
<span class="grey">Singh, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to
[<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. New RTCP XR Block Type Value</span>
This document assigns the block type value 35 in the IANA "RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
the "Independent Burst/Gap Discard Metrics Block".
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. New RTCP XR SDP Parameter</span>
This document also registers a new parameter "ind-burst-gap-discard"
in the "RTP Control Protocol Extended Reports (RTCP XR) Session
Description Protocol (SDP) Parameters Registry".
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Contact Information for Registrations</span>
The contact information for the registrations is:
ART Area Directors <art-ads@ietf.org>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
This block does not provide per-packet statistics, so the risk to
confidentiality documented in <a href="#section-7">Section 7</a>, paragraph 3 of [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]
does not apply. However, the gap indicated within this block could
be used to detect the timing of other events on the path between the
sender and receiver. For example, a competing multimedia stream
might cause a discard burst for the duration of the stream, allowing
the receiver of this block to know when the competing stream was
active. This risk is not a significant threat since the only
information leaked is the timing of the discard, not the cause.
Where this is a concern, the implementation SHOULD apply encryption
and authentication to this report block. For example, this can be
achieved by using the Audio-Visual Profile with Feedback (AVPF)
profile together with the Secure RTP profile, as defined in
[<a href="./rfc3711" title=""The Secure Real-time Transport Protocol (SRTP)"">RFC3711</a>]; an appropriate combination of those two profiles ("SAVPF")
is specified in [<a href="./rfc5124" title=""Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)"">RFC5124</a>]. Besides this, it is believed that this
RTCP XR block introduces no new security considerations beyond those
described in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
<span class="grey">Singh, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC3550">RFC3550</a>] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, <a href="./rfc3550">RFC 3550</a>, DOI 10.17487/RFC3550,
July 2003, <<a href="http://www.rfc-editor.org/info/rfc3550">http://www.rfc-editor.org/info/rfc3550</a>>.
[<a id="ref-RFC3611">RFC3611</a>] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
"RTP Control Protocol Extended Reports (RTCP XR)",
<a href="./rfc3611">RFC 3611</a>, DOI 10.17487/RFC3611, November 2003,
<<a href="http://www.rfc-editor.org/info/rfc3611">http://www.rfc-editor.org/info/rfc3611</a>>.
[<a id="ref-RFC3711">RFC3711</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
<a href="./rfc3711">RFC 3711</a>, DOI 10.17487/RFC3711, March 2004,
<<a href="http://www.rfc-editor.org/info/rfc3711">http://www.rfc-editor.org/info/rfc3711</a>>.
[<a id="ref-RFC4566">RFC4566</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", <a href="./rfc4566">RFC 4566</a>, DOI 10.17487/RFC4566,
July 2006, <<a href="http://www.rfc-editor.org/info/rfc4566">http://www.rfc-editor.org/info/rfc4566</a>>.
[<a id="ref-RFC5124">RFC5124</a>] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", <a href="./rfc5124">RFC 5124</a>, DOI 10.17487/RFC5124, February
2008, <<a href="http://www.rfc-editor.org/info/rfc5124">http://www.rfc-editor.org/info/rfc5124</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>>.
[<a id="ref-RFC5725">RFC5725</a>] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE
Report Block Type for RTP Control Protocol (RTCP) Extended
Reports (XRs)", <a href="./rfc5725">RFC 5725</a>, DOI 10.17487/RFC5725, February
2010, <<a href="http://www.rfc-editor.org/info/rfc5725">http://www.rfc-editor.org/info/rfc5725</a>>.
[<a id="ref-RFC6776">RFC6776</a>] Clark, A. and Q. Wu, "Measurement Identity and Information
Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", <a href="./rfc6776">RFC 6776</a>,
DOI 10.17487/RFC6776, October 2012,
<<a href="http://www.rfc-editor.org/info/rfc6776">http://www.rfc-editor.org/info/rfc6776</a>>.
<span class="grey">Singh, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
[<a id="ref-RFC7003">RFC7003</a>] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Discard Metric Reporting", <a href="./rfc7003">RFC 7003</a>, DOI 10.17487/RFC7003,
September 2013, <<a href="http://www.rfc-editor.org/info/rfc7003">http://www.rfc-editor.org/info/rfc7003</a>>.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-FLEX_FEC">FLEX_FEC</a>]
Singh, V., Begen, A., Zanaty, M., and G. Mandyam, "RTP
Payload Format for Flexible Forward Error Correction
(FEC)", Work in Progress, <a href="./draft-ietf-payload-flexible-fec-scheme-03">draft-ietf-payload-flexible-fec-</a>
<a href="./draft-ietf-payload-flexible-fec-scheme-03">scheme-03</a>, October 2016.
[<a id="ref-RFC4588">RFC4588</a>] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hakenberg, "RTP Retransmission Payload Format", <a href="./rfc4588">RFC 4588</a>,
DOI 10.17487/RFC4588, July 2006,
<<a href="http://www.rfc-editor.org/info/rfc4588">http://www.rfc-editor.org/info/rfc4588</a>>.
[<a id="ref-RFC6390">RFC6390</a>] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", <a href="https://www.rfc-editor.org/bcp/bcp170">BCP 170</a>, <a href="./rfc6390">RFC 6390</a>,
DOI 10.17487/RFC6390, October 2011,
<<a href="http://www.rfc-editor.org/info/rfc6390">http://www.rfc-editor.org/info/rfc6390</a>>.
[<a id="ref-RFC6709">RFC6709</a>] Carpenter, B., Aboba, B., Ed., and S. Cheshire, "Design
Considerations for Protocol Extensions", <a href="./rfc6709">RFC 6709</a>,
DOI 10.17487/RFC6709, September 2012,
<<a href="http://www.rfc-editor.org/info/rfc6709">http://www.rfc-editor.org/info/rfc6709</a>>.
[<a id="ref-RFC6792">RFC6792</a>] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use
of the RTP Monitoring Framework", <a href="./rfc6792">RFC 6792</a>,
DOI 10.17487/RFC6792, November 2012,
<<a href="http://www.rfc-editor.org/info/rfc6792">http://www.rfc-editor.org/info/rfc6792</a>>.
[<a id="ref-RFC6958">RFC6958</a>] Clark, A., Zhang, S., Zhao, J., and Q. Wu, Ed., "RTP
Control Protocol (RTCP) Extended Report (XR) Block for
Burst/Gap Loss Metric Reporting", <a href="./rfc6958">RFC 6958</a>,
DOI 10.17487/RFC6958, May 2013,
<<a href="http://www.rfc-editor.org/info/rfc6958">http://www.rfc-editor.org/info/rfc6958</a>>.
[<a id="ref-RFC7002">RFC7002</a>] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Discard Count Metric
Reporting", <a href="./rfc7002">RFC 7002</a>, DOI 10.17487/RFC7002, September
2013, <<a href="http://www.rfc-editor.org/info/rfc7002">http://www.rfc-editor.org/info/rfc7002</a>>.
<span class="grey">Singh, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Metrics Represented Using the Template from <a href="./rfc6390">RFC 6390</a></span>
a. Threshold Metric
* Defined in item a of <a href="./rfc7003#appendix-A">Appendix A of [RFC7003]</a>.
b. Sum of Burst Durations (ms)
* Metric Name: Sum of Burst Durations with Discarded RTP
Packets.
* Metric Description: The total duration of bursts of discarded
RTP packets in the period of the report.
* Method of Measurement or Calculation: See <a href="#section-3.2">Section 3.2</a>, Sum of
Burst Durations definition.
* Units of Measurement: See <a href="#section-3.2">Section 3.2</a>, Sum of Burst Durations
definition.
* Measurement Point(s) with Potential Measurement Domain: See
<a href="#section-3">Section 3</a>, first paragraph.
* Measurement Timing: See <a href="#section-3">Section 3</a>, second paragraph for
measurement timing and <a href="#section-3.2">Section 3.2</a> for Interval Metric flag.
* Use and Applications: See <a href="#section-1.4">Section 1.4</a>.
* Reporting Model: See [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
c. Packets Discarded in Bursts Metric
* Defined in item b of <a href="./rfc7003#appendix-A">Appendix A of [RFC7003]</a>.
d. Number of Bursts
* Metric Name: Number of discard bursts in RTP.
* Metric Description: The total number of bursts with discarded
RTP packets in the period of the report.
* Method of Measurement or Calculation: See <a href="#section-3.2">Section 3.2</a>, Number
of Bursts definition.
* Units of Measurement: See <a href="#section-3.2">Section 3.2</a> for the Number of Bursts
definition.
<span class="grey">Singh, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
* Measurement Point(s) with Potential Measurement Domain: See
<a href="#section-3">Section 3</a>, first paragraph.
* Measurement Timing: See <a href="#section-3">Section 3</a>, second paragraph for
measurement timing and <a href="#section-3.2">Section 3.2</a> for Interval Metric flag.
* Use and Applications: See <a href="#section-1.4">Section 1.4</a>.
* Reporting Model: See [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
e. Total Packets Expected in Bursts Metric
* Defined in item c of <a href="./rfc7003#appendix-A">Appendix A of [RFC7003]</a>.
f. Discard Count
* Defined in <a href="./rfc7002#appendix-A">Appendix A of [RFC7002]</a>.
Acknowledgments
The authors would like to thank Ben Campbell, Stephen Farrell, Paul
Kyzivat, Shucheng LIU, Jan Novak, and Dan Romascanu for providing
valuable feedback on this document.
Contributors
Qin Wu, Rachel Huang, and Alan Clark wrote <a href="./rfc7003">RFC 7003</a>, which this
document extends.
<span class="grey">Singh, et al. Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8015">RFC 8015</a> RTCP XR Burst/Gap Discard November 2016</span>
Authors' Addresses
Varun Singh
CALLSTATS I/O Oy
Runeberginkatu 4c A 4
Helsinki 00100
Finland
Email: varun@callstats.io
URI: <a href="https://www.callstats.io/about">https://www.callstats.io/about</a>
Colin Perkins
University of Glasgow
School of Computing Science
Glasgow G12 8QQ
United Kingdom
Email: csp@csperkins.org
Alan Clark
Telchemy Incorporated
2905 Premiere Parkway, Suite 280
Duluth, GA 30097
United States of America
Email: alan.d.clark@telchemy.com
Rachel Huang
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Email: Rachel@huawei.com
Singh, et al. Standards Track [Page 15]
</pre>
|
