idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.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 15, 2013) is 4021 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 670, but not defined == Unused Reference: 'RFC6709' is defined on line 507, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-15) exists of draft-ietf-xrblock-rtcp-xr-discard-11 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 S. Zhang 5 Expires: October 17, 2013 J. Zhao 6 STTRI 7 Q. Wu, Ed. 8 Huawei 9 April 15, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 12 Loss metric Reporting 13 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt 15 Abstract 17 This document defines an RTP Control Protocol (RTCP) Extended Report 18 (XR) Block that allows the reporting of Burst and Gap Loss metrics 19 for use in a range of RTP applications. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on October 17, 2013. 38 Copyright Notice 40 Copyright (c) 2013 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.1. Burst and Gap Loss Report Block . . . . . . . . . . . . . 3 57 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 58 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 59 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 62 3. Burst/Gap Loss Block . . . . . . . . . . . . . . . . . . . . . 6 63 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 64 3.2. Definition of Fields in Burst/Gap Loss Report Block . . . 6 65 3.3. Derived metrics based on reported metrics . . . . . . . . 9 66 4. Considerations for Voice-over-IP applications . . . . . . . . 11 67 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 68 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 69 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 71 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13 72 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13 73 6.3. Contact information for registrations . . . . . . . . . . 13 74 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 75 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 76 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 77 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 78 10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 79 10.2. Informative References . . . . . . . . . . . . . . . . . . 17 80 Appendix A. Metrics represented using RFC6390 Template . . . . . 18 81 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 23 82 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-11 . . . . . . . 23 83 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10 . . . . . . . 23 84 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 . . . . . . . 23 85 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 23 86 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 23 87 B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 23 88 B.7. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 24 89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 91 1. Introduction 93 1.1. Burst and Gap Loss Report Block 95 This document defines a new block type to augment those defined in 96 [RFC3611] for use in a range of RTP applications. The new block type 97 supports the reporting of the proportion of packets lost by the 98 network. The losses during loss bursts are reported, together with 99 the number of bursts and additional data allowing the calculation of 100 statistical parameters (mean and variance) of the distribution of 101 burst lengths. Some uses of these metrics depend on the availability 102 of the metric "cumulative number of packets lost" from RTCP 103 [RFC3550]. 105 This block provides information on transient IP problems. Burst/Gap 106 metrics are typically used in Cumulative reports, however they also 107 may be used in Interval reports. The burstiness of packet loss 108 affects user experience, may influence any sender strategies to 109 mitigate the problem, and may also have diagnostic value. 111 The metric belongs to the class of transport-related end system 112 metrics defined in [RFC6792]. 114 The definitions of Burst, Gap, Loss and Discard are consistent with 115 definitions in [RFC3611]. To accommodate the range of jitter buffer 116 algorithms and packet discard logic that may be used by implementors, 117 the method used to distinguish between bursts and gaps may be an 118 equivalent method to that defined in [RFC3611]. The method used 119 should produce the same result as that defined in [RFC3611] for 120 conditions of burst packet loss, but may produce different results 121 for conditions of time varying jitter. 123 1.2. RTCP and RTCP XR Reports 125 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 126 defined an extensible structure for reporting using an RTCP Extended 127 Report (XR). This document defines a new Extended Report block for 128 use with [RFC3550] and [RFC3611]. 130 1.3. Performance Metrics Framework 132 The Performance Metrics Framework [RFC6390] provides guidance on the 133 definition and specification of performance metrics. The RTP 134 Monitoring Architectures [RFC6792] provides guideline for reporting 135 block format using RTCP XR. The Metrics Block described in this 136 document are in accordance with the guidelines in [RFC6390] and 137 [RFC6792]. 139 1.4. Applicability 141 These metrics are applicable to a range of RTP applications which 142 contain jitter buffers and don't use stream repair means, e.g., 143 Forward Error Correction (FEC) [RFC5109] and/or retransmission 144 [RFC4588]. 146 2. Terminology 148 2.1. Standards Language 150 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 151 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 152 document are to be interpreted as described in RFC 2119 [RFC2119]. 154 In addition, the following terms are defined: 156 Received, Lost and Discarded 158 A packet shall be regarded as lost if it fails to arrive within an 159 implementation-specific time window. A packet that arrives within 160 this time window but is too early or late to be played out or 161 thrown away before playout due to packet duplication or redundancy 162 shall be regarded as discarded. A packet shall be classified as 163 one of received (or OK), discarded or lost. The metric 164 "cumulative number of packets lost" defined in [RFC3550] reports a 165 count of packets lost from the media stream (single SSRC within 166 single RTP session). Similarly the metric "number of packets 167 discarded" defined in [DISCARD] reports a count of packets 168 discarded from the media stream (single SSRC within single RTP 169 session) arriving at the receiver. Another metric defined in 170 [RFC5725] is available to report on packets which are not 171 recovered by any repair techniques which may be in use. 173 Bursts and Gaps 175 The terms Burst and Gap are used in a manner consistent with that 176 of RTCP XR [RFC3611]. RTCP XR views a RTP stream as being divided 177 into bursts, which are periods during which the loss rate is high 178 enough to cause noticeable quality degradation (generally over 5 179 percent loss rate), and gaps, which are periods during which lost 180 packets are infrequent and hence quality is generally acceptable. 182 3. Burst/Gap Loss Block 184 Metrics in this block report on Burst/Gap Loss in the stream arriving 185 at the RTP system. The measurement of these metrics are made at the 186 receiving end of the RTP stream. Instances of this Metrics Block 187 refer by Synchronization source (SSRC) to the separate auxiliary 188 Measurement Information block [RFC6776] which describes measurement 189 periods in use(see RFC6776 section 4.2). 191 This Metrics Block relies on the measurement period in the 192 Measurement Information block indicating the span of the report. 193 Senders MUST send this block in the same compound RTCP packet as the 194 measurement information block. Receivers MUST verify that the 195 measurement period is received in the same compound RTCP packet as 196 this Metrics Block. If not, this Metrics Block MUST be discarded. 198 3.1. Report Block Structure 200 Burst/Gap Loss metrics block 202 0 1 2 3 203 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 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | BT=NBGL | I |C| resv. | block length = 5 | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | SSRC of Source | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | Threshold | Sum of Burst Durations (ms) | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 | Packets Lost in Bursts | Total... | 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | ...Packets expected in bursts | Number of bursts | Sum of| 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | ...Squares of Burst Durations (ms-squared) | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 Figure 1: Report Block Structure 220 3.2. Definition of Fields in Burst/Gap Loss Report Block 222 Block type (BT): 8 bits 224 A Burst/Gap Loss Report Block is identified by the constant NBGL. 226 [Note to RFC Editor: please replace NBGL with the IANA provided 227 RTCP XR block type for this block.] 229 Interval Metric flag (I): 2 bits 231 This field is used to indicate whether the Burst/Gap Loss metrics 232 are Sampled, Interval or Cumulative metrics: 234 I=10: Interval Duration - the reported value applies to the 235 most recent measurement interval duration between successive 236 metrics reports. 238 I=11: Cumulative Duration - the reported value applies to the 239 accumulation period characteristic of cumulative measurements. 241 I=01: Sampled Value - the reported value is a sampled 242 instantaneous value. 244 In this document, Burst/Gap Loss Metrics can only be measured over 245 definite intervals, and cannot be sampled. Also, the value I=00 246 is reserved for future use. Senders MUST NOT use the values I=00 247 or I=01. If a block is received with I=00 or I=01, the receiver 248 MUST discard the block. 250 Loss and Discard Combination flag (C): 1 bit 252 The 'C' flag is used to indicate whether the loss/discard report 253 is combined with the burst gap loss report in the same compound 254 RTCP packet. The value is set to '1' if the loss/discard report 255 and the burst gap loss report are combined. Otherwise, the value 256 is set to '0'. If the 'C' flag is set to 1 but the burst gap 257 discard was not sent, the receiver MUST discard the burst gap 258 loss. 260 Reserved (resv): 5 bits 262 These bits are reserved. They MUST be set to zero by senders and 263 ignored by receivers (See RFC6709 section 4.2). 265 block length: 16 bits 267 The length of this report block in 32-bit words, minus one. For 268 the Burst/Gap Loss block, the block length is equal to 5. The 269 block MUST be discarded if the block length is set to a different 270 value. 272 SSRC of source: 32 bits 274 As defined in Section 4.1 of [RFC3611]. 276 Threshold: 8 bits 278 The Threshold is equivalent to Gmin in [RFC3611], i.e. the number 279 of successive packets that must be received prior to and following 280 a lost packet in order for this lost packet to be regarded as part 281 of a gap. Note that the threshold is calculated in accordance 282 with Gmin Calculation defined in section 4.7.2 of RFC3611. 284 Sum of Burst Durations (ms): 24 bits 286 The total duration of bursts of lost packets in the period of the 287 report (Interval or Cumulative). 289 The measured value is unsigned value. If the measured value 290 exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate 291 an over-range measurement. If the measurement is unavailable, the 292 value 0xFFFFFF MUST be reported. 294 Packets lost in bursts: 24 bits 296 The total number of packets lost during loss bursts. 298 The measured value is unsigned value. If the measured value 299 exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate 300 an over-range measurement. If the measurement is unavailable, the 301 value 0xFFFFFF MUST be reported. 303 Total packets expected in bursts: 24 bits 305 The total number of packets expected during loss bursts (that is, 306 the sum of received packets and lost packets). 308 The measured value is unsigned value. If the measured value 309 exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate 310 an over-range measurement. If the measurement is unavailable, the 311 value 0xFFFFFF MUST be reported. 313 Number of bursts: 16 bits 315 The number of bursts in the period of the report (Interval or 316 Cumulative). 318 The measured value is unsigned value. If the measured value 319 exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an 320 over-range measurement. If the measurement is unavailable, the 321 value 0xFFFF MUST be reported. 323 Sum of Squares of Burst Durations (ms-squared): 36 bits 325 The sum of the squares of burst durations (where individual burst 326 durations are expressed in ms) over in the period of the report 327 (Interval or Cumulative). The units for this quantity are 328 milliseconds-squared. 330 The measured value is unsigned value. If the measured value 331 exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE MUST be reported to 332 indicate an over-range measurement. If the measurement is 333 unavailable, the value 0xFFFFFFFFF MUST be reported. 335 3.3. Derived metrics based on reported metrics 337 The metrics described here are intended to be used as described in 338 this section, in conjunction with information from the Measurement 339 Information block [RFC6776] and also with the metric "cumulative 340 number of packets lost" provided in standard RTCP [RFC3550]. 342 These metrics provide information relevant to statistical parameters, 343 including: 345 o The fraction of packets lost during bursts (i.e., Burst Loss Rate 346 in [SUMSTAT]), which can be calculated using the metric " Packets 347 Loss in Bursts " and the metric " Total Packets expected in Bursts 348 " provided in the Burst/Gap Loss metrics block. 350 o The fraction of packets lost during gaps (i.e., Gap Loss Rate in 351 [SUMSTAT]), which can be calculated using the metric " Packets 352 Loss in Bursts " and the metric " Total Packets expected in Bursts 353 " provided in the Burst/Gap Loss metrics block. 355 o burst duration mean [SUMSTAT], which can be calculated using the 356 metric " Packets Loss in Bursts " and the metric " Total Packets 357 expected in Bursts " provided in the Burst/Gap Loss metrics block. 359 o burst duration variance [SUMSTAT], which can be calculated using 360 the metric " Packets Loss in Bursts " and the metric " Total 361 Packets expected in Bursts " provided in the Burst/Gap Loss 362 metrics block. 364 The details on calculation these parameters in the metrics are 365 described in [SUMSTAT]. 367 4. Considerations for Voice-over-IP applications 369 This Metrics Block is applicable to a broad range of RTP 370 applications. Where the metric is used with a Voice-overIP (VoIP) 371 application and the stream repair means is not available, the 372 following considerations apply. 374 RTCP XR views a call as being divided into bursts, which are periods 375 during which the loss rate is high enough to cause noticeable call 376 quality degradation (generally over 5 percent loss rate), and gaps, 377 which are periods during which lost packets are infrequent and hence 378 call quality is generally acceptable. 380 If Voice Activity Detection is used, the Burst and Gap Duration shall 381 be determined as if silence packets had been sent, i.e. a period of 382 silence in excess of Gmin packets will terminate a burst condition. 384 The recommended value for the threshold Gmin in [RFC3611] results in 385 a Burst being a period of time during which the call quality is 386 degraded to a similar extent to a typical Pulse-Code Modulation(PCM) 387 Severely Errored Second. 389 5. SDP Signaling 391 [RFC3611] defines the use of SDP (Session Description Protocol) 392 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 393 without prior signaling. 395 5.1. SDP rtcp-xr-attrib Attribute Extension 397 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 398 in [RFC3611] by providing an additional value of "xr-format" to 399 signal the use of the report block defined in this document. 401 xr-format =/ xr-bgl-block 403 xr-bgl-block = "burst-gap-loss" 405 5.2. Offer/Answer Usage 407 When SDP is used in offer-answer context, the SDP Offer/Answer usage 408 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 409 applies. For detailed usage in Offer/Answer for unilateral 410 parameter, refer to section 5.2 of [RFC3611]. 412 6. IANA Considerations 414 New block types for RTCP XR are subject to IANA registration. For 415 general guidelines on IANA considerations for RTCP XR, refer to 416 [RFC3611]. 418 6.1. New RTCP XR Block Type value 420 This document assigns the block type value NBGL in the IANA " RTP 421 Control Protocol Extended Reports (RTCP XR) Block Type Registry " to 422 the "Burst/Gap Loss Metrics Block". 424 [Note to RFC Editor: please replace NBGL with the IANA provided RTCP 425 XR block type for this block.] 427 6.2. New RTCP XR SDP Parameter 429 This document also registers a new parameter "burst-gap-loss" in the 430 " RTP Control Protocol Extended Reports (RTCP XR) Session Description 431 Protocol (SDP) Parameters Registry". 433 6.3. Contact information for registrations 435 The contact information for the registrations is: 437 Qin Wu (sunseawq@huawei.com) 439 101 Software Avenue, Yuhua District 440 Nanjing, Jiangsu 210012 441 China 443 7. Security Considerations 445 This block does not provide per-packet statistics, so the risk to 446 confidentiality documented in Section 7, paragraph 3 of [RFC3611] 447 does not apply. However the gaps indicated within this block could 448 be used to detect the timing of other events on the path between the 449 sender and receiver. For example, a competing multimedia stream 450 might cause a loss burst for the duration of the stream, allowing the 451 receiver of this block to know when the competing stream was active. 452 This risk is not a significant threat since the only information 453 leaked is the timing of the loss, not the cause. Besides this, it is 454 believed that this proposed RTCP XR report block introduces no other 455 new security considerations beyond those described in [RFC3611]. 457 8. Contributors 459 Geoff Hunt wrote the initial draft of this document. 461 9. Acknowledgments 463 The authors gratefully acknowledge reviews and feedback provided by 464 Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, 465 Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, 466 Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, 467 Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi 468 Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Adam Roach, 469 Dan Romascanu,Chris Lonvick, Alfred C.,Morton Jr., Pete Resnick, Ted 470 Lemon, Stephen Farrell, Richard Barnes, Benoit Claise. 472 10. References 474 10.1. Normative References 476 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 477 Requirement Levels", March 1997. 479 [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time 480 Applications", RFC 3550, July 2003. 482 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 483 Protocol Extended Reports (RTCP XR)", November 2003. 485 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 486 Description Protocol", July 2006. 488 [RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE 489 Report Block Type for RTP Control Protocol (RTCP) Extended 490 Reports (XRs)", RFC 5725, February 2020. 492 10.2. Informative References 494 [DISCARD] Wu, Q., "RTCP XR Report Block for Discard metric 495 Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-11, 496 December 2012. 498 [RFC4588] Rey, J., Leon, D., , A., Varsa, V., and R. Hakenberg, "RTP 499 Retransmission Payload Format", RFC 4588, July 2006. 501 [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error 502 Correction", RFC 5109, December 2007. 504 [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric 505 Development", RFC 6390, July 2011. 507 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 508 Considerations for Protocol Extensions", RFC 6709, 509 September 2012. 511 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 512 using SDES item and XR Block", RFC 6776, October 2012. 514 [RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792, 515 November 2012. 517 [SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics 518 Reporting", ID draft-ietf-xrblock-rtcp-xr-summary-stat-11, 519 March 2013. 521 Appendix A. Metrics represented using RFC6390 Template 523 RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC 524 number, when assigned. 526 a. Threshold Metric 528 * Metric Name: Threshold in RTP 530 * Metric Description: The Threshold is equivalent to Gmin in 531 [RFC3611], i.e. the number of successive RTP packets that must 532 be received prior to and following a lost RTP packet in order 533 for this lost RTP packet to be regarded as part of a gap. 535 * Method of Measurement or Calculation: See section 3.2, 536 Threshold definition [RFCXXXX]. 538 * Units of Measurement: See section 3.2, Threshold definition 539 [RFCXXXX]. 541 * Measurement Point(s) with Potential Measurement Domain: See 542 section 3, 1st paragraph [RFCXXXX]. 544 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 545 measurement timing and section 3.2 [RFCXXXX] for Interval 546 Metric flag. 548 * Use and applications: See section 1.4 [RFCXXXX]. 550 * Reporting model: See RFC3611. 552 b. Sum of Burst Durations Metric 554 * Metric Name: Sum of Burst Durations in RTP 556 * Metric Description: The total duration of bursts of lost RTP 557 packets in the period of the report. 559 * Method of Measurement or Calculation: See section 3.2, Sum of 560 Burst Durations definition [RFCXXXX]. 562 * Units of Measurement: See section 3.2, Sum of Burst Durations 563 definition [RFCXXXX]. 565 * Measurement Point(s) with Potential Measurement Domain: See 566 section 3, 1st paragraph [RFCXXXX]. 568 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 569 measurement timing and section 3.2 [RFCXXXX] for Interval 570 Metric flag. 572 * Use and applications: See section 1.4 [RFCXXXX]. 574 * Reporting model: See RFC3611. 576 c. Packets lost in bursts Metric 578 * Metric Name: RTP Packets lost in bursts 580 * Metric Description: The total number of RTP packets lost 581 during loss bursts. 583 * Method of Measurement or Calculation: See section 3.2, Packets 584 lost in bursts definition [RFCXXXX]. 586 * Units of Measurement: See section 3.2, Packets lost in bursts 587 definition [RFCXXXX]. 589 * Measurement Point(s) with Potential Measurement Domain: See 590 section 3, 1st paragraph [RFCXXXX]. 592 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 593 measurement timing and section 3.2 [RFCXXXX] for Interval 594 Metric flag. 596 * Use and applications: See section 1.4 [RFCXXXX]. 598 * Reporting model: See RFC3611. 600 d. Total packets expected in bursts Metric 602 * Metric Name: Total RTP packets expected in bursts 604 * Metric Description: The total number of RTP packets expected 605 during loss bursts (that is, the sum of received RTP packets 606 and lost RTP packets). 608 * Method of Measurement or Calculation: See section 3.2, Total 609 packets expected in bursts definition [RFCXXXX]. 611 * Units of Measurement: See section 3.2, Total packets expected 612 in bursts definition [RFCXXXX]. 614 * Measurement Point(s) with Potential Measurement Domain: See 615 section 3, 1st paragraph [RFCXXXX]. 617 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 618 measurement timing and section 3.2 [RFCXXXX] for Interval 619 Metric flag. 621 * Use and applications: See section 1.4 [RFCXXXX]. 623 * Reporting model: See RFC3611. 625 e. Number of bursts Metric 627 * Metric Name: Number of bursts in RTP 629 * Metric Description: The total duration of bursts of lost RTP 630 packets in the period of the report. 632 * Method of Measurement or Calculation: See section 3.2, Number 633 of bursts definition [RFCXXXX]. 635 * Units of Measurement: See section 3.2, Number of bursts 636 definition [RFCXXXX]. 638 * Measurement Point(s) with Potential Measurement Domain: See 639 section 3, 1st paragraph [RFCXXXX]. 641 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 642 measurement timing and section 3.2 [RFCXXXX] for Interval 643 Metric flag. 645 * Use and applications: See section 1.4 [RFCXXXX]. 647 * Reporting model: See RFC3611. 649 f. Sum of Squares of Burst Durations Metric 651 * Metric Name: Sum of Squares of Burst Durations in RTP 653 * Metric Description: The sum of the squares of burst durations 654 (where individual burst durations are expressed in ms) over in 655 the period of the report. 657 * Method of Measurement or Calculation: See section 3.2, Sum of 658 Squares of Burst Durations definition [RFCXXXX]. 660 * Units of Measurement: See section 3.2, Sum of Squares of Burst 661 Durations definition [RFCXXXX]. 663 * Measurement Point(s) with Potential Measurement Domain: See 664 section 3, 1st paragraph [RFCXXXX]. 666 * Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for 667 measurement timing and section 3.2 [RFCXXXX] for Interval 668 Metric flag. 670 * Use and applications: See section 1.4 [RFCXXXX]. 672 * Reporting model: See RFC3611. 674 Appendix B. Change Log 676 Note to the RFC-Editor: please remove this section prior to 677 publication as an RFC. 679 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-11 681 The following are the major changes compared to previous version: 683 o Incorporated Ted's proposed change during IESG review. 685 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10 687 The following are the major changes compared to previous version: 689 o IESG Review comments are addressed in this version. 691 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 693 The following are the major changes compared to previous version: 695 o IETF LC comments are addressed together with AD's comment on 696 Normative language in this version. 698 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 700 The following are the major changes compared to previous version: 702 o Move RFC6709 as one informative reference. 704 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 706 The following are the major changes compared to previous version: 708 o Editorial changes based on comments in the WGLC. 710 B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 712 The following are the major changes compared to previous version: 714 o SDP update based on SDP Directorate Review. 716 o Add some texts to get consistent with RFC6798 and Delay draft. 718 B.7. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 720 The following are the major changes compared to previous version: 722 o Outdated reference update. 724 o Editorial changes based on comments that applied to PDV and Delay 725 drafts. 727 Authors' Addresses 729 Alan Clark 730 Telchemy Incorporated 731 2905 Premiere Parkway, Suite 280 732 Duluth, GA 30097 733 USA 735 Email: alan.d.clark@telchemy.com 737 Sunshine Zhang 738 Shanghai Research Institute of China Telecom Corporation Limited 739 No.1835,South Pudong Road 740 Shanghai 200122 741 China 743 Email: zhangyx@sttri.com.cn 745 Jing Zhao 746 Shanghai Research Institute of China Telecom Corporation Limited 747 No.1835,South Pudong Road 748 Shanghai 200122 749 China 751 Email: zhaojing@sttri.com.cn 753 Qin Wu (editor) 754 Huawei 755 101 Software Avenue, Yuhua District 756 Nanjing, Jiangsu 210012 757 China 759 Email: sunseawq@huawei.com