idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-jb-10.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 2, 2013) is 4035 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 199 == Missing Reference: 'RFCXXXX' is mentioned on line 568, but not defined ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Downref: Normative reference to an Informational RFC: RFC 6709 Summary: 2 errors (**), 0 flaws (~~), 2 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 4, 2013 Aalto University 6 Q. Wu 7 Huawei 8 April 2, 2013 10 RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer 11 Metric Reporting 12 draft-ietf-xrblock-rtcp-xr-jb-10.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 4, 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 . . . . . . . . . . . . . . . . . . . . . . . . 10 69 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 10 70 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 10 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 72 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11 73 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11 74 6.3. Contact information for registrations . . . . . . . . . . 11 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 76 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 77 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 78 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 79 10.1. Normative References . . . . . . . . . . . . . . . . . . . 15 80 10.2. Informative References . . . . . . . . . . . . . . . . . . 15 81 Appendix A. Metrics represented using RFC6390 Template . . . . . 16 82 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 19 83 B.1. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 19 84 B.2. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 19 85 B.3. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 19 86 B.4. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 19 87 B.5. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 19 88 B.6. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 19 89 B.7. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 20 90 B.8. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 20 91 B.9. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 20 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 94 1. Introduction 96 1.1. Jitter Buffer Metrics Block 98 This document defines a new block type to augment those defined in 99 [RFC3611], for use in a range of RTP applications. 101 The new block type provides information on jitter buffer 102 configuration and performance. 104 The metric belongs to the class of transport-related end system 105 metrics defined in [RFC6792]. 107 Instances of this Metrics Block refer by Synchronization source 108 (SSRC) to the separate auxiliary Measurement Information block 109 [RFC6776] which contains information such as the SSRC of the measured 110 stream, and RTP sequence numbers and time intervals indicating the 111 span of the report. 113 1.2. RTCP and RTCP XR Reports 115 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 116 defines an extensible structure for reporting using an RTCP Extended 117 Report (XR). This document defines a new Extended Report block for 118 use with [RFC3550] and [RFC3611]. 120 1.3. Performance Metrics Framework 122 The Performance Metrics Framework [RFC6390] provides guidance on the 123 definition and specification of performance metrics. The RTP 124 Monitoring Architectures [RFC6792] provides guideline for reporting 125 block format using RTCP XR. Metrics described in this draft are in 126 accordance with the guidelines in [RFC6390]and [RFC6792]. 128 1.4. Applicability 130 Real-time applications employ a jitter buffer to absorb jitter 131 introduced on the path from source to destination. These metrics are 132 used to report how the jitter buffer at the receiving end of RTP 133 stream behaves as a result of jitter in the network and are 134 applicable to a range of RTP applications. 136 These metrics reflect how terminal-related factors affect real-time 137 application quality and are useful to provide better end-user quality 138 of experience (QoE). 140 2. Terminology 142 2.1. Standards Language 144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 146 document are to be interpreted as described in RFC 2119 [RFC2119]. 148 3. Jitter Buffer Operation 150 A jitter buffer is required to absorb delay variation in network 151 delivery of media packets. A jitter buffer works by holding media 152 data for a period of time after it is received and before it is 153 played out. Packets that arrive early are held in the jitter buffer 154 longer. If packets arrive too early they may be discarded if there 155 is no available jitter buffer space. If packets are delayed 156 excessively by the network they may be discarded if they miss their 157 playout time. 159 Overall user perceived delay = network round trip delay + local 160 (jitter buffer (nominal) delay + encoder serialization delay) + 161 remote (jitter buffer (nominal) delay + encoder serialization delay) 163 The jitter buffer can be considered as a time window with early edge 164 aligned with the delay corresponding to the earliest arriving packet 165 and late edge representing the maximum permissible delay before a 166 late arriving packet would be discarded. The delay applied to 167 packets that arrive on time or at their expected arrival time is 168 known as the Nominal Delay and this is equivalent to the time 169 difference/ buffer size difference between the on-time packets 170 insertion point and the point at which packets are read out. 172 The reference for the expected arrival time may, for example, be the 173 first packet in the session or the running average delay. If all 174 packets arrived at their expected arrival time then then every packet 175 would be held in the jitter buffer exactly the Nominal Delay. 177 The Jitter Buffer maximum delay is the delay that is applied to an 178 earliest arriving packet that is not discarded and corresponds to the 179 early edge of the jitter buffer time window. 181 3.1. Idealized Jitter Buffer 183 In practice jitter buffer implementations vary considerably however 184 should behave in a manner conceptually consistent with an idealized 185 jitter buffer described as follows: 187 (i). Receive the first packet and delay playout by D ms. Keep 188 the RTP timestamp and receive time as a reference. 190 RTP TS[1] 192 receive time[1] 194 Assume that both are normalized in ticks. 196 (ii). Receive the next packet 198 (iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive 199 time[n] - receive time[1]. If r = t then the packet arrived on 200 time. If r < t then the packet arrived late and if r > t then the 201 packet arrived early. 203 (iv). Delay playout of packet by D + (r -t) 205 (v). Go back to (ii) 207 Note that this idealized implementation assumes that the sender's RTP 208 clock is synchronized to the clock in the receiver which is used to 209 timestamp packet arrivals. If there is no such inherent 210 synchronization, the system may need to use an adaptive jitter buffer 211 or other techniques to ensure reliable reception. 213 3.2. Fixed Jitter Buffer 215 A fixed jitter buffer lacks provision to track network condition and 216 has a fixed size and packets leaving the jitter buffer have a 217 constant delay. For fixed jitter buffer implementation, the nominal 218 delay is set to a constant value corresponding to the packets that 219 arrive at their expected arrival time while the maximum delay is set 220 to a constant value corresponding to the fixed size of the jitter 221 buffer. 223 3.3. Adaptive Jitter Buffer 225 An adaptive jitter buffer can adapt to the change in the network's 226 delay and has variable size or variable delay. It allows the nominal 227 delay to be set to a low value initially, to minimize user perceived 228 delay, however can automatically extend the late edge (and possibly 229 also retract the early edge) of buffer window if a significant 230 proportion of packets are arriving late (and hence being discarded). 232 4. Jitter Buffer Metrics Block 234 This block describes the configuration and operating parameters of 235 the jitter buffer in the receiver of the RTP end system or RTP mixer 236 which sends the report. Instances of this Metrics Block refer by 237 SSRC to the separate auxiliary Measurement Information block 238 [RFC6776] which describes the measurement interval in use. This 239 Metrics Block relies on the measurement interval in the Measurement 240 Information block indicating the span of the report and should be 241 sent in the same compound RTCP packet as the measurement information 242 block. If the measurement interval is not received in the same 243 compound RTCP packet as this Metrics Block, this Metrics Block should 244 be discarded. 246 4.1. Report Block Structure 248 JB Metrics Block 250 0 1 2 3 251 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 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | BT=NJB | I |C| Rsvd. | block length=3 | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | SSRC of Source | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | JB nominal | JB maximum | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | JB high water mark | JB low water mark | 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 Figure 1: Report Block Structure 264 4.2. Definition of Fields in Jitter Buffer Metrics Block 266 Block type (BT): 8 bits 268 A Jitter Buffer Metrics Report Block is identified by the constant 269 NJB. 271 [Note to RFC Editor: please replace NJB with the IANA provided 272 RTCP XR block type for this block.] 274 Interval Metric flag (I): 2 bits 276 This field is used to indicate whether the Jitter Buffer metrics 277 are Sampled, Interval or Cumulative metrics: 279 I=01: Sampled Value - the reported value is a sampled 280 instantaneous value. 282 I=10: Interval Duration - the reported value applies to the 283 most recent measurement interval duration between successive 284 metrics reports. 286 I=11: Cumulative Duration - the reported value applies to the 287 accumulation period characteristic of cumulative measurements. 289 Jitter Buffer Configuration (C): 1 bit 291 This field is used to identify the jitter buffer method in use at 292 the receiver, according to the following code: 294 0 = Fixed jitter buffer 296 1 = Adaptive jitter buffer 298 Reserved (Rsvd.): 5 bits 300 These bits are reserved. They MUST be set to zero by senders 301 ignored by receivers (See [RFC6709] section 4.2). 303 Block Length: 16 bits 305 The length of this report block in 32-bit words, minus one, in 306 accordance with the definition in [RFC3611]. This field MUST be 307 set to 3 to match the fixed length of the report block. 309 jitter buffer nominal delay (JB nominal): 16 bits 311 This is the current nominal jitter buffer delay in milliseconds, 312 which corresponds to the nominal jitter buffer delay for packets 313 that arrive exactly on time. It is calculated based on the time 314 spend in the jitter buffer for the packet that arrives exactly on 315 time. This parameter MUST be provided for both fixed and adaptive 316 jitter buffer implementations. 318 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 319 reported to indicate an over-range measurement. If the 320 measurement is unavailable, the value 0xFFFF MUST be reported. 322 jitter buffer maximum delay (JB maximum): 16 bits 324 This is the current maximum jitter buffer delay in milliseconds 325 which corresponds to the earliest arriving packet that would not 326 be discarded. It is calculated based on the time spent in the 327 jitter buffer for the earliest arriving packet In simple queue 328 implementations this may correspond to the size of the jitter 329 buffer. In adaptive jitter buffer implementations, this value may 330 vary dynamically. This parameter MUST be provided for both fixed 331 and adaptive jitter buffer implementations. 333 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 334 reported to indicate an over-range measurement. If the 335 measurement is unavailable, the value 0xFFFF MUST be reported. 337 jitter buffer high water mark (JB high water mark): 16 bits 339 This is the highest value of the jitter buffer nominal delay in 340 milliseconds which occurred at any time during the reporting 341 interval. This parameter MUST be provided for adaptive jitter 342 buffer implementations and its value MUST be set to JB maximum for 343 fixed jitter buffer implementations. 345 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 346 reported to indicate an over-range measurement. If the 347 measurement is unavailable, the value 0xFFFF MUST be reported. 349 jitter buffer low water mark (JB low water mark): 16 bits 351 This is the lowest value of the jitter buffer nominal delay in 352 milliseconds which occurred at any time during the reporting 353 interval. This parameter MUST be provided for adaptive jitter 354 buffer implementations and its value MUST be set to JB maximum for 355 fixed jitter buffer implementations. 357 If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be 358 reported to indicate an over-range measurement. If the 359 measurement is unavailable, the value 0xFFFF MUST be reported. 361 5. SDP Signaling 363 [RFC3611] defines the use of SDP (Session Description Protocol) 364 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 365 be used without prior signaling (see section 5 of RFC3611). 367 5.1. SDP rtcp-xr-attrib Attribute Extension 369 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 370 in [RFC3611] by providing an additional value of "xr-format" to 371 signal the use of the report block defined in this document. 373 xr-format =/ xr-jb-block 375 xr-jb-block = "jitter-bfr" 377 5.2. Offer/Answer Usage 379 When SDP is used in offer-answer context, the SDP Offer/Answer usage 380 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 381 applies. For detailed usage of Offer/Answer for unilateral 382 parameter, refer to section 5.2 of [RFC3611]. 384 6. IANA Considerations 386 New block types for RTCP XR are subject to IANA registration. For 387 general guidelines on IANA considerations for RTCP XR, refer to 388 [RFC3611]. 390 6.1. New RTCP XR Block Type value 392 This document assigns the block type value NJB in the IANA "RTCP XR 393 Block Type Registry" to the "JB Metrics Block". 395 [Note to RFC Editor: please replace NJB with the IANA provided RTCP 396 XR block type for this block.] 398 6.2. New RTCP XR SDP Parameter 400 This document also registers a new parameter "jitter-bfr" in the 401 "RTCP XR SDP Parameters Registry". 403 6.3. Contact information for registrations 405 The contact information for the registrations is: 407 Qin Wu (sunseawq@huawei.com) 408 101 Software Avenue, Yuhua District 409 Nanjing, Jiangsu 210012 410 China 412 7. Security Considerations 414 It is believed that this proposed RTCP XR report block introduces no 415 new security considerations beyond those described in [RFC3611]. 416 This block does not provide per-packet statistics so the risk to 417 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 418 does not apply. 420 8. Contributors 422 Geoff Hunt wrote the initial draft of this document. 424 9. Acknowledgments 426 The authors gratefully acknowledge reviews and feedback provided by 427 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 428 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 429 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 430 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 431 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin 432 Perkin, Dan Romascanu, Kevin Gross and Glen Zorn. 434 10. References 436 10.1. Normative References 438 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 439 Requirement Levels", March 1997. 441 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 442 Applications", RFC 3550, July 2003. 444 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 445 Protocol Extended Reports (RTCP XR)", November 2003. 447 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 448 Description Protocol", July 2006. 450 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 451 Considerations for Protocol Extensions", RFC 6709, 452 September 2012. 454 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 455 using SDES item and XR Block", RFC 6776, August 2012. 457 10.2. Informative References 459 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 460 Development", RFC 6390, October 2011. 462 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 463 for RTP", RFC 6792, November 2012. 465 Appendix A. Metrics represented using RFC6390 Template 467 RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC 468 number, when assigned. 470 a. jitter buffer nominal delay Metric 472 * Metric Name: jitter buffer nominal delay 474 * Metric Description: The "expected arrival time" is the time 475 that a RTP packet would arrive if there was no delay 476 variation. The delay applied to packets that arrive at their 477 expected time is known as the Nominal Delay. 479 * Method of Measurement or Calculation: See section 4.2, jitter 480 buffer nominal delay definition [RFCXXXX]. 482 * Units of Measurement: See section 4.2, jitter buffer nominal 483 delay definition [RFCXXXX]. 485 * Measurement Point(s) with Potential Measurement Domain: See 486 section 4, 1st paragraph [RFCXXXX]. 488 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 489 measurement timing and section 4.2 paragraph [RFCXXXX] for 490 Interval Metric flag. 492 * Use and applications: See section 1.4 [RFCXXXX]. 494 * Reporting model: See RFC3611. 496 b. jitter buffer maximum delay Metric 498 * Metric Name: jitter buffer maximum delay 500 * Metric Description: It is the current maximum jitter buffer 501 delay for RTP traffic which corresponds to the earliest 502 arriving packet that would not be discarded. 504 * Method of Measurement or Calculation: See section 4.2, jitter 505 buffer maximum delay definition and section 3, the last 506 paragraph [RFCXXXX]. 508 * Units of Measurement: See section 4.2, jitter buffer maximum 509 delay definition [RFCXXXX]. 511 * Measurement Point(s) with Potential Measurement Domain: See 512 section 4, 1st paragraph [RFCXXXX]. 514 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 515 measurement timing and section 4.2 paragraph [RFCXXXX] for 516 Interval Metric flag. 518 * Use and applications: See section 1.4 [RFCXXXX]. 520 * Reporting model: See RFC3611. 522 c. jitter buffer high water mark Metric 524 * Metric Name: jitter buffer high water mark 526 * Metric Description: It is the highest value of the jitter 527 buffer nominal delay for RTP traffic which occurred at any 528 time during the reporting interval. 530 * Method of Measurement or Calculation: See section 4.2, jitter 531 buffer high water mark definition [RFCXXXX]. 533 * Units of Measurement: See section 4.2, jitter buffer nominal 534 delay definition [RFCXXXX]. 536 * Measurement Point(s) with Potential Measurement Domain: See 537 section 4, 1st paragraph [RFCXXXX]. 539 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 540 measurement timing and section 4.2 paragraph [RFCXXXX] for 541 Interval Metric flag. 543 * Use and applications: See section 1.4 [RFCXXXX]. 545 * Reporting model: See RFC3611. 547 d. jitter buffer low water mark Metric 549 * Metric Name: jitter buffer low water mark 551 * Metric Description: It is the lowest value of the jitter 552 buffer nominal delay for RTP traffic which occurred at any 553 time during the reporting interval. 555 * Method of Measurement or Calculation: See section 4.2, jitter 556 buffer low water mark definition [RFCXXXX]. 558 * Units of Measurement: See section 4.2, jitter buffer low water 559 mark definition [RFCXXXX]. 561 * Measurement Point(s) with Potential Measurement Domain: See 562 section 4, 1st paragraph [RFCXXXX]. 564 * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for 565 measurement timing and section 4.2 paragraph [RFCXXXX] for 566 Interval Metric flag. 568 * Use and applications: See section 1.4 [RFCXXXX]. 570 * Reporting model: See RFC3611. 572 Appendix B. Change Log 574 Note to the RFC-Editor: please remove this section prior to 575 publication as an RFC. 577 B.1. draft-ietf-xrblock-rtcp-xr-jb-10 579 The following are the major changes to previous version : 581 o Add some text to section 3.2 to clarify how fixed jitter buffer is 582 used. 584 o Other Editorial changes. 586 B.2. draft-ietf-xrblock-rtcp-xr-jb-09 588 The following are the major changes to previous version : 590 o Incorporate proposed changes by Kevin and proposed text by Alan to 591 address interoperability report issue. 593 o Add new appendix to format metrics using RFC6390 template. 595 B.3. draft-ietf-xrblock-rtcp-xr-jb-08 597 The following are the major changes to previous version : 599 o Rewrote descriptive text and definitions for clarification. 601 B.4. draft-ietf-xrblock-rtcp-xr-jb-07 603 The following are the major changes to previous version : 605 o Add one new section to discuss jitter buffer operation. 607 B.5. draft-ietf-xrblock-rtcp-xr-jb-05 609 The following are the major changes to previous version : 611 o Some editorial change changes based on the discussion with Glen 612 and Kevin on the list. 614 B.6. draft-ietf-xrblock-rtcp-xr-jb-03 616 The following are the major changes to previous version : 618 o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. 620 o Other editorial change changes aligning with PDV,Delay draft. 622 B.7. draft-ietf-xrblock-rtcp-xr-jb-02 624 The following are the major changes to previous version : 626 o Add some explanation text in the SDP offer/answer section. 628 o Add some text in applicability section to explain the use to 629 report jitter buffer metrics. 631 o Other editorial change changes aligning with PDV,Delay draft. 633 B.8. draft-ietf-xrblock-rtcp-xr-jb-01 635 The following are the major changes to previous version : 637 o Outdated reference update 639 o Add one Editor notes to ask clarification on the use of reporting 640 jitter buffer metrics. 642 o Other Editorial changes. 644 B.9. draft-ietf-xrblock-rtcp-xr-jb-00 646 The following are the major changes to previous version : 648 o Boilerplate updates. 650 o references updates 652 o allocate 32 bit field in report block for SSRC 654 o Other editorial changes to get alignment with MONARCH draft. 656 Authors' Addresses 658 Alan Clark 659 Telchemy Incorporated 660 2905 Premiere Parkway, Suite 280 661 Duluth, GA 30097 662 USA 664 Email: alan.d.clark@telchemy.com 666 Varun Singh 667 Aalto University 668 School of Electrical Engineering 669 Otakaari 5 A 670 Espoo, FIN 02150 671 Finland 673 Email: varun@comnet.tkk.fi 675 Qin Wu 676 Huawei 677 101 Software Avenue, Yuhua District 678 Nanjing, Jiangsu 210012 679 China 681 Email: sunseawq@huawei.com