idnits 2.17.1 draft-huang-xrblock-rtcp-xr-decodability-05.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 (July 16, 2012) is 4301 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) == Unused Reference: 'RFC2250' is defined on line 289, but no explicit reference was found in the text == Unused Reference: 'RFC3550' is defined on line 293, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ETSI' ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-17 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 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: January 17, 2013 H. Asaeda 6 Keio University 7 G. Zorn, Ed. 8 Network Zen 9 July 16, 2012 11 RTCP XR Report Block for TS Decodability Statistics Metric reporting 12 draft-huang-xrblock-rtcp-xr-decodability-05 14 Abstract 16 Transport Stream is a standard container format used in the 17 transmission and storage of multimedia data. Unicast/Multicast/ 18 Broadcast MPEG-TS over RTP is widely adopted in the IPTV deployment. 19 This document defines an RTCP XR Report Block that allows the 20 reporting of decodability statistics metrics related to transmissions 21 of MPEG-TS over RTP. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 17, 2013. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 60 3. TR 101 290 Decodability Statistics Metric Report Block . . . . 3 61 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 6 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 63 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 65 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 66 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 69 1. Introduction 71 The European Telecommunications Standards Institute (ETSI) has 72 defined a set of syntax and information consistency tests and 73 resulting indicators [ETSI] recommended for the monitoring of MPEG-2 74 Transport Streams (TS) [ISO-IEC.13818-1.2007]. The tests and 75 corresponding indicators are grouped according to priority: 77 o First priority - Necessary for de-codability (basic monitoring) 78 o Second priority - Recommended for continuous or periodic 79 monitoring 80 o Third priority - Recommended for application-dependant monitoring 82 This draft is based on information consistency tests and resulting 83 indicators in the [ETSI] and defines a new block type to augment 84 those defined in [RFC3611] for use with Transport Stream (TS) 85 [ISO-IEC.13818-1.2007]. The new block type supports reporting of the 86 number of each indicator in the first and second priority;third 87 priority indicators are not supported. This new block type can be 88 useful for measuring content stream or TS quality by checking TS 89 header information [ETSI] and identifying the existence, and 90 characterizing the severity, of bitstream packetization problem which 91 may affect users' perception of a service delivered over RTP; it may 92 also be useful for verifying the continued correct operation of an 93 existing system management. 95 The new report block is in compliance with the monitoring 96 architecture specified in [MONARCH] and the Performance Metrics 97 Framework [RFC6390]. The metric is applicable to any type of RTP 98 application that uses TS standard format for container of multimedia 99 data, for example MPEG4 TS content over RTP. 101 2. Terminology 103 2.1. Standards Language 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in RFC 2119 [RFC2119]. 109 3. TR 101 290 Decodability Statistics Metric Report Block 111 This block reports decodability statistics metrics beyond the 112 information carried in the standard RTCP packet format. It defines 113 eight metrics based on ETSI TR 101 290. Information is reported 114 about basic monitoring parameters necessary to ensure that the TS can 115 be decoded including: 117 o Transport Stream Synchronization Losses 118 o Sync byte errors 119 o Continuity count errors 121 and continuous monitoring parameters including: 123 o Transport errors 124 o Program Clock Reference (PCR) errors 125 o PCR repetition errors 126 o PCR discontinuity indicator errors 127 o Presentation Time Stamp (PTS) errors 129 The other parameters are ignored since they are not applied to all 130 the MPEG implentations. For further information on these parameters, 131 see [ETSI] 133 The Decodability Metrics Block has the following format: 135 0 1 2 3 136 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 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | BT=TBD | rvd | block length | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | SSRC of source | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | begin_seq | end_seq | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | Number of TSs | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | TS_sync_loss_count | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | Sync_byte_error_count | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | Continuity_count_error_count | 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | Transport_error_count | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | PCR_error_count | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | PCR_repetition_error_count | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | PCR_discontinuity_indicator_error_count | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | PTS_error_count | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 block type (BT): 8 bits 164 A TR 101 290 decodability metrics report block is identified by 165 the constant . 167 rvd: 8 bits 169 This field is reserved for future definition. In the absence of 170 such a definition, the bits in this field MUST be set to zero and 171 SHOULD be ignored by the receiver. 173 block length: 16 bits 175 The constant 11, in accordance with the definition of this field 176 in Section 3 of RFC 3611 [RFC3611]. 178 SSRC of source: 32 bits 180 As defined in Section 4.1 of [RFC3611]. 182 begin_seq: 16 bits 184 As defined in Section 4.1 of [RFC3611]. 186 end_seq: 16 bits 188 As defined in Section 4.1 of [RFC3611]. 190 Number of TSs: 32 bits 192 Number of TS in the above sequence number interval. 194 TS_sync_loss_count: 32 bits 196 Number of TS_sync_loss errors in the above sequence number 197 interval. 199 Sync_byte_error_count: 32 bits 201 Number of sync_byte_errors in the above sequence number interval. 203 Continuity_count_error_count: 32 bits 205 Number of Continuity_count_errors in the above sequence number 206 interval. 208 Transport_error_count: 32 bits 210 Number of Transport_errors in the above sequence number interval. 212 PCR_error_count: 32 bits 214 Number of PCR_errors in the above sequence number interval. 216 PCR_repetition_error_count: 32 bits 218 Number of PCR_repetition_errors in the above sequence number 219 interval. 221 PCR_discontinuity_indicator_error_count: 32 bits 223 Number of PCR_discontinuity_indicator_errors in the above sequence 224 number interval. 226 PTS_error_count: 32 bits 228 Number of PTS_errors in the above sequence number interval. 230 4. SDP Signaling 232 One new parameter is defined for the report block defined in this 233 document to be used with Session Description Protocol (SDP) [RFC4566] 234 using the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the 235 following syntax within the "rtcp-xr" attribute [RFC3611]: 237 rtcp-xr-attrib = "a=rtcp-xr:" 238 [xr-format *(SP xr-format)] CRLF 240 xr-format = decodability-metrics 242 decodability-metrics = "decodability-metrics" 244 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 245 and the full syntax of the "rtcp-xr" attribute. 247 5. IANA Considerations 249 New report block types for RTCP XR are subject to IANA registration. 250 For general guidelines on IANA allocations for RTCP XR, refer to 251 Section 6.2 of [RFC3611]. 253 This document assigns one new block type value in the RTCP XR Block 254 Type Registry: 256 Name: TDM 257 Long Name: TR 101 290 Decodability Metrics 258 Value 259 Reference: section 3 261 This document also registers one SDP [RFC4566] parameters for the 262 "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: 264 * "decodability-metrics" 266 The contact information for the registrations is: 268 Rachel Huang 269 rachel.huang@huawei.com 270 101 Software Avenue, Yuhua District 271 Nanjing, JiangSu 210012 China 273 6. Security Considerations 275 This proposed RTCP XR report block introduces no new security 276 considerations beyond those described in [RFC3611]. 278 7. References 280 7.1. Normative References 282 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 283 guidelines for DVB systems", Technical Report TR 101 290, 284 2001. 286 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 287 Requirement Levels", BCP 14, RFC 2119, March 1997. 289 [RFC2250] Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar, 290 "RTP Payload Format for MPEG1/MPEG2 Video", RFC 2250, 291 January 1998. 293 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 294 Jacobson, "RTP: A Transport Protocol for Real-Time 295 Applications", STD 64, RFC 3550, July 2003. 297 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 298 Protocol Extended Reports (RTCP XR)", RFC 3611, 299 November 2003. 301 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 302 Description Protocol", RFC 4566, July 2006. 304 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 305 Specifications: ABNF", STD 68, RFC 5234, January 2008. 307 7.2. Informative References 309 [ISO-IEC.13818-1.2007] 310 International Organization for Standardization, 311 "Information technology - Generic coding of moving 312 pictures and associated audio information: Systems", 313 ISO International Standard 13818-1, October 2007. 315 [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for 316 RTP", ID draft-ietf-avtcore-monarch-17, June 2012. 318 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 319 Performance Metric Development", BCP 170, RFC 6390, 320 October 2011. 322 Authors' Addresses 324 Rachel Huang 325 Huawei 326 101 Software Avenue, Yuhua District 327 Nanjing 210012 328 China 330 Email: rachel.huang@huawei.com 332 Qin Wu 333 Huawei 334 101 Software Avenue, Yuhua District 335 Nanjing, Jiangsu 210012 336 China 338 Email: bill.wu@huawei.com 339 Hitoshi Asaeda 340 Keio University 341 Graduate School of Media and Governance 5322 Endo 342 Fujisawa, Kanagawa 252-0882 343 Japan 345 Email: asaeda@wide.ad.jp 347 Glen Zorn (editor) 348 Network Zen 349 227/358 Thanon Sanphawut 350 Bang Na, Bangkok 10260 351 Thailand 353 Phone: +66 (0) 87-040-4617 354 Email: glenzorn@gmail.com