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
|
<pre>Internet Engineering Task Force (IETF) A. Clark
Request for Comments: 6776 Telchemy
Category: Standards Track Q. Wu
ISSN: 2070-1721 Huawei
October 2012
<span class="h1">Measurement Identity and Information Reporting Using a</span>
<span class="h1">Source Description (SDES) Item and an RTCP Extended Report (XR) Block</span>
Abstract
This document defines an RTP Control Protocol (RTCP) Source
Description (SDES) item and an RTCP Extended Report (XR) block
carrying parameters that identify and describe a measurement period
to which one or more other RTCP XR blocks may refer.
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/rfc6776">http://www.rfc-editor.org/info/rfc6776</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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</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>. RTCP and RTCP XRs . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Performance Metrics Framework . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.3">1.3</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>. Measurement Identity SDES Item . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. APSI: Application-Specific Identifier SDES Item . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. Measurement Information XR Block . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Report Block Structure . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
4.2. Definition of Fields in Measurement Information Report
Block . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</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 SDES Item Type Value . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5.2">5.2</a>. New RTCP XR Block Type Value . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5.3">5.3</a>. Contact Information for Registrations . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document defines one new RTP Control Protocol (RTCP) Source
Description (SDES) [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>] item and one new Extended Report (XR)
block carrying parameters that identify and describe a measurement
period to which one or more other RTCP XR blocks may refer.
The SDES item provides a field for an application-specific auxiliary
identifier. This identifier may be used to correlate data in XR
blocks within an RTP session with data from a non-RTP session.
An RTCP Measurement Identity SDES packet may be associated with a set
of RTCP XR metrics blocks that share the same application-specific
measurement identifier.
The XR block does not contain any measurement results (metrics).
Instead, it provides information relevant to a measurement reported
in one or more other block types, including:
o the sequence number of the first packet of the RTP session,
o the extended sequence numbers of the first packet of the current
measurement interval, and the last packet included in the
measurement,
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
o the duration of the most recent measurement interval, and
o the duration of the interval applicable to cumulative measurements
(which may be the duration of the RTP session to date).
The calculation method of the extended RTP sequence number is
provided in the Real-time Transport Protocol (RTP) [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>].
The RTCP XR block containing the measurement information is intended
to provide a single copy of the information necessary to relate
measurement data in the RTCP XR blocks to the stream and measurement
period to which they refer. Commonly, multiple other small metric
blocks contain measurement data for the same stream and period, and
overhead would be large if all of these metric blocks carried
duplicated data for measurement identification.
The RTCP XR block may be associated with a set of RTCP XR metrics
blocks that share the same information relevant to a reported
measurement. There may be several such sets in an RTCP packet, in
which each set shares the same information relevant to a reported
measurement. There may also be RTCP XR blocks in the packet that are
not associated with a Measurement Information block, for example,
blocks that were defined before the Measurement Identity and
information mechanism were introduced by this document.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. RTCP and RTCP XRs</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>]
defines an extensible structure for reporting by using an RTCP XR.
[<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] also defines the use of XR blocks. This document defines a
new Extended Report block.
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</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=""Monitoring Architectures for RTP"">MONARCH</a>] provides guidelines for reporting
block format using RTCP XR. The SDES item and XR block described in
this document are in accordance with [<a href="./rfc6390" title=""Guidelines for Considering New Performance Metric Development"">RFC6390</a>] and [<a href="#ref-MONARCH" title=""Monitoring Architectures for RTP"">MONARCH</a>].
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Applicability</span>
The RTCP SDES item and the RTCP XR block defined in this document
provide information relevant to the measurements for members of a
family of RTCP XR metrics blocks that are designed to use it. To use
the mechanism defined here, the RTCP XR block containing measurement
information is not required to be in the same RTCP packet as the SDES
item containing measurement identity.
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
<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>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Measurement Identity SDES Item</span>
This section defines the format of the Measurement Identity SDES
item. The SDES item is carried in the RTCP SDES packet. The packet
format for the RTCP SDES is defined in <a href="./rfc3550#section-6.5">Section 6.5 of [RFC3550]</a>.
Each SDES packet is composed of a header with fixed-length fields for
version, source count, packet type (PT), and length, followed by zero
or more SDES items. In the SDES packet, the PT field is set to SDES
(202).
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. APSI: Application-Specific Identifier SDES Item</span>
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APSI=10 | length |application-specific identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ....
+-+-+-+-+-+-+-+-+
The application-specific identifier is an additional identifier that
is useful in the context of a specific application, e.g., an MPEG-2
transport identifier [<a href="#ref-MPEG2" title=""Standard 13818-1, Information technology -- Generic coding of moving pictures and associated audio information: Systems"">MPEG2</a>]. This item MUST be ignored by
applications that are not configured to make use of it. The
identifier is variable length. Its length is described by the length
field. The value of the length field does not include the two-octet
SDES item header.
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Measurement Information XR Block</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Report Block Structure</span>
0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=14 | Reserved | block length = 7 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of stream source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | first sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended first sequence number of interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended last sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Interval) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Cumulative) - Seconds (bit 0-31) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Cumulative) - Fraction (bit 0-31) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Report Block Structure
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Definition of Fields in Measurement Information Report Block</span>
Block type (BT): 8 bits
A Measurement Information Block is identified by the constant 14.
Reserved: 8 bits
These bits are reserved. They MUST be set to zero by senders and
ignored by receivers.
Block Length: 16 bits
The length of this report block in 32-bit words minus one. For
the Measurement Information Block, the block length is equal to 7.
SSRC of source: 32 bits
As defined in <a href="./rfc3611#section-4.1">Section 4.1 of [RFC3611]</a>.
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
Reserved: 16 bits
These bits are reserved. They MUST be set to zero by senders and
ignored by receivers.
First sequence number: 16 bits
The RTP sequence number of the first received RTP packet of the
session, used to determine the number of packets contributing to
cumulative measurements.
Extended first sequence number of interval: 32 bits
The extended RTP sequence number of the first received RTP packet
of the current measurement interval. The extended sequence number
is expressed as the low 16-bit value containing the sequence
number received in an RTP data packet and the most significant
16-bit value containing the corresponding count of sequence number
cycles. For additional information on extended sequence numbers,
see the "extended highest sequence number received" definition in
<a href="./rfc3550#section-6.4.1">Section 6.4.1 of RFC 3550</a> and <a href="./rfc3550#appendix-A.1">Appendix A.1 of RFC 3550</a>.
Extended last sequence number: 32 bits
The extended RTP sequence number of the last received RTP packet
that contributed to this measurement. The extended sequence
number is expressed as the low 16-bit value containing the
sequence number received in an RTP data packet and the most
significant 16-bit value containing the corresponding count of
sequence number cycles. For additional information on extended
sequence numbers, see the "extended highest sequence number
received" definition in <a href="./rfc3550#section-6.4.1">Section 6.4.1 of RFC 3550</a> and <a href="./rfc3550#appendix-A.1">Appendix A.1
of RFC 3550</a>.
Measurement Duration (Interval): 32 bits
The duration, expressed in units of 1/65536 seconds, of the
reporting interval applicable to Interval reports that use this
Measurement Information Block. The value of this field can be
calculated by the receiver of the RTP media stream, for example,
based on received RTP media packets or using the RTCP method
described in [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>].
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
Measurement Duration (Cumulative): 64 bits
The duration of the reporting interval applicable to Cumulative
reports that use this Measurement Information Block. The value of
this field is represented using a 64-bit 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 unsigned fixed-point
number with the integer part in the first 32 bits and the
fractional part in the last 32 bits. It can be calculated by the
receiver of the RTP media stream, for example, based on received
RTP media packets or using the RTCP method described in [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
A new SDES item type for RTCP SDES and a new XR block type for RTCP
XR have been registered with IANA. For general guidelines on IANA
considerations, refer to [<a href="./rfc3550" title=""RTP: A Transport Protocol for Real-Time Applications"">RFC3550</a>] for RTCP SDES and [<a href="./rfc3611" title=""RTP Control Protocol Extended Reports (RTCP XR)"">RFC3611</a>] for
RTCP XR.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. New RTCP SDES Item Type Value</span>
This document adds the Measurement Identity SDES item to the IANA
"RTP SDES item types" registry as follows:
abbrev. name value
APSI Application-Specific Identifier 10
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. New RTCP XR Block Type Value</span>
This document assigns the block type value 14 in the IANA "RTCP XR
Block Type Registry" to the "Measurement Information Block".
<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="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
RTCP reports can contain sensitive information, including information
about the nature and duration of a session established between two or
more endpoints. Therefore, the use of security mechanisms with RTP,
as documented in <a href="./rfc3550#section-9">Section 9 of [RFC3550]</a>, applies.
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.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., Ed., Caceres, R., Ed., and A. Clark, Ed.,
"RTP Control Protocol Extended Reports (RTCP XR)",
<a href="./rfc3611">RFC 3611</a>, November 2003.
[<a id="ref-RFC5905">RFC5905</a>] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", <a href="./rfc5905">RFC 5905</a>, June 2010.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-MONARCH">MONARCH</a>] Wu, Q., Hunt, G., and P. Arden, "Monitoring Architectures
for RTP", Work in Progress, September 2012.
[<a id="ref-MPEG2">MPEG2</a>] ISO/IEC, "Standard 13818-1, Information technology --
Generic coding of moving pictures and associated audio
information: Systems", October 2007.
[<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.
<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="./rfc6776">RFC 6776</a> Measurement Identity and Duration October 2012</span>
Authors' Addresses
Alan Clark
Telchemy Incorporated
2905 Premiere Parkway, Suite 280
Duluth, GA 30097
United States
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 9]
</pre>
|
