idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-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 (October 22, 2012) is 4204 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 25, 2013 H. Asaeda 6 NICT 7 G. Zorn, Ed. 8 Network Zen 9 October 22, 2012 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for TS 12 Decodability Statistics Metric reporting 13 draft-ietf-xrblock-rtcp-xr-decodability-02 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 25, 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 system management 98 tool. 100 The new report block is in compliance with the monitoring 101 architecture specified in Wu, et al. [MONARCH] and the Performance 102 Metrics Framework [RFC6390]. The metric is applicable to any type of 103 RTP application that uses the TS standard format for multimedia data; 104 for example, MPEG4 TS content over RTP. 106 2. Terminology 108 2.1. Standards Language 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in RFC 2119 [RFC2119]. 114 3. TR 101 290 Decodability Statistics Metric Report Block 116 This block reports decodability statistics metrics beyond the 117 information carried in the standard RTCP packet format. It defines 118 eight metrics based on ETSI TR 101 290. Information is reported 119 about basic monitoring parameters necessary to ensure that the TS can 120 be decoded including: 122 o Transport Stream Synchronization Losses 123 o Sync byte errors 124 o Continuity count errors 126 and continuous monitoring parameters including: 128 o Transport errors 129 o Program Clock Reference (PCR) errors 130 o PCR repetition errors 131 o PCR discontinuity indicator errors 132 o Presentation Time Stamp (PTS) errors 134 The other parameters are ignored since they do not apply to all MPEG 135 implementations. For further information on these parameters, see 136 [ETSI]. 138 The Decodability Metrics Block has the following format: 140 0 1 2 3 141 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 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 | BT=TBD | Reserved | block length | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | SSRC of source | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | begin_seq | end_seq | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | Number of TSs | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | TS_sync_loss_count | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 153 | Sync_byte_error_count | 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Continuity_count_error_count | 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Transport_error_count | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | PCR_error_count | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | PCR_repetition_error_count | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | PCR_discontinuity_indicator_error_count | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | PTS_error_count | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 block type (BT): 8 bits 170 A TR 101 290 decodability metrics report block is identified by 171 the constant . 173 Reserved: 8 bits 175 This field is reserved for future definition. In the absence of 176 such a definition, the bits in this field MUST be set to zero and 177 SHOULD be ignored by the receiver. 179 block length: 16 bits 181 The constant 11, in accordance with the definition of this field 182 in Section 3 of RFC 3611. 184 SSRC of source: 32 bits 186 As defined in Section 4.1 of RFC 3611. 188 begin_seq: 16 bits 190 As defined in Section 4.1 of RFC 3611. 192 end_seq: 16 bits 194 As defined in Section 4.1 of RFC 3611. 196 Number of TSs: 32 bits 198 Number of TS in the above sequence number interval. 200 TS_sync_loss_count: 32 bits 202 Number of TS_sync_loss errors in the above sequence number 203 interval. 205 Sync_byte_error_count: 32 bits 207 Number of sync_byte_errors in the above sequence number interval. 209 Continuity_count_error_count: 32 bits 211 Number of Continuity_count_errors in the above sequence number 212 interval. 214 Transport_error_count: 32 bits 216 Number of Transport_errors in the above sequence number interval. 218 PCR_error_count: 32 bits 220 Number of PCR_errors in the above sequence number interval. 222 PCR_repetition_error_count: 32 bits 224 Number of PCR_repetition_errors in the above sequence number 225 interval. 227 PCR_discontinuity_indicator_error_count: 32 bits 229 Number of PCR_discontinuity_indicator_errors in the above sequence 230 number interval. 232 PTS_error_count: 32 bits 234 Number of PTS_errors in the above sequence number interval. 236 4. SDP Signaling 238 RFC 3611 defines the use of SDP (Session Description Protocol) 239 [RFC4566] for signaling the use of RTCP XR blocks. XR blocks MAY be 240 used without prior signaling. 242 4.1. SDP rtcp-xr-attrib Atrribute Extension 244 This session augments the SDP attribute "rtcp-xr" defined in Section 245 5.1 of RFC 3611 by providing an additional value of "xr-format" to 246 signal the use of the report block defined in this document. 248 xr-format =/ decodability-metrics 250 decodability-metrics = "decodability-metrics" 252 4.2. Offer/Answer Usage 254 When SDP is used in offer-answer context, the SDP Offer/Answer usage 255 defined in RFC 3611 applies. 257 5. IANA Considerations 259 New report block types for RTCP XR are subject to IANA registration. 260 For general guidelines on IANA allocations for RTCP XR, refer to 261 Section 6.2 ofRFC 3611. 263 This document assigns one new block type value in the RTCP XR Block 264 Type Registry: 266 Name: TDM 267 Long Name: TR 101 290 Decodability Metrics 268 Value 269 Reference: Section 3 271 This document also registers one SDP [RFC4566] parameters for the 272 "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: 274 * "decodability-metrics" 276 The contact information for the registrations is: 278 Rachel Huang 279 rachel.huang@huawei.com 280 101 Software Avenue, Yuhua District 281 Nanjing, JiangSu 210012 China 283 6. Security Considerations 285 This proposed RTCP XR report block introduces no new security 286 considerations beyond those described in RFC 3611. 288 7. Acknowledgements 290 Thanks to Ray van Brandenburg for useful review and suggestions. 292 8. References 294 8.1. Normative References 296 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 297 guidelines for DVB systems", Technical Report TR 101 290, 298 2001. 300 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 301 Requirement Levels", BCP 14, RFC 2119, March 1997. 303 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 304 Protocol Extended Reports (RTCP XR)", RFC 3611, 305 November 2003. 307 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 308 Description Protocol", RFC 4566, July 2006. 310 8.2. Informative References 312 [ISO-IEC.13818-1.2007] 313 International Organization for Standardization, 314 "Information technology - Generic coding of moving 315 pictures and associated audio information: Systems", 316 ISO International Standard 13818-1, October 2007. 318 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 319 RTP", ID draft-ietf-avtcore-monarch-22, September 2012. 321 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 322 Performance Metric Development", BCP 170, RFC 6390, 323 October 2011. 325 Authors' Addresses 327 Rachel Huang 328 Huawei 329 101 Software Avenue, Yuhua District 330 Nanjing 210012 331 China 333 Email: rachel.huang@huawei.com 335 Qin Wu 336 Huawei 337 101 Software Avenue, Yuhua District 338 Nanjing, Jiangsu 210012 339 China 341 Email: bill.wu@huawei.com 342 Hitoshi Asaeda 343 National Institute of Information and Communications Technology 344 4-2-1 Nukui-Kitamachi 345 Koganei, Tokyo 184-8795 346 Japan 348 Email: asaeda@nict.go.jp 350 Glen Zorn (editor) 351 Network Zen 352 227/358 Thanon Sanphawut 353 Bang Na, Bangkok 10260 354 Thailand 356 Phone: +66 (0) 909-201060 357 Email: glenzorn@gmail.com