idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 17, 2012) is 4141 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI' ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Huang 3 Internet-Draft Q. Wu 4 Intended status: Standards Track Huawei 5 Expires: June 20, 2013 H. Asaeda 6 NICT 7 G. Zorn, Ed. 8 Network Zen 9 December 17, 2012 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG 12 Transport Stream Decodability Statistics Metric reporting 13 draft-ietf-xrblock-rtcp-xr-decodability-03 15 Abstract 17 An MPEG Transport Stream (TS) is a standard container format used in 18 the transmission and storage of multimedia data. Unicast/Multicast/ 19 Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This 20 document defines an RTP Control Protocol (RTCP) Extended Report (XR) 21 Block that allows the reporting of MPEG Transport Stream decodability 22 statistics metrics related to transmissions of MPEG-TS over RTP. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on June 20, 2013. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3 60 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 61 1.3. Performance Metrics Framework . . . . . . . . . . . . . . . 3 62 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 65 3. MPEG Transport Stream Decodability Statistics Metric 66 Report Block . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 7 69 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 70 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 72 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 73 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 74 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 75 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 78 1. Introduction 80 1.1. MPEG Transport Stream Decodability Metrics 82 The European Telecommunications Standards Institute (ETSI) has 83 defined a set of syntax and information consistency tests and 84 corresponding indicators [ETSI] that are recommended for the 85 monitoring of MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The 86 tests and corresponding indicators are grouped according to priority: 88 o First priority - Necessary for de-codability (basic monitoring) 89 o Second priority - Recommended for continuous or periodic 90 monitoring 91 o Third priority - Recommended for application-dependant monitoring 93 This memo is based on information consistency tests and resulting 94 indicators defined by ETSI [ETSI] and defines a new block type to 95 augment those defined in Freidman, et al. [RFC3611] for use with 96 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type 97 supports reporting of the number of occurrences of each indicator in 98 the first and second priorities; third priority indicators are not 99 supported. 101 1.2. RTCP and RTCP XR Reports 103 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 104 defined an extensible structure for reporting using an RTCP Extended 105 Report (XR). This document defines a new Extended Report block for 106 use with [RFC3550] and [RFC3611]. 108 1.3. Performance Metrics Framework 110 The Performance Metrics Framework [RFC6390] provides guidance on the 111 definition and specification of performance metrics. The RTP 112 Monitoring Architectures [RFC6792] provides guideline for reporting 113 block format using RTCP XR. The new report block described in this 114 memo is in compliance with the monitoring architecture specified in 115 [RFC6792] and the Performance Metrics Framework [RFC6390]. 117 1.4. Applicability 119 These metrics are applicable to any type of RTP application that uses 120 the MPEG-TS standard format for multimedia data; for example, MPEG4 121 TS content over RTP. This new block type can be useful for measuring 122 content stream or TS quality by checking TS header information [ETSI] 123 and identifying the existence, and characterizing the severity, of 124 bitstream packetization problems which may affect users' perception 125 of a service delivered over RTP; it may also be useful for verifying 126 the continued correct operation of an existing system management 127 tool. 129 2. Terminology 131 2.1. Standards Language 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 135 document are to be interpreted as described in RFC 2119 [RFC2119]. 137 3. MPEG Transport Stream Decodability Statistics Metric Report Block 139 This block reports MPEG transport stream decodability statistics 140 metrics beyond the information carried in the standard RTCP packet 141 format, which are measured at the receiving end of the RTP stream. 142 It defines eight metrics based on ETSI TR 101 290. Information is 143 reported about basic monitoring parameters necessary to ensure that 144 the TS can be decoded including: 146 o Transport Stream Synchronization Losses 147 o Sync byte errors 148 o Continuity count errors 150 and continuous monitoring parameters including: 152 o Transport errors 153 o Program Clock Reference (PCR) errors 154 o PCR repetition errors 155 o PCR discontinuity indicator errors 156 o Presentation Time Stamp (PTS) errors 158 The other parameters are ignored since they do not apply to all MPEG 159 implementations. For further information on these parameters, see 160 [ETSI]. 162 The MPEG-TS Decodability Metrics Block has the following format: 164 0 1 2 3 165 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 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | BT=TSDM | Reserved | block length | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | SSRC of source | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | begin_seq | end_seq | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | Number of TSs | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | TS_sync_loss_count | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | Sync_byte_error_count | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | Continuity_count_error_count | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Transport_error_count | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | PCR_error_count | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | PCR_repetition_error_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | PCR_discontinuity_indicator_error_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | PTS_error_count | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 block type (BT): 8 bits 194 A TR 101 290 MPEG-TS decodability metrics report block is 195 identified by the constant . 197 Reserved: 8 bits 199 This field is reserved for future definition. In the absence of 200 such a definition, the bits in this field MUST be set to zero and 201 SHOULD be ignored by the receiver. 203 block length: 16 bits 205 The constant 11, in accordance with the definition of this field 206 in Section 3 of RFC 3611. The block MUST be discarded if the 207 block length is set to a different value. 209 SSRC of source: 32 bits 211 As defined in Section 4.1 of RFC 3611. 213 begin_seq: 16 bits 215 As defined in Section 4.1 of RFC 3611. 217 end_seq: 16 bits 219 As defined in Section 4.1 of RFC 3611. 221 Number of TSs: 32 bits 223 Number of TS in the above sequence number interval. 225 TS_sync_loss_count: 32 bits 227 Number of TS_sync_loss errors in the above sequence number 228 interval. It is calculated based on the occurrence of errors for 229 "TS_sync_loss"parameter defined in the table 5.2.1 of ETSI TR 101 230 290 (See section 5.5.1 of ETSI TR 101 290). 232 Sync_byte_error_count: 32 bits 234 Number of sync_byte_errors in the above sequence number interval. 235 It is calculated in the same way as TS_sync_loss_count, i.e.,based 236 on the occurrence of errors for "Sync_byte_error"parameter defined 237 in the table 5.2.1 of ETSI TR 101 290. 239 Continuity_count_error_count: 32 bits 241 Number of Continuity_count_errors in the above sequence number 242 interval. Simiarly, it is calculated based on the occurrence of 243 errors for "Continuity_count_error"parameter defined in the table 244 5.2.1 of ETSI TR 101 290. 246 Transport_error_count: 32 bits 248 Number of Transport_errors in the above sequence number interval. 249 Simiarly, it is calculated based on the occurrence of errors for 250 "Transport_error" parameter defined in the table 5.2.2 of ETSI TR 251 101 290. 253 PCR_error_count: 32 bits 255 Number of PCR_errors in the above sequence number interval. 256 Simiarly, it is calculated based on the occurrence of errors for 257 "PCR_error"parameter defined in the table 5.2.2 of ETSI TR 101 258 290. 260 PCR_repetition_error_count: 32 bits 262 Number of PCR_repetition_errors in the above sequence number 263 interval. Simiarly, it is calculated based on the occurrence of 264 errors for "PCR_repetition_error"parameter defined in the table 265 5.2.2 of ETSI TR 101 290. 267 PCR_discontinuity_indicator_error_count: 32 bits 269 Number of PCR_discontinuity_indicator_errors in the above sequence 270 number interval. Simiarly, it is calculated based on the 271 occurrence of errors for 272 "PCR_discontinuity_indicator_error"parameter defined in the table 273 5.2.2 of ETSI TR 101 290. 275 PTS_error_count: 32 bits 277 Number of PTS_errors in the above sequence number interval. 278 Simiarly, it is calculated based on the occurrence of errors for 279 "PTS_error"parameter defined in the table 5.2.2 of ETSI TR 101 280 290. 282 4. SDP Signaling 284 RFC 3611 defines the use of SDP (Session Description Protocol) 285 [RFC4566] for signaling the use of RTCP XR blocks. XR blocks MAY be 286 used without prior signaling. 288 4.1. SDP rtcp-xr-attrib Atrribute Extension 290 This session augments the SDP attribute "rtcp-xr" defined in Section 291 5.1 of RFC 3611 by providing an additional value of "xr-format" to 292 signal the use of the report block defined in this document. 294 xr-format =/ ts-decodability-metrics 296 ts-decodability-metrics = "ts-decodability-metrics" 298 4.2. Offer/Answer Usage 300 When SDP is used in offer-answer context, the SDP Offer/Answer usage 301 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 302 applies. For detailed usage in Offer/Answer for unilateral 303 parameter, refer to section 5.2 of [RFC3611]. 305 5. IANA Considerations 307 New report block types for RTCP XR are subject to IANA registration. 308 For general guidelines on IANA allocations for RTCP XR, refer to 309 Section 6.2 ofRFC 3611. 311 This document assigns one new block type value in the RTCP XR Block 312 Type Registry: 314 Name: TSDM 315 Long Name: TR 101 290 MPEG Transport Stream Decodability Metrics 316 Value 317 Reference: Section 3 319 This document also registers one SDP [RFC4566] parameters for the 320 "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: 322 * "ts-decodability-metrics" 324 The contact information for the registrations is: 326 Qin Wu 327 sunseawq@huawei.com 328 101 Software Avenue, Yuhua District 329 Nanjing, JiangSu 210012 China 331 6. Security Considerations 333 This proposed RTCP XR report block introduces no new security 334 considerations beyond those described in RFC 3611. 336 7. Acknowledgements 338 Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin and Dan 339 Romascanufor useful review and suggestions. 341 8. References 342 8.1. Normative References 344 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 345 guidelines for DVB systems", Technical Report TR 101 290, 346 2001. 348 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 349 Requirement Levels", BCP 14, RFC 2119, March 1997. 351 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 352 Applications", RFC 3550, July 2003. 354 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 355 Protocol Extended Reports (RTCP XR)", RFC 3611, 356 November 2003. 358 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 359 Description Protocol", RFC 4566, July 2006. 361 8.2. Informative References 363 [ISO-IEC.13818-1.2007] 364 International Organization for Standardization, 365 "Information technology - Generic coding of moving 366 pictures and associated audio information: Systems", 367 ISO International Standard 13818-1, October 2007. 369 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 370 Performance Metric Development", BCP 170, RFC 6390, 371 October 2011. 373 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 374 RTP Monitoring Framework", RFC 6792, November 2012. 376 Authors' Addresses 378 Rachel Huang 379 Huawei 380 101 Software Avenue, Yuhua District 381 Nanjing 210012 382 China 384 Email: rachel.huang@huawei.com 385 Qin Wu 386 Huawei 387 101 Software Avenue, Yuhua District 388 Nanjing, Jiangsu 210012 389 China 391 Email: bill.wu@huawei.com 393 Hitoshi Asaeda 394 National Institute of Information and Communications Technology 395 4-2-1 Nukui-Kitamachi 396 Koganei, Tokyo 184-8795 397 Japan 399 Email: asaeda@nict.go.jp 401 Glen Zorn (editor) 402 Network Zen 403 227/358 Thanon Sanphawut 404 Bang Na, Bangkok 10260 405 Thailand 407 Phone: +66 (0) 909-201060 408 Email: glenzorn@gmail.com