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) H. Asaeda
Request for Comments: 7244 NICT
Category: Standards Track Q. Wu
ISSN: 2070-1721 R. Huang
Huawei
May 2014
<span class="h1">RTP Control Protocol (RTCP) Extended Report (XR) Blocks</span>
<span class="h1">for Synchronization Delay and Offset Metrics Reporting</span>
Abstract
This document defines two RTP Control Protocol (RTCP) Extended Report
(XR) blocks that allow the reporting of initial synchronization delay
and synchronization offset 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="./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/rfc7244">http://www.rfc-editor.org/info/rfc7244</a>.
Copyright Notice
Copyright (c) 2014 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">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</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>. Synchronization Delay and Offset Metrics Reporting Blocks ..2
<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-4">4</a>
<a href="#section-2.1">2.1</a>. Standards Language .........................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. RTP Flow Initial Synchronization Delay Report Block .............<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Metric Block Structure .....................................<a href="#page-5">5</a>
3.2. Definition of Fields in RTP Flow Initial
Synchronization Delay Metrics Block ........................<a href="#page-5">5</a>
<a href="#section-4">4</a>. RTP Flow Synchronization Offset Metrics Block ...................<a href="#page-6">6</a>
<a href="#section-4.1">4.1</a>. Metric Block Structure .....................................<a href="#page-7">7</a>
4.2. Definition of Fields in RTP Flow General
Synchronization Offset Metrics Block .......................<a href="#page-7">7</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-attrib 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-9">9</a>
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-10">10</a>
<a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-10">10</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-10">10</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-10">10</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-11">11</a>
<a href="#appendix-A">Appendix A</a>. Metrics Represented Using the Template from <a href="./rfc6390">RFC 6390</a> ..12
<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>. Synchronization Delay and Offset Metrics Reporting Blocks</span>
This document defines two new block types 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 first new block type supports reporting of the Initial
Synchronization Delay to establish a multimedia session. Information
is recorded about the time difference between the start of RTP
sessions and the time the RTP receiver acquires all components of RTP
sessions in the multimedia session [<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>].
The second new block type supports reporting of the relative
synchronization offset time of two arbitrary streams (e.g., between
audio and video streams), with the same RTCP CNAME included in RTCP
Source description items (SDES) packets [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>].
These metrics belong to the class of transport-level metrics defined
in [<a href="./rfc6792" title=""Guidelines for Use of the RTP Monitoring Framework"">RFC6792</a>].
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
<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 -- the 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>
When joining each session in layered video sessions [<a href="./rfc6190" title=""RTP Payload Format for Scalable Video Coding"">RFC6190</a>] or the
multimedia session, a receiver may not synchronize playout across the
multimedia session or layered video session until RTCP Sender Report
(SR) packets have been received on all components of RTP sessions.
The components of RTP sessions are per-media-type RTP sessions for
the multimedia sessions or per-layer RTP sessions for the layered
video sessions. For multicast sessions, the Initial Synchronization
Delay metric varies with the session bandwidth, the number of
members, and the number of senders in the session. The RTP Flow
Initial Synchronization Delay Metrics Block defined in this document
can be used to report such a metric, i.e., the Initial
Synchronization Delay to receive all the RTP streams belonging to the
same multimedia session or layered video session. In the absence of
packet loss, the Initial Synchronization Delay is equal to the
average time taken to receive the first RTCP packet in the RTP
session with the longest RTCP reporting interval. In the presence of
packet loss, the media synchronization should rely on the in-band
mapping of RTP and NTP-format timestamps [<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>] or wait until the
reporting interval has passed, and the next RTCP SR packet is sent.
Receivers of the RTP Flow Initial Synchronization Delay Metrics Block
could use this metric to compare with targets (i.e., Service Level
Agreement or thresholds of the system) to help ensure the quality of
real-time application performance.
In an RTP multimedia session, there can be an arbitrary number of
streams carried in different RTP sessions, with the same RTCP CNAME.
These streams may be not synchronized with each other. For example,
one audio stream and one video stream belong to the same session, and
the audio stream is transmitted lagging behind the video stream for
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
multiple tens of milliseconds [<a href="#ref-TR-126" title=""Triple-play Services Quality of Experience (QoE) Requirements"">TR-126</a>]. The RTP Flow Synchronization
Offset block can be used to report such synchronization offset
between video and audio streams. This block is also applied to the
case where an RTP session can contain media streams with media from
multiple media types. The metrics defined in the RTP Flow
Synchronization Offset Metrics Block can be used by the network
manager for troubleshooting and dealing with user-experience issues.
<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>. Standards 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>].
In addition, the following terms are defined:
Initial Synchronization Delay:
A multimedia session comprises a set of concurrent RTP sessions
among a common group of participants, using one RTP session for
each media type. The Initial Synchronization Delay is the average
time for the receiver to synchronize all components of a
multimedia session [<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>].
Synchronization Offset:
Synchronization between two media streams must be maintained to
ensure satisfactory Quality of Experience (QoE). Two media
streams can be of the same or different media types belonging to
one RTP session, or of different media types belonging to one
multimedia session. The Synchronization Offset is the relative
time difference of the two media streams that need to be
synchronized.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. RTP Flow Initial Synchronization Delay Metrics Block</span>
This block is sent by RTP receivers and reports the Initial
Synchronization Delay beyond the information carried in the standard
RTCP packet format. Information is recorded about the time
difference between the start of the multimedia session and the time
when the RTP receiver acquires all components of RTP sessions
[<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>] measured at the receiving end of the RTP stream.
This block needs to be exchanged only occasionally, for example, sent
once at the start of the RTP session.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Metric Block Structure</span>
The RTP Flow Initial Synchronization Delay Metrics Block has the
following format:
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=27 | Reserved | Block length=2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Initial Synchronization Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 RTP Flow Initial Synchronization Delay</span>
<span class="h3"> Metrics Block</span>
Block type (BT): 8 bits
The RTP Flow Initial Synchronization Delay Metrics Block is
identified by the constant 27.
Reserved: 8 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 constant 2, in accordance with the definition of this field in
<a href="./rfc3611#section-3">Section 3 of RFC 3611</a> [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
SSRC of source: 32 bits
The SSRC of the media source SHALL be set to the value of the SSRC
identifier carried in any arbitrary component of RTP sessions
belonging to the same multimedia session.
Initial Synchronization Delay: 32 bits
The average delay, expressed in units of 1/65536 seconds, from the
beginning of the multimedia session [<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>] to the time when
RTCP packets are received on all of the component RTP sessions.
It is recommended that the beginning of the multimedia session is
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
chosen as the time when the receiver has joined the first RTP
session of the multimedia session. The value of the Initial
Synchronization Delay is calculated based on received RTCP SR
packets or the RTP header extension containing the in-band mapping
of RTP and NTP-format timestamps [<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>]. If there is no packet
loss, the Initial Synchronization Delay is expected to be equal to
the average time taken to receive the first RTCP packet in the RTP
session with the longest RTCP reporting interval or to the average
time taken to receive the first RTP header extension containing
the in-band mapping of RTP and NTP-format timestamps.
If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. RTP Flow Synchronization Offset Metrics Block</span>
In the RTP multimedia sessions or one RTP session, there can be an
arbitrary number of media streams and each media stream (e.g., audio
stream or video stream) is sent in a separate RTP stream. In case of
one RTP session, each media stream or each medium uses a different
SSRC. The receiver correlates these media streams that need to be
synchronized by means of the RTCP CNAME contained in the RTCP Source
Description (SDES) packets [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>].
This block is sent by RTP receivers and reports the synchronization
offset of two arbitrary RTP streams that need to be synchronized in
the RTP multimedia session. Information is recorded about the
relative average time difference between two arbitrary RTP streams
(the reporting stream and the reference stream) with the same CNAME
and measured at the receiving end of the RTP stream. In order to
tell what the offset of the reporting stream is relative to, the
block for the reference stream with synchronization offset of zero
should be reported.
Instances of this block refer by synchronization source (SSRC) to the
separate auxiliary Measurement Information block [<a href="./rfc6776" title=""Measurement Identity and information Reporting using SDES item and XR Block"">RFC6776</a>], which
describes measurement periods in use (see <a href="./rfc6776#section-4.2">Section 4.2 of [RFC6776]</a>).
This metrics block relies on the measurement period in the
Measurement Information block indicating the span of the report and
SHOULD be sent in the same compound RTCP packet as the Measurement
Information Block. If the measurement period is not received in the
same compound RTCP packet as this block, this block MUST be
discarded.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Metric Block Structure</span>
The RTP Flow General Synchronization Offset Metrics Block has the
following format:
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=28 | I | Reserved | Block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Synchronization Offset, most significant word |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Synchronization Offset, least significant word |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Report Block Structure
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Definition of Fields in RTP Flow General Synchronization Offset</span>
<span class="h3"> Metrics Block</span>
Block type (BT): 8 bits
The RTP Flow General Synchronization Offset Metrics Block is
identified by the constant 28.
Interval Metric Flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Discard
Summary Statistics metrics are Sampled, Interval, or Cumulative
metrics:
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 value I=00 is the reserved value and MUST
NOT be used. If the value I=00 is received, then the XR block
MUST be ignored by the receiver.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
Reserved: 6 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
MUST be ignored by the receiver.
Block length: 16 bits
The constant 3, in accordance with the definition of this field in
<a href="./rfc3611#section-3">Section 3 of RFC 3611</a> [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>].
SSRC of Source: 32 bits
The SSRC of the media source SHALL be set to the value of the SSRC
identifier of the reporting RTP stream to which the XR relates.
Synchronization Offset: 64 bits
The synchronization offset of the reporting RTP stream relative to
the reference stream with the same CNAME. The calculation of
Synchronization Offset is similar to the Difference D calculation
in the <a href="./rfc3550">RFC 3550</a>. That is to say, if Si is the NTP timestamp from
the reporting RTP packet i, Ri is the time of arrival in NTP
timestamp units for reporting RTP packet i, Sj is the NTP
timestamp from the reference RTP packet j, and Rj is the time of
arrival in NTP timestamp units for reference RTP packet j, then
the value of the Synchronization Offset D may be expressed as
D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)
If in-band delivery of NTP-format timestamps is supported
[<a href="./rfc6051" title=""Rapid Synchronisation of RTP Flows"">RFC6051</a>], Si and Sj should be obtained directly from the RTP
packets where NTP timestamps are available. If not, Si and Sj
should be calculated from their corresponding RTP timestamps. The
value of the Synchronization Offset is represented using a 64-bit
signed NTP-format timestamp as defined in [<a href="./rfc5905" title=""Network Time Protocol Version 4: Protocol and Algorithms Specification"">RFC5905</a>], which is a
64-bit signed fixed-point number with the integer part in the
first 32 bits and the fractional part in the last 32 bits. A
positive value of the Synchronization Offset means that the
reporting stream leads before the reference stream, while a
negative one means the reporting stream lags behind the reference
stream. The Synchronization Offset of zero means the stream is
the reference stream.
If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
<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 MAY 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-attrib Attribute Extension</span>
Using the Augmented Backus-Naur Form (ABNF) [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>], two new
parameters are defined for the two report blocks defined in this
document to be used with SDP [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>]. They have the following
syntax within the "rtcp-xr" attribute [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>]:
xr-format =/ xr-rfisd-block
/ xr-rfso-block
xr-rfisd-block = "rtp-flow-init-syn-delay"
xr-rfso-block = "rtp-flow-syn-offset"
Refer to <a href="./rfc3611#section-5.1">Section 5.1 of RFC 3611</a> [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] for a detailed description
and the full syntax of the "rtcp-xr" attribute.
<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 the offer/answer context, the SDP Offer/Answer
usage defined in [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] applies.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
New report block types for RTCP XR are subject to IANA registration.
For general guidelines on IANA allocations for RTCP XR, refer to
<a href="./rfc3611#section-6.2">Section 6.2 of [RFC3611]</a>.
This document assigns two new block type values in the RTCP XR Block
Type Registry:
Name: RFISD
Long Name: RTP Flow Initial Synchronization Delay
Value 27
Reference: <a href="#section-3">Section 3</a>
Name: RFSO
Long Name: RTP Flow Synchronization Offset
Value 28
Reference: <a href="#section-4">Section 4</a>
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
This document also registers two new SDP [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] parameters for the
"rtcp-xr" attribute in the RTCP XR SDP Parameters Registry:
* "rtp-flow-init-syn-delay "
* "rtp-flow-syn-offset"
The contact information for the registrations is:
RAI Area Directors <rai-ads@tools.ietf.org>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
When using Secure RTP [<a href="./rfc3711" title=""The Secure Real-time Transport Protocol (SRTP)"">RFC3711</a>], or other media-layer security,
reporting accurate synchronization offset information can expose some
details about the timing of the cryptographic operations that are
used to protect the media. There is a possibility that this timing
information might enable a side-channel attack on the encryption. For
environments where this attack is a concern, implementations need to
take care to ensure cryptographic processing and media compression
take the same amount of time irrespective of the media content, to
avoid the potential attack.
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="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The authors would like to thank Bill Ver Steeg, David R. Oran, Ali
Begen, Colin Perkins, Roni Even, Kevin Gross, Jing Zhao, Fernando
Boronat Segui, Mario Montagud Climent, Youqing Yang, Wenxiao Yu,
Yinliang Hu, Jonathan Lennox, and Stephen Farrel for their valuable
comments and suggestions on this document.
<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.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
[<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-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-RFC5905">RFC5905</a>] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network
Time Protocol Version 4: Protocol and Algorithms
Specification", <a href="./rfc5905">RFC 5905</a>, June 2010.
[<a id="ref-RFC6051">RFC6051</a>] Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP
Flows", <a href="./rfc6051">RFC 6051</a>, November 2010.
[<a id="ref-RFC6190">RFC6190</a>] Wenger, S., Wang, Y., Schierl, T., and A. Eleftheriadis,
"RTP Payload Format for Scalable Video Coding", <a href="./rfc6190">RFC 6190</a>,
May 2011.
[<a id="ref-RFC6776">RFC6776</a>] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", <a href="./rfc6776">RFC 6776</a>, August 2012.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC6390">RFC6390</a>] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", <a href="./rfc6390">RFC 6390</a>, October 2011.
[<a id="ref-RFC6792">RFC6792</a>] Wu, Q., "Guidelines for Use of the RTP Monitoring
Framework", <a href="./rfc6792">RFC 6792</a>, November 2012.
[<a id="ref-TR-126">TR-126</a>] Broadband Forum, "Triple-play Services Quality of
Experience (QoE) Requirements", Technical Report TR-126,
December 2006.
[<a id="ref-Y.1540">Y.1540</a>] ITU-T, "IP packet transfer and availability performance
parameters", ITU-T Recommendation Y.1540, November 2007.
<span class="grey">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</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. Initial Synchronization Delay Metric
* Metric Name: RTP Initial Synchronization Delay
* Metric Description: See the definition of "Initial
Synchronization Delay" in <a href="#section-2.1">Section 2.1</a>.
* Method of Measurement or Calculation: See the definition of
the "Initial Synchronization Delay" field in <a href="#section-3.2">Section 3.2</a>.
* Units of Measurement: See the definition of the "Initial
Synchronization Delay" field in <a href="#section-3.2">Section 3.2</a>.
* Measurement Point(s) with Potential Measurement Domain: See
the first paragraph of <a href="#section-3">Section 3</a>.
* Measurement Timing: See the second paragraph of <a href="#section-3">Section 3</a>.
* Use and applications: See <a href="#section-1.4">Section 1.4</a>.
* Reporting model: See <a href="./rfc3611">RFC 3611</a>.
b. Synchronization Offset Metric
* Metric Name: RTP Synchronization Offset Delay
* Metric Description: See the definition of "Synchronization
Offset" in <a href="#section-1.2">Section 1.2</a>.
* Method of Measurement or Calculation: See the definition of
the "Synchronization Offset" field in <a href="#section-4.2">Section 4.2</a>.
* Units of Measurement: See the definition of the
"Synchronization Offset" field in <a href="#section-4.2">Section 4.2</a>.
* Measurement Point(s) with Potential Measurement Domain: See
the second paragraph of <a href="#section-4">Section 4</a>.
* Measurement Timing: See the third paragraph of <a href="#section-4.2">Section 4.2</a> for
measurement timing and the 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">Asaeda, 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="./rfc7244">RFC 7244</a> SDO Report Blocks May 2014</span>
Authors' Addresses
Hitoshi Asaeda
National Institute of Information and Communications Technology
4-2-1 Nukui-Kitamachi
Koganei, Tokyo 184-8795
Japan
EMail: asaeda@nict.go.jp
Qin Wu
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
EMail: bill.wu@huawei.com
Rachel Huang
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
EMail: Rachel@huawei.com
Asaeda, et al. Standards Track [Page 13]
</pre>
|
