idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-decodability-01.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 (October 18, 2012) is 4201 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: April 21, 2013 H. Asaeda 6 NICT 7 G. Zorn, Ed. 8 Network Zen 9 October 18, 2012 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for TS 12 Decodability Statistics Metric reporting 13 draft-ietf-xrblock-rtcp-xr-decodability-01 15 Abstract 17 Transport Stream (TS) is a standard container format used in the 18 transmission and storage of multimedia data. Unicast/Multicast/ 19 Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This 20 document defines an RTP Control Protocol (RTCP) Extended Report (XR) 21 Block that allows the reporting of decodability statistics metrics 22 related to transmissions of MPEG-TS over RTP. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on April 21, 2013. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 61 3. TR 101 290 Decodability Statistics Metric Report Block . . . . 3 62 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 6 64 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 6 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 73 1. Introduction 75 The European Telecommunications Standards Institute (ETSI) has 76 defined a set of syntax and information consistency tests and 77 corresponding indicators [ETSI] that are recommended for the 78 monitoring of MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The 79 tests and corresponding indicators are grouped according to priority: 81 o First priority - Necessary for de-codability (basic monitoring) 82 o Second priority - Recommended for continuous or periodic 83 monitoring 84 o Third priority - Recommended for application-dependant monitoring 86 This draft is based on information consistency tests and resulting 87 indicators defined by ETSI [ETSI] and defines a new block type to 88 augment those defined in Freidman, et al. [RFC3611] for use with 89 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type 90 supports reporting of the number of occurances of each indicator in 91 the first and second priorities; third priority indicators are not 92 supported. This new block type can be useful for measuring content 93 stream or TS quality by checking TS header information [ETSI] and 94 identifying the existence, and characterizing the severity, of 95 bitstream packetization problems which may affect users' perception 96 of a service delivered over RTP; it may also be useful for verifying 97 the continued correct operation of an existing management system. 99 The new report block is in compliance with the monitoring 100 architecture specified in Wu, et al. [MONARCH] and the Performance 101 Metrics Framework [RFC6390]. The metric is applicable to any type of 102 RTP application that uses the TS standard format for multimedia data; 103 for example, MPEG4 TS content over RTP. 105 2. Terminology 107 2.1. Standards Language 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 111 document are to be interpreted as described in RFC 2119 [RFC2119]. 113 3. TR 101 290 Decodability Statistics Metric Report Block 115 This block reports decodability statistics metrics beyond the 116 information carried in the standard RTCP packet format. It defines 117 eight metrics based on ETSI TR 101 290. Information is reported 118 about basic monitoring parameters necessary to ensure that the TS can 119 be decoded including: 121 o Transport Stream Synchronization Losses 122 o Sync byte errors 123 o Continuity count errors 125 and continuous monitoring parameters including: 127 o Transport errors 128 o Program Clock Reference (PCR) errors 129 o PCR repetition errors 130 o PCR discontinuity indicator errors 131 o Presentation Time Stamp (PTS) errors 133 The other parameters are ignored since they do not apply to all MPEG 134 implementations. For further information on these parameters, see 135 [ETSI]. 137 The Decodability Metrics Block has the following format: 139 0 1 2 3 140 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 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | BT=TBD | Reserved | block length | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | SSRC of source | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | begin_seq | end_seq | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | Number of TSs | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | TS_sync_loss_count | 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | Sync_byte_error_count | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | Continuity_count_error_count | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Transport_error_count | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | PCR_error_count | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | PCR_repetition_error_count | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | PCR_discontinuity_indicator_error_count | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | PTS_error_count | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 block type (BT): 8 bits 169 A TR 101 290 decodability metrics report block is identified by 170 the constant . 172 Reserved: 8 bits 174 This field is reserved for future definition. In the absence of 175 such a definition, the bits in this field MUST be set to zero and 176 SHOULD be ignored by the receiver. 178 block length: 16 bits 180 The constant 11, in accordance with the definition of this field 181 in Section 3 of RFC 3611. 183 SSRC of source: 32 bits 185 As defined in Section 4.1 of RFC 3611. 187 begin_seq: 16 bits 189 As defined in Section 4.1 of RFC 3611. 191 end_seq: 16 bits 193 As defined in Section 4.1 of RFC 3611. 195 Number of TSs: 32 bits 197 Number of TS in the above sequence number interval. 199 TS_sync_loss_count: 32 bits 201 Number of TS_sync_loss errors in the above sequence number 202 interval. 204 Sync_byte_error_count: 32 bits 206 Number of sync_byte_errors in the above sequence number interval. 208 Continuity_count_error_count: 32 bits 210 Number of Continuity_count_errors in the above sequence number 211 interval. 213 Transport_error_count: 32 bits 215 Number of Transport_errors in the above sequence number interval. 217 PCR_error_count: 32 bits 219 Number of PCR_errors in the above sequence number interval. 221 PCR_repetition_error_count: 32 bits 223 Number of PCR_repetition_errors in the above sequence number 224 interval. 226 PCR_discontinuity_indicator_error_count: 32 bits 228 Number of PCR_discontinuity_indicator_errors in the above sequence 229 number interval. 231 PTS_error_count: 32 bits 233 Number of PTS_errors in the above sequence number interval. 235 4. SDP Signaling 237 RFC 3611 defines the use of SDP (Session Description Protocol) 238 [RFC4566] for signaling the use of RTCP XR blocks. XR blocks MAY be 239 used without prior signaling. 241 4.1. SDP rtcp-xr-attrib Atrribute Extension 243 This session augments the SDP attribute "rtcp-xr" defined in Section 244 5.1 of RFC 3611 by providing an additional value of "xr-format" to 245 signal the use of the report block defined in this document. 247 xr-format =/ decodability-metrics 249 decodability-metrics = "decodability-metrics" 251 4.2. Offer/Answer Usage 253 When SDP is used in offer-answer context, the SDP Offer/Answer usage 254 defined in RFC 3611 applies. 256 5. IANA Considerations 258 New report block types for RTCP XR are subject to IANA registration. 259 For general guidelines on IANA allocations for RTCP XR, refer to 260 Section 6.2 ofRFC 3611. 262 This document assigns one new block type value in the RTCP XR Block 263 Type Registry: 265 Name: TDM 266 Long Name: TR 101 290 Decodability Metrics 267 Value 268 Reference: Section 3 270 This document also registers one SDP [RFC4566] parameters for the 271 "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: 273 * "decodability-metrics" 275 The contact information for the registrations is: 277 Rachel Huang 278 rachel.huang@huawei.com 279 101 Software Avenue, Yuhua District 280 Nanjing, JiangSu 210012 China 282 6. Security Considerations 284 This proposed RTCP XR report block introduces no new security 285 considerations beyond those described in RFC 3611. 287 7. Acknowledgements 289 Thanks to Ray van Brandenburg for useful review and suggestions. 291 8. References 293 8.1. Normative References 295 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 296 guidelines for DVB systems", Technical Report TR 101 290, 297 2001. 299 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 300 Requirement Levels", BCP 14, RFC 2119, March 1997. 302 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 303 Protocol Extended Reports (RTCP XR)", RFC 3611, 304 November 2003. 306 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 307 Description Protocol", RFC 4566, July 2006. 309 8.2. Informative References 311 [ISO-IEC.13818-1.2007] 312 International Organization for Standardization, 313 "Information technology - Generic coding of moving 314 pictures and associated audio information: Systems", 315 ISO International Standard 13818-1, October 2007. 317 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 318 RTP", ID draft-ietf-avtcore-monarch-22, September 2012. 320 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 321 Performance Metric Development", BCP 170, RFC 6390, 322 October 2011. 324 Authors' Addresses 326 Rachel Huang 327 Huawei 328 101 Software Avenue, Yuhua District 329 Nanjing 210012 330 China 332 Email: rachel.huang@huawei.com 334 Qin Wu 335 Huawei 336 101 Software Avenue, Yuhua District 337 Nanjing, Jiangsu 210012 338 China 340 Email: bill.wu@huawei.com 341 Hitoshi Asaeda 342 National Institute of Information and Communications Technology 343 4-2-1 Nukui-Kitamachi 344 Koganei, Tokyo 184-8795 345 Japan 347 Email: asaeda@nict.go.jp 349 Glen Zorn (editor) 350 Network Zen 351 227/358 Thanon Sanphawut 352 Bang Na, Bangkok 10260 353 Thailand 355 Phone: +66 (0) 909-201060 356 Email: glenzorn@gmail.com