idnits 2.17.00 (12 Aug 2021) /tmp/idnits28296/draft-xia-xrblock-rtcp-xr-layered-statistics-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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 15, 2011) is 3894 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: 'RFC3550' is defined on line 267, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: draft-ietf-avtcore-monarch has been published as RFC 6792 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Xia 3 Internet-Draft Huawei 4 Intended status: Standards Track G. Zorn 5 Expires: March 18, 2012 Network Zen 6 Q. Wu 7 Huawei 8 R. Schott 9 Deutsche Telekom 10 September 15, 2011 12 RTCP XR Blocks for layered Stream statistics metric reporting 13 draft-xia-xrblock-rtcp-xr-layered-statistics-01 15 Abstract 17 This document defines an RTCP XR Report Block and associated SDP 18 parameters that allow the reporting of layered stream statistics 19 metrics for use in a range of RTP applications. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on March 18, 2012. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 70 3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 4. Layered Streams Statistics Metrics Block . . . . . . . . . . . 3 72 4.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 4 73 4.2. Definition of Fields in layered stream statistics 74 Metrics Block . . . . . . . . . . . . . . . . . . . . . . . 4 75 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 78 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 79 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 80 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 81 9.2. Informative References . . . . . . . . . . . . . . . . . . 7 82 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 7 83 A.1. draft-xia-xrblock-rtcp-xr-layered-statistics-01 . . . . . . 7 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 86 1. Introduction 88 This draft defines a new block type to augment those defined in 89 [RFC3611], for use in a range of RTP applications. 91 The new block type provides layered streams statistics beyond the 92 information carried in the Statistics Summary Report Block RTCP 93 packet specified in the section 4.6 of RFC 3611 [RFC3611]. 94 Information is recorded about lost layered component packets, 95 duplicated layered component packets. 97 The metrics belong to the class of transport level metrics defined in 98 [MONARCH] (work in progress). 100 2. Terminology 102 2.1. Standards Language 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in RFC 2119 [RFC2119]. 108 In addition, the following terms are defined: 110 Layered Component Packet 112 a RTP packet using layered codecs containing the specified layered 113 component, e.g., encoded stream at the base layer or at the 114 enhancement layer. 116 3. Applicability 118 Layered Streams Statistics Metrics Block can be applied to any real 119 time applications that use layered or multi-description video coding. 121 4. Layered Streams Statistics Metrics Block 123 Metrics in this block report on lost packets, duplicated packets in 124 the layered stream arriving at the RTP system. 126 4.1. Metric Block Structure 128 The report block contents are dependent upon a series of flag bits 129 carried in the first part of the header. Not all parameters need to 130 be reported in each block. Flags indicate which are and which are 131 not reported. The fields corresponding to unreported parameters MUST 132 be present, but are set to zero. The receiver MUST ignore any 133 Perceptual Quality Metrics Block with a non-zero value in any field 134 flagged as unreported. 136 The Layered Stream Statistics metrics Block has the following format: 138 0 1 2 3 139 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 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 | BT=TBD |I|T|D| rsd. | block length | 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 | SSRC of source | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | begin_seq | end_seq | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | Lost_Layered Component Packets | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | Dup Layered Component_Packets | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 4.2. Definition of Fields in layered stream statistics Metrics Block 154 Block type (BT): 8 bits 155 The Layered stream Statistics Metrics Block is identified by the 156 constant . 158 Interval Metric flag (I): 1 bit 160 This field is used to indicate whether the Basic Loss/Discard 161 metrics are Interval or Cumulative metrics, that is, whether the 162 reported values applies to the most recent measurement interval 163 duration between successive metrics reports (I=1) (the Interval 164 Duration) or to the accumulation period characteristic of 165 cumulative measurements (I=0) (the Cumulative Duration). 167 Layer Type flag (T): 1 bit 168 This field is used to indicate the Layer Type of layered video to 169 be reported. LT is set to 0 if the loss_component_packet field 170 and dup_component packet contain the base layer packet in layered 171 codecs,e.g, SVC in [RFC6190], 1 if the loss_component packet field 172 and dup_component packet contain enhancement layer packet in 173 layered codec. 175 Layer Dependency (D): 1 bit 177 This field is used to indicate the layer dependency between 178 different enhancement layers if there is more than one enhancement 179 layers. D is set to 0 if there is no layer dependency between 180 different enhancement layers, 1 if there is layer dependency 181 between different enhancement layers. 183 Rsd.: 5 bits 184 This field is reserved for future definition. In the absence of 185 such a definition, the bits in this field MUST be set to zero and 186 MUST be ignored by the receiver. 188 Block length: 16 bits 189 The constant 3, in accordance with the definition of this field in 190 Section 3 of RFC 3611 [RFC3611]. 192 begin_seq: 16 bits 193 As defined in Section 4.1 of RFC 3611 [RFC3611]. 195 end_seq: 16 bits 196 As defined in Section 4.1 of RFC 3611 [RFC3611]. 198 Lost_Layered Component Packets: 32 bits 199 Number of lost_component packets in the above sequence number 200 interval. 202 Dup_Layered Component Packets: 32 bits 203 Number of dup_component packets in the above sequence number 204 interval. 206 5. SDP Signaling 208 One new parameter is defined for the report block defined in this 209 document to be used with Session Description Protocol (SDP) [RFC4566] 210 using the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the 211 following syntax within the "rtcp-xr" attribute [RFC3611]: 213 rtcp-xr-attrib = "a=rtcp-xr:" 214 [xr-format *(SP xr-format)] CRLF 215 xr-format = layered-stream-stat-metrics 216 layered-stream-stat-metrics = "layered-stream-stat-metrics" 217 ["=" stat-flag *("," stat-flag)] 218 stat-flag = "base layer packet" 219 / "enhancment layer packet" 221 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 222 and the full syntax of the "rtcp-xr" attribute. 224 6. IANA Considerations 226 New report block type for RTCP XR is subject to IANA registration. 227 For general guidelines on IANA allocations for RTCP XR, refer to 228 Section 6.2 of [RFC3611]. 230 This document assigns one new block type value in the RTCP XR Block 231 Type Registry: 233 Name: LSSM 234 Long Name: Layered Stream Statistics Metrics 235 Value 236 Reference: Section 4 238 This document also registers one new SDP [RFC4566] parameter for the 239 "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 241 * "layered-stream-stat-metrics" 243 The contact information for the registrations is: 245 Qin Wu 246 sunseawq@huawei.com 247 101 Software Avenue, Yuhua District 248 Nanjing, JiangSu 210012 China 250 7. Security Considerations 252 The new RTCP XR report blocks proposed in this document introduces no 253 new security considerations beyond those described in [RFC3611]. 255 8. Acknowledgements 257 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 258 Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and Yinliang 259 Hu for their valuable comments and suggestions on this document. 261 9. References 262 9.1. Normative References 264 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 265 Requirement Levels", BCP 14, RFC 2119, March 1997. 267 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 268 Jacobson, "RTP: A Transport Protocol for Real-Time 269 Applications", STD 64, RFC 3550, July 2003. 271 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 272 Protocol Extended Reports (RTCP XR)", RFC 3611, 273 November 2003. 275 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 276 Description Protocol", RFC 4566, July 2006. 278 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 279 Specifications: ABNF", STD 68, RFC 5234, January 2008. 281 [RFC6190] Wenger, S., Wang, Y., Schierl, T., and A. Eleftheriadis, 282 "RTP Payload Format for Scalable Video Coding", RFC 6190, 283 May 2011. 285 9.2. Informative References 287 [MONARCH] Wu, Q., "Monitoring Architectures for RTP", 288 ID draft-ietf-avtcore-monarch-00, April 2011. 290 Appendix A. Change Log 292 A.1. draft-xia-xrblock-rtcp-xr-layered-statistics-01 294 The following are the major changes compared to previous version 00: 295 o Add the layer dependency field in the format of this metric block. 296 o Clear unused references. 297 o Other Editorial changes. 299 Authors' Addresses 301 Jinwei Xia 302 Huawei 303 101 Software Avenue, Yuhua District 304 Nanjing, Jiangsu 210012 305 China 307 Email: xiajinwei@huawei.com 309 Glen Zorn 310 Network Zen 311 77/440 Soi Phoomjit, Rama IV Road 312 Phra Khanong, Khlong Toie 313 Bangkok 10110 314 Thailand 316 Phone: +66 (0) 87 502 4274 317 Email: gwz@net-zen.net 319 Qin Wu 320 Huawei 321 101 Software Avenue, Yuhua District 322 Nanjing, Jiangsu 210012 323 China 325 Email: sunseawq@huawei.com 327 Roland Schott 328 Deutsche Telekom 329 Deutsche-Telekom-Allee 7 330 Darmstadt 64295 331 Germany 333 Email: Roland.Schott@telekom.de