idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-13.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 (June 28, 2013) is 3948 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 198 == 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-08 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: December 30, 2013 Aalto University 6 Q. Wu 7 Huawei 8 June 28, 2013 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for De-Jitter 11 Buffer Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-13.txt 14 Abstract 16 This document defines an RTP Control Protocol (RTCP) Extended Report 17 (XR) Block that allows the reporting of De-Jitter Buffer metrics for 18 a 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 December 30, 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. De-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. De-Jitter Buffer Operation . . . . . . . . . . . . . . . . . . 5 62 3.1. Idealized De-Jitter Buffer . . . . . . . . . . . . . . . . 5 63 3.2. Fixed De-Jitter Buffer . . . . . . . . . . . . . . . . . . 6 64 3.3. Adaptive De-Jitter Buffer . . . . . . . . . . . . . . . . 6 65 4. De-Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . 7 66 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7 67 4.2. Definition of Fields in De-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-12 . . . . . . . . . . . . . 20 84 B.2. draft-ietf-xrblock-rtcp-xr-jb-11 . . . . . . . . . . . . . 20 85 B.3. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 20 86 B.4. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 20 87 B.5. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 20 88 B.6. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 20 89 B.7. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 21 90 B.8. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 21 91 B.9. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 21 92 B.10. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 21 93 B.11. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 21 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 96 1. Introduction 98 1.1. De-Jitter Buffer Metrics Block 100 This document defines a new block type to augment those defined in 101 [RFC3611], for use in a range of RTP applications. 103 The new block type provides information on jitter buffer 104 configuration and performance. 106 The metric belongs to the class of transport-related end system 107 metrics defined in [RFC6792]. 109 Instances of this metrics block refer by Synchronization source 110 (SSRC) to the separate auxiliary Measurement Information block 111 [RFC6776] which contains information such as the SSRC of the measured 112 stream, and RTP sequence numbers and time intervals indicating the 113 span of the report. 115 1.2. RTCP and RTCP XR Reports 117 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 118 defines an extensible structure for reporting using an RTCP Extended 119 Report (XR). This document defines a new Extended Report block for 120 use with [RFC3550] and [RFC3611]. 122 1.3. Performance Metrics Framework 124 The Performance Metrics Framework [RFC6390] provides guidance on the 125 definition and specification of performance metrics. The RTP 126 Monitoring Architectures [RFC6792] provides guideline for reporting 127 block format using RTCP XR. Metrics described in this draft are in 128 accordance with the guidelines in [RFC6390]and [RFC6792]. 130 1.4. Applicability 132 Real-time applications employ a de-de-jitter buffer [RFC5481] to 133 absorb jitter introduced on the path from source to destination. 134 These metrics are used to report how the de-jitter buffer at the 135 receiving end of RTP stream behaves as a result of jitter in the 136 network; and they are applicable to a range of RTP applications. 138 These metrics are corresponding to terminal related factors that 139 affect real-time application quality and are useful to provide better 140 end-user quality of experience (QoE) when these terminal-related 141 factors are used as inputs to calculate QoE metrics [QMB]. 143 2. Terminology 145 2.1. Standards Language 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 149 document are to be interpreted as described in RFC 2119 [RFC2119]. 151 3. De-Jitter Buffer Operation 153 A de-jitter buffer is required to absorb delay variation in network 154 delivery of media packets. A de-jitter buffer works by holding media 155 data for a period of time after it is received and before it is 156 played out. Packets that arrive early are held in the de-jitter 157 buffer longer. If packets arrive too early they may be discarded if 158 there is no available de-jitter buffer space. If packets are delayed 159 excessively by the network they may be discarded if they miss their 160 playout time. 162 The de-jitter buffer can be considered as a time window with early 163 edge aligned with the delay corresponding to the earliest arriving 164 packet and late edge representing the maximum permissible delay 165 before a late arriving packet would be discarded. The delay applied 166 to packets that arrive on time or at their expected arrival time is 167 known as the Nominal Delay and this is equivalent to the time 168 difference/ buffer size difference between the on-time packets 169 insertion point and the point at which packets are read out. 171 The reference for the expected arrival time may, for example, be the 172 first packet in the session or the running average delay. If all 173 packets arrived at their expected arrival time, then every packet 174 would be held in the de-jitter buffer exactly the Nominal Delay. 176 The de-jitter buffer maximum delay is the delay that is applied to an 177 earliest arriving packet that is not discarded and corresponds to the 178 early edge of the de-jitter buffer time window. 180 3.1. Idealized De-Jitter Buffer 182 In practice de-jitter buffer implementations vary considerably 183 however they should behave in a manner conceptually consistent with 184 an idealized de-jitter buffer described as follows: 186 (i). Receive the first packet and delay playout by D ms. Keep 187 the RTP timestamp and receive time as a reference. 189 RTP Timestamp(TS)[1] 191 receive time[1] 193 Assume that both are normalized in ticks (there are 10 000 ticks 194 in a millisecond). 196 (ii). Receive the next packet 197 (iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive 198 time[n] - receive time[1]. If r == t then the packet arrived on 199 time. If r < t then the packet arrived late and if r > t then the 200 packet arrived early. 202 (iv). Delay playout of packet by D + (r-t) 204 (v). Go back to (ii) 206 Note that this idealized implementation assumes that the sender's RTP 207 clock is synchronized to the clock in the receiver which is used to 208 timestamp packet arrivals. If there is no such inherent 209 synchronization, the system may need to use an adaptive de-jitter 210 buffer or other techniques to ensure reliable reception. 212 3.2. Fixed De-Jitter Buffer 214 A fixed de-jitter buffer lacks provision to track network condition 215 and has a fixed size and packets leaving the de-jitter buffer have a 216 constant delay. For fixed de-jitter buffer implementation, the 217 nominal delay is set to a constant value corresponding to the packets 218 that arrive at their expected arrival time while the maximum delay is 219 set to a constant value corresponding to the fixed size of the de- 220 jitter buffer. 222 3.3. Adaptive De-Jitter Buffer 224 An adaptive de-jitter buffer can adapt to the change in the network's 225 delay and has variable size or variable delay. It allows the nominal 226 delay to be set to a low value initially, to minimize user perceived 227 delay, however can automatically extend the late edge (and possibly 228 also retract the early edge) of buffer window if a significant 229 proportion of packets are arriving late (and hence being discarded). 231 4. De-Jitter Buffer Metrics Block 233 This block describes the configuration and operating parameters of 234 the de-jitter buffer in the receiver of the RTP end system or RTP 235 mixer which sends the report. Instances of this metrics block refer 236 by SSRC to the separate auxiliary Measurement Information Block 237 [RFC6776] which describes the measurement interval in use. This 238 metrics block relies on the measurement interval in the Measurement 239 Information Block indicating the span of the report and MUST be sent 240 in the same compound RTCP packet as the Measurement Information 241 Block. If the measurement interval is not received in the same 242 compound RTCP packet as this metrics block, this metrics block MUST 243 be discarded. 245 4.1. Report Block Structure 247 De-Jitter Buffer (DJB) Metrics Block 249 0 1 2 3 250 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 251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 252 | BT=DJB | I |C| Rsvd. | block length=3 | 253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 | SSRC of Source | 255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 | DJB nominal | DJB maximum | 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | DJB high water mark | DJB low water mark | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 Figure 1: Report Block Structure 263 4.2. Definition of Fields in De-Jitter Buffer Metrics Block 265 Block type (BT): 8 bits 267 A de-jitter buffer Metrics Report Block is identified by the 268 constant DJB. 270 [Note to RFC Editor: please replace DJB with the IANA provided 271 RTCP XR block type for this block.] 273 Interval Metric flag (I): 2 bits 275 This field is used to indicate whether the de-jitter buffer 276 metrics are Sampled, Interval or Cumulative metrics: 278 I=01: Sampled Value - the reported value is a sampled 279 instantaneous value. 281 I=10: Interval Duration - the reported value applies to the 282 most recent measurement interval duration between successive 283 metrics reports. 285 I=11: Cumulative Duration - the reported value applies to the 286 accumulation period characteristic of cumulative measurements. 288 In this document, de-jitter buffer Metrics can only be sampled , 289 and cannot be measured over definite intervals. Also, the value 290 I=00 is reserved for future use. Senders MUST NOT use the values 291 I=00 or I=10 or I=11. If a block is received with I=00 or I=10 or 292 I=11, the receiver MUST discard the block. 294 Jitter Buffer Configuration (C): 1 bit 296 This field is used to identify the de-jitter buffer method in use 297 at the receiver, according to the following code: 299 0 = Fixed de-jitter buffer 301 1 = Adaptive de-jitter buffer 303 Reserved (Rsvd.): 5 bits 305 These bits are reserved. They MUST be set to zero by senders 306 ignored by receivers (See [RFC6709] section 4.2). 308 Block Length: 16 bits 310 The length of this report block in 32-bit words, minus one, in 311 accordance with the definition in [RFC3611]. This field MUST be 312 set to 3 to match the fixed length of the report block. 314 de-jitter buffer nominal delay (DJB nominal): 16 bits 316 This is the current nominal de-jitter buffer delay in 317 milliseconds, which corresponds to the nominal de-jitter buffer 318 delay for packets that arrive exactly on time. It is calculated 319 based on the time spent in the de-jitter buffer for the packet 320 that arrives exactly on time. This parameter MUST be provided for 321 both fixed and adaptive de-jitter buffer implementations. 323 The measured value is unsigned value. If the measured value 324 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 325 over-range measurement. If the measurement is unavailable, the 326 value 0xFFFF MUST be reported. 328 de-jitter buffer maximum delay (DJB maximum): 16 bits 330 This is the current maximum de-jitter buffer delay in milliseconds 331 which corresponds to the earliest arriving packet that would not 332 be discarded. It is calculated based on the time spent in the de- 333 jitter buffer for the earliest arriving packet In simple queue 334 implementations this may correspond to the size of the de-jitter 335 buffer. In adaptive de-jitter buffer implementations, this value 336 may vary dynamically. This parameter MUST be provided for both 337 fixed and adaptive de-jitter buffer implementations. 339 The measured value is unsigned value. If the measured value 340 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 341 over-range measurement. If the measurement is unavailable, the 342 value 0xFFFF MUST be reported. 344 de-jitter buffer high water mark (DJB high water mark): 16 bits 346 This is the highest value of the de-jitter buffer nominal delay in 347 milliseconds which occurred at any time during the reporting 348 interval. This parameter MUST be provided for adaptive de-jitter 349 buffer implementations and its value MUST be set to JB maximum for 350 fixed de-jitter buffer implementations. 352 The measured value is unsigned value. If the measured value 353 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 354 over-range measurement. If the measurement is unavailable, the 355 value 0xFFFF MUST be reported. 357 de-jitter buffer low water mark (DJB low water mark): 16 bits 359 This is the lowest value of the de-jitter buffer nominal delay in 360 milliseconds which occurred at any time during the reporting 361 interval. This parameter MUST be provided for adaptive de-jitter 362 buffer implementations and its value MUST be set to JB maximum for 363 fixed de-jitter buffer implementations. 365 The measured value is unsigned value. If the measured value 366 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 367 over-range measurement. If the measurement is unavailable, the 368 value 0xFFFF MUST be reported. 370 5. SDP Signaling 372 [RFC3611] defines the use of SDP (Session Description Protocol) 373 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 374 be used without prior signaling (see section 5 of RFC3611). 376 5.1. SDP rtcp-xr-attrib Attribute Extension 378 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 379 in [RFC3611] by providing an additional value of "xr-format" to 380 signal the use of the report block defined in this document. 382 xr-format =/ xr-djb-block 384 xr-djb-block = "de-jitter-buffer" 386 5.2. Offer/Answer Usage 388 When SDP is used in offer-answer context [RFC3264], the SDP Offer/ 389 Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute 390 parameters applies. For detailed usage of Offer/Answer for 391 unilateral parameter, refer to section 5.2 of [RFC3611]. 393 6. IANA Considerations 395 New block types for RTCP XR are subject to IANA registration. For 396 general guidelines on IANA considerations for RTCP XR, refer to 397 [RFC3611]. 399 6.1. New RTCP XR Block Type value 401 This document assigns the block type value DJB in the IANA "RTP 402 Control Protocol Extended Reports (RTCP XR) Block Type Registry" to 403 the "De-Jitter Buffer Metrics Block". 405 [Note to RFC Editor: please replace DJB with the IANA provided RTCP 406 XR block type for this block.] 408 6.2. New RTCP XR SDP Parameter 410 This document also registers a new parameter "de-jitter-buffer" in 411 the "RTP Control Protocol Extended Reports (RTCP XR) Session 412 Description Protocol (SDP) Parameters Registry". 414 6.3. Contact information for registrations 416 The contact information for the registrations is: 418 Qin Wu (sunseawq@huawei.com) 419 101 Software Avenue, Yuhua District 420 Nanjing, Jiangsu 210012 421 China 423 7. Security Considerations 425 It is believed that this proposed RTCP XR report block introduces no 426 new security considerations beyond those described in [RFC3611]. 427 This block does not provide per-packet statistics so the risk to 428 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 429 does not apply. 431 8. Contributors 433 Geoff Hunt wrote the initial draft of this document. 435 9. Acknowledgments 437 The authors gratefully acknowledge reviews and feedback provided by 438 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 439 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 440 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 441 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 442 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin 443 Perkin, Dan Romascanu, Kevin Gross ,Glen Zorn, Spencer Dawkins and 444 Benoit Claise. 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-08, May 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. de-jitter buffer nominal delay Metric 495 * Metric Name: de-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, de- 503 jitter buffer nominal delay definition [RFCXXXX]. 505 * Units of Measurement: See section 4.2, de-jitter buffer 506 nominal 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. de-jitter buffer maximum delay Metric 521 * Metric Name: de-jitter buffer maximum delay in RTP 523 * Metric Description: It is the current maximum de-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, de- 528 jitter buffer maximum delay definition and section 3, the last 529 paragraph [RFCXXXX]. 531 * Units of Measurement: See section 4.2, de-jitter buffer 532 maximum 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. de-jitter buffer high water mark Metric 547 * Metric Name: de-jitter buffer high water mark in RTP 549 * Metric Description: It is the highest value of the de-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, de- 554 jitter buffer high water mark definition [RFCXXXX]. 556 * Units of Measurement: See section 4.2, de-jitter buffer 557 nominal 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. de-jitter buffer low water mark Metric 572 * Metric Name: de-jitter buffer low water mark in RTP 574 * Metric Description: It is the lowest value of the de-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, de- 579 jitter buffer low water mark definition [RFCXXXX]. 581 * Units of Measurement: See section 4.2, de-jitter buffer low 582 water 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-12 602 The following are the major changes to previous version : 604 o Editorial changes based on recieved comments. 606 B.2. draft-ietf-xrblock-rtcp-xr-jb-11 608 The following are the major changes to previous version : 610 o Comments in WGLC and from PM-DIR review are addressed in this 611 version. 613 B.3. draft-ietf-xrblock-rtcp-xr-jb-10 615 The following are the major changes to previous version : 617 o Add some text to section 3.2 to clarify how fixed de-jitter buffer 618 is used. 620 o Other Editorial changes. 622 B.4. draft-ietf-xrblock-rtcp-xr-jb-09 624 The following are the major changes to previous version : 626 o Incorporate proposed changes by Kevin and proposed text by Alan to 627 address interoperability report issue. 629 o Add new appendix to format metrics using RFC6390 template. 631 B.5. draft-ietf-xrblock-rtcp-xr-jb-08 633 The following are the major changes to previous version : 635 o Rewrote descriptive text and definitions for clarification. 637 B.6. draft-ietf-xrblock-rtcp-xr-jb-07 639 The following are the major changes to previous version : 641 o Add one new section to discuss de-jitter buffer operation. 643 B.7. draft-ietf-xrblock-rtcp-xr-jb-05 645 The following are the major changes to previous version : 647 o Some editorial change changes based on the discussion with Glen 648 and Kevin on the list. 650 B.8. draft-ietf-xrblock-rtcp-xr-jb-03 652 The following are the major changes to previous version : 654 o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. 656 o Other editorial change changes aligning with PDV,Delay draft. 658 B.9. draft-ietf-xrblock-rtcp-xr-jb-02 660 The following are the major changes to previous version : 662 o Add some explanation text in the SDP offer/answer section. 664 o Add some text in applicability section to explain the use to 665 report de-jitter buffer metrics. 667 o Other editorial change changes aligning with PDV,Delay draft. 669 B.10. draft-ietf-xrblock-rtcp-xr-jb-01 671 The following are the major changes to previous version : 673 o Outdated reference update 675 o Add one Editor notes to ask clarification on the use of reporting 676 de-jitter buffer metrics. 678 o Other Editorial changes. 680 B.11. draft-ietf-xrblock-rtcp-xr-jb-00 682 The following are the major changes to previous version : 684 o Boilerplate updates. 686 o references updates 688 o allocate 32 bit field in report block for SSRC 689 o Other editorial changes to get alignment with MONARCH draft. 691 Authors' Addresses 693 Alan Clark 694 Telchemy Incorporated 695 2905 Premiere Parkway, Suite 280 696 Duluth, GA 30097 697 USA 699 Email: alan.d.clark@telchemy.com 701 Varun Singh 702 Aalto University 703 School of Electrical Engineering 704 Otakaari 5 A 705 Espoo, FIN 02150 706 Finland 708 Email: varun@comnet.tkk.fi 710 Qin Wu 711 Huawei 712 101 Software Avenue, Yuhua District 713 Nanjing, Jiangsu 210012 714 China 716 Email: sunseawq@huawei.com