idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-10.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 (March 21, 2013) is 4054 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: September 22, 2013 H. Asaeda 6 NICT 7 G. Zorn 8 Network Zen 9 March 21, 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-10 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 decodability statistics metrics 23 related to transmissions of MPEG2 TS over RTP. The metrics specified 24 in the RTCP XR Block are not dependent on Program specific 25 information carried in MPEG TS. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 22, 2013. 44 Copyright Notice 46 Copyright (c) 2013 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 3 63 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 64 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 65 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 66 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 68 3. MPEG2 TS PSI Independent Decodability Statistics Metrics 69 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 71 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7 72 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 73 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 74 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 75 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 76 5.3. Contact information for registrations . . . . . . . . . . 8 77 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 78 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 79 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 80 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 81 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 84 1. Introduction 86 1.1. MPEG2 Transport Stream Decodability Metrics 88 The European Telecommunications Standards Institute (ETSI) has 89 defined a set of syntax and information consistency tests and 90 corresponding indicators [ETSI] that are recommended for the 91 monitoring of MPEG2 Transport Streams [ISO-IEC.13818-1.2007]. The 92 tests and corresponding indicators are grouped according to priority: 94 o First priority - Necessary for decodability (basic monitoring) 95 o Second priority - Recommended for continuous or periodic 96 monitoring 97 o Third priority - Recommended for application-dependent monitoring 99 This memo is based on information consistency tests and resulting 100 indicators defined by ETSI [ETSI] and defines a new block type to 101 augment those defined in Freidman, et al. [RFC3611] for use with 102 MPEG2 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block 103 type supports reporting of the number of occurrences of each Program 104 Specific Information (PSI) Independent indicator in the first and 105 second priorities; third priority indicators are not supported. 107 1.2. RTCP and RTCP XR Reports 109 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 110 defined an extensible structure for reporting using an RTCP Extended 111 Report (XR). This document defines a new Extended Report block for 112 use with [RFC3550] and [RFC3611]. 114 1.3. Performance Metrics Framework 116 The Performance Metrics Framework [RFC6390] provides guidance on the 117 definition and specification of performance metrics. The RTP 118 Monitoring Architectures [RFC6792] provides guideline for reporting 119 block format using RTCP XR. The new report block described in this 120 memo is in compliance with the monitoring architecture specified in 121 [RFC6792] and the Performance Metrics Framework [RFC6390]. 123 1.4. Applicability 125 These metrics are applicable to any type of RTP application that uses 126 the MPEG2 TS standard format for multimedia data; for example, MPEG4 127 over MPEG2 TS over RTP. This new block type can be useful for 128 measuring content stream or TS quality by checking TS header 129 information [ETSI] and identifying the existence, and characterizing 130 the severity, of bitstream packetization problems which may affect 131 users' perception of a service delivered over RTP; it may also be 132 useful for verifying the continued correct operation of an existing 133 system management tool. 135 2. Terminology 137 2.1. Standards Language 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 141 document are to be interpreted as described in RFC 2119 [RFC2119]. 143 3. MPEG2 TS PSI Independent Decodability Statistics Metrics Block 145 This block reports MPEG2 TS PSI Independent decodability statistics 146 metrics beyond the information carried in the standard RTCP packet 147 format, which are measured at the receiving end of the RTP stream. 148 It describes eight metrics specified in [ETSI]. Information is 149 reported about basic monitoring parameters necessary to ensure that 150 the TS can be decoded including: 152 o Transport Stream Synchronization Losses 153 o Sync byte errors 154 o Continuity count errors 156 and continuous monitoring parameters necessary to ensure the 157 continuous decoding including: 159 o Transport errors 160 o Program Clock Reference (PCR) errors 161 o PCR repetition errors 162 o PCR discontinuity indicator errors 163 o PCR accuracy errors 164 o Presentation Time Stamp (PTS) errors 166 The other parameters are ignored since they do not apply to all MPEG2 167 implementations. For further information on these parameters, see 168 [ETSI]. 170 The MPEG2 TS PSI Independent Decodability Metrics Block has the 171 following format: 173 0 1 2 3 174 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 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 | BT=MTPID | Reserved | block length | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | SSRC of source | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | begin_seq | end_seq | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | TS_sync_loss_count | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Sync_byte_error_count | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | Continuity_count_error_count | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | Transport_error_count | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | PCR_error_count | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 | PCR_repetition_error_count | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | PCR_discontinuity_indicator_error_count | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | PCR_accuracy_error_count | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 | PTS_error_count | 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 block type (BT): 8 bits 203 The MPEG2 TS PSI Independent Decodability Metrics Block is 204 identified by the constant . 206 Reserved: 8 bits 208 These bits are reserved. They MUST be set to zero by senders 209 ignored by receivers (See [RFC6709] section 4.2). 211 block length: 16 bits 213 The constant 11, in accordance with the definition of this field 214 in Section 3 of RFC 3611. The block MUST be discarded if the 215 block length is set to a different value. 217 SSRC of source: 32 bits 219 As defined in Section 4.1 of RFC 3611. 221 begin_seq: 16 bits 223 As defined in Section 4.1 of RFC 3611. 225 end_seq: 16 bits 227 As defined in Section 4.1 of RFC 3611. 229 TS_sync_loss_count: 32 bits 231 Number of TS_sync_loss errors in the above sequence number 232 interval. It is calculated based on the occurrence of errors for 233 "TS_sync_loss"parameter defined in the section 5.2.1 of 234 [ETSI](Also see section 5.5.1 of [ETSI]). 236 Sync_byte_error_count: 32 bits 238 Number of sync_byte_errors in the above sequence number interval. 239 It is calculated in the same way as TS_sync_loss_count, i.e.,based 240 on the occurrence of errors for "Sync_byte_error"parameter defined 241 in the section 5.2.1 of [ETSI]. 243 Continuity_count_error_count: 32 bits 245 Number of Continuity_count_errors in the above sequence number 246 interval. Similarly, it is calculated based on the occurrence of 247 errors for "Continuity_count_error" parameter defined in the 248 section 5.2.1 of [ETSI]. 250 Transport_error_count: 32 bits 252 Number of Transport_errors in the above sequence number interval. 253 Similarly, it is calculated based on the occurrence of errors for 254 "Transport_error" parameter defined in the section 5.2.2 of 255 [ETSI]. 257 PCR_error_count: 32 bits 259 Number of PCR_errors in the above sequence number interval. 260 Similarly, it is calculated based on the occurrence of errors for 261 "PCR_error" parameter defined in the section 5.2.2 of [ETSI]. 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]. 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]. 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]. 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]. 290 4. SDP Signaling 292 RFC 3611 defines the use of SDP (Session Description Protocol) 293 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 294 MAY be used without prior signaling (See section 5 of RFC3611). 296 4.1. SDP rtcp-xr-attrib Attribute Extension 298 This session augments the SDP attribute "rtcp-xr" defined in Section 299 5.1 of RFC 3611 by providing an additional value of "xr-format" to 300 signal the use of the report block defined in this document. 302 xr-format =/ xr-tpid-block 304 xr-tpid-block = "ts-psi-indep-decodability" 306 4.2. Offer/Answer Usage 308 When SDP is used in offer-answer context, the SDP Offer/Answer usage 309 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 310 applies. For detailed usage of Offer/Answer for unilateral 311 parameter, refer to section 5.2 of [RFC3611]. 313 5. IANA Considerations 315 New report block types for RTCP XR are subject to IANA registration. 316 For general guidelines on IANA allocations for RTCP XR, refer to 317 Section 6.2 of RFC 3611. 319 5.1. New RTCP XR Block Type value 321 This document assigns the block type value MTPID in the IANA " RTP 322 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 323 the "MPEG2 Transport Stream PSI Independent Decodability Statistics 324 Metrics Block". 326 [Note to RFC Editor: please replace MPITD with the IANA provided RTCP 327 XR block type for this block.] 329 5.2. New RTCP XR SDP Parameter 331 This document also registers a new parameter "ts-psi-indep- 332 decodability" in the "RTP Control Protocol Extended Reports (RTCP XR) 333 Session Description Protocol (SDP) Parameters Registry". 335 5.3. Contact information for registrations 337 The contact information for the registrations is: 339 Qin Wu 340 sunseawq@huawei.com 341 101 Software Avenue, Yuhua District 342 Nanjing, JiangSu 210012 China 344 6. Security Considerations 346 This proposed RTCP XR report block introduces no new security 347 considerations beyond those described in RFC 3611. 349 7. Acknowledgements 351 Thanks to Ray van Brandenburg, Claire Bi, Colin Perkin, Roni Even, 352 Dan Romascanu and Ali Begen for useful review and suggestions. 354 8. References 356 8.1. Normative References 358 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 359 guidelines for DVB systems", Technical Report TR 101 290, 360 2001. 362 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 363 Requirement Levels", BCP 14, RFC 2119, March 1997. 365 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 366 Applications", RFC 3550, July 2003. 368 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 369 Protocol Extended Reports (RTCP XR)", RFC 3611, 370 November 2003. 372 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 373 Description Protocol", RFC 4566, July 2006. 375 8.2. Informative References 377 [ISO-IEC.13818-1.2007] 378 International Organization for Standardization, 379 "Information technology - Generic coding of moving 380 pictures and associated audio information: Systems", 381 ISO International Standard 13818-1, October 2007. 383 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 384 Performance Metric Development", BCP 170, RFC 6390, 385 October 2011. 387 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 388 Considerations for Protocol Extensions", RFC 6709, 389 September 2012. 391 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 392 RTP Monitoring Framework", RFC 6792, November 2012. 394 Authors' Addresses 396 Rachel Huang 397 Huawei 398 101 Software Avenue, Yuhua District 399 Nanjing 210012 400 China 402 Email: rachel.huang@huawei.com 404 Qin Wu 405 Huawei 406 101 Software Avenue, Yuhua District 407 Nanjing, Jiangsu 210012 408 China 410 Email: bill.wu@huawei.com 412 Hitoshi Asaeda 413 National Institute of Information and Communications Technology 414 4-2-1 Nukui-Kitamachi 415 Koganei, Tokyo 184-8795 416 Japan 418 Email: asaeda@nict.go.jp 420 Glen Zorn 421 Network Zen 422 227/358 Thanon Sanphawut 423 Bang Na, Bangkok 10260 424 Thailand 426 Phone: +66 (0) 909-201060 427 Email: glenzorn@gmail.com