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
|
<pre>Internet Engineering Task Force (IETF) A. Clark
Request for Comments: 6798 Telchemy
Category: Standards Track Q. Wu
ISSN: 2070-1721 Huawei
November 2012
<span class="h1">RTP Control Protocol (RTCP) Extended Report (XR) Block</span>
<span class="h1">for Packet Delay Variation Metric Reporting</span>
Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of packet delay variation
metrics for 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/rfc6798">http://www.rfc-editor.org/info/rfc6798</a>.
Copyright Notice
Copyright (c) 2012 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 & Wu Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Packet Delay Variation Metrics Block .......................<a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. RTCP and RTCP XR 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-2.1">2.1</a>. Requirements Language ......................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Notations ..................................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Packet Delay Variation 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>
<a href="#section-3.2">3.2</a>. Definition of Fields in PDV Metrics Block ..................<a href="#page-5">5</a>
<a href="#section-3.3">3.3</a>. Guidance on Use of PDV Metrics .............................<a href="#page-8">8</a>
<a href="#section-3.4">3.4</a>. Examples of Use ............................................<a href="#page-9">9</a>
<a href="#section-4">4</a>. SDP Signaling ...................................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-10">10</a>
<a href="#section-5.1">5.1</a>. New RTCP XR Block Type Value ..............................<a href="#page-10">10</a>
<a href="#section-5.2">5.2</a>. New RTCP XR SDP Parameter .................................<a href="#page-10">10</a>
<a href="#section-5.3">5.3</a>. Contact Information for Registrations .....................<a href="#page-11">11</a>
<a href="#section-5.4">5.4</a>. New Registry of PDV Types .................................<a href="#page-11">11</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-11">11</a>
<a href="#section-7">7</a>. Contributors ...................................................<a href="#page-12">12</a>
<a href="#section-8">8</a>. Acknowledgments ................................................<a href="#page-12">12</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-12">12</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-12">12</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-13">13</a>
<span class="grey">Clark & Wu Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</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>. Packet Delay Variation Metrics 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 provides information on Packet Delay Variation
(PDV) using one of several standard metrics, for example, Mean
Absolute Packet Delay Variation 2 (MAPDV2) (Clause 6.2.3.2 of
[<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>]) or 2-point PDV (Clause 6.2.4 of [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>]).
The metrics belong to the class of transport metrics defined in
[<a href="#ref-MONARCH" title=""Guidelines for Use of the RTP Monitoring Framework"">MONARCH</a>].
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. RTCP and RTCP XR 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 architectures [<a href="#ref-MONARCH" title=""Guidelines for Use of the RTP Monitoring Framework"">MONARCH</a>] provides guidelines for reporting
block format using RTCP XR. The XR 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="#ref-MONARCH" title=""Guidelines for Use of the RTP Monitoring Framework"">MONARCH</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 wide range of RTP applications in
which the application streams are sensitive to delay variation
[<a href="./rfc5481" title=""Packet Delay Variation Applicability Statement"">RFC5481</a>]. For example, applications could use the measurements of
these metrics to help adjust the size of adaptive jitter buffers to
improve performance. Network managers can use these metrics to
compare actual delay variation to targets (i.e., a numerical
objective or Service Level Agreement) to help ensure the quality of
real-time application performance.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirements Language</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 & Wu Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Notations</span>
This report block makes use of binary fractions. The terminology
used is
Numeric formats S X:Y
where S indicates a two's complement signed representation, X
the number of bits prior to the decimal place, and Y the number
of bits after the decimal place.
Hence, 8:8 represents an unsigned number in the range 0.0 to
255.996 with a granularity of 0.0039. S7:8 represents the
range -127.996 to +127.996. 0:16 represents a proper binary
fraction with range as follows:
0.0 to 1 - 1/65536 = 0.9999847
however, note that use of flag values at the top of the numeric
range slightly reduces this upper limit. For example, if the
16-bit values 0xfffe and 0xffff are used as flags for "over-
range" and "unavailable" conditions, a 0:16 quantity has a
range as follows:
0.0 to 1 - 3/65536 = 0.9999542
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Packet Delay Variation Metrics Block</span>
Metrics in this block report on packet delay variation in the stream
arriving at the RTP system. The measurement of these metrics is made
at the receiving end of the RTP stream. Instances of this metric
block refer by synchronization source (SSRC) 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 contains
measurement intervals. This metric block relies on the measurement
interval given by the value of the "Measurement Duration (Interval)"
field in the Measurement Information Block to indicate 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 for this metric block, this metric block MUST be discarded.
<span class="grey">Clark & Wu Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Report Block Structure</span>
PDV metrics block:
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=15 | I |pdvtyp |Rsv| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pos PDV Threshold/Peak | Pos PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neg PDV Threshold/Peak | Neg PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean PDV | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 PDV Metrics Block</span>
Block type (BT): 8 bits
A Packet Delay Variation Metrics Block is identified by the
constant 15.
Interval Metric flag (I): 2 bit
This field is used to indicate whether the Packet Delay Variation
metrics are Sampled, Interval, or Cumulative metrics [<a href="#ref-MONARCH" title=""Guidelines for Use of the RTP Monitoring Framework"">MONARCH</a>],
that is, whether the reported values apply to the most recent
measurement interval duration between successive metrics reports
(I=10) (the Interval Duration), or they apply to the accumulation
period characteristic of cumulative measurements (I=11) (the
Cumulative Duration), or they are a sampled instantaneous value
(I=01) (Sampled Value). The value I=00 is reserved and MUST NOT
be used. If the value I=00 is received, then the XR block MUST be
ignored by the receiver.
Packet Delay Variation Metric Type (pdvtyp): 4 bits
Packet Delay Variation Metric Type is of type enumerated and is
interpreted as an unsigned, 4-bit integer. This field is used to
identify the Packet Delay Variation Metric Type used in this
report block, according to the following code:
<span class="grey">Clark & Wu Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
bits 014-011
0: MAPDV2, Clause 6.2.3.2 of [<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>],
1: 2-point PDV, Clause 6.2.4 of [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>].
Rsv: 2 bits
This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and
ignored by the receiver.
block length: 16 bits
The length of this report block is in 32-bit words, minus one.
For the Packet Delay Variation Metrics Block, the block length is
equal to 4.
SSRC of source: 32 bits
This field is as defined in <a href="./rfc3611#section-4.1">Section 4.1 of [RFC3611]</a>.
Positive PDV Threshold/Peak: 16 bits
This field is associated with the Positive PDV percentile and
expressed in milliseconds with numeric format S11:4. The term
"Positive" represents that the packets are arriving later than the
expected time.
If the measured value is less than -2047.9375 (the value that
would be coded as 0x8001), the value 0x8000 SHOULD be reported to
indicate an over-range negative measurement. If the measured
value is greater than +2047.8125 (the value that would be coded as
0x7FFD), the value 0x7FFE SHOULD be reported to indicate an over-
range positive measurement. If the measurement is unavailable,
the value 0x7FFF MUST be reported.
Positive PDV Percentile: 16 bits
This field indicates the percentages of packets in the RTP stream
for which individual packet delays were less than the Positive PDV
Threshold. It is expressed in numeric format 8:8 with values from
0 to 100th percentile.
If the measurement is unavailable, the value 0xFFFF MUST be
reported.
<span class="grey">Clark & Wu Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
Negative PDV Threshold/Peak: 16 bits
This field is associated with the Negative PDV percentile and
expressed in milliseconds with numeric format S11:4. The term
"Negative" represents that the packets are arriving earlier than
the expected time.
If the measured value is more negative than -2047.9375 (the value
that would be coded as 0x8001), the value 0x8000 SHOULD be
reported to indicate an over-range negative measurement. If the
measured value is more positive than +2047.8125 (the value that
would be coded as 0x7FFD), the value 0x7FFE SHOULD be reported to
indicate an over-range positive measurement. If the measurement
is unavailable, the value 0x7FFF MUST be reported.
Negative PDV Percentile: 16 bits
This field indicates the percentages of packets in the RTP stream
for which individual packet delays were more than the Negative PDV
Threshold. It is expressed in numeric format 8:8 with values from
0 to 100th percentile.
If the measurement is unavailable, the value 0xFFFF MUST be
reported.
If the PDV Type indicated is 2-point PDV and the Positive and
Negative PDV percentiles are set to 100.0, then the Positive and
Negative Threshold/Peak PDV values are the peak values measured
during the reporting interval (which may be from the start of the
call for cumulative reports). In this case, the difference
between the Positive and Negative Threshold/Peak values defines
the range of 2-point PDV.
Mean PDV: 16 bits
The mean PDV value of data packets is expressed in milliseconds
with Numeric format S11:4 format.
For MAPDV2, this value is generated according to Clause 6.2.3.2 of
[<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>]. For interval reports, the MAPDV2 value is reset at the
start of the interval.
For 2-point PDV, the value reported is the mean of per-packet
2-point PDV values. This metric indicates the arrival time of the
first media packet of the session with respect to the mean of the
arrival times of every packet of the session. A single value of
the metric (for a single session) may not be useful by itself, but
its average over a number of sessions may be useful in diagnosing
<span class="grey">Clark & Wu Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
media delay at session startup. For example, this might occur if
media packets are often delayed behind signaling packets due to
head-of-line blocking.
If the measured value is more negative than -2047.9375 (the value
that would be coded as 0x8001), the value 0x8000 SHOULD be
reported to indicate an over-range negative measurement. If the
measured value is more positive than +2047.8125 (the value that
would be coded as 0x7FFD), the value 0x7FFE SHOULD be reported to
indicate an over-range positive measurement. If the measurement
is unavailable, the value 0x7FFF MUST be reported.
Reserved: 16 bits
These bits are reserved for future definition. They MUST be set
to zero by the sender and ignored by the receiver.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Guidance on Use of PDV Metrics</span>
This subsection provides informative guidance on when it might be
appropriate to use each of the PDV metric types.
MAPDV2 (Clause 6.2.3.2 of [<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>]) is the envelope of instantaneous
(per-packet) delay when compared to the short-term moving average
delay. This metric could be useful in determining residual
impairment when an RTP end system uses an adaptive de-jitter buffer
that tracks the average delay variation, provided that the averaging
behavior of the adaptive algorithm is similar to that of the MAPDV2
algorithm.
2-point PDV (Clause 6.2.4 of [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>]) reports absolute packet delay
variation with respect to a defined reference packet transfer delay.
Note that the reference packet is generally selected as the packet
with minimum delay based on the most common criterion (see Sections <a href="#section-1">1</a>
and 5.1 of [<a href="./rfc5481" title=""Packet Delay Variation Applicability Statement"">RFC5481</a>]). In an RTP context, the two "points" are at
the sender (the synchronization source that applies RTP timestamps)
and at the receiver. The value of this metric for the packet with
index j is identical to the quantity D(i,j) defined in <a href="./rfc3550#section-6.4.1">Section 6.4.1
of [RFC3550]</a>, and the packet index i should be set equal to the index
of the reference packet for the metric in practice. The metric
includes the effect of the frequency offsets of clocks in both the
sender and receiver end systems, so it is useful mainly in networks
where synchronization is distributed. As well as measuring packet
delay variation in such networks, it may be used to ensure that
synchronization is effective, for example, where the network carries
ISDN data traffic over RTP [<a href="./rfc4040" title=""RTP Payload Format for a 64 kbit/s Transparent Call"">RFC4040</a>]. The metric is likely to be
useful in networks that use fixed de-jitter buffering, because it may
be used to determine the length of the required de-jitter buffer, or
<span class="grey">Clark & Wu Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
to determine if network performance has deteriorated such that
existing de-jitter buffers are too small to accommodate the observed
delay variation.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Examples of Use</span>
(a) To report MAPDV2 [<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>]:
Pos PDV Threshold = 50.0; Pos PDV Percentile = 95.3; Neg PDV
Threshold = 50.0 (note this implies -50 ms); Neg PDV Percentile
= 98.4; PDV type = 0 (MAPDV2)
causes average MAPDV2 to be reported in the Mean PDV field.
Note that implementations either may fix the reported
percentile and calculate the associated PDV level or may fix a
threshold PDV level and calculate the associated percentile.
From a practical implementation perspective, it is simpler to
use the second of these approaches (except of course in the
extreme case of the 100th percentile).
(b) To report 2-point PDV [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>]:
Pos PDV Threshold = 60 (note this implies +60 ms); Pos PDV
Percentile = 96.3; Neg PDV Threshold = 0; Neg PDV Percentile =
0; PDV type = 1 (2-point PDV)
causes 2-point PDV to be reported in the Mean PDV field.
2-point PDV, according to [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>] is the difference in delay
between the current packet and the referenced packet of the
stream. If the sending and receiving clocks are not
synchronized, this metric includes the effect of relative
timing drift.
<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. XR blocks MAY be used
without prior signaling.
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.
<span class="grey">Clark & Wu Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
xr-format =/ xr-pdv-block
xr-pdv-block = "pkt-dly-var" [ "," pdvtype ] [ "," nspec "," pspec ]
pdvtype = "pdv=" ( "0" ; MAPDV2 ITU-T G.1020
/ "1" ; 2-point PDV ITU-T Y.1540
/ 1*2DIGIT ) ;Value 2~15 are valid and
;reserved for future use
nspec = ("nthr=" fixpoint) ; negative PDV threshold (ms)
/ ("npc=" fixpoint ) ; negative PDV percentile
pspec = ("pthr=" fixpoint) ; positive PDV threshold (ms)
/ ("ppc=" fixpoint) ; positive PDV percentile
fixpoint = 1*DIGIT "." 1*DIGIT ; fixed point decimal
DIGIT = <as defined in <a href="./rfc5234#section-3.4">Section 3.4 of [RFC5234]</a>>
When SDP is used in offer/answer, a system sending SDP may request a
specific type of PDV measurement. In addition, they may state a
specific percentile or threshold value and expect to receive the
corresponding threshold or percentile metric, respectively. The
system receiving the SDP SHOULD send the PDV metrics requested, but
if the metric is not available, the system receiving the SDP MUST
send the metric block with the flag value indicating that the metric
is unavailable.
<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="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 15 in the IANA "RTCP XR
Block Type" registry to the "Packet Delay Variation 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-dly-var" in the
"RTCP XR SDP Parameters" registry.
<span class="grey">Clark & Wu Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Contact Information for Registrations</span>
The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. New Registry of PDV Types</span>
This document creates a new registry to be called "RTCP XR PDV block
- PDV type" as a sub-registry of the "RTP Control Protocol Extended
Reports (RTCP XR) Block Type Registry". Policies for this new
registry are as follows:
o The information required to support an assignment is an
unambiguous definition of the new metric, covering the base
measurements and how they are processed to generate the reported
metric. This should include the units of measurement, how values
of the metric are reported in the three 16-bit fields "Pos PDV
Threshold/Peak", "Neg PDV Threshold/Peak", and "Mean PDV" within
the report block, and how the metric uses the two 16-bit fields
"Pos PDV Percentile" and "Neg PDV Percentile".
o The review process for the registry is "Specification Required" as
described in <a href="./rfc5226#section-4.1">Section 4.1 of [RFC5226]</a>.
o Entries in the registry are unsigned 4-bit integers. The valid
range is 0 to 15 corresponding to the 4-bit field "pdvtyp" in the
block. Values are to be recorded in decimal.
o Initial assignments are as follows:
* 0: MAPDV2, Clause 6.2.3.2 of [<a href="#ref-G.1020" title=""Performance parameter definitions for quality of speech and other voiceband applications utilizing IP networks"">G.1020</a>],
* 1: 2-point PDV, Clause 6.2.4 of [<a href="#ref-Y.1540" title=""IP packet transfer and availability performance parameters"">Y.1540</a>],
* 2-15: Reserved for future use.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
It is believed that this proposed 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="grey">Clark & Wu Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contributors</span>
Geoff Hunt wrote the initial version of this document.
<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, Bob Biskner, Kevin Connor,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Jing Zhao,
Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn, Shida Schubert,
Benoit Claise, Adrian Farrel, and Pete Resnick.
<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-G.1020">G.1020</a>] ITU-T Rec. G. 1020, "Performance parameter definitions for
quality of speech and other voiceband applications
utilizing IP networks", July 2006.
[<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-RFC4040">RFC4040</a>] Kreuter, R., "RTP Payload Format for a 64 kbit/s
Transparent Call", <a href="./rfc4040">RFC 4040</a>, April 2005.
[<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-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 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.
<span class="grey">Clark & Wu Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6798">RFC 6798</a> RTCP XR Packet Delay Variation November 2012</span>
[<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.
[<a id="ref-Y.1540">Y.1540</a>] ITU-T Rec. Y.1540, "IP packet transfer and availability
performance parameters", November 2007.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-MONARCH">MONARCH</a>] Wu, W., Hunt, G., and P. Arden, "Guidelines for Use of the
RTP Monitoring Framework", Work in Progress,
September 2012.
[<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-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.
Authors' Addresses
Alan Clark
Telchemy Incorporated
2905 Premiere Parkway, Suite 280
Duluth, GA 30097
USA
EMail: alan.d.clark@telchemy.com
Qin Wu
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
EMail: sunseawq@huawei.com
Clark & Wu Standards Track [Page 13]
</pre>
|
