Debian Codegraph @

rfc6990.html

raw
1 <pre>Internet Engineering Task Force (IETF) R. Huang
2 Request for Comments: 6990 Q. Wu
3 Category: Standards Track Huawei
4 ISSN: 2070-1721 H. Asaeda
5 NICT
6 G. Zorn
7 Network Zen
8 August 2013
9
10
11 <span class="h1">RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2</span>
12 <span class="h1">Transport Stream (TS) Program Specific Information (PSI) Independent</span>
13 <span class="h1">Decodability Statistics Metrics Reporting</span>
14
15 Abstract
16
17 An MPEG-2 Transport Stream (TS) is a standard container format used
18 in the transmission and storage of multimedia data. Unicast/
19 multicast MPEG-2 TS over RTP is widely deployed in IPTV systems.
20 This document defines an RTP Control Protocol (RTCP) Extended Report
21 (XR) block that allows the reporting of MPEG-2 TS decodability
22 statistics metrics related to transmissions of MPEG-2 TS over RTP.
23 The metrics specified in the RTCP XR block are not dependent on
24 Program Specific Information (PSI) carried in MPEG-2 TS.
25
26 Status of This Memo
27
28 This is an Internet Standards Track document.
29
30 This document is a product of the Internet Engineering Task Force
31 (IETF). It represents the consensus of the IETF community. It has
32 received public review and has been approved for publication by the
33 Internet Engineering Steering Group (IESG). Further information on
34 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
35
36 Information about the current status of this document, any errata,
37 and how to provide feedback on it may be obtained at
38 <a href="http://www.rfc-editor.org/info/rfc6990">http://www.rfc-editor.org/info/rfc6990</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Huang, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-1.1">1.1</a>. MPEG-2 Transport Stream Decodability Metrics . . . . . . <a href="#page-3">3</a>
76 <a href="#section-1.2">1.2</a>. RTCP and RTCP Extended Reports . . . . . . . . . . . . . <a href="#page-3">3</a>
77 <a href="#section-1.3">1.3</a>. Performance Metrics Framework . . . . . . . . . . . . . . <a href="#page-3">3</a>
78 <a href="#section-1.4">1.4</a>. Applicability . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
79 <a href="#section-2">2</a>. Standards Language . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
80 3. MPEG-2 TS PSI-Independent Decodability Statistics Metrics
81 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
82 <a href="#section-4">4</a>. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
83 <a href="#section-4.1">4.1</a>. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . <a href="#page-8">8</a>
84 <a href="#section-4.2">4.2</a>. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
85 <a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
86 <a href="#section-5.1">5.1</a>. New RTCP XR Block Type Value . . . . . . . . . . . . . . <a href="#page-8">8</a>
87 <a href="#section-5.2">5.2</a>. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
88 <a href="#section-5.3">5.3</a>. Contact Information for Registrations . . . . . . . . . . <a href="#page-9">9</a>
89 <a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
90 <a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
91 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
92 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
93 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Huang, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. MPEG-2 Transport Stream Decodability Metrics</span>
116
117 The European Telecommunications Standards Institute (ETSI) has
118 defined a set of syntax and information consistency tests and
119 corresponding indicators [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>] that are recommended for the
120 monitoring of MPEG-2 Transport Streams [<a href="#ref-ISO-IEC.13818-1.2013">ISO-IEC.13818-1.2013</a>]. The
121 tests and corresponding indicators are grouped according to priority:
122
123 o First priority - Necessary for decodability (basic monitoring)
124
125 o Second priority - Recommended for continuous or periodic
126 monitoring
127
128 o Third priority - Recommended for application-dependent monitoring
129
130 This memo is based on information consistency tests and resulting
131 indicators defined by ETSI [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>] and defines a new block type to
132 augment those defined in [<a href="./rfc3611" title="&quot;RTP Control Protocol Extended Reports (RTCP XR)&quot;">RFC3611</a>] for use with MPEG-2 Transport
133 Stream (TS) [<a href="#ref-ISO-IEC.13818-1.2013">ISO-IEC.13818-1.2013</a>]. The new block type supports
134 reporting of the number of occurrences of each PSI-independent
135 indicator in the first and second priorities; third priority
136 indicators are not supported.
137
138 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. RTCP and RTCP Extended Reports</span>
139
140 The use of RTCP for reporting is defined in [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]. [<a href="./rfc3611" title="&quot;RTP Control Protocol Extended Reports (RTCP XR)&quot;">RFC3611</a>]
141 defined an extensible structure for reporting using an RTCP Extended
142 Report (XR). This document defines a new Extended Report block for
143 use with [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] and [<a href="./rfc3611" title="&quot;RTP Control Protocol Extended Reports (RTCP XR)&quot;">RFC3611</a>].
144
145 <span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Performance Metrics Framework</span>
146
147 "Guidelines for Considering New Performance Metric Development"
148 [<a href="./rfc6390" title="&quot;Guidelines for Considering New Performance Metric Development&quot;">RFC6390</a>] provides guidance on the definition and specification of
149 performance metrics. "Guidelines for Use of the RTP Monitoring
150 Framework" [<a href="./rfc6792" title="&quot;Guidelines for Use of the RTP Monitoring Framework&quot;">RFC6792</a>] provides guidance on the reporting block format
151 using RTCP XR. The new report block described in this memo is in
152 compliance with the monitoring architecture specified in [<a href="./rfc6792" title="&quot;Guidelines for Use of the RTP Monitoring Framework&quot;">RFC6792</a>]
153 and the performance metrics framework [<a href="./rfc6390" title="&quot;Guidelines for Considering New Performance Metric Development&quot;">RFC6390</a>].
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Huang, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
167
168
169 <span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a>. Applicability</span>
170
171 This block type allows a count of MPEG-2 Transport Stream quality
172 metrics that are measured in accordance with ETSI TR 101290 [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>] to
173 be reported by an endpoint. These metrics are useful for identifying
174 bitstream packetization and transport stream encoding problems that
175 may affect the user's perception of a video service delivered over
176 RTP.
177
178 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Standards Language</span>
179
180 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
181 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
182 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
183
184 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MPEG-2 TS PSI-Independent Decodability Statistics Metrics Block</span>
185
186 ETSI TR 101290 [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>] generally defines metrics related to error
187 events while this document contains counts of those metrics defined
188 in [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>]. The block defined in this document reports MPEG-2 TS PSI-
189 independent decodability statistics metrics beyond the information
190 carried in the standard RTCP packet format, which are measured at the
191 receiving end of the RTP stream. It contains counts of eight metrics
192 defined in ETSI TR 101290 [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>]. Information is reported about
193 basic monitoring parameters necessary to ensure that the TS can be
194 decoded, including:
195
196 o Transport Stream Synchronization Losses
197
198 o Sync byte errors
199
200 o Continuity count errors
201
202 and continuous monitoring parameters necessary to ensure the
203 continuous decoding, including:
204
205 o Transport errors
206
207 o Program Clock Reference (PCR) errors
208
209 o PCR repetition errors
210
211 o PCR discontinuity indicator errors
212
213 o PCR accuracy errors
214
215 o Presentation Time Stamp (PTS) errors
216
217
218
219
220 <span class="grey">Huang, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
223
224
225 The other parameters are ignored since they do not apply to all
226 MPEG-2 implementations. For further information on these parameters,
227 see [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>]. Note that when the report of this block spans across
228 more than one measurement interval [<a href="./rfc6776" title="&quot;Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block&quot;">RFC6776</a>], the count of the
229 metrics (e.g., Sync byte errors and PCR errors) defined in [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>] may
230 reflect a problem in the current or previous measurement interval.
231
232 The MPEG-2 TS PSI-Independent Decodability Statistics Metrics Block
233 has the following format:
234
235 0 1 2 3
236 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
237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
238 | BT=22 | Reserved | Block Length |
239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
240 | SSRC of Source |
241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
242 | begin_seq | end_seq |
243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
244 | TS_sync_loss_count |
245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
246 | Sync_byte_error_count |
247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
248 | Continuity_count_error_count |
249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
250 | Transport_error_count |
251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
252 | PCR_error_count |
253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
254 | PCR_repetition_error_count |
255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
256 | PCR_discontinuity_indicator_error_count |
257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
258 | PCR_accuracy_error_count |
259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
260 | PTS_error_count |
261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
262
263 Block Type (BT): 8 bits
264
265 The MPEG-2 TS PSI-Independent Decodability Statistics Metrics
266 Block is identified by the constant 22.
267
268
269 Reserved: 8 bits
270
271 These bits are reserved. They MUST be set to zero by senders and
272 ignored by receivers (see <a href="./rfc6709#section-4.2">[RFC6709] Section&nbsp;4.2</a>).
273
274
275
276 <span class="grey">Huang, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
279
280
281 Block Length: 16 bits
282
283 The constant 11, in accordance with the definition of this field
284 in <a href="./rfc3611#section-3">Section&nbsp;3 of RFC 3611</a>. The block MUST be discarded if the
285 block length is set to a different value.
286
287
288 Synchronization source (SSRC) of Source: 32 bits
289
290 As defined in <a href="./rfc3611#section-4.1">Section&nbsp;4.1 of RFC 3611</a>.
291
292
293 begin_seq: 16 bits
294
295 The RTP sequence number corresponding to the start of the
296 measurement period, as defined in <a href="./rfc3611#section-4.1">Section&nbsp;4.1 of RFC 3611</a>.
297
298
299 end_seq: 16 bits
300
301 The RTP sequence number corresponding to the end of the
302 measurement period, as defined in <a href="./rfc3611#section-4.1">Section&nbsp;4.1 of RFC 3611</a>.
303
304
305 TS_sync_loss_count: 32 bits
306
307 A count of the number of TS_sync_loss errors that occurred in the
308 above sequence number interval. A TS_sync_loss error occurs when
309 there are two or more consecutive incorrect sync bytes within the
310 MPEG-2 TS, as defined in Section 5.2.1 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
311
312
313 Sync_byte_error_count: 32 bits
314
315 A count of the number of Sync_byte_errors that occurred in the
316 above sequence number interval. A sync byte error occurs when the
317 sync byte is not equal to 0x47 in any TS packet contained in the
318 MPEG-2 TS, as defined in Section 5.2.1 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
319
320
321 Continuity_count_error_count: 32 bits
322
323 A count of the number of Continuity_count_errors that occurred in
324 the above sequence number interval. A Continuity_count_error
325 occurs when any of the following faults happen within the MPEG-2
326 TS -- incorrect packet order, a packet occurs more than twice, or
327 a packet is lost, as defined in Section 5.2.1 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
328
329
330
331
332 <span class="grey">Huang, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
335
336
337 Transport_error_count: 32 bits
338
339 A count of the number of Transport_errors that occurred in the
340 above sequence number interval. A Transport_error occurs when an
341 erroneous TS packet cannot be corrected within the MPEG-2 TS, as
342 defined in Section 5.2.2 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
343
344
345 PCR_error_count: 32 bits
346
347 A count of the number of PCR_errors that occurred in the above
348 sequence number interval. A PCR_error occurs if the primary clock
349 reference (PCR) is not seen for more than 100 ms within the MPEG-2
350 TS, as defined in Section 5.2.2 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>]. The time interval
351 between two consecutive PCR values should be no more than 40 ms.
352
353
354 PCR_repetition_error_count: 32 bits
355
356 A count of the number of PCR_repetition_errors that occurred in
357 the above sequence number interval. A PCR_repetition_error occurs
358 when the time interval between two consecutive PCR values is more
359 than 40 ms within the MPEG-2 TS, as defined in Section 5.2.2 of
360 [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
361
362
363 PCR_discontinuity_indicator_error_count: 32 bits
364
365 A count of the number of PCR_discontinuity_indicator_errors that
366 occurred in the above sequence number interval. A
367 PCR_discontinuity_indicator_error occurs if the time interval
368 between two consecutive PCR values is more than 100 ms within the
369 MPEG-2 TS, as defined in Section 5.2.2 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
370
371
372 PCR_accuracy_error_count: 32 bits
373
374 A count of the number of PCR_accuracy_errors that occurred in the
375 above sequence number interval. A PCR_accuracy_error occurs when
376 the PCR accuracy of the selected program is outside the range of
377 +/-500 ns within the MPEG-2 TS, as defined in Section 5.2.2 of
378 [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>].
379
380
381
382
383
384
385
386
387
388 <span class="grey">Huang, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
391
392
393 PTS_error_count: 32 bits
394
395 A count of the number of PTS_errors that occurred in the above
396 sequence number interval. A PTS_error occurs when the PTS
397 repetition is more than 700 ms within the MPEG-2 TS, as defined in
398 Section 5.2.2 of [<a href="#ref-ETSI" title="&quot;Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems&quot;">ETSI</a>]. Note that the PTS is contained in the
399 MPEG-2 TS and is used to aid the decoder in presenting the program
400 on time, at the correct speed, and synchronized.
401
402 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. SDP Signaling</span>
403
404 <a href="./rfc3611">RFC 3611</a> defines the use of the Session Description Protocol (SDP)
405 [<a href="./rfc4566" title="&quot;SDP: Session Description Protocol&quot;">RFC4566</a>] for signaling the use of RTCP XR blocks. However, XR
406 blocks MAY be used without prior signaling (see Section 5 of <a href="./rfc3611">RFC</a>
407 <a href="./rfc3611">3611</a>).
408
409 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. SDP rtcp-xr Attribute Extension</span>
410
411 This session augments the SDP attribute "rtcp-xr" defined in
412 <a href="./rfc3611#section-5.1">Section&nbsp;5.1 of RFC 3611</a> by providing an additional value of
413 "xr-format" to signal the use of the report block defined in this
414 document. The ABNF [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>] syntax is as follows.
415
416 xr-format =/ xr-tpid-block
417
418 xr-tpid-block = "ts-psi-indep-decodability"
419
420 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Offer/Answer Usage</span>
421
422 When SDP is used in Offer/Answer context, the SDP Offer/Answer usage
423 defined in [<a href="./rfc3611" title="&quot;RTP Control Protocol Extended Reports (RTCP XR)&quot;">RFC3611</a>] for unilateral "rtcp-xr" attribute parameters
424 applies. For detailed usage of Offer/Answer for unilateral
425 parameters, refer to <a href="./rfc3611#section-5.2">Section&nbsp;5.2 of [RFC3611]</a>.
426
427 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
428
429 New report block types for RTCP XR are subject to IANA registration.
430 For general guidelines on IANA allocations for RTCP XR, refer to
431 <a href="./rfc3611#section-6.2">Section&nbsp;6.2 of RFC 3611</a>.
432
433 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. New RTCP XR Block Type Value</span>
434
435 This document assigns the block type value 22 in the IANA "RTP
436 Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
437 the "MPEG-2 Transport Stream PSI-Independent Decodability Statistics
438 Metrics Block".
439
440
441
442
443
444 <span class="grey">Huang, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
447
448
449 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. New RTCP XR SDP Parameter</span>
450
451 This document also registers the new parameter "ts-psi-
452 indep-decodability" in the "RTP Control Protocol Extended Reports
453 (RTCP XR) Session Description Protocol (SDP) Parameters Registry".
454
455 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Contact Information for Registrations</span>
456
457 The contact information for registrations is:
458
459 Qin Wu ([email protected])
460 101 Software Avenue, Yuhua District
461 Nanjing, Jiangsu 210012
462 China
463
464 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
465
466 There might be some relationship between reported error counters and
467 contractual Service Level Agreements (SLAs); hence, an attack (e.g.,
468 RTP endpoints reporting false data, or an attacker in the path
469 modifying the data being reported) might deliberately corrupt these
470 error counters, resulting in financial implications for the network
471 operator (either as a result of unneeded performance metrics, or
472 penalty charges for SLA failure).
473
474 A solution to prevent such an attack is to apply an authentication
475 and integrity protection framework for the RTCP XR block. This can
476 be accomplished using the RTP profile that combines Secure RTP
477 [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>] and the Audio-Visual Profile with Feedback (AVPF) into
478 Secure AVPF (SAVPF) [<a href="./rfc5124" title="&quot;Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)&quot;">RFC5124</a>].
479
480 Besides this, the RTCP XR block in this document introduces no new
481 security considerations beyond those described in [<a href="./rfc3611" title="&quot;RTP Control Protocol Extended Reports (RTCP XR)&quot;">RFC3611</a>].
482
483 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
484
485 Thanks to Ray van Brandenburg, Claire Bi, Colin Perkins, Roni Even,
486 Dan Romascanu, Ali Begen, Alexey Melnikov, Bert Wijnen, Gonzalo
487 Camarillo, Benoit Claise, and Alan Clark for useful reviews and
488 suggestions.
489
490 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
491
492 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
493
494 [<a id="ref-ETSI">ETSI</a>] ETSI, "Digital Video Broadcasting (DVB); Measurement
495 guidelines for DVB systems", Technical Report TR 101 290,
496 2001.
497
498
499
500 <span class="grey">Huang, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
503
504
505 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
506 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
507
508 [<a id="ref-RFC3550">RFC3550</a>] Schulzrinne, H., Casner, S., Frederick, R., and V.
509 Jacobson, "RTP: A Transport Protocol for Real-Time
510 Applications", STD 64, <a href="./rfc3550">RFC 3550</a>, July 2003.
511
512 [<a id="ref-RFC3611">RFC3611</a>] Friedman, T., Caceres, R., and A. Clark, "RTP Control
513 Protocol Extended Reports (RTCP XR)", <a href="./rfc3611">RFC 3611</a>, November
514 2003.
515
516 [<a id="ref-RFC3711">RFC3711</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
517 Norrman, "The Secure Real-time Transport Protocol (SRTP)",
518 <a href="./rfc3711">RFC 3711</a>, March 2004.
519
520 [<a id="ref-RFC4566">RFC4566</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
521 Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.
522
523 [<a id="ref-RFC5124">RFC5124</a>] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
524 Real-time Transport Control Protocol (RTCP)-Based Feedback
525 (RTP/SAVPF)", <a href="./rfc5124">RFC 5124</a>, February 2008.
526
527 [<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
528 Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
529
530 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
531
532 [<a id="ref-ISO-IEC.13818-1.2013">ISO-IEC.13818-1.2013</a>]
533 International Organization for Standardization,
534 "Information technology - Generic coding of moving
535 pictures and associated audio information: Systems", ISO
536 International Standard 13818-1, May 2013.
537
538 [<a id="ref-RFC6390">RFC6390</a>] Clark, A. and B. Claise, "Guidelines for Considering New
539 Performance Metric Development", <a href="https://www.rfc-editor.org/bcp/bcp170">BCP 170</a>, <a href="./rfc6390">RFC 6390</a>,
540 October 2011.
541
542 [<a id="ref-RFC6709">RFC6709</a>] Carpenter, B., Aboba, B., and S. Cheshire, "Design
543 Considerations for Protocol Extensions", <a href="./rfc6709">RFC 6709</a>,
544 September 2012.
545
546 [<a id="ref-RFC6776">RFC6776</a>] Clark, A. and Q. Wu, "Measurement Identity and Information
547 Reporting Using a Source Description (SDES) Item and an
548 RTCP Extended Report (XR) Block", <a href="./rfc6776">RFC 6776</a>, October 2012.
549
550 [<a id="ref-RFC6792">RFC6792</a>] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
551 RTP Monitoring Framework", <a href="./rfc6792">RFC 6792</a>, November 2012.
552
553
554
555
556 <span class="grey">Huang, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6990">RFC 6990</a> RTCP XR TS Decodability August 2013</span>
559
560
561 Authors' Addresses
562
563 Rachel Huang
564 Huawei
565 101 Software Avenue, Yuhua District
566 Nanjing 210012
567 China
568
569 EMail: [email protected]
570
571
572 Qin Wu
573 Huawei
574 101 Software Avenue, Yuhua District
575 Nanjing, Jiangsu 210012
576 China
577
578 EMail: [email protected]
579
580
581 Hitoshi Asaeda
582 National Institute of Information and Communications Technology
583 4-2-1 Nukui-Kitamachi
584 Koganei, Tokyo 184-8795
585 Japan
586
587 EMail: [email protected]
588
589
590 Glen Zorn
591 Network Zen
592 227/358 Thanon Sanphawut
593 Bang Na, Bangkok 10260
594 Thailand
595
596 Phone: +66 (0) 8-1000-4155
597 EMail: [email protected]
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 Huang, et al. Standards Track [Page 11]
613 </pre>