idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-09.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 (February 25, 2013) is 4071 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: August 29, 2013 H. Asaeda 6 NICT 7 G. Zorn 8 Network Zen 9 February 25, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 12 Transport Stream (TS) Program Specific Information (PSI) Independent 13 Decodability Statistics Metrics reporting 14 draft-ietf-xrblock-rtcp-xr-decodability-09 16 Abstract 18 An MPEG2 Transport Stream (TS) is a standard container format used in 19 the transmission and storage of multimedia data. Unicast/Multicast 20 MPEG2 TS over RTP is widely deployed in IPTV systems. This document 21 defines an RTP Control Protocol (RTCP) Extended Report (XR) Block 22 that allows the reporting of MPEG2 TS Program Specific Information 23 (PSI) Independent decodability statistics metrics related to 24 transmissions of MPEG2 TS over RTP. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on August 29, 2013. 43 Copyright Notice 45 Copyright (c) 2013 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 3 62 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 63 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 64 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 67 3. MPEG2 TS PSI Independent Decodability Statistics Metrics 68 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 70 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7 71 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 72 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 73 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 74 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 75 5.3. Contact information for registrations . . . . . . . . . . 8 76 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 77 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 78 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 80 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 83 1. Introduction 85 1.1. MPEG2 Transport Stream Decodability Metrics 87 The European Telecommunications Standards Institute (ETSI) has 88 defined a set of syntax and information consistency tests and 89 corresponding indicators [ETSI] that are recommended for the 90 monitoring of MPEG2 Transport Streams [ISO-IEC.13818-1.2007]. The 91 tests and corresponding indicators are grouped according to priority: 93 o First priority - Necessary for decodability (basic monitoring) 94 o Second priority - Recommended for continuous or periodic 95 monitoring 96 o Third priority - Recommended for application-dependent monitoring 98 This memo is based on information consistency tests and resulting 99 indicators defined by ETSI [ETSI] and defines a new block type to 100 augment those defined in Freidman, et al. [RFC3611] for use with 101 MPEG2 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block 102 type supports reporting of the number of occurrences of each Program 103 Specific Information (PSI) Independent indicator in the first and 104 second priorities; third priority indicators are not supported. 106 1.2. RTCP and RTCP XR Reports 108 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 109 defined an extensible structure for reporting using an RTCP Extended 110 Report (XR). This document defines a new Extended Report block for 111 use with [RFC3550] and [RFC3611]. 113 1.3. Performance Metrics Framework 115 The Performance Metrics Framework [RFC6390] provides guidance on the 116 definition and specification of performance metrics. The RTP 117 Monitoring Architectures [RFC6792] provides guideline for reporting 118 block format using RTCP XR. The new report block described in this 119 memo is in compliance with the monitoring architecture specified in 120 [RFC6792] and the Performance Metrics Framework [RFC6390]. 122 1.4. Applicability 124 These metrics are applicable to any type of RTP application that uses 125 the MPEG2 TS standard format for multimedia data; for example, MPEG4 126 over MPEG2 TS over RTP. This new block type can be useful for 127 measuring content stream or TS quality by checking TS header 128 information [ETSI] and identifying the existence, and characterizing 129 the severity, of bitstream packetization problems which may affect 130 users' perception of a service delivered over RTP; it may also be 131 useful for verifying the continued correct operation of an existing 132 system management tool. 134 2. Terminology 136 2.1. Standards Language 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [RFC2119]. 142 3. MPEG2 TS PSI Independent Decodability Statistics Metrics Block 144 This block reports MPEG2 TS PSI Independent decodability statistics 145 metrics beyond the information carried in the standard RTCP packet 146 format, which are measured at the receiving end of the RTP stream. 147 It describes eight metrics specified in ETSI TR 101 290. Information 148 is reported about basic monitoring parameters necessary to ensure 149 that the TS can be decoded including: 151 o Transport Stream Synchronization Losses 152 o Sync byte errors 153 o Continuity count errors 155 and continuous monitoring parameters necessary to ensure the 156 continuous decoding including: 158 o Transport errors 159 o Program Clock Reference (PCR) errors 160 o PCR repetition errors 161 o PCR discontinuity indicator errors 162 o PCR accuracy errors 163 o Presentation Time Stamp (PTS) errors 165 The other parameters are ignored since they do not apply to all MPEG2 166 implementations. For further information on these parameters, see 167 [ETSI]. 169 The MPEG2 TS PSI Independent Decodability Metrics Block has the 170 following format: 172 0 1 2 3 173 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 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | BT=MTPID | Reserved | block length | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | SSRC of source | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | begin_seq | end_seq | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | TS_sync_loss_count | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | Sync_byte_error_count | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Continuity_count_error_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | Transport_error_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | PCR_error_count | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | PCR_repetition_error_count | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | PCR_discontinuity_indicator_error_count | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | PCR_accuracy_error_count | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | PTS_error_count | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 block type (BT): 8 bits 202 The MPEG2 TS PSI Independent Decodability Metrics Block is 203 identified by the constant . 205 Reserved: 8 bits 207 These bits are reserved. They MUST be set to zero by senders 208 ignored by receivers (See [RFC6709] section 4.2). 210 block length: 16 bits 212 The constant 11, in accordance with the definition of this field 213 in Section 3 of RFC 3611. The block MUST be discarded if the 214 block length is set to a different value. 216 SSRC of source: 32 bits 218 As defined in Section 4.1 of RFC 3611. 220 begin_seq: 16 bits 222 As defined in Section 4.1 of RFC 3611. 224 end_seq: 16 bits 226 As defined in Section 4.1 of RFC 3611. 228 TS_sync_loss_count: 32 bits 230 Number of TS_sync_loss errors in the above sequence number 231 interval. It is calculated based on the occurrence of errors for 232 "TS_sync_loss"parameter defined in the section 5.2.1 of ETSI TR 233 101 290 (See section 5.5.1 of ETSI TR 101 290). 235 Sync_byte_error_count: 32 bits 237 Number of sync_byte_errors in the above sequence number interval. 238 It is calculated in the same way as TS_sync_loss_count, i.e.,based 239 on the occurrence of errors for "Sync_byte_error"parameter defined 240 in the section 5.2.1 of ETSI TR 101 290. 242 Continuity_count_error_count: 32 bits 244 Number of Continuity_count_errors in the above sequence number 245 interval. Similarly, it is calculated based on the occurrence of 246 errors for "Continuity_count_error" parameter defined in the 247 section 5.2.1 of ETSI TR 101 290. 249 Transport_error_count: 32 bits 251 Number of Transport_errors in the above sequence number interval. 252 Similarly, it is calculated based on the occurrence of errors for 253 "Transport_error" parameter defined in the section 5.2.2 of ETSI 254 TR 101 290. 256 PCR_error_count: 32 bits 258 Number of PCR_errors in the above sequence number interval. 259 Similarly, it is calculated based on the occurrence of errors for 260 "PCR_error" parameter defined in the section 5.2.2 of ETSI TR 101 261 290. 263 PCR_repetition_error_count: 32 bits 265 Number of PCR_repetition_errors in the above sequence number 266 interval. Similarly, it is calculated based on the occurrence of 267 errors for "PCR_repetition_error" parameter defined in the section 268 5.2.2 of ETSI TR 101 290. 270 PCR_discontinuity_indicator_error_count: 32 bits 272 Number of PCR_discontinuity_indicator_errors in the above sequence 273 number interval. Similarly, it is calculated based on the 274 occurrence of errors for "PCR_discontinuity_indicator_error" 275 parameter defined in the section 5.2.2 of ETSI TR 101 290. 277 PCR_error_count: 32 bits 279 Number of PCR_accuracy_errors in the above sequence number 280 interval. Similarly, it is calculated based on the occurrence of 281 errors for "PCR_accuracy_error" parameter defined in the section 282 5.2.2 of ETSI TR 101 290. 284 PTS_error_count: 32 bits 286 Number of PTS_errors in the above sequence number interval. 287 Similarly, it is calculated based on the occurrence of errors for 288 "PTS_error" parameter defined in the section 5.2.2 of ETSI TR 101 289 290. 291 4. SDP Signaling 293 RFC 3611 defines the use of SDP (Session Description Protocol) 294 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 295 MAY be used without prior signaling (See section 5 of RFC3611). 297 4.1. SDP rtcp-xr-attrib Attribute Extension 299 This session augments the SDP attribute "rtcp-xr" defined in Section 300 5.1 of RFC 3611 by providing an additional value of "xr-format" to 301 signal the use of the report block defined in this document. 303 xr-format =/ xr-tpid-block 305 xr-tpid-block = "ts-psi-indep-decodability" 307 4.2. Offer/Answer Usage 309 When SDP is used in offer-answer context, the SDP Offer/Answer usage 310 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 311 applies. For detailed usage of Offer/Answer for unilateral 312 parameter, refer to section 5.2 of [RFC3611]. 314 5. IANA Considerations 316 New report block types for RTCP XR are subject to IANA registration. 317 For general guidelines on IANA allocations for RTCP XR, refer to 318 Section 6.2 of RFC 3611. 320 5.1. New RTCP XR Block Type value 322 This document assigns the block type value MTPID in the IANA " RTP 323 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 324 the "MPEG2 Transport Stream PSI Independent Decodability Statistics 325 Metrics Block". 327 [Note to RFC Editor: please replace MPITD with the IANA provided RTCP 328 XR block type for this block.] 330 5.2. New RTCP XR SDP Parameter 332 This document also registers a new parameter "ts-psi-indep- 333 decodability" in the "RTP Control Protocol Extended Reports (RTCP XR) 334 Session Description Protocol (SDP) Parameters Registry". 336 5.3. Contact information for registrations 338 The contact information for the registrations is: 340 Qin Wu 341 sunseawq@huawei.com 342 101 Software Avenue, Yuhua District 343 Nanjing, JiangSu 210012 China 345 6. Security Considerations 347 This proposed RTCP XR report block introduces no new security 348 considerations beyond those described in RFC 3611. 350 7. Acknowledgements 352 Thanks to Ray van Brandenburg, Claire Bi, Colin Perkin, Roni Even, 353 Dan Romascanu and Ali Begen for useful review and suggestions. 355 8. References 357 8.1. Normative References 359 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 360 guidelines for DVB systems", Technical Report TR 101 290, 361 2001. 363 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 364 Requirement Levels", BCP 14, RFC 2119, March 1997. 366 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 367 Applications", RFC 3550, July 2003. 369 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 370 Protocol Extended Reports (RTCP XR)", RFC 3611, 371 November 2003. 373 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 374 Description Protocol", RFC 4566, July 2006. 376 8.2. Informative References 378 [ISO-IEC.13818-1.2007] 379 International Organization for Standardization, 380 "Information technology - Generic coding of moving 381 pictures and associated audio information: Systems", 382 ISO International Standard 13818-1, October 2007. 384 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 385 Performance Metric Development", BCP 170, RFC 6390, 386 October 2011. 388 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 389 Considerations for Protocol Extensions", RFC 6709, 390 September 2012. 392 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 393 RTP Monitoring Framework", RFC 6792, November 2012. 395 Authors' Addresses 397 Rachel Huang 398 Huawei 399 101 Software Avenue, Yuhua District 400 Nanjing 210012 401 China 403 Email: rachel.huang@huawei.com 405 Qin Wu 406 Huawei 407 101 Software Avenue, Yuhua District 408 Nanjing, Jiangsu 210012 409 China 411 Email: bill.wu@huawei.com 413 Hitoshi Asaeda 414 National Institute of Information and Communications Technology 415 4-2-1 Nukui-Kitamachi 416 Koganei, Tokyo 184-8795 417 Japan 419 Email: asaeda@nict.go.jp 421 Glen Zorn 422 Network Zen 423 227/358 Thanon Sanphawut 424 Bang Na, Bangkok 10260 425 Thailand 427 Phone: +66 (0) 909-201060 428 Email: glenzorn@gmail.com