idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-psi-decodability-02.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 (April 23, 2014) is 3657 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: October 25, 2014 R. Even 6 Gesher Erove Ltd 7 Q. Wu, Ed. 8 R. Huang 9 Huawei 10 April 23, 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-02 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 October 25, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 3 64 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 65 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 66 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 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 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 74 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 75 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 76 5.3. Contact information for registrations . . . . . . . . . . 9 77 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 78 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 80 7.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 [RFC3611] for use with MPEG2 Transport 101 Stream (TS) [ISO-IEC.13818-1.2007]. The new block type supports 102 reporting of the number of occurrences of each Program Specific 103 Information (PSI) indicator in the first and second priorities that 104 supplements information from PSI independent Decodability Statistics 105 Metrics Block [RFC6990]; 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 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 The other parameters are ignored since they do not apply to all MPEG2 168 implementations. For further information on these parameters, see 169 [ETSI]. 171 The MPEG2 TS PSI Decodability Metrics Block has the 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=MTPD | Reserved | block length | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | SSRC of source | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | begin_seq | end_seq | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | PAT_error_count | PAT_error_2_count | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | PMT_error_count | PMT_error_2_count | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | PID_error_count | CRC_error_count | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | CAT_error_count | Reserved | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 block type (BT): 8 bits 193 The MPEG2 TS PSI Decodability Metrics Block is identified by the 194 constant . 196 Reserved: 8 bits 198 These bits are reserved. They MUST be set to zero by senders 199 ignored by receivers (See [RFC6709] section 4.2). 201 block length: 16 bits 203 The constant 6, in accordance with the definition of this field in 204 Section 3 of RFC 3611. The block MUST be discarded if the block 205 length is set to a different value. 207 SSRC of source: 32 bits 209 As defined in Section 4.1 of RFC 3611. 211 begin_seq: 16 bits 213 As defined in Section 4.1 of RFC 3611. 215 end_seq: 16 bits 217 As defined in Section 4.1 of RFC 3611. 219 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 it does not occur at least every 0.5s or the table has an ID 225 other than 0x 00, as defined in section 5.2.1 of [ETSI]. Every 226 program within the MPEG TS stream is listed in the PAT; if it is 227 missing, then no programs can be decoded. 229 The measured value is unsigned value. If the measurement is 230 unavailable, the value 0xFFFF MUST be reported. Note that 231 PAT_error_count and PAT_error_2_count MUST NOT be reported at the 232 same time in the same metric block. If PAT_error_count is 233 reported, PAT_error_2_count MUST be set to 0xFFFF. 235 PAT_error_2_count: 16 bits 237 A count of the number of PAT2 errors that occurred in the above 238 sequence number interval. A PAT2 error occurs when it does not 239 occur at least every 0.5s or the table has an ID other than 0x 00 240 or there is more than one table ID 0x 00 inside the packet with 241 the PAT PID, as defined in section 5.2.1 of [ETSI]. 243 The measured value is unsigned value. If the measurement is 244 unavailable, the value 0xFFFF MUST be reported. Note that 245 PAT_error_count and PAT_error_2_count MUST NOT be reported at the 246 same time in the same metric block. If PAT_error_2_count is 247 reported, PAT_error_count MUST be set to 0xFFFF. 249 PMT_error_count: 16 bits 251 A count of the number of PMT_errors that occurred in the above 252 sequence number interval. A PMT_error occurs when the program map 253 table (PMT) does not come up at least every 0.5s on the PID that 254 is referred to in the PAT, as defined in the section 5.2.1 of 255 [ETSI]. 257 The measured value is unsigned value. If the measurement is 258 unavailable, the value 0xFFFF MUST be reported. Note that 259 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 260 same time in the same metric block. If PMT_error_count is 261 reported, PMT_error_2_count MUST be set to 0xFFFF. 263 PMT_error_2_count: 16 bits 265 A count of the number of PMT2 errors that occurred in the above 266 sequence number interval. A PMT2_error occurs when the program 267 map table (PMT) does not come up at least every 0.5s on the PID 268 that is referred to in the PAT, as defined in the section 5.2.1 of 269 [ETSI]. 271 The measured value is unsigned value. If the measurement is 272 unavailable, the value 0xFFFF MUST be reported. Note that 273 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 274 same time in the same metric block. If PMT_error_2_count is 275 reported, PMT_error_count MUST be set to 0xFFFF. 277 PID_error_count: 16 bits 279 A count of the number of PID_errors that occurred in the above 280 sequence number interval. A PID_error occurs when MPEG TS streams 281 are remultiplexed and any PID doesn't refer to an actual data 282 stream, as defined in the section 5.2.2 of [ETSI]. 284 The measured value is unsigned value. If the measurement is 285 unavailable, the value 0xFFFF MUST be reported. 287 CRC_error_count: 16 bits 289 A count of the number of CRC_errors that occurred in the above 290 sequence number interval. A CRC_error occurs if data corruption 291 occurred in any of the following tables -- CAT, PAT, PMT, Network 292 Information Table (NIT), Event Information Table (EIT), Bouquet 293 Association Table (BAT), Service Description Table (SDT) or Time 294 Offset Table (TOT), as defined in the section 5.2.2 of [ETSI]. 296 The measured value is unsigned value. If the measurement is 297 unavailable, the value 0xFFFF MUST be reported. 299 CAT_error_count: 16 bits 301 A count of the number of CAT_errors that occurred in the above 302 sequence number interval. A CAT_error occurs when the table has 303 an ID other than 0x 01,as defined in the section 5.2.2 of [ETSI]. 305 The measured value is unsigned value. If the measurement is 306 unavailable, the value 0xFFFF MUST be reported. 308 Reserved: 16 bits 310 These bits are reserved. They MUST be set to zero by senders 311 ignored by receivers (See [RFC6709] section 4.2). 313 4. SDP Signaling 315 RFC 3611 defines the use of SDP (Session Description Protocol) 316 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 317 MAY be used without prior signaling (See section 5 of RFC3611). 319 4.1. SDP rtcp-xr-attrib Attribute Extension 321 This session augments the SDP attribute "rtcp-xr" defined in Section 322 5.1 of RFC 3611 by providing an additional value of "xr-format" to 323 signal the use of the report block defined in this document. 325 xr-format =/ xr-tpd-block 327 xr-tpd-block = "ts-psi-decodability" 329 4.2. Offer/Answer Usage 331 When SDP is used in offer-answer context, the SDP Offer/Answer usage 332 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 333 applies. For detailed usage of Offer/Answer for unilateral 334 parameter, refer to section 5.2 of [RFC3611]. 336 5. IANA Considerations 338 New report block types for RTCP XR are subject to IANA registration. 339 For general guidelines on IANA allocations for RTCP XR, refer to 340 Section 6.2 of RFC 3611. 342 5.1. New RTCP XR Block Type value 344 This document assigns the block type value MTPD in the IANA " RTP 345 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 346 the "MPEG2 Transport Stream PSI Decodability Statistics Metrics 347 Block". 349 [Note to RFC Editor: please replace MTPD with the IANA provided RTCP 350 XR block type for this block.] 352 5.2. New RTCP XR SDP Parameter 354 This document also registers a new parameter "ts-psi-decodability" in 355 the "RTP Control Protocol Extended Reports (RTCP XR) Session 356 Description Protocol (SDP) Parameters Registry". 358 5.3. Contact information for registrations 360 The contact information for the registrations is: 362 Qin Wu 363 sunseawq@huawei.com 364 101 Software Avenue, Yuhua District 365 Nanjing, JiangSu 210012 China 367 6. Security Considerations 369 This proposed RTCP XR report block introduces no new security 370 considerations beyond those described in RFC 3611. 372 7. References 374 7.1. Normative References 376 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 377 guidelines for DVB systems", Technical Report TR 101 290, 378 2001. 380 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 381 Requirement Levels", BCP 14, RFC 2119, March 1997. 383 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 384 Applications", RFC 3550, July 2003. 386 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 387 Protocol Extended Reports (RTCP XR)", RFC 3611, 388 November 2003. 390 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 391 Description Protocol", RFC 4566, July 2006. 393 7.2. Informative References 395 [ISO-IEC.13818-1.2007] 396 International Organization for Standardization, 397 "Information technology - Generic coding of moving 398 pictures and associated audio information: Systems", 399 ISO International Standard 13818-1, October 2007. 401 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 402 Performance Metric Development", BCP 170, RFC 6390, 403 October 2011. 405 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 406 Considerations for Protocol Extensions", RFC 6709, 407 September 2012. 409 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 410 RTP Monitoring Framework", RFC 6792, November 2012. 412 [RFC6990] Wu, Q., "RTP Control Protocol (RTCP) Extended Report (XR) 413 Block for MPEG2 Transport Stream (TS) Program Specific 414 Information (PSI) Independent Decodability Statistics 415 Metrics reporting", RFC 6990, May 2013. 417 Authors' Addresses 419 Jiangang Tong 420 Shanghai Research Institure of China Telecom Corporation Limited 421 No.1835,South Pudong Road 422 Shanghai 200122 423 China 425 Email: tongjg@sttri.com.cn 427 Claire Bi (editor) 428 Shanghai Research Institure of China Telecom Corporation Limited 429 No.1835,South Pudong Road 430 Shanghai 200122 431 China 433 Email: bijy@sttri.com.cn 435 Roni Even 436 Gesher Erove Ltd 437 14 David Hamelech 438 Tel Aviv 64953 439 Israel 441 Email: ron.even.tlv@gmail.com 442 Qin Wu (editor) 443 Huawei 444 101 Software Avenue, Yuhua District 445 Nanjing, Jiangsu 210012 446 China 448 Email: bill.wu@huawei.com 450 Rachel Huang 451 Huawei 452 101 Software Avenue, Yuhua District 453 Nanjing, Jiangsu 210012 454 China 456 Email: rachel.huang@huawei.com