idnits 2.17.1 draft-huang-avt-rtcp-xr-decodability-00.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 16, 2010) is 4941 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: 'DSLF' is defined on line 324, but no explicit reference was found in the text == Unused Reference: 'G.1082' is defined on line 328, but no explicit reference was found in the text == Unused Reference: 'IEEE' is defined on line 332, 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) 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: April 19, 2011 October 16, 2010 7 RTCP XR Report Block for TS Decodability Statistics Metric reporting 8 draft-huang-avt-rtcp-xr-decodability-00 10 Abstract 12 This document defines an RTCP XR Report Block that allows the 13 reporting of Decodability Statistics Metric used for Transport 14 Stream. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on April 19, 2011. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 53 2.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. TR 101 290 Decodability Statistics Metric Report Block . . . . 3 55 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 6 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 57 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 58 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 7.1. Normative References . . . . . . . . . . . . . . . . . . . 8 60 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 63 1. Introduction 65 This draft defines a new block type to augment those defined in 66 [RFC3611] for use in Transport Stream. The new block type supports 67 the reporting of consistency of Transport Stream [ETSI]. This new 68 block type can be useful for identifying the existence, and 69 characterising the severity, of a packet transport problem which may 70 affect users' perception of a service delivered over RTP, also useful 71 for Verifying the continued correct operation of an existing system 72 management and providing accurate measures of Transport Stream 73 quality for operators. 75 The metric is applicable to any other types of RTP application that 76 use TS standard format for transmission and storage of audio, video, 77 and data. 79 2. Terminology 81 2.1. Standards Language 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in RFC 2119 [RFC2119]. 87 In addition, the following terms are defined: 89 2.2. Acronyms 91 SSRC 92 Synchronization Source [RFC3550] 94 TS 95 Transport Stream [ISO-IEC.13818-1.2007] 97 3. TR 101 290 Decodability Statistics Metric Report Block 99 This block reports decodability statistics metric beyond the 100 information carried in the standard RTCP packet format. Information 101 is recorded about the number of Transport Stream Synchronization 102 Losses, Sync byte errors, Continuity count errors, Transport errors, 103 Program Clock Reference (PCR) errors, PCR repetition errors, PCR 104 discontinuity indicator errors, and Presentation Time Stamp (PTS) 105 errors [ETSI]. Such information can be useful for network management 106 and video quality monitoring. 108 Note that this is not only applicable to MPEG-2 RTP streams 110 [RFC2250],but also applicable to any other video codec using 111 Transport Stream as input. 113 The report block contents are dependent upon a series of flag bits 114 carried in the first part of the header. Not all parameters need to 115 be reported in each block. Flags indicate which are and which are 116 not reported. The fields corresponding to unreported parameters MUST 117 be present, but are set to zero. The receiver MUST ignore any 118 Decodability Metrics Block with a non-zero value in any field flagged 119 as unreported. 121 The Decodability Metrics Block has the following format: 123 0 1 2 3 124 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 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 | BT=TBD |L|B|C|T|P|S|rvd| block length | 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | SSRC of source | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | begin_seq | end_seq | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Number of packets | Number of TSs | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Transport Stream Synchronization Losses | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Sync byte errors | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Continuity count errors | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | Transport errors | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | PCR errors | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | PCR repetition errors | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | PCR discontinuity indicator errors | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | PTS errors | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 block type (BT): 8 bits 152 A TR 101 290 decodability metrics report block is identified by 153 the constant . 155 Transport Stream Synchronization Loss flag (L): 1 bit 156 Bit set to 1 if the Transport Stream Synchronization Loss field 157 contains a report, 0 otherwise. 159 Sync byte error flag (B): 1 bit 160 Bit set to 1 if the Sync byte error field contains a report, 0 161 otherwise. 163 Continuity count error flag (C): 1 bit 164 Bit set to 1 if the Continuity count error field contains a 165 report, 0 otherwise. 167 Transport error flag (T): 1 bit 168 Bit set to 1 if the Transport error field contains a report, 0 169 otherwise. 171 PCR related error flag (P): 1 bit 172 Bit set to 1 if the PCR error field, PCR repetition error field 173 and PCR discontinuity indicator error fields contain a report, 0 174 otherwise. 176 PTS error flag (S): 1 bit 177 Bit set to 1 if the PTS error field contains a report, 0 178 otherwise. 180 rvd: 2 bits 181 This field is reserved for future definition. In the absence of 182 such a definition, the bits in this field MUST be set to zero and 183 MUST be ignored by the receiver. 185 block length: 16 bits 186 The constant 10, in accordance with the definition of this field 187 in Section 3 of RFC 3611 [RFC3611]. 189 SSRC of source: 32 bits 190 As defined in Section 4.1 of [RFC3611]. 192 begin_seq: 16 bits 193 As defined in Section 4.1 of [RFC3611]. 195 end_seq: 16 bits 196 As defined in Section 4.1 of [RFC3611]. 198 Number of Packets: 16 bits 199 Number of RTP packets in the above sequence number interval. 201 Number of TSs: 16 bits 202 Number of Transport Streams in the above sequence number interval. 204 Transport Stream Synchronization Losses: 32 bits 205 Number of Transport Stream Synchronization Losses in the above 206 sequence number interval. 208 Sync byte errors: 32 bits 209 Number of Transport sync byte errors in the above sequence number 210 interval. 211 Continuity count error: 32 bits 212 Number of Transport Continuity count errors in the above sequence 213 number interval. 215 Transport errors: 32 bits 216 Number of Transport errors in the above sequence number interval. 218 PCR errors: 32 bits 219 Number of PCR errors in the above sequence number interval. 221 PCR repetition errors: 32 bits 222 Number of Transport PCR repetition errors in the above sequence 223 number interval. 225 PCR discontinuity indicator errors: 32 bits 226 Number of PCR discontinuity indicator errors in the above sequence 227 number interval. 229 PTS errors: 32 bits 230 Number of PTS errors in the above sequence number interval. 232 4. SDP Signaling 234 One new parameters are defined for the one report blocks defined in 235 this document to be used with Session Description Protocol (SDP) 236 [RFC4566] using the Augmented Backus-Naur Form (ABNF) [RFC5234]. 237 They have the following syntax within the "rtcp-xr" attribute 238 [RFC3611]: 240 rtcp-xr-attrib = "a=rtcp-xr:" 241 [xr-format *(SP xr-format)] CRLF 243 xr-format = decodability-metrics 245 decodability-metrics = "decodability-metrics" 246 ["=" stat-flag *("," stat-flag)] 247 stat-flag = "TS Synchronization Loss " 248 / "Sync byte error " 249 / "Continuity count error " 250 / "Transport error" 251 / "PCR related error" 252 / "PTS error" 254 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 255 and the full syntax of the "rtcp-xr" attribute. 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 of [RFC3611]. 263 This document assigns one new block type values 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 Parameters Registry: 274 * "decodability-metrics" 276 The contact information for the registrations is: 278 Rachel Huang 279 Rachel@huawei.com 280 101 Software Avenue, Yuhua District 281 Nanjing, JiangSu 210012 China 283 6. Security Considerations 285 TBC 287 7. References 289 7.1. Normative References 291 [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement 292 guidelines for DVB systems", Technical Report TR 101 290, 293 2001. 295 [ISO-IEC.13818-1.2007] 296 International Organization for Standardization, 297 "Information technology - Generic coding of moving 298 pictures and associated audio information: Systems", 299 ISO International Standard 13818-1, October 2007. 301 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 302 Requirement Levels", BCP 14, RFC 2119, March 1997. 304 [RFC2250] Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar, 305 "RTP Payload Format for MPEG1/MPEG2 Video", RFC 2250, 306 January 1998. 308 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 309 Jacobson, "RTP: A Transport Protocol for Real-Time 310 Applications", STD 64, RFC 3550, July 2003. 312 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 313 Protocol Extended Reports (RTCP XR)", RFC 3611, 314 November 2003. 316 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 317 Description Protocol", RFC 4566, July 2006. 319 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 320 Specifications: ABNF", STD 68, RFC 5234, January 2008. 322 7.2. Informative References 324 [DSLF] Rahrer, T., Ed., Fiandra, Ed., and Wright, Ed., "Triple- 325 play Services Quality of Experience (QoE) Requirements", 326 DSL Forum Technical Report TR-126, December 2006. 328 [G.1082] ITU-T, "Measurement-based methods for improving the 329 robustness of IPTV performance", ITU-T 330 Recommendation G.1082, April 2009. 332 [IEEE] IEEE, "Human Perception of Jitter and Media 333 Synchronization", IEEE Journal on Selected Areas in 334 Communications Vol. 14, No. 1, January 1996. 336 [P.NAMS] ITU-T, "Non-intrusive parametric model for the Assessment 337 of performance of Multimedia Streaming", ITU-T 338 Recommendation P.NAMS, November 2009. 340 Authors' Addresses 342 Rachel Huang 343 Huawei 344 101 Software Avenue, Yuhua District 345 Nanjing 210012 346 China 348 Email: Rachel@huawei.com 350 Qin Wu 351 Huawei 352 101 Software Avenue, Yuhua District 353 Nanjing, Jiangsu 210012 354 China 356 Email: sunseawq@huawei.com