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
|
<pre>Internet Engineering Task Force (IETF) A. Clark
Request for Comments: 7002 Telchemy
Category: Standards Track G. Zorn
ISSN: 2070-1721 Network Zen
Q. Wu
Huawei
September 2013
<span class="h1">RTP Control Protocol (RTCP) Extended Report (XR) Block</span>
<span class="h1">for Discard Count Metric Reporting</span>
Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of a simple discard count metric
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="./rfc5741#section-2">Section 2 of RFC 5741</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/rfc7002">http://www.rfc-editor.org/info/rfc7002</a>.
Copyright Notice
Copyright (c) 2013 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.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Discard Count Report Block . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.2">1.2</a>. RTCP and RTCP Extended Reports . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.3">1.3</a>. Performance Metrics Framework . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.4">1.4</a>. Applicability . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Discard Count Metrics Block . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Report Block Structure . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
3.2. Definition of Fields in the Discard Count Metrics Block . 5
<a href="#section-4">4</a>. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5.1">5.1</a>. New RTCP XR Block Type Value . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.2">5.2</a>. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.3">5.3</a>. Contact Information for Registrations . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7">7</a>. Contributors . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8">8</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#appendix-A">Appendix A</a>. Metrics Represented Using the Template from <a href="./rfc6390">RFC 6390</a> 11
<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>. Discard Count Report Block</span>
This document defines a new block type to augment those defined in
[<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] for use in a range of RTP applications. The new block type
supports the reporting of the number of packets that are received
correctly but are never played out, typically because they arrive too
late (buffer underflow) or too early (buffer overflow) to be played
out. The metric is applicable both to systems that use packet loss
repair techniques (such as forward error correction [<a href="./rfc5109" title=""RTP Payload Format for Generic Forward Error Correction"">RFC5109</a>] or
retransmission [<a href="./rfc4588" title=""RTP Retransmission Payload Format"">RFC4588</a>]) and to those that do not.
This metric is useful for identifying the existence, and
characterizing the severity, of packet transport problems that may
affect users' perceptions of a service delivered over RTP.
This block may be used in conjunction with [<a href="./rfc7003" title=""RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>], which provides
additional information on the pattern of discarded packets. However,
the metric in [<a href="./rfc7003" title=""RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>] may be used independently of the metrics in
this block.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
When a Discard Count Metrics Block is sent together with a Burst/Gap
Discard Metrics Block (defined in [<a href="./rfc7003" title=""RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting"">RFC7003</a>]) to the media sender or
RTP-based network management system, the information carried in the
Discard Count Metrics Block and the Burst/Gap Discard Metrics Block
allows systems receiving the blocks to calculate burst/gap summary
statistics (e.g., the gap discard rate).
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>].
<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>
"Guidelines for Considering New Performance Metric Development"
[<a href="./rfc6390" title=""Guidelines for Considering New Performance Metric Development"">RFC6390</a>] provides guidance on the definition and specification of
performance metrics. "Guidelines for Use of the RTP Monitoring
Framework" [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>] provides guidance for reporting 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>
This metric is believed to be applicable to a large class of RTP
applications that use a de-jitter buffer [<a href="./rfc5481" title=""Packet Delay Variation Applicability Statement"">RFC5481</a>].
Discards due to late or early arriving packets affect user
experience. The reporting of discards alerts senders and other
receivers to the need to adjust their transmission or reception
strategies. The reports allow network managers to diagnose these
user experience problems.
The ability to detect duplicate packets can be used by managers to
detect network layer or sender behavior, which may indicate network
or device issues. Based on the reports, these issues may be
addressed prior to any impact on user experience.
<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>].
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
In addition, the following terms are defined:
Received, Lost, and Discarded
A packet shall be regarded as lost if it fails to arrive within an
implementation-specific time window. A packet that arrives within
this time window but is either too early or too late to be played
out or is thrown away before playout due to packet duplication or
redundancy shall be regarded 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. A packet shall be classified as one of the
following: received (or OK), discarded, or lost. The discard
count metric counts only discarded packets. 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" reports a
count of packets discarded from the media stream (single SSRC
within a single RTP session) arriving at the 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 may be in use.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Discard Count Metrics Block</span>
Metrics in this block report on the number of packets discarded in
the stream arriving at the RTP end system. The measurement of these
metrics is made at the receiving end of the RTP stream. Instances of
this metrics block use the 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 interval in the Measurement Information
Block indicating the span of the report and MUST be sent in the same
compound RTCP packet as the Measurement Information Block. If the
measurement interval is not received in the same compound RTCP packet
as this metrics block, this metrics block MUST be discarded.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</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 Discard Count 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=24 | I |DT | resv | Block Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Discard Count Metrics Block</span>
Block Type (BT): 8 bits
A Discard Count Metrics Block is identified by the constant 24.
Interval Metric flag (I): 2 bits
This field indicates whether the reported metric is an Interval,
Cumulative, or Sampled metric [<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.
I=01: Sampled Value - the reported value is a sampled
instantaneous value.
In this document, the discard count metric can only be measured
over definite intervals and cannot be sampled. Accordingly, the
value I=01, indicating a sampled value, MUST NOT be sent, and MUST
be discarded when received. In addition, the value I=00 is
reserved and also MUST NOT be sent, and MUST be discarded when
received.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
Discard Type (DT): 2 bits
This field is used to identify the discard type used in this
report block. The discard type is defined as follows:
00: Report packet discarded or being thrown away before playout
due to packet duplication.
01: Report packet discarded due to too early to be played out.
10: Report packet discarded due to too late to be played out.
The value DT=11 is reserved for future definition and MUST NOT be
sent, and MUST be discarded when received.
An endpoint MAY report any combination of discard types in each
reporting interval by including several Discard Count Metrics
Blocks in a single RTCP XR packet.
Some systems send duplicate RTP packets for robustness or error
resilience. This is NOT RECOMMENDED since it breaks RTCP packet
statistics. If duplication is desired for error resilience, the
mechanism described in [<a href="#ref-RTPDUP" title=""Duplicating RTP Streams"">RTPDUP</a>] can be used, since this will not
cause breakage of RTP streams or RTCP statistics.
Reserved (resv): 4 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, in
accordance with the definition in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]. This field MUST be
set to 2 to match the fixed length of the report block. 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.1">Section 4.1 of [RFC3611]</a>.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
Discard Count
Number of packets discarded over the period (Interval or
Cumulative) covered by this report.
The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFFFD, the value 0xFFFFFFFE MUST be reported to
indicate an over-range measurement. If the measurement is
unavailable, the value 0xFFFFFFFF MUST be reported.
Note that the number of packets expected in the period associated
with this metric (whether Interval or Cumulative) is available
from the difference between a pair of extended sequence numbers in
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>], so it need not be
repeated in this block.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. SDP Signaling</span>
[<a id="ref-RFC3611">RFC3611</a>] defines the use of the Session Description Protocol (SDP)
[<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] for signaling the use of XR blocks. However, XR blocks MAY
be used without prior signaling (see <a href="./rfc3611#section-5">Section 5 of RFC 3611</a>).
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.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-pdc-block
xr-pdc-block = "pkt-discard-count"
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.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 of Offer/Answer for unilateral
parameters, refer to <a href="./rfc3611#section-5.2">Section 5.2 of [RFC3611]</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</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="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. New RTCP XR Block Type Value</span>
This document assigns the block type value 24 in the IANA "RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
the "Discard Count Metrics Block".
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. New RTCP XR SDP Parameter</span>
This document also registers a new parameter "pkt-discard-count" in
the "RTP Control Protocol Extended Reports (RTCP XR) Session
Description Protocol (SDP) Parameters Registry".
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Contact Information for Registrations</span>
The following contact information is provided for all registrations
in this document:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
In some situations, returning very detailed error information (e.g.,
over-range measurement or measurement unavailable) using this report
block can provide an attacker with insight into the security
processing. 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>].
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.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contributors</span>
Geoff Hunt wrote the initial draft of this document.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span>
The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Claire Bi, Bob Biskner,
Gonzalo Camarillo, Benoit Claise, Kevin Connor, Claus Dahm, Spencer
Dawkins, Randy Ethier, Roni Even, Stephen Farrel, Jim Frauenthal,
Kevin Gross, Albert Higashi, Tom Hock, Shane Holthaus, Paul Jones,
Rajesh Kumar, Keith Lantz, Jonathan Lennox, Mohamed Mostafa, Amy
Pendleton, Colin Perkins, Mike Ramalho, Ravi Raviraj, Dan Romascanu,
Albrecht Schwarz, Varun Singh, Tom Taylor, Dan Wing, and Hideaki
Yamada.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.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>, March 1997.
[<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>, July 2003.
[<a id="ref-RFC3611">RFC3611</a>] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", <a href="./rfc3611">RFC 3611</a>, November
2003.
[<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>, March 2004.
[<a id="ref-RFC4566">RFC4566</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.
[<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>, February 2008.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
[<a id="ref-RFC6709">RFC6709</a>] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", <a href="./rfc6709">RFC 6709</a>,
September 2012.
[<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>, October 2012.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<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>,
July 2006.
[<a id="ref-RFC5109">RFC5109</a>] Li, A., "RTP Payload Format for Generic Forward Error
Correction", <a href="./rfc5109">RFC 5109</a>, December 2007.
[<a id="ref-RFC5481">RFC5481</a>] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", <a href="./rfc5481">RFC 5481</a>, March 2009.
[<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>, February 2010.
[<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>,
October 2011.
[<a id="ref-RFC6792">RFC6792</a>] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
RTP Monitoring Framework", <a href="./rfc6792">RFC 6792</a>, November 2012.
[<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>, September 2013.
[<a id="ref-RTPDUP">RTPDUP</a>] Begen, A. and C. Perkins, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22Duplicating+RTP+Streams%22'>"Duplicating RTP Streams"</a>, Work
in Progress, March 2013.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</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. Number of Packets Discarded Metric
* Metric Name: Number of RTP packets discarded.
* Metric Description: Number of RTP packets discarded over the
period covered by this report.
* Method of Measurement or Calculation: See <a href="#section-3.2">Section 3.2</a>, Discard
Count definition.
* Units of Measurement: See <a href="#section-3.2">Section 3.2</a>, Discard Count
definition.
* Measurement Point(s) with Potential Measurement Domain: See
<a href="#section-3">Section 3</a>, 1st paragraph.
* Measurement Timing: See <a href="#section-3">Section 3</a>, 1st 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">RFC 3611</a>.
<span class="grey">Clark, 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="./rfc7002">RFC 7002</a> RTCP XR Discard September 2013</span>
Authors' Addresses
Alan Clark
Telchemy Incorporated
2905 Premiere Parkway, Suite 280
Duluth, GA 30097
USA
EMail: alan.d.clark@telchemy.com
Glen Zorn
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 8-1000-4155
EMail: glenzorn@gmail.com
Qin Wu
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
EMail: sunseawq@huawei.com
Clark, et al. Standards Track [Page 12]
</pre>
|
