idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14.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 26, 2013) is 4018 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) == Missing Reference: 'RFCXXXX' is mentioned on line 552, but not defined == Unused Reference: 'RFC6709' is defined on line 469, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-xrblock-rtcp-xr-discard-11 ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 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 R. Huang 5 Expires: October 28, 2013 Q. Wu, Ed. 6 Huawei 7 April 26, 2013 9 RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 10 Discard metric Reporting 11 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14.txt 13 Abstract 15 This document defines an RTP Control Protocol(RTCP) Extended Report 16 (XR) Block that allows the reporting of Burst and Gap Discard metrics 17 for use in a range of RTP applications. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on October 28, 2013. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Burst and Gap Discard Report Block . . . . . . . . . . . . 3 55 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 56 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 57 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 60 3. Burst/Gap Discard Block . . . . . . . . . . . . . . . . . . . 6 61 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 62 3.2. Definition of Fields in Burst/Gap Discard Report Block . . 6 63 3.3. Derived metrics based on reported metrics . . . . . . . . 8 64 4. Considerations for Voice-over-IP applications . . . . . . . . 10 65 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 66 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 67 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12 70 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 71 6.3. Contact information for registrations . . . . . . . . . . 12 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 73 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 74 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 75 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 76 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 77 10.2. Informative References . . . . . . . . . . . . . . . . . . 16 78 Appendix A. Metrics represented using RFC6390 Template . . . . . 18 79 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 21 80 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14 . . . . . 21 81 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13 . . . . . 21 82 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12 . . . . . 21 83 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11 . . . . . 21 84 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10 . . . . . 21 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 87 1. Introduction 89 1.1. Burst and Gap Discard Report Block 91 This document defines a new block type to augment those defined in 92 [RFC3611] for use in a range of RTP applications. The new block type 93 supports the reporting of the proportion of packets discarded by the 94 jitter buffer at the receiver, using packet discard logic according 95 to the jitter buffer algorithms. The discards during discard bursts 96 are reported, together with the number of bursts. This block is 97 intended to be used in conjunction with [DISCARD] which provides the 98 total packets discarded, and on which this block therefore depends. 99 However the metric in [DISCARD] may be used independently of the 100 metrics in this block. 102 This block provides information on transient IP problems. Burst/Gap 103 metrics are typically used in cumulative reports, however they also 104 may be used in interval reports (see the Interval Metric flag in 105 section 3.2). The burstiness of packet discard affects user 106 experience, may influence any sender strategies to mitigate the 107 problem, and may also have diagnostic value. 109 The metric belongs to the class of transport-related end system 110 metrics defined in [RFC6792]. 112 The definitions of Burst, Gap, Loss and Discard are consistent with 113 definitions in [RFC3611]. To accommodate the range of jitter buffer 114 algorithms and packet discard logic that may be used by implementors, 115 the method used to distinguish between bursts and gaps shall use an 116 equivalent method to that defined in the section 4.7.2 of [RFC3611]. 117 Note that Reporting the specific jitter buffer algorithms and/or 118 packet discard logic is out of scope of this document. 120 1.2. RTCP and RTCP XR Reports 122 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 123 defined an extensible structure for reporting using an RTCP Extended 124 Report (XR). This document defines a new Extended Report block for 125 use with [RFC3550] and [RFC3611]. 127 1.3. Performance Metrics Framework 129 The Performance Metrics Framework [RFC6390] provides guidance on the 130 definition and specification of performance metrics. The RTP 131 Monitoring Architectures [RFC6792] provides guideline for reporting 132 block format using RTCP XR. The metrics block described in this 133 document are in accordance with the guidelines in [RFC6390] and 134 [RFC6792]. 136 1.4. Applicability 138 These metrics are applicable to a range of RTP applications which 139 contain de-jitter buffers [RFC5481] at the receiving end to smooth 140 variation in packet arriving time and don't use stream repair means, 141 e.g., Forward Error Correction (FEC) [RFC5109] and/or retransmission 142 [RFC4588]. 144 2. Terminology 146 2.1. Standards Language 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 149 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 150 document are to be interpreted as described in RFC 2119 [RFC2119]. 152 In addition, the following terms are defined: 154 Received, Lost and Discarded 156 A packet shall be regarded as lost if it fails to arrive within an 157 implementation-specific time window. A packet that arrives within 158 this time window but is either too early to be played out or too 159 late to be played out or thrown away before playout due to packet 160 duplication or redundancy shall be regarded as discarded. A 161 packet shall not be regarded as discarded if it arrives within 162 this time window but is dropped during decoding by some higher 163 layer decoder, e.g., due to a decoding error. A packet shall be 164 classified as one of received (or OK), discarded or lost. The 165 metric "cumulative number of packets lost" defined in [RFC3550] 166 reports a count of packets lost from the media stream (single SSRC 167 within single RTP session). Similarly the metric "number of 168 packets discarded" defined in [DISCARD] reports a count of packets 169 discarded from the media stream (single SSRC within single RTP 170 session) arriving at the receiver. Another metric defined in 171 [RFC5725] is available to report on packets which are not 172 recovered by any repair techniques which may be in use. Note that 173 the term discard defined here build on the Discard definition 174 [RFC3611], but extend the concept to take into account the packet 175 duplication, and report different types of discard counts 176 [DISCARD]. 178 Bursts and Gaps 180 The terms Burst and Gap are used in a manner consistent with that 181 of RTCP XR [RFC3611]. RTCP XR views a RTP stream as being divided 182 into bursts, which are periods during which the discard rate is 183 high enough to cause noticeable quality degradation (generally 184 over 5 percent discard rate), and gaps, which are periods during 185 which discarded packets are infrequent and hence quality is 186 generally acceptable. 188 3. Burst/Gap Discard Block 190 Metrics in this block report on Burst/Gap Discard in the stream 191 arriving at the RTP system. The measurement of these metrics are 192 made at the receiving end of the RTP stream. Instances of this 193 metrics block refer by Synchronization source (SSRC) to the separate 194 auxiliary Measurement Information Block [RFC6776] which describes 195 measurement periods in use (see RFC6776 section 4.2). 197 This metrics block relies on the measurement period in the 198 Measurement Information Block indicating the span of the report. 199 Senders MUST send this block in the same compound RTCP packet as the 200 Measurement Information Block. Receivers MUST verify that the 201 measurement period is received in the same compound RTCP packet as 202 this metrics block. If not, this metrics block MUST be discarded. 204 3.1. Report Block Structure 206 Burst/Gap Discard Metrics Block 208 0 1 2 3 209 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 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | BT=NBGD | I | resv. | block length = 3 | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | SSRC of Source | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | Threshold | Packets Discarded in Bursts | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Total Packets expected in Bursts | Reserved. | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Figure 1: Report Block Structure 222 3.2. Definition of Fields in Burst/Gap Discard Report Block 224 Block type (BT): 8 bits 226 A Burst/Gap Discard Report Block is identified by the constant 227 NBGD. 229 [Note to RFC Editor: please replace NBGD with the IANA provided 230 RTCP XR block type for this block.] 232 Interval Metric flag (I): 2 bits 234 This field is used to indicate whether the Burst/Gap Discard 235 metrics are Sampled, Interval or Cumulative metrics [RFC6792]: 237 I=10: Interval Duration - the reported value applies to the 238 most recent measurement interval duration between successive 239 metrics reports. 241 I=11: Cumulative Duration - the reported value applies to the 242 accumulation period characteristic of cumulative measurements. 244 I=01: Sampled Value - the reported value is a sampled 245 instantaneous value. 247 In this document, Burst/Gap Discard Metrics can only be measured 248 over definite intervals, and cannot be sampled. Also, the value 249 I=00 is reserved for future use. Senders MUST NOT use the values 250 I=00 or I=01. If a block is received with I=00 or I=01, the 251 receiver MUST discard the block. 253 Reserved (resv): 6 bits 255 These bits are reserved. They MUST be set to zero by senders and 256 ignored by receivers (See RFC6709 section 4.2). 258 block length: 16 bits 260 The length of this report block in 32-bit words, minus one. For 261 the Burst/Gap discard block, the block length is equal to 3. The 262 block MUST be discarded if the block length is set to a different 263 value. 265 SSRC of source: 32 bits 267 As defined in Section 4.1 of [RFC3611]. 269 Threshold: 8 bits 271 The Threshold is equivalent to Gmin in [RFC3611], i.e. the number 272 of successive packets that must not be discarded prior to and 273 following a discard packet in order for this discarded packet to 274 be regarded as part of a gap. Note that the threshold is set in 275 accordance with Gmin Calculation defined in section 4.7.2 of 276 RFC3611. 278 Packets discarded in bursts: 24 bits 280 The total number of packets discarded during discard bursts. 282 The measured value is unsigned value. If the measured value 283 exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate 284 an over-range measurement. If the measurement is unavailable, the 285 value 0xFFFFFF MUST be reported. 287 Total packets expected in bursts: 24 bits 289 The total number of packets expected during discarded bursts (that 290 is, the sum of received packets and lost packets). 292 The measured value is unsigned value. If the measured value 293 exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate 294 an over-range measurement. If the measurement is unavailable, the 295 value 0xFFFFFF MUST be reported. 297 Reserved (resv): 8 bits 299 These bits are reserved. They MUST be set to zero by senders and 300 ignored by receivers (See RFC6709 section 4.2). 302 3.3. Derived metrics based on reported metrics 304 The metrics described here are intended to be used in conjunction 305 with information from the Measurement Information Block [RFC6776] and 306 also with the metric "number of packets discarded" provided in the 307 RTCP XR Discard Count Block [DISCARD]. 309 These metrics provide the following information relevant to 310 statistical parameters, including: 312 o The fraction of packets discarded during bursts (burst discard 313 rate in [SUMSTAT]), which can be calculated using the metric " 314 Packets Discarded in Bursts " and the metric " Total Packets 315 expected in Bursts " provided in the Burst/Gap Discard Metrics 316 Block. 318 o The fraction of packets discarded during gaps (gap discard rate in 319 [SUMSTAT]), which can be calculated using the metric " Packets 320 Discarded in Bursts " and the metric " Total Packets expected in 321 Bursts " provided in the Burst/Gap Discard Metrics Block. 323 The details on calculation these parameters in the metrics are 324 described in [SUMSTAT]. 326 4. Considerations for Voice-over-IP applications 328 This metrics block is applicable to a broad range of RTP 329 applications. Where the metric is used with a Voice over IP (VoIP) 330 application and the stream repair means is not available, the 331 following considerations apply. 333 RTCP XR views a call as being divided into bursts, which are periods 334 during which the discard rate is high enough to cause noticeable call 335 quality degradation (generally over 5 percent discard rate), and 336 gaps, which are periods during which discarded packets are infrequent 337 and hence call quality is generally acceptable. 339 If voice activity detection is used, the Burst and Gap Duration shall 340 be determined as if silence packets had been sent, i.e. a period of 341 silence in excess of Gmin packets will terminate a burst condition. 343 The recommended value for the threshold Gmin in [RFC3611] results in 344 a Burst being a period of time during which the call quality is 345 degraded to a similar extent to a typical pulse-code modulation(PCM) 346 severely errored second. 348 5. SDP Signaling 350 [RFC3611] defines the use of SDP (Session Description Protocol) 351 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 352 without prior signaling. 354 5.1. SDP rtcp-xr-attrib Attribute Extension 356 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 357 in [RFC3611] by providing an additional value of "xr-format" to 358 signal the use of the report block defined in this document. 360 xr-format =/ xr-bgd-block 362 xr-bgd-block = "burst-gap-discard" 364 5.2. Offer/Answer Usage 366 When SDP is used in offer-answer context, the SDP Offer/Answer usage 367 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 368 applies. For detailed usage in Offer/Answer for unilateral 369 parameter, refer to section 5.2 of [RFC3611]. 371 6. IANA Considerations 373 New block types for RTCP XR are subject to IANA registration. For 374 general guidelines on IANA considerations for RTCP XR, refer to 375 [RFC3611]. 377 6.1. New RTCP XR Block Type value 379 This document assigns the block type value NBGD in the IANA " RTP 380 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 381 the "Burst/Gap Discard Metrics Block". 383 [Note to RFC Editor: please replace NBGD with the IANA provided RTCP 384 XR block type for this block.] 386 6.2. New RTCP XR SDP Parameter 388 This document also registers a new parameter "burst-gap-discard" in 389 the "RTP Control Protocol Extended Reports (RTCP XR) Session 390 Description Protocol (SDP) Parameters Registry". 392 6.3. Contact information for registrations 394 The contact information for the registrations is: 396 Qin Wu (sunseawq@huawei.com) 398 101 Software Avenue, Yuhua District 399 Nanjing, Jiangsu 210012 400 China 402 7. Security Considerations 404 It is believed that this proposed RTCP XR report block introduces no 405 new security considerations beyond those described in [RFC3611]. 406 This block does not provide per-packet statistics so the risk to 407 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 408 does not apply. 410 8. Contributors 412 Geoff Hunt wrote the initial draft of this document. 414 9. Acknowledgments 416 The authors gratefully acknowledge reviews and feedback provided by 417 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 418 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 419 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 420 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 421 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Paul 422 Kyzivat,Claire Bi,Stephen Farrell, Benoit Claise and Dan Romascanu. 424 10. References 426 10.1. Normative References 428 [DISCARD] Wu, Q., "RTCP XR Report Block for Discard Count metric 429 Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-11, 430 December 2012. 432 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 433 Requirement Levels", March 1997. 435 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 436 Applications", RFC 3550, July 2003. 438 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 439 Protocol Extended Reports (RTCP XR)", November 2003. 441 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 442 Description Protocol", July 2006. 444 [RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE 445 Report Block Type for RTP Control Protocol (RTCP) Extended 446 Reports (XRs)", RFC 5725, February 2020. 448 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 449 using SDES item and XR Block", RFC 6776, October 2012. 451 [SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics 452 Reporting", ID draft-ietf-xrblock-rtcp-xr-summary-stat-11, 453 March 2013. 455 10.2. Informative References 457 [RFC4588] Rey, J., Leon, D., , A., Varsa, V., and R. Hakenberg, "RTP 458 Retransmission Payload Format", RFC 4588, July 2006. 460 [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error 461 Correction", RFC 5109, December 2007. 463 [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation 464 Applicability Statement", RFC 5481, March 2009. 466 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 467 Development", RFC 6390, October 2011. 469 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 470 Considerations for Protocol Extensions", RFC 6709, 471 September 2012. 473 [RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792, 474 November 2012. 476 Appendix A. Metrics represented using RFC6390 Template 478 RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC 479 number, when assigned. 481 a. Threshold Metric 483 * Metric Name: Threshold in RTP 485 * Metric Description: The Threshold is equivalent to Gmin in 486 [RFC3611], i.e. the number of successive packets that must not 487 be discarded prior to and following a discard packet in order 488 for this discarded packet to be regarded as part of a gap. 490 * Method of Measurement or Calculation: See section 3.2, 491 Threshold definition [RFCXXXX]. 493 * Units of Measurement: See section 3.2, Threshold definition 494 [RFCXXXX]. 496 * Measurement Point(s) with Potential Measurement Domain: See 497 section 3, 1st paragraph [RFCXXXX]. 499 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 500 measurement timing and section 3.2 [RFCXXXX] for Interval 501 Metric flag. 503 * Use and applications: See section 1.4 [RFCXXXX]. 505 * Reporting model: See RFC3611. 507 b. Packets discarded in bursts Metric 509 * Metric Name: RTP Packets discarded in bursts 511 * Metric Description: The total number of RTP packets discarded 512 during discard bursts. 514 * Method of Measurement or Calculation: See section 3.2, Packets 515 discarded in bursts definition [RFCXXXX]. 517 * Units of Measurement: See section 3.2, Packets discarded in 518 bursts definition [RFCXXXX]. 520 * Measurement Point(s) with Potential Measurement Domain: See 521 section 3, 1st paragraph [RFCXXXX]. 523 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 524 measurement timing and section 3.2 [RFCXXXX] for Interval 525 Metric flag. 527 * Use and applications: See section 1.4 [RFCXXXX]. 529 * Reporting model: See RFC3611. 531 c. Total packets expected in bursts Metric 533 * Metric Name: Total RTP packets expected in bursts 535 * Metric Description: The total number of packets expected 536 during discarded bursts (that is, the sum of received packets 537 and lost packets). 539 * Method of Measurement or Calculation: See section 3.2, Total 540 packets expected in bursts definition [RFCXXXX]. 542 * Units of Measurement: See section 3.2, Total packets expected 543 in bursts definition [RFCXXXX]. 545 * Measurement Point(s) with Potential Measurement Domain: See 546 section 3, 1st paragraph [RFCXXXX]. 548 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 549 measurement timing and section 3.2 [RFCXXXX] for Interval 550 Metric flag. 552 * Use and applications: See section 1.4 [RFCXXXX]. 554 * Reporting model: See RFC3611. 556 Appendix B. Change Log 558 Note to the RFC-Editor: please remove this section prior to 559 publication as an RFC. 561 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14 563 The following are the major changes compared to previous version: 565 o Editorial changes to address comments raised in IESG review and 566 other Directorate review. 568 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13 570 The following are the major changes compared to previous version: 572 o Additional editorial changes to Burst Gap discard draft to get in 573 line with Burst Gap Loss draft. 575 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12 577 The following are the major changes compared to previous version: 579 o Similar changes to Burst Gap loss draft to get in line with Burst 580 Gap Loss draft. 582 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11 584 The following are the major changes compared to previous version: 586 o Similar changes to Burst Gap loss draft to address IESG review 587 comments apply to this document. 589 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10 591 The following are the major changes compared to previous version: 593 o Move RFC6709 as one informative reference. 595 Authors' Addresses 597 Alan Clark 598 Telchemy Incorporated 599 2905 Premiere Parkway, Suite 280 600 Duluth, GA 30097 601 USA 603 Email: alan.d.clark@telchemy.com 605 Rachel Huang 606 Huawei Technologies Co., Ltd. 607 101 Software Avenue, Yuhua District 608 Nanjing, Jiangsu 210012 609 China 611 Email: Rachel@huawei.com 613 Qin Wu (editor) 614 Huawei 615 101 Software Avenue, Yuhua District 616 Nanjing, Jiangsu 210012 617 China 619 Email: sunseawq@huawei.com