idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-11.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 (April 27, 2013) is 4017 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) -- Looks like a reference, but probably isn't: '1' on line 201 == Missing Reference: 'RFCXXXX' is mentioned on line 591, but not defined ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-17) exists of draft-ietf-xrblock-rtcp-xr-qoe-06 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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: October 29, 2013 Aalto University 6 Q. Wu 7 Huawei 8 April 27, 2013 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer 11 Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-11.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 October 29, 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 Operation . . . . . . . . . . . . . . . . . . . 5 62 3.1. Idealized Jitter Buffer . . . . . . . . . . . . . . . . . 5 63 3.2. Fixed Jitter Buffer . . . . . . . . . . . . . . . . . . . 6 64 3.3. Adaptive Jitter Buffer . . . . . . . . . . . . . . . . . . 6 65 4. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 7 66 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7 67 4.2. Definition of Fields in Jitter Buffer Metrics Block . . . 7 68 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 69 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 70 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 72 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12 73 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 74 6.3. Contact information for registrations . . . . . . . . . . 12 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 76 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 77 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 78 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 79 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 80 10.2. Informative References . . . . . . . . . . . . . . . . . . 16 81 Appendix A. Metrics represented using RFC6390 Template . . . . . 17 82 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20 83 B.1. draft-ietf-xrblock-rtcp-xr-jb-11 . . . . . . . . . . . . . 20 84 B.2. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 20 85 B.3. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 20 86 B.4. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 20 87 B.5. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 20 88 B.6. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 20 89 B.7. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 21 90 B.8. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 21 91 B.9. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 21 92 B.10. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 21 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 95 1. Introduction 97 1.1. Jitter Buffer Metrics Block 99 This document defines a new block type to augment those defined in 100 [RFC3611], for use in a range of RTP applications. 102 The new block type provides information on jitter buffer 103 configuration and performance. 105 The metric belongs to the class of transport-related end system 106 metrics defined in [RFC6792]. 108 Instances of this metrics block refer by Synchronization source 109 (SSRC) to the separate auxiliary Measurement Information block 110 [RFC6776] which contains information such as the SSRC of the measured 111 stream, and RTP sequence numbers and time intervals indicating the 112 span of the report. 114 1.2. RTCP and RTCP XR Reports 116 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 117 defines an extensible structure for reporting using an RTCP Extended 118 Report (XR). This document defines a new Extended Report block for 119 use with [RFC3550] and [RFC3611]. 121 1.3. Performance Metrics Framework 123 The Performance Metrics Framework [RFC6390] provides guidance on the 124 definition and specification of performance metrics. The RTP 125 Monitoring Architectures [RFC6792] provides guideline for reporting 126 block format using RTCP XR. Metrics described in this draft are in 127 accordance with the guidelines in [RFC6390]and [RFC6792]. 129 1.4. Applicability 131 Real-time applications employ a de-jitter buffer [RFC5481] to absorb 132 jitter introduced on the path from source to destination. These 133 metrics are used to report how the jitter buffer at the receiving end 134 of RTP stream behaves as a result of jitter in the network and are 135 applicable to a range of RTP applications. 137 These metrics are corresponding to terminal related factors that 138 affect real-time application quality and are useful to provide better 139 end-user quality of experience (QoE) when these terminal-related 140 factors are used as inputs to calculate QoE metrics [QMB]. 142 2. Terminology 144 2.1. Standards Language 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 148 document are to be interpreted as described in RFC 2119 [RFC2119]. 150 3. Jitter Buffer Operation 152 A jitter buffer is required to absorb delay variation in network 153 delivery of media packets. A jitter buffer works by holding media 154 data for a period of time after it is received and before it is 155 played out. Packets that arrive early are held in the jitter buffer 156 longer. If packets arrive too early they may be discarded if there 157 is no available jitter buffer space. If packets are delayed 158 excessively by the network they may be discarded if they miss their 159 playout time. 161 Overall user perceived delay = network round trip delay + local 162 (jitter buffer (nominal) delay + encoder serialization delay) + 163 remote (jitter buffer (nominal) delay + encoder serialization delay) 165 The jitter buffer can be considered as a time window with early edge 166 aligned with the delay corresponding to the earliest arriving packet 167 and late edge representing the maximum permissible delay before a 168 late arriving packet would be discarded. The delay applied to 169 packets that arrive on time or at their expected arrival time is 170 known as the Nominal Delay and this is equivalent to the time 171 difference/ buffer size difference between the on-time packets 172 insertion point and the point at which packets are read out. 174 The reference for the expected arrival time may, for example, be the 175 first packet in the session or the running average delay. If all 176 packets arrived at their expected arrival time, then every packet 177 would be held in the jitter buffer exactly the Nominal Delay. 179 The Jitter Buffer maximum delay is the delay that is applied to an 180 earliest arriving packet that is not discarded and corresponds to the 181 early edge of the jitter buffer time window. 183 3.1. Idealized Jitter Buffer 185 In practice jitter buffer implementations vary considerably however 186 they should behave in a manner conceptually consistent with an 187 idealized jitter buffer described as follows: 189 (i). Receive the first packet and delay playout by D ms. Keep 190 the RTP timestamp and receive time as a reference. 192 RTP TS[1] 194 receive time[1] 196 Assume that both are normalized in ticks. 198 (ii). Receive the next packet 200 (iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive 201 time[n] - receive time[1]. If r = t then the packet arrived on 202 time. If r < t then the packet arrived late and if r > t then the 203 packet arrived early. 205 (iv). Delay playout of packet by D + (r-t) 207 (v). Go back to (ii) 209 Note that this idealized implementation assumes that the sender's RTP 210 clock is synchronized to the clock in the receiver which is used to 211 timestamp packet arrivals. If there is no such inherent 212 synchronization, the system may need to use an adaptive jitter buffer 213 or other techniques to ensure reliable reception. 215 3.2. Fixed Jitter Buffer 217 A fixed jitter buffer lacks provision to track network condition and 218 has a fixed size and packets leaving the jitter buffer have a 219 constant delay. For fixed jitter buffer implementation, the nominal 220 delay is set to a constant value corresponding to the packets that 221 arrive at their expected arrival time while the maximum delay is set 222 to a constant value corresponding to the fixed size of the jitter 223 buffer. 225 3.3. Adaptive Jitter Buffer 227 An adaptive jitter buffer can adapt to the change in the network's 228 delay and has variable size or variable delay. It allows the nominal 229 delay to be set to a low value initially, to minimize user perceived 230 delay, however can automatically extend the late edge (and possibly 231 also retract the early edge) of buffer window if a significant 232 proportion of packets are arriving late (and hence being discarded). 234 4. Jitter Buffer Metrics Block 236 This block describes the configuration and operating parameters of 237 the jitter buffer in the receiver of the RTP end system or RTP mixer 238 which sends the report. Instances of this metrics block refer by 239 SSRC to the separate auxiliary Measurement Information Block 240 [RFC6776] which describes the measurement interval in use. This 241 metrics block relies on the measurement interval in the Measurement 242 Information Block indicating the span of the report and MUST be sent 243 in the same compound RTCP packet as the Measurement Information 244 Block. If the measurement interval is not received in the same 245 compound RTCP packet as this metrics block, this metrics block MUST 246 be discarded. 248 4.1. Report Block Structure 250 JB Metrics Block 252 0 1 2 3 253 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 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | BT=NJB | I |C| Rsvd. | block length=3 | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | SSRC of Source | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | JB nominal | JB maximum | 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 | JB high water mark | JB low water mark | 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 Figure 1: Report Block Structure 266 4.2. Definition of Fields in Jitter Buffer Metrics Block 268 Block type (BT): 8 bits 270 A Jitter Buffer Metrics Report Block is identified by the constant 271 NJB. 273 [Note to RFC Editor: please replace NJB with the IANA provided 274 RTCP XR block type for this block.] 276 Interval Metric flag (I): 2 bits 278 This field is used to indicate whether the Jitter Buffer metrics 279 are Sampled, Interval or Cumulative metrics: 281 I=01: Sampled Value - the reported value is a sampled 282 instantaneous value. 284 I=10: Interval Duration - the reported value applies to the 285 most recent measurement interval duration between successive 286 metrics reports. 288 I=11: Cumulative Duration - the reported value applies to the 289 accumulation period characteristic of cumulative measurements. 291 In this document, Jitter Buffer Metrics can only be sampled , and 292 cannot be measured over definite intervals. Also, the value I=00 293 is reserved for future use. Senders MUST NOT use the values I=00 294 or I=10 or I=11. If a block is received with I=00 or I=10 or 295 I=11, the receiver MUST discard the block. 297 Jitter Buffer Configuration (C): 1 bit 299 This field is used to identify the jitter buffer method in use at 300 the receiver, according to the following code: 302 0 = Fixed jitter buffer 304 1 = Adaptive jitter buffer 306 Reserved (Rsvd.): 5 bits 308 These bits are reserved. They MUST be set to zero by senders 309 ignored by receivers (See [RFC6709] section 4.2). 311 Block Length: 16 bits 313 The length of this report block in 32-bit words, minus one, in 314 accordance with the definition in [RFC3611]. This field MUST be 315 set to 3 to match the fixed length of the report block. 317 jitter buffer nominal delay (JB nominal): 16 bits 319 This is the current nominal jitter buffer delay in milliseconds, 320 which corresponds to the nominal jitter buffer delay for packets 321 that arrive exactly on time. It is calculated based on the time 322 spend in the jitter buffer for the packet that arrives exactly on 323 time. This parameter MUST be provided for both fixed and adaptive 324 jitter buffer implementations. 326 The measured value is unsigned value. If the measured value 327 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 328 over-range measurement. If the measurement is unavailable, the 329 value 0xFFFF MUST be reported. 331 jitter buffer maximum delay (JB maximum): 16 bits 333 This is the current maximum jitter buffer delay in milliseconds 334 which corresponds to the earliest arriving packet that would not 335 be discarded. It is calculated based on the time spent in the 336 jitter buffer for the earliest arriving packet In simple queue 337 implementations this may correspond to the size of the jitter 338 buffer. In adaptive jitter buffer implementations, this value may 339 vary dynamically. This parameter MUST be provided for both fixed 340 and adaptive jitter buffer implementations. 342 The measured value is unsigned value. If the measured value 343 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 344 over-range measurement. If the measurement is unavailable, the 345 value 0xFFFF MUST be reported. 347 jitter buffer high water mark (JB high water mark): 16 bits 349 This is the highest value of the jitter buffer nominal delay in 350 milliseconds which occurred at any time during the reporting 351 interval. This parameter MUST be provided for adaptive jitter 352 buffer implementations and its value MUST be set to JB maximum for 353 fixed jitter buffer implementations. 355 The measured value is unsigned value. If the measured value 356 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 357 over-range measurement. If the measurement is unavailable, the 358 value 0xFFFF MUST be reported. 360 jitter buffer low water mark (JB low water mark): 16 bits 362 This is the lowest value of the jitter buffer nominal delay in 363 milliseconds which occurred at any time during the reporting 364 interval. This parameter MUST be provided for adaptive jitter 365 buffer implementations and its value MUST be set to JB maximum for 366 fixed jitter buffer implementations. 368 The measured value is unsigned value. If the measured value 369 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 370 over-range measurement. If the measurement is unavailable, the 371 value 0xFFFF MUST be reported. 373 5. SDP Signaling 375 [RFC3611] defines the use of SDP (Session Description Protocol) 376 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 377 be used without prior signaling (see section 5 of RFC3611). 379 5.1. SDP rtcp-xr-attrib Attribute Extension 381 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 382 in [RFC3611] by providing an additional value of "xr-format" to 383 signal the use of the report block defined in this document. 385 xr-format =/ xr-jb-block 387 xr-jb-block = "jitter-buffer" 389 5.2. Offer/Answer Usage 391 When SDP is used in offer-answer context [RFC3264], the SDP Offer/ 392 Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute 393 parameters applies. For detailed usage of Offer/Answer for 394 unilateral parameter, refer to section 5.2 of [RFC3611]. 396 6. IANA Considerations 398 New block types for RTCP XR are subject to IANA registration. For 399 general guidelines on IANA considerations for RTCP XR, refer to 400 [RFC3611]. 402 6.1. New RTCP XR Block Type value 404 This document assigns the block type value NJB in the IANA "RTCP XR 405 Block Type Registry" to the "JB Metrics Block". 407 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 408 XR block type for this block.] 410 6.2. New RTCP XR SDP Parameter 412 This document also registers a new parameter "jitter-buffer" in the 413 "RTCP XR SDP Parameters Registry". 415 6.3. Contact information for registrations 417 The contact information for the registrations is: 419 Qin Wu (sunseawq@huawei.com) 420 101 Software Avenue, Yuhua District 421 Nanjing, Jiangsu 210012 422 China 424 7. Security Considerations 426 It is believed that this proposed RTCP XR report block introduces no 427 new security considerations beyond those described in [RFC3611]. 428 This block does not provide per-packet statistics so the risk to 429 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 430 does not apply. 432 8. Contributors 434 Geoff Hunt wrote the initial draft of this document. 436 9. Acknowledgments 438 The authors gratefully acknowledge reviews and feedback provided by 439 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 440 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 441 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 442 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 443 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin 444 Perkin, Dan Romascanu, Kevin Gross and Glen Zorn. 446 10. References 448 10.1. Normative References 450 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 451 Requirement Levels", March 1997. 453 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 454 with the Session Description Protocol (SDP)", RFC 3264, 455 June 2002. 457 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 458 Applications", RFC 3550, July 2003. 460 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 461 Protocol Extended Reports (RTCP XR)", November 2003. 463 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 464 Description Protocol", July 2006. 466 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 467 using SDES item and XR Block", RFC 6776, August 2012. 469 10.2. Informative References 471 [QMB] Clark, A., "RTP Control Protocol (RTCP) Extended Report 472 (XR) Blocks for QoE Metric Reporting", 473 ID draft-ietf-xrblock-rtcp-xr-qoe-06, February 2013. 475 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 476 Applicability Statement", RFC 5481, March 2009. 478 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 479 Development", RFC 6390, October 2011. 481 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 482 Considerations for Protocol Extensions", RFC 6709, 483 September 2012. 485 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 486 for RTP", RFC 6792, November 2012. 488 Appendix A. Metrics represented using RFC6390 Template 490 RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC 491 number, when assigned. 493 a. jitter buffer nominal delay Metric 495 * Metric Name: jitter buffer nominal delay in RTP 497 * Metric Description: The "expected arrival time" is the time 498 that a RTP packet would arrive if there was no delay 499 variation. The delay applied to packets that arrive at their 500 expected time is known as the Nominal Delay. 502 * Method of Measurement or Calculation: See section 4.2, jitter 503 buffer nominal delay definition [RFCXXXX]. 505 * Units of Measurement: See section 4.2, jitter buffer nominal 506 delay definition [RFCXXXX]. 508 * Measurement Point(s) with Potential Measurement Domain: See 509 section 4, 1st paragraph [RFCXXXX]. 511 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 512 measurement timing and section 4.2 paragraph [RFCXXXX] for 513 Interval Metric flag. 515 * Use and applications: See section 1.4 [RFCXXXX]. 517 * Reporting model: See RFC3611. 519 b. jitter buffer maximum delay Metric 521 * Metric Name: jitter buffer maximum delay in RTP 523 * Metric Description: It is the current maximum jitter buffer 524 delay for RTP traffic which corresponds to the earliest 525 arriving packet that would not be discarded. 527 * Method of Measurement or Calculation: See section 4.2, jitter 528 buffer maximum delay definition and section 3, the last 529 paragraph [RFCXXXX]. 531 * Units of Measurement: See section 4.2, jitter buffer maximum 532 delay definition [RFCXXXX]. 534 * Measurement Point(s) with Potential Measurement Domain: See 535 section 4, 1st paragraph [RFCXXXX]. 537 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 538 measurement timing and section 4.2 paragraph [RFCXXXX] for 539 Interval Metric flag. 541 * Use and applications: See section 1.4 [RFCXXXX]. 543 * Reporting model: See RFC3611. 545 c. jitter buffer high water mark Metric 547 * Metric Name: jitter buffer high water mark in RTP 549 * Metric Description: It is the highest value of the jitter 550 buffer nominal delay for RTP traffic which occurred at any 551 time during the reporting interval. 553 * Method of Measurement or Calculation: See section 4.2, jitter 554 buffer high water mark definition [RFCXXXX]. 556 * Units of Measurement: See section 4.2, jitter buffer nominal 557 delay definition [RFCXXXX]. 559 * Measurement Point(s) with Potential Measurement Domain: See 560 section 4, 1st paragraph [RFCXXXX]. 562 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 563 measurement timing and section 4.2 paragraph [RFCXXXX] for 564 Interval Metric flag. 566 * Use and applications: See section 1.4 [RFCXXXX]. 568 * Reporting model: See RFC3611. 570 d. jitter buffer low water mark Metric 572 * Metric Name: jitter buffer low water mark in RTP 574 * Metric Description: It is the lowest value of the jitter 575 buffer nominal delay for RTP traffic which occurred at any 576 time during the reporting interval. 578 * Method of Measurement or Calculation: See section 4.2, jitter 579 buffer low water mark definition [RFCXXXX]. 581 * Units of Measurement: See section 4.2, jitter buffer low water 582 mark definition [RFCXXXX]. 584 * Measurement Point(s) with Potential Measurement Domain: See 585 section 4, 1st paragraph [RFCXXXX]. 587 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 588 measurement timing and section 4.2 paragraph [RFCXXXX] for 589 Interval Metric flag. 591 * Use and applications: See section 1.4 [RFCXXXX]. 593 * Reporting model: See RFC3611. 595 Appendix B. Change Log 597 Note to the RFC-Editor: please remove this section prior to 598 publication as an RFC. 600 B.1. draft-ietf-xrblock-rtcp-xr-jb-11 602 The following are the major changes to previous version : 604 o Comments in WGLC and from PM-DIR review are addressed in this 605 version. 607 B.2. draft-ietf-xrblock-rtcp-xr-jb-10 609 The following are the major changes to previous version : 611 o Add some text to section 3.2 to clarify how fixed jitter buffer is 612 used. 614 o Other Editorial changes. 616 B.3. draft-ietf-xrblock-rtcp-xr-jb-09 618 The following are the major changes to previous version : 620 o Incorporate proposed changes by Kevin and proposed text by Alan to 621 address interoperability report issue. 623 o Add new appendix to format metrics using RFC6390 template. 625 B.4. draft-ietf-xrblock-rtcp-xr-jb-08 627 The following are the major changes to previous version : 629 o Rewrote descriptive text and definitions for clarification. 631 B.5. draft-ietf-xrblock-rtcp-xr-jb-07 633 The following are the major changes to previous version : 635 o Add one new section to discuss jitter buffer operation. 637 B.6. draft-ietf-xrblock-rtcp-xr-jb-05 639 The following are the major changes to previous version : 641 o Some editorial change changes based on the discussion with Glen 642 and Kevin on the list. 644 B.7. draft-ietf-xrblock-rtcp-xr-jb-03 646 The following are the major changes to previous version : 648 o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. 650 o Other editorial change changes aligning with PDV,Delay draft. 652 B.8. draft-ietf-xrblock-rtcp-xr-jb-02 654 The following are the major changes to previous version : 656 o Add some explanation text in the SDP offer/answer section. 658 o Add some text in applicability section to explain the use to 659 report jitter buffer metrics. 661 o Other editorial change changes aligning with PDV,Delay draft. 663 B.9. draft-ietf-xrblock-rtcp-xr-jb-01 665 The following are the major changes to previous version : 667 o Outdated reference update 669 o Add one Editor notes to ask clarification on the use of reporting 670 jitter buffer metrics. 672 o Other Editorial changes. 674 B.10. draft-ietf-xrblock-rtcp-xr-jb-00 676 The following are the major changes to previous version : 678 o Boilerplate updates. 680 o references updates 682 o allocate 32 bit field in report block for SSRC 684 o Other editorial changes to get alignment with MONARCH draft. 686 Authors' Addresses 688 Alan Clark 689 Telchemy Incorporated 690 2905 Premiere Parkway, Suite 280 691 Duluth, GA 30097 692 USA 694 Email: alan.d.clark@telchemy.com 696 Varun Singh 697 Aalto University 698 School of Electrical Engineering 699 Otakaari 5 A 700 Espoo, FIN 02150 701 Finland 703 Email: varun@comnet.tkk.fi 705 Qin Wu 706 Huawei 707 101 Software Avenue, Yuhua District 708 Nanjing, Jiangsu 210012 709 China 711 Email: sunseawq@huawei.com