idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-psi-decodability-00.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 5, 2013) is 3788 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: June 8, 2014 R. Even 6 Gesher Erove Ltd 7 Q. Wu, Ed. 8 R. Huang 9 Huawei 10 December 5, 2013 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-00 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 June 8, 2014. 45 Copyright Notice 47 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . 3 69 3. MPEG2 TS PSI Decodability Statistics Metrics Block . . . . . 3 70 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 71 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 7 72 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 7 73 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 79 7.1. Normative References . . . . . . . . . . . . . . . . . . 8 80 7.2. Informative References . . . . . . . . . . . . . . . . . 9 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 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 97 This memo is based on information consistency tests and resulting 98 indicators defined by ETSI [ETSI] and defines a new block type to 99 augment those defined in Freidman, et al. [RFC3611] for use with 100 MPEG2 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block 101 type supports reporting of the number of occurrences of each Program 102 Specific Information (PSI) indicator in the first and second 103 priorities that supplements information from PSI independent 104 Decodability Statistics Metrics Block [RFC6990]; third priority 105 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 144 ETSI TR 101290 [ETSI] generally defines metrics related to error 145 events while this document contains counts of those metrics defined 146 in [ETSI]. The block defined in this document reports MPEG2 TS PSI 147 decodability statistics metrics beyond the information carried in the 148 standard RTCP packet format and PSI independent Decodability Metrics 149 Block [RFC6990], which are measured at the receiving end of the RTP 150 stream. It contains counts of six metrics defined in ETSI TR 101290 151 [ETSI]. Information is reported about basic monitoring parameters 152 necessary to ensure that the TS can be decoded including: 154 o Program Association Table(PAT) errors 155 o PAT 2 errors 156 o Program Map Table(PMT) errors 157 o PMT 2 errors 158 o Packet Identifier(PID) errors 160 and continuous monitoring parameters necessary to ensure the 161 continuous decoding including: 163 o Cyclic Redundancy Check (CRC) errors 164 o Conditional Access Table (CAT) 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 Decodability Metrics Block has the 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=MTPD | Reserved | block length | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | SSRC of source | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | begin_seq | end_seq | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | PAT_error_count | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | PAT_error_2_count | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | PMT_error_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | PMT_error_2_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | PID_error_count | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | CRC_error_count | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | CAT_error_count | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 block type (BT): 8 bits 198 The MPEG2 TS PSI Decodability Metrics Block is identified by the 199 constant . 201 Reserved: 8 bits 203 These bits are reserved. They MUST be set to zero by senders 204 ignored by receivers (See [RFC6709] section 4.2). 206 block length: 16 bits 208 The constant 11, in accordance with the definition of this field 209 in Section 3 of RFC 3611. The block MUST be discarded if the 210 block length is set to a different value. 212 SSRC of source: 32 bits 214 As defined in Section 4.1 of RFC 3611. 216 begin_seq: 16 bits 218 As defined in Section 4.1 of RFC 3611. 220 end_seq: 16 bits 222 As defined in Section 4.1 of RFC 3611. 224 PAT_error_count: 32 bits 226 A count of the number of PAT errors that occurred in the above 227 sequence number interval. The program association table (PAT) is 228 the only packet with packet ID (PID) 0x 0000. A PAT error occurs 229 when it does not occur at least every 0.5s or the table has an ID 230 other than 0x 00, as defined in section 5.2.1 of [ETSI]. Every 231 program within the MPEG TS stream is listed in the PAT; if it is 232 missing, then no programs can be decoded. 234 The measured value is unsigned value. If the measurement is 235 unavailable, the value 0xFFFF MUST be reported. Note that 236 PAT_error_count and PAT_error_2_count MUST NOT be reported at the 237 same time in the same metric block. If PAT_error_count is 238 reported, PAT_error_2_count MUST be set to 0xFFFF. 240 PAT_error_2_count: 32 bits 242 A count of the number of PAT2 errors that occurred in the above 243 sequence number interval. A PAT2 error occurs when it does not 244 occur at least every 0.5s or the table has an ID other than 0x 00 245 or there is more than one table ID 0x 00 inside the packet with 246 the PAT PID, as defined in 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: 32 bits 256 A count of the number of PMT_errors that occurred in the above 257 sequence number interval. A PMT_error occurs when the program map 258 table (PMT) does not come up at least every 0.5s on the PID that 259 is referred to in the PAT, as defined in the section 5.2.1 of 260 [ETSI]. 262 The measured value is unsigned value. If the measurement is 263 unavailable, the value 0xFFFF MUST be reported. Note that 264 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 265 same time in the same metric block. If PMT_error_count is 266 reported, PMT_error_2_count MUST be set to 0xFFFF. 268 PMT_error_2_count: 32 bits 270 A count of the number of PMT2 errors that occurred in the above 271 sequence number interval. A PMT2_error occurs when the program 272 map table (PMT) does not come up at least every 0.5s on the PID 273 that is referred to in the PAT, as defined in the section 5.2.1 of 274 [ETSI]. 276 The measured value is unsigned value. If the measurement is 277 unavailable, the value 0xFFFF MUST be reported. Note that 278 PMT_error_count and PMT_error_2_count MUST NOT be reported at the 279 same time in the same metric block. If PMT_error_2_count is 280 reported, PMT_error_count MUST be set to 0xFFFF. 282 PID_error_count: 32 bits 283 A count of the number of PID_errors that occurred in the above 284 sequence number interval. A PID_error occurs when MPEG TS streams 285 are remultiplexed and any PID doesn't refer to an actual data 286 stream, as defined in the section 5.2.2 of [ETSI]. 288 CRC_error_count: 32 bits 290 A count of the number of CRC_errors that occurred in the above 291 sequence number interval. A CRC_error occurs if data corruption 292 occurred in any of the following tables -\u002D CAT, PAT, PMT, 293 Network Information Table(NIT), Event Information Table(EIT), 294 Bouquet Association Table(BAT), Service Description Table(SDT) or 295 Time Offset Table(TOT), as defined in the section 5.2.2 of [ETSI]. 297 CAT_error_count: 32 bits 299 A count of the number of CAT_errors that occurred in the above 300 sequence number interval. A CAT_error occurs when the table has 301 an ID other than 0x 01,as defined in the section 5.2.2 of [ETSI]. 303 4. SDP Signaling 305 RFC 3611 defines the use of SDP (Session Description Protocol) 306 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 307 MAY be used without prior signaling (See section 5 of RFC3611). 309 4.1. SDP rtcp-xr-attrib Attribute Extension 311 This session augments the SDP attribute "rtcp-xr" defined in 312 Section 5.1 of RFC 3611 by providing an additional value of "xr- 313 format" to signal the use of the report block defined in this 314 document. 316 xr-format =/ xr-tpd-block 318 xr-tpdd-block = "ts-psi-decodability" 320 4.2. Offer/Answer Usage 322 When SDP is used in offer-answer context, the SDP Offer/Answer usage 323 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 324 applies. For detailed usage of Offer/Answer for unilateral 325 parameter, refer to section 5.2 of [RFC3611]. 327 5. IANA Considerations 328 New report block types for RTCP XR are subject to IANA registration. 329 For general guidelines on IANA allocations for RTCP XR, refer to 330 Section 6.2 of RFC 3611. 332 5.1. New RTCP XR Block Type value 334 This document assigns the block type value MTPD in the IANA " RTP 335 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 336 the "MPEG2 Transport Stream PSI Decodability Statistics Metrics 337 Block". 339 [Note to RFC Editor: please replace MTPD with the IANA provided RTCP 340 XR block type for this block.] 342 5.2. New RTCP XR SDP Parameter 344 This document also registers a new parameter "ts-psi-decodability" in 345 the "RTP Control Protocol Extended Reports (RTCP XR) Session 346 Description Protocol (SDP) Parameters Registry". 348 5.3. Contact information for registrations 350 The contact information for the registrations is: 352 Qin Wu 353 sunseawq@huawei.com 354 101 Software Avenue, Yuhua District 355 Nanjing, JiangSu 210012 China 357 6. Security Considerations 359 This proposed RTCP XR report block introduces no new security 360 considerations beyond those described in RFC 3611. 362 7. References 364 7.1. Normative References 366 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 367 guidelines for DVB systems", Technical Report TR 101 290, 368 2001. 370 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 371 Requirement Levels", BCP 14, RFC 2119, March 1997. 373 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 374 Applications", RFC 3550, July 2003. 376 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 377 Protocol Extended Reports (RTCP XR)", RFC 3611, November 378 2003. 380 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 381 Description Protocol", RFC 4566, July 2006. 383 7.2. Informative References 385 [ISO-IEC.13818-1.2007] 386 International Organization for Standardization, 387 "Information technology - Generic coding of moving 388 pictures and associated audio information: Systems", ISO 389 International Standard 13818-1, October 2007. 391 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 392 Performance Metric Development", BCP 170, RFC 6390, 393 October 2011. 395 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 396 Considerations for Protocol Extensions", RFC 6709, 397 September 2012. 399 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 400 RTP Monitoring Framework", RFC 6792, November 2012. 402 [RFC6990] Wu, Q., "RTP Control Protocol (RTCP) Extended Report (XR) 403 Block for MPEG2 Transport Stream (TS) Program Specific 404 Information (PSI) Independent Decodability Statistics 405 Metrics reporting", RFC 6990, May 2013. 407 Authors' Addresses 409 Jiangang Tong 410 Shanghai Research Institure of China Telecom Corporation Limited 411 No.1835,South Pudong Road 412 Shanghai 200122 413 China 415 Email: tongjg@sttri.com.cn 416 Claire Bi (editor) 417 Shanghai Research Institure of China Telecom Corporation Limited 418 No.1835,South Pudong Road 419 Shanghai 200122 420 China 422 Email: bijy@sttri.com.cn 424 Roni Even 425 Gesher Erove Ltd 426 14 David Hamelech 427 Tel Aviv 64953 428 Israel 430 Email: ron.even.tlv@gmail.com 432 Qin Wu (editor) 433 Huawei 434 101 Software Avenue, Yuhua District 435 Nanjing, Jiangsu 210012 436 China 438 Email: bill.wu@huawei.com 440 Rachel Huang 441 Huawei 442 101 Software Avenue, Yuhua District 443 Nanjing, Jiangsu 210012 444 China 446 Email: rachel.huang@huawei.com