idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-03.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 (December 14, 2012) is 4143 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) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Downref: Normative reference to an Informational RFC: RFC 6709 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 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: June 17, 2013 Aalto University 6 Q. Wu 7 Huawei 8 December 14, 2012 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer 11 Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-03.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 June 17, 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 61 3. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 5 62 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 63 3.2. Definition of Fields in Jitter Buffer Metrics Block . . . 5 64 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 65 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8 66 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 68 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 69 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 70 5.3. Contact information for registrations . . . . . . . . . . 9 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 72 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 73 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 75 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 76 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 77 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 78 A.1. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 14 79 A.2. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 14 80 A.3. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 14 81 A.4. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 14 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 84 1. Introduction 86 1.1. Jitter Buffer Metrics Block 88 This document 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 information on jitter buffer 92 configuration and performance. 94 The metric belongs to the class of transport-related end system 95 metrics defined in [RFC6792]. 97 Instances of this Metrics Block refer by SSRC to the separate 98 auxiliary Measurement Information block [RFC6776] which contains 99 information such as the SSRC of the measured stream, and RTP sequence 100 numbers and time intervals indicating the span of the report. 102 1.2. RTCP and RTCP XR Reports 104 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 105 defined an extensible structure for reporting using an RTCP Extended 106 Report (XR). This document defines a new Extended Report block for 107 use with [RFC3550] and [RFC3611]. 109 1.3. Performance Metrics Framework 111 The Performance Metrics Framework [RFC6390] provides guidance on the 112 definition and specification of performance metrics. The RTP 113 Monitoring Architectures [RFC6792] provides guideline for reporting 114 block format using RTCP XR. Metrics described in this draft are in 115 accordance with the guidelines in [RFC6390][RFC6792]. 117 1.4. Applicability 119 Real-time applications employ a jitter buffer to smooth out jitter 120 encountered on the path from source to destination. These metrics 121 are used to measure how the jitter buffer behave as a result of the 122 jitter and applicable to a range of RTP applications. These metrics 123 reflect terminal related factor that most affects real-time 124 application quality and useful to provide more precise estimation for 125 user experience to the quality of real-time application performance 126 and also valuable to network manager in troubleshooting network. 128 2. Terminology 130 2.1. Standards Language 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 134 document are to be interpreted as described in RFC 2119 [RFC2119]. 136 3. Jitter Buffer Metrics Block 138 This block describes the configuration and operating parameters of 139 the jitter buffer in the receiver of the RTP end system or RTP mixer 140 which sends the report. Instances of this Metrics Block refer by 141 SSRC to the separate auxiliary Measurement Information block 142 [RFC6776] which contains measurement intervals. This metric block 143 relies on the measurement interval in the Measurement Information 144 block indicating the span of the report and should be sent in the 145 same compound RTCP packet as the measurement information block. If 146 the measurement interval is not received in the same compound RTCP 147 packet as this metric block, this metric block should be discarded. 149 3.1. Report Block Structure 151 JB Metrics Block 153 0 1 2 3 154 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 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | BT=NJB | I |C|Reserved | block length=3 | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | SSRC of Source | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | JB nominal | JB maximum | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | JB high water mark | JB low water mark | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 Figure 1: Report Block Structure 167 3.2. Definition of Fields in Jitter Buffer Metrics Block 169 Block type (BT): 8 bits 171 A Jitter Buffer Metrics Report Block is identified by the constant 172 NJB. 174 [Note to RFC Editor: please replace NJB with the IANA provided 175 RTCP XR block type for this block.] 177 Interval Metric flag (I): 2 bits 179 This field is used to indicate whether the Jitter Buffer metrics 180 are Sampled, Interval or Cumulative metrics: 182 I=10: Interval Duration - the reported value applies to the 183 most recent measurement interval duration between successive 184 metrics reports. 186 I=11: Cumulative Duration - the reported value applies to the 187 accumulation period characteristic of cumulative measurements. 189 I=01: Sampled Value - the reported value is a sampled 190 instantaneous value. 192 Jitter Buffer Configuration (C): 1 bit 194 This field is used to identify the jitter buffer method in use at 195 the receiver, according to the following code: 197 0 = Fixed jitter buffer 199 1 = Adaptive jitter buffer 201 Reserved: 5 bits 203 These bits are reserved. They MUST be set to zero by senders 204 ignored by receivers (See [RFC6709] section 4.2). 206 Block Length: 16 bits 208 The length of this report block in 32-bit words, minus one and 209 MUST be set to 3, in accordance with the definition of this field 210 in [RFC3611]. The block MUST be discarded if the block length is 211 set to a different value. 213 jitter buffer nominal delay (JB nominal): 16 bits 215 This is the current nominal jitter buffer delay in milliseconds, 216 which corresponds to the nominal jitter buffer delay for packets 217 that arrive exactly on time. It is calculated based on the time 218 for packets spent in the jitter buffer. This parameter MUST be 219 provided for both fixed and adaptive jitter buffer 220 implementations. 222 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 223 reported to indicate an over-range measurement. If the 224 measurement is unavailable, the value 0xFFFF MUST be reported. 226 jitter buffer maximum delay (JB maximum): 16 bits 228 This is the current maximum jitter buffer delay in milliseconds 229 which corresponds to the earliest arriving packet that would not 230 be discarded. In simple queue implementations this may correspond 231 to the nominal size. In adaptive jitter buffer implementations, 232 this value may change dynamically. This parameter MUST be 233 provided for both fixed and adaptive jitter buffer 234 implementations. 236 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 237 reported to indicate an over-range measurement. If the 238 measurement is unavailable, the value 0xFFFF MUST be reported. 240 jitter buffer high water mark (JB high water mark): 16 bits 242 This is the highest value of the jitter buffer nominal delay in 243 milliseconds which occurred at any time during the reporting 244 interval. 246 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 247 reported to indicate an over-range measurement. If the 248 measurement is unavailable, the value 0xFFFF MUST be reported. 250 jitter buffer low water mark (JB low water mark): 16 bits 252 This is the lowest value of the jitter buffer nominal delay in 253 milliseconds which occurred at any time during the reporting 254 interval. 256 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 257 reported to indicate an over-range measurement. If the 258 measurement is unavailable, the value 0xFFFF MUST be reported. 260 4. SDP Signaling 262 [RFC3611] defines the use of SDP (Session Description Protocol) 263 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 264 without prior signaling. 266 4.1. SDP rtcp-xr-attrib Attribute Extension 268 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 269 in [RFC3611] by providing an additional value of "xr-format" to 270 signal the use of the report block defined in this document. 272 xr-format =/ xr-jb-block 274 xr-jb-block = "jitter-bfr" 276 4.2. Offer/Answer Usage 278 When SDP is used in offer-answer context, the SDP Offer/Answer usage 279 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 280 applies. For detailed usage in Offer/Answer for unilateral 281 parameter, refer to section 5.2 of [RFC3611]. 283 5. IANA Considerations 285 New block types for RTCP XR are subject to IANA registration. For 286 general guidelines on IANA considerations for RTCP XR, refer to 287 [RFC3611]. 289 5.1. New RTCP XR Block Type value 291 This document assigns the block type value NJB in the IANA "RTCP XR 292 Block Type Registry" to the "JB Metrics Block". 294 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 295 XR block type for this block.] 297 5.2. New RTCP XR SDP Parameter 299 This document also registers a new parameter "jitter-bfr" in the 300 "RTCP XR SDP Parameters Registry". 302 5.3. Contact information for registrations 304 The contact information for the registrations is: 306 Qin Wu (sunseawq@huawei.com) 307 101 Software Avenue, Yuhua District 308 Nanjing, Jiangsu 210012 309 China 311 6. Security Considerations 313 It is believed that this proposed RTCP XR report block introduces no 314 new security considerations beyond those described in [RFC3611]. 315 This block does not provide per-packet statistics so the risk to 316 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 317 does not apply. 319 7. Contributors 321 Geoff Hunt wrote the initial draft of this document. 323 8. Acknowledgments 325 The authors gratefully acknowledge reviews and feedback provided by 326 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 327 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 328 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 329 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 330 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin 331 Perkin and Dan Romascanu. 333 9. References 335 9.1. Normative References 337 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 338 Requirement Levels", March 1997. 340 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 341 Applications", RFC 3550, July 2003. 343 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 344 Protocol Extended Reports (RTCP XR)", November 2003. 346 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 347 Description Protocol", July 2006. 349 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 350 Considerations for Protocol Extensions", RFC 6709, 351 September 2012. 353 9.2. Informative References 355 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 356 Development", RFC 6390, October 2011. 358 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 359 using SDES item and XR Block", RFC 6776, August 2012. 361 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 362 for RTP", RFC 6792, November 2012. 364 Appendix A. Change Log 366 Note to the RFC-Editor: please remove this section prior to 367 publication as an RFC. 369 A.1. draft-ietf-xrblock-rtcp-xr-jb-03 371 The following are the major changes to previous version : 373 o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. 375 o Other editorial change changes aligning with PDV,Delay draft. 377 A.2. draft-ietf-xrblock-rtcp-xr-jb-02 379 The following are the major changes to previous version : 381 o Add some explaination text in the SDP offer/answer section. 383 o Add some text in applicability section to explain the use to 384 report jitter buffer metrics. 386 o Other editorial change changes aligning with PDV,Delay draft. 388 A.3. draft-ietf-xrblock-rtcp-xr-jb-01 390 The following are the major changes to previous version : 392 o Outdated reference update 394 o Add one Editor notes to ask clarification on the use of reporting 395 jitter buffer metrics. 397 o Other Editorial changes. 399 A.4. draft-ietf-xrblock-rtcp-xr-jb-00 401 The following are the major changes to previous version : 403 o Boilerplate updates. 405 o references updates 407 o allocate 32 bit field in report block for SSRC 409 o Other editorial changes to get alignment with MONARCH draft. 411 Authors' Addresses 413 Alan Clark 414 Telchemy Incorporated 415 2905 Premiere Parkway, Suite 280 416 Duluth, GA 30097 417 USA 419 Email: alan.d.clark@telchemy.com 421 Varun Singh 422 Aalto University 423 School of Electrical Engineering 424 Otakaari 5 A 425 Espoo, FIN 02150 426 Finland 428 Email: varun@comnet.tkk.fi 430 Qin Wu 431 Huawei 432 101 Software Avenue, Yuhua District 433 Nanjing, Jiangsu 210012 434 China 436 Email: sunseawq@huawei.com