idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-psi-decodability-04.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 (June 5, 2014) is 3584 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 J. Tong 3 Internet-Draft C. Bi, Ed. 4 Intended status: Standards Track China Telecom 5 Expires: December 7, 2014 R. Even 6 Gesher Erove Ltd 7 Q. Wu, Ed. 8 R. Huang 9 Huawei 10 June 5, 2014 12 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 13 Transport Stream (TS) Program Specific Information (PSI) Decodability 14 Statistics Metrics reporting 15 draft-ietf-xrblock-rtcp-xr-psi-decodability-04 17 Abstract 19 An MPEG2 Transport Stream (TS) is a standard container format used in 20 the transmission and storage of multimedia data. Unicast/Multicast 21 MPEG2 TS over RTP is widely deployed in IPTV systems. This document 22 defines an RTP Control Protocol (RTCP) Extended Report (XR) Block 23 that allows the reporting of MPEG2 TS decodability statistics metrics 24 related to transmissions of MPEG2 TS over RTP. The metrics specified 25 in the RTCP XR Block are related to Program specific information 26 carried in MPEG TS. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on December 7, 2014. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 2 64 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . 3 65 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 66 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2.1. Standards Language . . . . . . . . . . . . . . . . . . . 4 69 3. MPEG2 TS PSI Decodability Statistics Metrics Block . . . . . 4 70 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 71 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 8 72 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 8 73 4.3. Usage Outside of Offer/Answer . . . . . . . . . . . . . . 8 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 75 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . 8 76 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 77 5.3. Contact information for registrations . . . . . . . . . . 9 78 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 79 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 80 7.1. Normative References . . . . . . . . . . . . . . . . . . 9 81 7.2. Informative References . . . . . . . . . . . . . . . . . 10 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 [RFC3611] for use with MPEG2 Transport 102 Stream (TS) [ISO-IEC.13818-1.2007]. The new block type supports 103 reporting of the number of occurrences of each Program Specific 104 Information (PSI) indicator in the first and second priorities that 105 supplements information from PSI independent Decodability Statistics 106 Metrics Block [RFC6990]; third priority indicators are not supported. 108 1.2. RTCP and RTCP XR Reports 110 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 111 defined an extensible structure for reporting using an RTCP Extended 112 Report (XR). This document defines a new Extended Report block for 113 use with [RFC3550] and [RFC3611]. 115 1.3. Performance Metrics Framework 117 The Performance Metrics Framework [RFC6390] provides guidance on the 118 definition and specification of performance metrics. The RTP 119 Monitoring Architectures [RFC6792] provides guideline for reporting 120 block format using RTCP XR. The new report block described in this 121 memo is in compliance with the monitoring architecture specified in 122 [RFC6792] and the Performance Metrics Framework [RFC6390]. 124 1.4. Applicability 126 These metrics are applicable to any type of RTP application that uses 127 the MPEG2 TS standard format for multimedia data; for example, MPEG4 128 over MPEG2 TS over RTP. This new block type can be useful for 129 measuring content stream or TS quality by checking TS header 130 information [ETSI] and identifying the existence, and characterizing 131 the severity, of bitstream packetization problems which may affect 132 users' perception of a service delivered over RTP; it may also be 133 useful for verifying the continued correct operation of an existing 134 system management tool. 136 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 Decodability Statistics Metrics Block 145 ETSI TR 101290 [ETSI] generally defines metrics related to error 146 events while this document contains counts of those metrics defined 147 in [ETSI]. The block defined in this document reports MPEG2 TS PSI 148 decodability statistics metrics beyond the information carried in the 149 standard RTCP packet format and PSI independent Decodability Metrics 150 Block [RFC6990], which are measured at the receiving end of the RTP 151 stream. It contains counts of six metrics defined in ETSI TR 101290 152 [ETSI]. Information is reported about basic monitoring parameters 153 necessary to ensure that the TS can be decoded including: 155 o Program Association Table(PAT) errors 156 o PAT 2 errors 157 o Program Map Table(PMT) errors 158 o PMT 2 errors 159 o Packet Identifier(PID) errors 161 and continuous monitoring parameters necessary to ensure the 162 continuous decoding including: 164 o Cyclic Redundancy Check (CRC) errors 165 o Conditional Access Table (CAT) errors 167 In these parameters,scrambling may be considered. The other 168 parameters are ignored since they do not apply to all MPEG2 169 implementations. For further detailed information on these 170 parameters, see [ETSI]. 172 The MPEG2 TS PSI Decodability Metrics Block has the following format: 174 0 1 2 3 175 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 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | BT=MTPD | Reserved | block length | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | SSRC of source | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | begin_seq | end_seq | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | PAT_error_count | PAT_error_2_count | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | PMT_error_count | PMT_error_2_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | PID_error_count | CRC_error_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | CAT_error_count | Reserved | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 block type (BT): 8 bits 194 The MPEG2 TS PSI Decodability Metrics Block is identified by the 195 constant . 197 Reserved: 8 bits 199 These bits are reserved. They MUST be set to zero by senders 200 ignored by receivers (See [RFC6709] section 4.2). 202 block length: 16 bits 204 The constant 6, in accordance with the definition of this field in 205 Section 3 of RFC 3611. The block MUST be discarded if the block 206 length is set to a different value. 208 SSRC of source: 32 bits 210 As defined in Section 4.1 of RFC 3611. 212 begin_seq: 16 bits 214 As defined in Section 4.1 of RFC 3611. 216 end_seq: 16 bits 218 As defined in Section 4.1 of RFC 3611. 220 PAT_error_count: 16 bits 221 A count of the number of PAT errors that occurred in the above 222 sequence number interval. The program association table (PAT) is 223 the only packet with packet ID (PID) 0x 0000. A PAT error occurs 224 when: (1) a packet with PID 0x0000 does not occur at least every 225 0.5 seconds, or (2) a packet with PID 0x0000 does not contain a 226 table_id 0x00 (i.e., a PAT), or (3)Scrambling_control_field in the 227 TS packet header is not 00 for a packet with PID 0x0000. See 228 section 5.2.1 of [ETSI]. Every program within the MPEG TS stream 229 is listed in the PAT; if it is missing, then no programs can be 230 decoded. 232 The measured value is unsigned value. If the measurement is 233 unavailable, the value 0xFFFF MUST be reported. Note that 234 PAT_error_count and PAT_error_2_count MUST NOT be reported at the 235 same time in the same metric block. If PAT_error_count is 236 reported, PAT_error_2_count MUST be set to 0xFFFF. 238 PAT_error_2_count: 16 bits 240 A count of the number of PAT2 errors that occurred in the above 241 sequence number interval. A PAT2 error occurs when: (1) a packet 242 with PID 0x0000 containing table_id 0x00 does not occur at least 243 every 0.5 seconds,or (2) a packet with PID 0x0000 contains one 244 table with table_id other than 0x00, or (3) 245 Scrambling_control_field in the TS packet header is not 00 for a 246 packet with PID 0x0000. See section 5.2.1 of [ETSI]. 248 The measured value is unsigned value. If the measurement is 249 unavailable, the value 0xFFFF MUST be reported. Note that 250 PAT_error_count and PAT_error_2_count MUST NOT be reported at the 251 same time in the same metric block. If PAT_error_2_count is 252 reported, PAT_error_count MUST be set to 0xFFFF. 254 PMT_error_count: 16 bits 256 A count of the number of PMT_errors that occurred in the above 257 sequence number interval. A PMT_error occurs when: (1) a packet 258 containing one table with table_id 0x02(i.e.,a PMT) does not occur 259 at least every 0.5s on the PID that is referred to in the PAT, 260 or(2) Scrambling_control_field in the TS packet header is not 00 261 for all packets with PID containing one table with table_id 0x02 262 (i.e. a PMT). See the section 5.2.1 of [ETSI]. 264 The measured value is unsigned value. If the measurement is 265 unavailable, the value 0xFFFF MUST be reported. Note that 266 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 267 same time in the same metric block. If PMT_error_count is 268 reported, PMT_error_2_count MUST be set to 0xFFFF. 270 PMT_error_2_count: 16 bits 272 A count of the number of PMT2 errors that occurred in the above 273 sequence number interval. A PMT2_error occurs when: (1) a packet 274 containing table_id 0x02(i.e.,a PMT) does not occur at least every 275 0.5s on each program_map_PID which is referred to in the PAT, or 276 (2) Scrambling_control_field in the TS packet header is not 00 for 277 all packets containing one table with table_id 0x02 (i.e. a PMT) 278 on each program_map_PID which is referred to in the PAT. See 279 section 5.2.1 of [ETSI]. 281 The measured value is unsigned value. If the measurement is 282 unavailable, the value 0xFFFF MUST be reported. Note that 283 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 284 same time in the same metric block. If PMT_error_2_count is 285 reported, PMT_error_count MUST be set to 0xFFFF. 287 PID_error_count: 16 bits 289 A count of the number of PID_errors that occurred in the above 290 sequence number interval. A PID_error occurs when MPEG TS streams 291 are remultiplexed and any PID doesn't refer to an actual data 292 stream, as defined in the section 5.2.1 of [ETSI]. 294 The measured value is unsigned value. If the measurement is 295 unavailable, the value 0xFFFF MUST be reported. 297 CRC_error_count: 16 bits 299 A count of the number of CRC_errors that occurred in the above 300 sequence number interval. A CRC_error occurs if data corruption 301 occurred in any of the following tables -- CAT, PAT, PMT, Network 302 Information Table (NIT), Event Information Table (EIT), Bouquet 303 Association Table (BAT), Service Description Table (SDT) or Time 304 Offset Table (TOT), as defined in the section 5.2.2 of [ETSI]. 306 The measured value is unsigned value. If the measurement is 307 unavailable, the value 0xFFFF MUST be reported. 309 CAT_error_count: 16 bits 311 A count of the number of CAT_errors that occurred in the above 312 sequence number interval. A CAT_error occurs when: (1) a packet 313 with PID 0x0001 contains one table with table_id other than 314 0x01(i.e.,not a CAT), or (2) A packet does not contain one table 315 with table_id = 0x01 (i.e. a CAT) when scrambling is employed 316 ((i.e., scrambling_control field is set as a value other than 317 00)). See the section 5.2.2 of [ETSI]. 319 The measured value is unsigned value. If the measurement is 320 unavailable, the value 0xFFFF MUST be reported. 322 Reserved: 16 bits 324 These bits are reserved. They MUST be set to zero by senders 325 ignored by receivers (See [RFC6709] section 4.2). 327 4. SDP Signaling 329 RFC 3611 defines the use of SDP (Session Description Protocol) 330 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 331 MAY be used without prior signaling (See section 5 of RFC3611). 333 4.1. SDP rtcp-xr-attrib Attribute Extension 335 This session augments the SDP attribute "rtcp-xr" defined in 336 Section 5.1 of RFC 3611 by providing an additional value of "xr- 337 format" to signal the use of the report block defined in this 338 document. 340 xr-format =/ xr-tpd-block 342 xr-tpd-block = "ts-psi-decodability" 344 4.2. Offer/Answer Usage 346 When SDP is used in offer-answer context, the SDP Offer/Answer usage 347 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 348 applies. For detailed usage of Offer/Answer for unilateral 349 parameter, refer to section 5.2 of [RFC3611]. 351 4.3. Usage Outside of Offer/Answer 353 For usage outside of Offer/Answer,refer to section 5.3 of [RFC3611]. 355 5. IANA Considerations 357 New report block types for RTCP XR are subject to IANA registration. 358 For general guidelines on IANA allocations for RTCP XR, refer to 359 Section 6.2 of RFC 3611. 361 5.1. New RTCP XR Block Type value 363 This document assigns the block type value MTPD in the IANA " RTP 364 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 365 the "MPEG2 Transport Stream PSI Decodability Statistics Metrics 366 Block". 368 [Note to RFC Editor: please replace MTPD with the IANA provided RTCP 369 XR block type for this block.] 371 5.2. New RTCP XR SDP Parameter 373 This document also registers a new parameter "ts-psi-decodability" in 374 the "RTP Control Protocol Extended Reports (RTCP XR) Session 375 Description Protocol (SDP) Parameters Registry". 377 5.3. Contact information for registrations 379 The contact information for the registrations is: 381 RAI Area Directors 383 6. Security Considerations 385 This proposed RTCP XR report block introduces no new security 386 considerations beyond those described in RFC 3611. 388 7. References 390 7.1. Normative References 392 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 393 guidelines for DVB systems", Technical Report TR 101 290, 394 2001. 396 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 397 Requirement Levels", BCP 14, RFC 2119, March 1997. 399 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 400 Applications", RFC 3550, July 2003. 402 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 403 Protocol Extended Reports (RTCP XR)", RFC 3611, November 404 2003. 406 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 407 Description Protocol", RFC 4566, July 2006. 409 7.2. Informative References 411 [ISO-IEC.13818-1.2007] 412 International Organization for Standardization, 413 "Information technology - Generic coding of moving 414 pictures and associated audio information: Systems", ISO 415 International Standard 13818-1, October 2007. 417 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 418 Performance Metric Development", BCP 170, RFC 6390, 419 October 2011. 421 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 422 Considerations for Protocol Extensions", RFC 6709, 423 September 2012. 425 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 426 RTP Monitoring Framework", RFC 6792, November 2012. 428 [RFC6990] Wu, Q., "RTP Control Protocol (RTCP) Extended Report (XR) 429 Block for MPEG2 Transport Stream (TS) Program Specific 430 Information (PSI) Independent Decodability Statistics 431 Metrics reporting", RFC 6990, May 2013. 433 Authors' Addresses 435 Jiangang Tong 436 Shanghai Research Institure of China Telecom Corporation Limited 437 No.1835,South Pudong Road 438 Shanghai 200122 439 China 441 Email: tongjg@sttri.com.cn 443 Claire Bi (editor) 444 Shanghai Research Institure of China Telecom Corporation Limited 445 No.1835,South Pudong Road 446 Shanghai 200122 447 China 449 Email: bijy@sttri.com.cn 450 Roni Even 451 Gesher Erove Ltd 452 14 David Hamelech 453 Tel Aviv 64953 454 Israel 456 Email: ron.even.tlv@gmail.com 458 Qin Wu (editor) 459 Huawei 460 101 Software Avenue, Yuhua District 461 Nanjing, Jiangsu 210012 462 China 464 Email: bill.wu@huawei.com 466 Rachel Huang 467 Huawei 468 101 Software Avenue, Yuhua District 469 Nanjing, Jiangsu 210012 470 China 472 Email: rachel.huang@huawei.com