idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-11.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 7, 2013) is 4009 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: October 9, 2013 H. Asaeda 6 NICT 7 G. Zorn 8 Network Zen 9 April 7, 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-11 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 October 9, 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 . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 8 76 5.3. Contact information for registrations . . . . . . . . . . 8 77 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 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 [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) Independent indicator in the first and second 105 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 This block type allows a counts of MPEG Transport Stream quality 126 metrics that are measured in accordance with ETSI TR 101290 [ETSI] to 127 be reported by an endpoint. These metrics are useful for identifying 128 bitstream packetization and transport stream encoding problems that 129 may affect the user's perception of a video service delivered over 130 RTP. 132 2. Terminology 134 2.1. Standards Language 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 138 document are to be interpreted as described in RFC 2119 [RFC2119]. 140 3. MPEG2 TS PSI Independent Decodability Statistics Metrics Block 142 ETSI TR 101290 [ETSI] generally defines metrics related to error 143 events while this document contains counts of those metrics defined 144 in [ETSI]. The block defined in this document reports MPEG2 TS PSI 145 Independent decodability statistics metrics beyond the information 146 carried in the standard RTCP packet format, which are measured at the 147 receiving end of the RTP stream. It contains counts of eight metrics 148 defined in ETSI TR 101290 [ETSI]. Information is reported about 149 basic monitoring parameters necessary to ensure that the TS can be 150 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]. Note that when the report of this block spans across more 169 than one measurement intervals [RFC6776], the count of the metrics 170 (e.g., Sync byte errors, PCR errors )defined in [ETSI] may reflect a 171 problem in the current or previous measurement interval. 173 The MPEG2 TS PSI Independent Decodability Metrics Block has the 174 following format: 176 0 1 2 3 177 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 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | BT=MTPID | Reserved | block length | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | SSRC of source | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | begin_seq | end_seq | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | TS_sync_loss_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | Sync_byte_error_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Continuity_count_error_count | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | Transport_error_count | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | PCR_error_count | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | PCR_repetition_error_count | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | PCR_discontinuity_indicator_error_count | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | PCR_accuracy_error_count | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | PTS_error_count | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 block type (BT): 8 bits 206 The MPEG2 TS PSI Independent Decodability Metrics Block is 207 identified by the constant . 209 Reserved: 8 bits 211 These bits are reserved. They MUST be set to zero by senders and 212 ignored by receivers (See [RFC6709] section 4.2). 214 block length: 16 bits 216 The constant 11, in accordance with the definition of this field 217 in Section 3 of RFC 3611. The block MUST be discarded if the 218 block length is set to a different value. 220 SSRC of source: 32 bits 222 As defined in Section 4.1 of RFC 3611. 224 begin_seq: 16 bits 226 The RTP sequence number corresponding to the start of the 227 measurement period, as defined in Section 4.1 of RFC 3611. 229 end_seq: 16 bits 231 The RTP sequence number corresponding to the end of the 232 measurement period, as defined in Section 4.1 of RFC 3611. 234 TS_sync_loss_count: 32 bits 236 A count of the number of TS_sync_loss errors that occurred in the 237 above sequence number interval. A TS_sync_loss error occurs when 238 there are two or more consecutive incorrect sync bytes within the 239 MPEG TS stream, as defined in section 5.2.1 of [ETSI]. 241 Sync_byte_error_count: 32 bits 243 A count of the number of Sync_byte_errors that occurred in the 244 above sequence number interval. A sync byte error occurs when the 245 sync byte is not equal to 0x47 in any TS packet contained in the 246 MPEG TS stream, as defined in section 5.2.1 of [ETSI]. 248 Continuity_count_error_count: 32 bits 250 A count of the number of Continuity_count_errors that occurred in 251 the above sequence number interval. A Continuity_count_error 252 occurs when any of the following faults happen within the MPEG TS 253 stream - incorrect packet order, a packet occurs more than twice 254 or a packet is lost,as defined in the section 5.2.1 of [ETSI]. 256 Transport_error_count: 32 bits 258 A count of the number of Transport_errors that occurred in the 259 above sequence number interval. A Transport_error occurs when 260 erroneous TS packet can not be corrected within the MPEG TS 261 stream. as defined in the section 5.2.2 of [ETSI]. 263 PCR_error_count: 32 bits 265 A count of the number of PCR_errors that occurred in the above 266 sequence number interval. A PCR_error occurs if the primary clock 267 reference (PCR) is not seen for more than 100ms within the MPEG TS 268 stream, as defined in the section 5.2.2 of [ETSI]. The time 269 interval between two consecutive PCR values should be no more than 270 40ms. 272 PCR_repetition_error_count: 32 bits 274 A count of the number of PCR_repetition_errors that occurred in 275 the above sequence number interval. A PCR_repeition_error occurs 276 when the time interval between two consecutive PCR values is more 277 than 40ms within the MPEG TS stream,as defined in the section 278 5.2.2 of [ETSI]. 280 PCR_discontinuity_indicator_error_count: 32 bits 282 A count of the number of PCR_discontinuity_indicator_errors that 283 occurred in the above sequence number interval. A 284 PCR_discontinuity_indicator_error occurs if the time interval 285 between two consecutive PCR values is more than 100ms within the 286 MPEG TS stream, as defined in the section 5.2.2 of [ETSI]. 288 PCR_accuracy_error_count: 32 bits 290 A count of the Number of PCR_accuracy_errors that occurred in the 291 above sequence number interval. A PCR_accuracy_error occurs when 292 the PCR accuracy of the selected program is outside the range of 293 +/-500ns within the MPEG TS stream,as defined in the section 5.2.2 294 of [ETSI]. 296 PTS_error_count: 32 bits 298 A count of the number of PTS_errors that occurred in the above 299 sequence number interval. A PTS_error occurs when the PTS 300 repetition is more than 700ms within the MPEG TS stream, as 301 defined in the section 5.2.2 of[ETSI]. Note that the PTS is 302 contained in the MPEG-2 TS stream and is used to aid the decoder 303 in presenting the program on time, at the correct speed and 304 synchronized. 306 4. SDP Signaling 308 RFC 3611 defines the use of SDP (Session Description Protocol) 309 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 310 MAY be used without prior signaling (See section 5 of RFC3611). 312 4.1. SDP rtcp-xr-attrib Attribute Extension 314 This session augments the SDP attribute "rtcp-xr" defined in Section 315 5.1 of RFC 3611 by providing an additional value of "xr-format" to 316 signal the use of the report block defined in this document. 318 xr-format =/ xr-tpid-block 320 xr-tpid-block = "ts-psi-indep-decodability" 322 4.2. Offer/Answer Usage 324 When SDP is used in offer-answer context, the SDP Offer/Answer usage 325 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 326 applies. For detailed usage of Offer/Answer for unilateral 327 parameter, refer to section 5.2 of [RFC3611]. 329 5. IANA Considerations 331 New report block types for RTCP XR are subject to IANA registration. 332 For general guidelines on IANA allocations for RTCP XR, refer to 333 Section 6.2 of RFC 3611. 335 5.1. New RTCP XR Block Type value 337 This document assigns the block type value MTPID in the IANA " RTP 338 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 339 the "MPEG2 Transport Stream PSI Independent Decodability Statistics 340 Metrics Block". 342 [Note to RFC Editor: please replace MPITD with the IANA provided RTCP 343 XR block type for this block.] 345 5.2. New RTCP XR SDP Parameter 347 This document also registers a new parameter "ts-psi-indep- 348 decodability" in the "RTP Control Protocol Extended Reports (RTCP XR) 349 Session Description Protocol (SDP) Parameters Registry". 351 5.3. Contact information for registrations 353 The contact information for the registrations is: 355 Qin Wu 356 sunseawq@huawei.com 357 101 Software Avenue, Yuhua District 358 Nanjing, JiangSu 210012 China 360 6. Security Considerations 362 This proposed RTCP XR report block introduces no new security 363 considerations beyond those described in RFC 3611. 365 7. Acknowledgements 367 Thanks to Ray van Brandenburg, Claire Bi, Colin Perkin, Roni Even, 368 Dan Romascanu, Ali Begen and Alan Clark for useful review and 369 suggestions. 371 8. References 373 8.1. Normative References 375 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 376 guidelines for DVB systems", Technical Report TR 101 290, 377 2001. 379 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 380 Requirement Levels", BCP 14, RFC 2119, March 1997. 382 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 383 Applications", RFC 3550, July 2003. 385 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 386 Protocol Extended Reports (RTCP XR)", RFC 3611, 387 November 2003. 389 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 390 Description Protocol", RFC 4566, July 2006. 392 8.2. Informative References 394 [ISO-IEC.13818-1.2007] 395 International Organization for Standardization, 396 "Information technology - Generic coding of moving 397 pictures and associated audio information: Systems", 398 ISO International Standard 13818-1, October 2007. 400 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 401 Performance Metric Development", BCP 170, RFC 6390, 402 October 2011. 404 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 405 Considerations for Protocol Extensions", RFC 6709, 406 September 2012. 408 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 409 using SDES item and XR Block", RFC 6776, August 2012. 411 [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the 412 RTP Monitoring Framework", RFC 6792, November 2012. 414 Authors' Addresses 416 Rachel Huang 417 Huawei 418 101 Software Avenue, Yuhua District 419 Nanjing 210012 420 China 422 Email: rachel.huang@huawei.com 424 Qin Wu 425 Huawei 426 101 Software Avenue, Yuhua District 427 Nanjing, Jiangsu 210012 428 China 430 Email: bill.wu@huawei.com 432 Hitoshi Asaeda 433 National Institute of Information and Communications Technology 434 4-2-1 Nukui-Kitamachi 435 Koganei, Tokyo 184-8795 436 Japan 438 Email: asaeda@nict.go.jp 440 Glen Zorn 441 Network Zen 442 227/358 Thanon Sanphawut 443 Bang Na, Bangkok 10260 444 Thailand 446 Phone: +66 (0) 909-201060 447 Email: glenzorn@gmail.com