idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-07.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 (January 16, 2013) is 4111 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: July 20, 2013 H. Asaeda 6 NICT 7 G. Zorn, Ed. 8 Network Zen 9 January 16, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG 12 Transport Stream (TS) Program Specific Information (PSI) Independent 13 Decodability Statistics Metric reporting 14 draft-ietf-xrblock-rtcp-xr-decodability-07 16 Abstract 18 An MPEG Transport Stream (TS) is a standard container format used in 19 the transmission and storage of multimedia data. Unicast/Multicast/ 20 Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This 21 document defines an RTP Control Protocol (RTCP) Extended Report (XR) 22 Block that allows the reporting of MPEG TS Program Specific 23 Information (PSI) Independent decodability statistics metrics related 24 to transmissions of MPEG-TS over RTP. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on July 20, 2013. 43 Copyright Notice 45 Copyright (c) 2013 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3 62 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 63 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 64 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 65 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 67 3. MPEG TS PSI Independent Decodability Statistics Metric 68 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 70 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7 71 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 72 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 73 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 74 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 75 5.3. Contact information for registrations . . . . . . . . . . 8 76 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 77 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 78 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 80 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 83 1. Introduction 85 1.1. MPEG 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 MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The 91 tests and corresponding indicators are grouped according to priority: 93 o First priority - Necessary for de-codability (basic monitoring) 94 o Second priority - Recommended for continuous or periodic 95 monitoring 96 o Third priority - Recommended for application-dependant 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 Freidman, et al. [RFC3611] for use with MPEG 101 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type 102 supports reporting of the number of occurrences of each Program 103 Specific Information (PSI) Independent indicator in the first and 104 second priorities; third priority indicators are not supported. 106 1.2. RTCP and RTCP XR Reports 108 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 109 defined an extensible structure for reporting using an RTCP Extended 110 Report (XR). This document defines a new Extended Report block for 111 use with [RFC3550] and [RFC3611]. 113 1.3. Performance Metrics Framework 115 The Performance Metrics Framework [RFC6390] provides guidance on the 116 definition and specification of performance metrics. The RTP 117 Monitoring Architectures [RFC6792] provides guideline for reporting 118 block format using RTCP XR. The new report block described in this 119 memo is in compliance with the monitoring architecture specified in 120 [RFC6792] and the Performance Metrics Framework [RFC6390]. 122 1.4. Applicability 124 These metrics are applicable to any type of RTP application that uses 125 the MPEG-TS standard format for multimedia data; for example, MPEG4 126 TS content over RTP. This new block type can be useful for measuring 127 content stream or TS quality by checking TS header information [ETSI] 128 and identifying the existence, and characterizing the severity, of 129 bitstream packetization problems which may affect users' perception 130 of a service delivered over RTP; it may also be useful for verifying 131 the continued correct operation of an existing system management 132 tool. 134 2. Terminology 136 2.1. Standards Language 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [RFC2119]. 142 3. MPEG TS PSI Independent Decodability Statistics Metric Block 144 This block reports MPEG TS PSI Independent decodability statistics 145 metrics beyond the information carried in the standard RTCP packet 146 format, which are measured at the receiving end of the RTP stream. 147 It describes eight metrics specified in ETSI TR 101 290. Information 148 is reported about basic monitoring parameters necessary to ensure 149 that the TS can be decoded including: 151 o Transport Stream Synchronization Losses 152 o Sync byte errors 153 o Continuity count errors 155 and continuous monitoring parameters necessary to ensure the 156 continuous decoding including: 158 o Transport errors 159 o Program Clock Reference (PCR) errors 160 o PCR repetition errors 161 o PCR discontinuity indicator errors 162 o PCR accuracy errors 163 o Presentation Time Stamp (PTS) errors 165 The other parameters are ignored since they do not apply to all MPEG 166 implementations. For further information on these parameters, see 167 [ETSI]. 169 The MPEG-TS PSI Independent Decodability Metrics Block has the 170 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=TSDM | Reserved | block length | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | SSRC of source | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 | begin_seq | end_seq | 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | Number of TSs | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 | TS_sync_loss_count | 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 | Sync_byte_error_count | 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 187 | Continuity_count_error_count | 188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 | Transport_error_count | 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | PCR_error_count | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | PCR_repetition_error_count | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | PCR_discontinuity_indicator_error_count | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | PCR_accuracy_error_count | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | PTS_error_count | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 block type (BT): 8 bits 204 The MPEG-TS PSI Independent Decodability Metrics Block is 205 identified by the constant . 207 Reserved: 8 bits 209 These bits are reserved. They MUST be set to zero by senders 210 ignored by receivers (See [RFC6709] section 4.2). 212 block length: 16 bits 214 The constant 12, in accordance with the definition of this field 215 in Section 3 of RFC 3611. The block MUST be discarded if the 216 block length is set to a different value. 218 SSRC of source: 32 bits 220 As defined in Section 4.1 of RFC 3611. 222 begin_seq: 16 bits 224 As defined in Section 4.1 of RFC 3611. 226 end_seq: 16 bits 228 As defined in Section 4.1 of RFC 3611. 230 Number of TSs: 32 bits 232 Number of TS in the above sequence number interval. 234 TS_sync_loss_count: 32 bits 236 Number of TS_sync_loss errors in the above sequence number 237 interval. It is calculated based on the occurrence of errors for 238 "TS_sync_loss"parameter defined in the section 5.2.1 of ETSI TR 239 101 290 (See section 5.5.1 of ETSI TR 101 290). 241 Sync_byte_error_count: 32 bits 243 Number of sync_byte_errors in the above sequence number interval. 244 It is calculated in the same way as TS_sync_loss_count, i.e.,based 245 on the occurrence of errors for "Sync_byte_error"parameter defined 246 in the section 5.2.1 of ETSI TR 101 290. 248 Continuity_count_error_count: 32 bits 250 Number of Continuity_count_errors in the above sequence number 251 interval. Simiarly, it is calculated based on the occurrence of 252 errors for "Continuity_count_error"parameter defined in the 253 section 5.2.1 of ETSI TR 101 290. 255 Transport_error_count: 32 bits 257 Number of Transport_errors in the above sequence number interval. 258 Simiarly, it is calculated based on the occurrence of errors for 259 "Transport_error" parameter defined in the section 5.2.2 of ETSI 260 TR 101 290. 262 PCR_error_count: 32 bits 264 Number of PCR_errors in the above sequence number interval. 265 Simiarly, it is calculated based on the occurrence of errors for 266 "PCR_error"parameter defined in the section 5.2.2 of ETSI TR 101 267 290. 269 PCR_repetition_error_count: 32 bits 271 Number of PCR_repetition_errors in the above sequence number 272 interval. Simiarly, it is calculated based on the occurrence of 273 errors for "PCR_repetition_error"parameter defined in the section 274 5.2.2 of ETSI TR 101 290. 276 PCR_discontinuity_indicator_error_count: 32 bits 278 Number of PCR_discontinuity_indicator_errors in the above sequence 279 number interval. Simiarly, it is calculated based on the 280 occurrence of errors for 281 "PCR_discontinuity_indicator_error"parameter defined in the 282 section 5.2.2 of ETSI TR 101 290. 284 PCR_error_count: 32 bits 286 Number of PCR_accuracy_errors in the above sequence number 287 interval. Simiarly, it is calculated based on the occurrence of 288 errors for "PCR_accuracy_error"parameter defined in the section 289 5.2.2 of ETSI TR 101 290. 291 PTS_error_count: 32 bits 293 Number of PTS_errors in the above sequence number interval. 294 Simiarly, it is calculated based on the occurrence of errors for 295 "PTS_error"parameter defined in the section 5.2.2 of ETSI TR 101 296 290. 298 4. SDP Signaling 300 RFC 3611 defines the use of SDP (Session Description Protocol) 301 [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks 302 MAY be used without prior signaling (See section 5 of RFC3611). 304 4.1. SDP rtcp-xr-attrib Attribute Extension 306 This session augments the SDP attribute "rtcp-xr" defined in Section 307 5.1 of RFC 3611 by providing an additional value of "xr-format" to 308 signal the use of the report block defined in this document. 310 xr-format =/ xr-nptd-block 312 xr-nptd-block = "non-psi-ts-decodability" 314 4.2. Offer/Answer Usage 316 When SDP is used in offer-answer context, the SDP Offer/Answer usage 317 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 318 applies. For detailed usage of Offer/Answer for unilateral 319 parameter, refer to section 5.2 of [RFC3611]. 321 5. IANA Considerations 323 New report block types for RTCP XR are subject to IANA registration. 324 For general guidelines on IANA allocations for RTCP XR, refer to 325 Section 6.2 ofRFC 3611. 327 5.1. New RTCP XR Block Type value 329 This document assigns the block type value MPID in the IANA " RTP 330 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 331 the " MPEG Transport Stream PSI Independent Decodability Statistics 332 Metric Block". 334 [Note to RFC Editor: please replace MPID with the IANA provided RTCP 335 XR block type for this block.] 337 5.2. New RTCP XR SDP Parameter 339 This document also registers a new parameter " non-psi-ts- 340 decodability " in the "RTP Control Protocol Extended Reports (RTCP 341 XR) Session Description Protocol (SDP) Parameters Registry". 343 5.3. Contact information for registrations 345 The contact information for the registrations is: 347 Qin Wu 348 sunseawq@huawei.com 349 101 Software Avenue, Yuhua District 350 Nanjing, JiangSu 210012 China 352 6. Security Considerations 354 This proposed RTCP XR report block introduces no new security 355 considerations beyond those described in RFC 3611. 357 7. Acknowledgements 359 Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin,Roni Even and 360 Dan Romascanufor useful review and suggestions. 362 8. References 364 8.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, 378 November 2003. 380 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 381 Description Protocol", RFC 4566, July 2006. 383 8.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", 389 ISO 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 Authors' Addresses 404 Rachel Huang 405 Huawei 406 101 Software Avenue, Yuhua District 407 Nanjing 210012 408 China 410 Email: rachel.huang@huawei.com 412 Qin Wu 413 Huawei 414 101 Software Avenue, Yuhua District 415 Nanjing, Jiangsu 210012 416 China 418 Email: bill.wu@huawei.com 420 Hitoshi Asaeda 421 National Institute of Information and Communications Technology 422 4-2-1 Nukui-Kitamachi 423 Koganei, Tokyo 184-8795 424 Japan 426 Email: asaeda@nict.go.jp 428 Glen Zorn (editor) 429 Network Zen 430 227/358 Thanon Sanphawut 431 Bang Na, Bangkok 10260 432 Thailand 434 Phone: +66 (0) 909-201060 435 Email: glenzorn@gmail.com