idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (November 26, 2012) is 4169 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: 'RFC2119' is defined on line 328, but no explicit reference was found in the text == Unused Reference: 'RFC6709' is defined on line 340, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Downref: Normative reference to an Informational RFC: RFC 6709 Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Audio/Video Transport Working Group A. Clark 3 Internet-Draft Telchemy 4 Intended status: Standards Track V. Singh 5 Expires: May 30, 2013 Aalto University 6 Q. Wu 7 Huawei 8 November 26, 2012 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer 11 Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-02.txt 14 Abstract 16 This document defines an RTP Control Protocol (RTCP) Extended Report 17 (XR) Block that allows the reporting of Jitter Buffer metrics for a 18 range of RTP applications. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on May 30, 2013. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . 3 56 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 57 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 58 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 4 60 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 61 2.2. Definition of Fields in Jitter Buffer Metrics Block . . . 4 62 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 63 3.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7 64 3.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 7 65 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 66 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 67 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 68 4.3. Contact information for registrations . . . . . . . . . . 8 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 70 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 10 71 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 74 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 75 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 76 A.1. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 13 77 A.2. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 13 78 A.3. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 13 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 81 1. Introduction 83 1.1. Jitter Buffer Metrics Block 85 This document defines a new block type to augment those defined in 86 [RFC3611], for use in a range of RTP applications. 88 The new block type provides information on jitter buffer 89 configuration and performance. 91 The metric belongs to the class of transport-related end system 92 metrics defined in [RFC6792]. 94 Instances of this Metrics Block refer by SSRC to the separate 95 auxiliary Measurement Information block [RFC6776] which contains 96 information such as the SSRC of the measured stream, and RTP sequence 97 numbers and time intervals indicating the span of the report. 99 1.2. RTCP and RTCP XR Reports 101 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 102 defined an extensible structure for reporting using an RTCP Extended 103 Report (XR). This document defines a new Extended Report block for 104 use with [RFC3550] and [RFC3611]. 106 1.3. Performance Metrics Framework 108 The Performance Metrics Framework [RFC6390] provides guidance on the 109 definition and specification of performance metrics. The RTP 110 Monitoring Architectures [RFC6792] provides guideline for reporting 111 block format using RTCP XR. Metrics described in this draft are in 112 accordance with the guidelines in [RFC6390][RFC6792]. 114 1.4. Applicability 116 Real-time applications employ a jitter buffer to smooth out jitter 117 encountered on the path from source to destination. These metrics 118 are used to measure how the jitter buffer behave as a result of the 119 jitter and applicable to a range of RTP applications. These metrics 120 reflect terminal related factor that most affects real-time 121 application quality and useful to provide more precise estimation for 122 user experience to the quality of real-time application performance 123 and also valuable to network manager in troubleshooting network. 125 2. Jitter Buffer Metrics Block 127 This block describes the configuration and operating parameters of 128 the jitter buffer in the receiver of the RTP end system or RTP mixer 129 which sends the report. Instances of this Metrics Block refer by 130 SSRC to the separate auxiliary Measurement Information block 131 [RFC6776] which contains measurement intervals. This metric block 132 relies on the measurement interval in the Measurement Information 133 block indicating the span of the report and should be sent in the 134 same compound RTCP packet as the measurement information block. If 135 the measurement interval is not received in the same compound RTCP 136 packet as this metric block, this metric block should be discarded. 138 2.1. Report Block Structure 140 JB Metrics Block 142 0 1 2 3 143 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 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | BT=NJB | I |jb cfg |rsv| block length=3 | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | SSRC of Source | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | JB nominal | JB maximum | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | JB high water mark | JB low water mark | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 Figure 1: Report Block Structure 156 2.2. Definition of Fields in Jitter Buffer Metrics Block 158 Block type (BT): 8 bits 160 A Jitter Buffer Metrics Report Block is identified by the constant 161 NJB. 163 [Note to RFC Editor: please replace NJB with the IANA provided 164 RTCP XR block type for this block.] 166 Interval Metric flag (I): 2 bits 168 This field is used to indicate whether the Jitter Buffer metrics 169 are Sampled, Interval or Cumulative metrics: 171 I=10: Interval Duration - the reported value applies to the 172 most recent measurement interval duration between successive 173 metrics reports. 175 I=11: Cumulative Duration - the reported value applies to the 176 accumulation period characteristic of cumulative measurements. 178 I=01: Sampled Value - the reported value is a sampled 179 instantaneous value. 181 Jitter Buffer Configuration (jb cfg): 4 bits 183 This field is used to identify the jitter buffer method in use at 184 the receiver, according to the following code: 186 bits 014-011 188 0 = Fixed jitter buffer 190 1 = Adaptive jitter buffer 192 Other values reserved 194 Reserved (rsv): 2 bits 196 These bits are reserved. They MUST be set to zero by senders 197 ignored by receivers (See RFC6709 section 4.2). 199 Block Length: 16 bits 201 The length of this report block in 32-bit words, minus one and 202 MUST be set to 3, in accordance with the definition of this field 203 in [RFC3611]. The block MUST be discarded if the block length is 204 set to a different value. 206 jitter buffer nominal delay (JB nominal): 16 bits 208 This is the current nominal jitter buffer delay in milliseconds, 209 which corresponds to the nominal jitter buffer delay for packets 210 that arrive exactly on time. It is calculated based on the time 211 for packets spent in the jitter buffer. This parameter MUST be 212 provided for both fixed and adaptive jitter buffer 213 implementations. 215 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 216 reported to indicate an over-range measurement. If the 217 measurement is unavailable, the value 0xFFFF SHOULD be reported. 219 jitter buffer maximum delay (JB maximum): 16 bits 221 This is the current maximum jitter buffer delay in milliseconds 222 which corresponds to the earliest arriving packet that would not 223 be discarded. In simple queue implementations this may correspond 224 to the nominal size. In adaptive jitter buffer implementations, 225 this value may dynamically. This parameter MUST be provided for 226 both fixed and adaptive jitter buffer implementations. 228 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 229 reported to indicate an over-range measurement. If the 230 measurement is unavailable, the value 0xFFFF SHOULD be reported. 232 jitter buffer high water mark (JB high water mark): 16 bits 234 This is the highest value of the jitter buffer nominal delay in 235 milliseconds which occurred at any time during the reporting 236 interval. 238 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 239 reported to indicate an over-range measurement. If the 240 measurement is unavailable, the value 0xFFFF SHOULD be reported. 242 jitter buffer low water mark (JB low water mark): 16 bits 244 This is the lowest value of the jitter buffer nominal delay in 245 milliseconds which occurred at any time during the reporting 246 interval. 248 If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be 249 reported to indicate an over-range measurement. If the 250 measurement is unavailable, the value 0xFFFF SHOULD be reported. 252 3. SDP Signaling 254 [RFC3611] defines the use of SDP (Session Description Protocol) 255 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 256 without prior signaling. 258 3.1. SDP rtcp-xr-attrib Attribute Extension 260 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 261 in [RFC3611] by providing an additional value of "xr-format" to 262 signal the use of the report block defined in this document. 264 xr-format =/ xr-jb-block 266 xr-jb-block = "jitter-bfr" 268 3.2. Offer/Answer Usage 270 When SDP is used in offer-answer context, the SDP Offer/Answer usage 271 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 272 applies. For detailed usage in Offer/Answer for unilateral 273 parameter, refer to section 5.2 of [RFC3611]. 275 4. IANA Considerations 277 New block types for RTCP XR are subject to IANA registration. For 278 general guidelines on IANA considerations for RTCP XR, refer to 279 [RFC3611]. 281 4.1. New RTCP XR Block Type value 283 This document assigns the block type value NJB in the IANA "RTCP XR 284 Block Type Registry" to the "JB Metrics Block". 286 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 287 XR block type for this block.] 289 4.2. New RTCP XR SDP Parameter 291 This document also registers a new parameter "jitter-bfr" in the 292 "RTCP XR SDP Parameters Registry". 294 4.3. Contact information for registrations 296 The contact information for the registrations is: 298 Qin Wu (sunseawq@huawei.com) 299 101 Software Avenue, Yuhua District 300 Nanjing, Jiangsu 210012 301 China 303 5. Security Considerations 305 It is believed that this proposed RTCP XR report block introduces no 306 new security considerations beyond those described in [RFC3611]. 307 This block does not provide per-packet statistics so the risk to 308 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 309 does not apply. 311 6. Contributors 313 Geoff Hunt wrote the initial draft of this document. 315 7. Acknowledgments 317 The authors gratefully acknowledge reviews and feedback provided by 318 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 319 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 320 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 321 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 322 Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. 324 8. References 326 8.1. Normative References 328 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 329 Requirement Levels", March 1997. 331 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 332 Applications", RFC 3550, July 2003. 334 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 335 Protocol Extended Reports (RTCP XR)", November 2003. 337 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 338 Description Protocol", July 2006. 340 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 341 Considerations for Protocol Extensions", RFC 6709, 342 September 2012. 344 8.2. Informative References 346 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 347 Development", RFC 6390, October 2011. 349 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 350 using SDES item and XR Block", RFC 6776, August 2012. 352 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 353 for RTP", RFC 6792, November 2012. 355 Appendix A. Change Log 357 Note to the RFC-Editor: please remove this section prior to 358 publication as an RFC. 360 A.1. draft-ietf-xrblock-rtcp-xr-jb-02 362 The following are the major changes to previous version : 364 o Add some explaination text in the SDP offer/answer section. 366 o Add some text in applicability section to explain the use to 367 report jitter buffer metrics. 369 o Other editorial change changes aligning with PDV,Delay draft. 371 A.2. draft-ietf-xrblock-rtcp-xr-jb-01 373 The following are the major changes to previous version : 375 o Outdated reference update 377 o Add one Editor notes to ask clarification on the use of reporting 378 jitter buffer metrics. 380 o Other Editorial changes. 382 A.3. draft-ietf-xrblock-rtcp-xr-jb-00 384 The following are the major changes to previous version : 386 o Boilerplate updates. 388 o references updates 390 o allocate 32 bit field in report block for SSRC 392 o Other editorial changes to get alignment with MONARCH draft. 394 Authors' Addresses 396 Alan Clark 397 Telchemy Incorporated 398 2905 Premiere Parkway, Suite 280 399 Duluth, GA 30097 400 USA 402 Email: alan.d.clark@telchemy.com 404 Varun Singh 405 Aalto University 406 School of Electrical Engineering 407 Otakaari 5 A 408 Espoo, FIN 02150 409 Finland 411 Email: varun@comnet.tkk.fi 413 Qin Wu 414 Huawei 415 101 Software Avenue, Yuhua District 416 Nanjing, Jiangsu 210012 417 China 419 Email: sunseawq@huawei.com