idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-06.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 (January 10, 2013) is 4116 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: July 14, 2013 Aalto University 6 Q. Wu 7 Huawei 8 January 10, 2013 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer 11 Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-06.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 July 14, 2013. 37 Copyright Notice 39 Copyright (c) 2013 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-05 . . . . . . . . . . . . . 14 79 A.2. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 14 80 A.3. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 14 81 A.4. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 14 82 A.5. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 14 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 85 1. Introduction 87 1.1. Jitter Buffer Metrics Block 89 This document defines a new block type to augment those defined in 90 [RFC3611], for use in a range of RTP applications. 92 The new block type provides information on jitter buffer 93 configuration and performance. 95 The metric belongs to the class of transport-related end system 96 metrics defined in [RFC6792]. 98 Instances of this Metrics Block refer by Synchronization source 99 (SSRC) to the separate auxiliary Measurement Information block 100 [RFC6776] which contains information such as the SSRC of the measured 101 stream, and RTP sequence numbers and time intervals indicating the 102 span of the report. 104 1.2. RTCP and RTCP XR Reports 106 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 107 defines an extensible structure for reporting using an RTCP Extended 108 Report (XR). This document defines a new Extended Report block for 109 use with [RFC3550] and [RFC3611]. 111 1.3. Performance Metrics Framework 113 The Performance Metrics Framework [RFC6390] provides guidance on the 114 definition and specification of performance metrics. The RTP 115 Monitoring Architectures [RFC6792] provides guideline for reporting 116 block format using RTCP XR. Metrics described in this draft are in 117 accordance with the guidelines in [RFC6390]and [RFC6792]. 119 1.4. Applicability 121 Real-time applications employ a jitter buffer to absorb jitter 122 introduced on the path from source to destination. These metrics are 123 used to report how the jitter buffer at the receiving end of RTP 124 stream behaves as a result of jitter in the network and are 125 applicable to a range of RTP applications. 127 These metrics reflect how terminal-related factors affect real-time 128 application quality and are useful to provide better end-user quality 129 of experience (QoE). 131 2. Terminology 133 2.1. Standards Language 135 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 136 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 137 document are to be interpreted as described in RFC 2119 [RFC2119]. 139 3. Jitter Buffer Metrics Block 141 This block describes the configuration and operating parameters of 142 the jitter buffer in the receiver of the RTP end system or RTP mixer 143 which sends the report. Instances of this Metrics Block refer by 144 SSRC to the separate auxiliary Measurement Information block 145 [RFC6776] which describes the measurement interval in use. This 146 Metrics Block relies on the measurement interval in the Measurement 147 Information block indicating the span of the report and should be 148 sent in the same compound RTCP packet as the measurement information 149 block. If the measurement interval is not received in the same 150 compound RTCP packet as this Metrics Block, this Metrics Block should 151 be discarded. 153 3.1. Report Block Structure 155 JB Metrics Block 157 0 1 2 3 158 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 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | BT=NJB | I |C| Rsvd. | block length=3 | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | SSRC of Source | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | JB nominal | JB maximum | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | JB high water mark | JB low water mark | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 Figure 1: Report Block Structure 171 3.2. Definition of Fields in Jitter Buffer Metrics Block 173 Block type (BT): 8 bits 175 A Jitter Buffer Metrics Report Block is identified by the constant 176 NJB. 178 [Note to RFC Editor: please replace NJB with the IANA provided 179 RTCP XR block type for this block.] 181 Interval Metric flag (I): 2 bits 183 This field is used to indicate whether the Jitter Buffer metrics 184 are Sampled, Interval or Cumulative metrics: 186 I=10: Interval Duration - the reported value applies to the 187 most recent measurement interval duration between successive 188 metrics reports. 190 I=11: Cumulative Duration - the reported value applies to the 191 accumulation period characteristic of cumulative measurements. 193 I=01: Sampled Value - the reported value is a sampled 194 instantaneous value. 196 Jitter Buffer Configuration (C): 1 bit 198 This field is used to identify the jitter buffer method in use at 199 the receiver, according to the following code: 201 0 = Fixed jitter buffer 203 1 = Adaptive jitter buffer 205 Reserved (Rsvd.): 5 bits 207 These bits are reserved. They MUST be set to zero by senders 208 ignored by receivers (See [RFC6709] section 4.2). 210 Block Length: 16 bits 212 The length of this report block in 32-bit words, minus one, in 213 accordance with the definition in [RFC3611]. This field MUST be 214 set to 3 to match the fixed length of the report block. 216 jitter buffer nominal delay (JB nominal): 16 bits 218 This is the current nominal jitter buffer delay in milliseconds, 219 which corresponds to the nominal jitter buffer delay for packets 220 that arrive exactly on time. It is calculated based on the 221 difference between the receipt time and the playout time for the 222 packet that arrives exactly on time. This parameter MUST be 223 provided for both fixed and adaptive jitter buffer 224 implementations. 226 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 227 reported to indicate an over-range measurement. If the 228 measurement is unavailable, the value 0xFFFF MUST be reported. 230 jitter buffer maximum delay (JB maximum): 16 bits 232 This is the current maximum jitter buffer delay in milliseconds 233 which corresponds to the earliest arriving packet that would not 234 be discarded. It is calculated based on the difference between 235 the receipt time and the playout time for the earliest arriving 236 packet. In simple queue implementations this may correspond to 237 the size of the jitter buffer. In adaptive jitter buffer 238 implementations, this value may vary dynamically from JB low water 239 mark to JB high water mark (See below). This parameter MUST be 240 provided for both fixed and adaptive jitter buffer 241 implementations. 243 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 244 reported to indicate an over-range measurement. If the 245 measurement is unavailable, the value 0xFFFF MUST be reported. 247 jitter buffer high water mark (JB high water mark): 16 bits 249 This is the highest value of the jitter buffer nominal delay in 250 milliseconds which occurred at any time during the reporting 251 interval. This parameter MUST be provided for adaptive jitter 252 buffer implementations and its value MUST be set to JB maximum for 253 fixed jitter buffer implementations. 255 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 256 reported to indicate an over-range measurement. If the 257 measurement is unavailable, the value 0xFFFF MUST be reported. 259 jitter buffer low water mark (JB low water mark): 16 bits 261 This is the lowest value of the jitter buffer nominal delay in 262 milliseconds which occurred at any time during the reporting 263 interval. This parameter MUST be provided for adaptive jitter 264 buffer implementations and its value MUST be set to JB maximum for 265 fixed jitter buffer implementations. 267 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 268 reported to indicate an over-range measurement. If the 269 measurement is unavailable, the value 0xFFFF MUST be reported. 271 4. SDP Signaling 273 [RFC3611] defines the use of SDP (Session Description Protocol) 274 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 275 be used without prior signaling (see section 5 of RFC3611). 277 4.1. SDP rtcp-xr-attrib Attribute Extension 279 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 280 in [RFC3611] by providing an additional value of "xr-format" to 281 signal the use of the report block defined in this document. 283 xr-format =/ xr-jb-block 285 xr-jb-block = "jitter-bfr" 287 4.2. Offer/Answer Usage 289 When SDP is used in offer-answer context, the SDP Offer/Answer usage 290 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 291 applies. For detailed usage of Offer/Answer for unilateral 292 parameter, refer to section 5.2 of [RFC3611]. 294 5. IANA Considerations 296 New block types for RTCP XR are subject to IANA registration. For 297 general guidelines on IANA considerations for RTCP XR, refer to 298 [RFC3611]. 300 5.1. New RTCP XR Block Type value 302 This document assigns the block type value NJB in the IANA "RTCP XR 303 Block Type Registry" to the "JB Metrics Block". 305 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 306 XR block type for this block.] 308 5.2. New RTCP XR SDP Parameter 310 This document also registers a new parameter "jitter-bfr" in the 311 "RTCP XR SDP Parameters Registry". 313 5.3. Contact information for registrations 315 The contact information for the registrations is: 317 Qin Wu (sunseawq@huawei.com) 318 101 Software Avenue, Yuhua District 319 Nanjing, Jiangsu 210012 320 China 322 6. Security Considerations 324 It is believed that this proposed RTCP XR report block introduces no 325 new security considerations beyond those described in [RFC3611]. 326 This block does not provide per-packet statistics so the risk to 327 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 328 does not apply. 330 7. Contributors 332 Geoff Hunt wrote the initial draft of this document. 334 8. Acknowledgments 336 The authors gratefully acknowledge reviews and feedback provided by 337 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 338 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 339 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 340 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 341 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin 342 Perkin, Dan Romascanu, Kevin Gross and Glen Zorn. 344 9. References 346 9.1. Normative References 348 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 349 Requirement Levels", March 1997. 351 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 352 Applications", RFC 3550, July 2003. 354 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 355 Protocol Extended Reports (RTCP XR)", November 2003. 357 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 358 Description Protocol", July 2006. 360 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 361 Considerations for Protocol Extensions", RFC 6709, 362 September 2012. 364 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 365 using SDES item and XR Block", RFC 6776, August 2012. 367 9.2. Informative References 369 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 370 Development", RFC 6390, October 2011. 372 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 373 for RTP", RFC 6792, November 2012. 375 Appendix A. Change Log 377 Note to the RFC-Editor: please remove this section prior to 378 publication as an RFC. 380 A.1. draft-ietf-xrblock-rtcp-xr-jb-05 382 The following are the major changes to previous version : 384 o Some editorial change changes based on the discussion with Glen 385 and Kevin on the list. 387 A.2. draft-ietf-xrblock-rtcp-xr-jb-03 389 The following are the major changes to previous version : 391 o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. 393 o Other editorial change changes aligning with PDV,Delay draft. 395 A.3. draft-ietf-xrblock-rtcp-xr-jb-02 397 The following are the major changes to previous version : 399 o Add some explanation text in the SDP offer/answer section. 401 o Add some text in applicability section to explain the use to 402 report jitter buffer metrics. 404 o Other editorial change changes aligning with PDV,Delay draft. 406 A.4. draft-ietf-xrblock-rtcp-xr-jb-01 408 The following are the major changes to previous version : 410 o Outdated reference update 412 o Add one Editor notes to ask clarification on the use of reporting 413 jitter buffer metrics. 415 o Other Editorial changes. 417 A.5. draft-ietf-xrblock-rtcp-xr-jb-00 419 The following are the major changes to previous version : 421 o Boilerplate updates. 423 o references updates 425 o allocate 32 bit field in report block for SSRC 427 o Other editorial changes to get alignment with MONARCH draft. 429 Authors' Addresses 431 Alan Clark 432 Telchemy Incorporated 433 2905 Premiere Parkway, Suite 280 434 Duluth, GA 30097 435 USA 437 Email: alan.d.clark@telchemy.com 439 Varun Singh 440 Aalto University 441 School of Electrical Engineering 442 Otakaari 5 A 443 Espoo, FIN 02150 444 Finland 446 Email: varun@comnet.tkk.fi 448 Qin Wu 449 Huawei 450 101 Software Avenue, Yuhua District 451 Nanjing, Jiangsu 210012 452 China 454 Email: sunseawq@huawei.com