idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 25, 2013) is 4043 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 934, but not defined == Unused Reference: 'RFC6390' is defined on line 673, but no explicit reference was found in the text == Unused Reference: 'RFC6709' is defined on line 676, but no explicit reference was found in the text == Outdated reference: A later version (-14) exists of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 == Outdated reference: A later version (-12) exists of draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 == Outdated reference: A later version (-15) exists of draft-ietf-xrblock-rtcp-xr-discard-09 ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: Standards Track R. Schott 5 Expires: September 26, 2013 Deutsche Telekom 6 Q. Wu, Ed. 7 R. Huang 8 Huawei 9 March 25, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-11 15 Abstract 17 This document defines three RTP Control Protocol (RTCP) Extended 18 Report (XR) Blocks that allow the reporting of loss, duplication and 19 discard summary statistics metrics 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 September 26, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 1.1. Summary Statistics Metrics . . . . . . . . . . . . . . . . 4 57 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 58 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4 59 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 62 3. Transport Related End System Metrics . . . . . . . . . . . . . 5 63 3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 5 64 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 6 65 3.1.2. Definition of Fields in Loss Summary Statistics 66 Block . . . . . . . . . . . . . . . . . . . . . . . . 6 67 3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 8 68 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 9 69 3.2.2. Definition of Fields in Burst/Gap Discard Summary 70 Statistics Block . . . . . . . . . . . . . . . . . . . 9 71 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 11 72 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 11 73 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 11 74 4.1.2. Definition of Fields in Frame Impairment Summary 75 Statistics Block . . . . . . . . . . . . . . . . . . . 12 76 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 13 77 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 13 78 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 14 79 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 80 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 14 81 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 14 82 6.3. Contact information for registrations . . . . . . . . . . 15 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 84 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 87 9.2. Informative References . . . . . . . . . . . . . . . . . . 16 88 Appendix A. Metrics represented using RFC6390 Template . . . . . 16 89 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 22 90 B.1. draft-ietf-xrblock-rtcp-xr-summary-stat-11 . . . . . . . . 22 91 B.2. draft-ietf-xrblock-rtcp-xr-summary-stat-10 . . . . . . . . 22 92 B.3. draft-ietf-xrblock-rtcp-xr-summary-stat-09 . . . . . . . . 22 93 B.4. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 22 94 B.5. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 22 95 B.6. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 22 96 B.7. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 22 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 99 1. Introduction 101 1.1. Summary Statistics Metrics 103 This draft defines three new block types to augment those defined in 104 [RFC3611] for use in a range of RTP applications. 106 o Burst/Gap Loss Summary Statistics Metrics Block 107 o Burst/Gap Discard Summary Statistics Metrics Block 108 o Frame Impairment Statistics Summary Metrics Block 110 The first two block types support the reporting of burst gap loss/ 111 discard summary statistics including packet loss/discard proportion, 112 mean and variance and belong to the class of transport-related end 113 system metrics defined in [RFC6792]. These two blocks are intended 114 to be used in conjunction with information from the Burst Gap Loss 115 Metrics Block [BGLOSS] or Burst Gap Discard Metrics Block 116 [BGDISCARD], and on which these two blocks therefore depend. The 117 metrics in the Burst Gap Loss Metrics block or Burst Gap Discard 118 Metrics Block are consistent with the definitions of Burst, Gap, Loss 119 and Discard in RTCP XR [RFC3611]. 121 The third block supports the reporting of detailed video statistics 122 for each frame type, including the number of frames received, lost 123 and discarded of each frame type in the Group of Pictures (GOP) and 124 additional data allowing the calculation of statistical parameters 125 (e.g.,the proportion of each frame type impaired by packet loss and 126 discard). The metrics defined in this block belong to the class of 127 application layer metrics defined in [RFC6792]. 129 1.2. RTCP and RTCP XR Reports 131 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 132 defined an extensible structure for reporting using an RTCP Extended 133 Report (XR). This document defines a new Extended Report block for 134 use with [RFC3550] and [RFC3611]. 136 1.3. Performance Metrics Framework 138 The RTP Monitoring Architectures [RFC6792] provides guideline for 139 reporting block format using RTCP XR. Metrics described in this 140 draft are in accordance with the guidelines in [RFC6792]. 142 1.4. Applicability 144 These metrics are applicable to a wide range of RTP applications and 145 reflect transient IP problems that affect user experience. They can 146 be used to form an accurate assessment of users' quality of 147 experience and influence sender strategies to mitigate the problem. 149 2. Terminology 151 2.1. Standards Language 153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 155 document are to be interpreted as described in RFC 2119 [RFC2119]. 157 In addition, the following terms are defined: 159 Frame Type 161 In many cases, a video frame is compressed using different 162 algorithms. Frame type is used to identify different algorithms 163 for video frames. Two frame Types used in the different video 164 algorithms are the Key frame and Derived frames. The Key frame is 165 independently coded without prediction from other pictures and 166 used as a reference frame for predicting other pictures. Derived 167 frames are predicatively coded and derived from a Key frame using 168 a prediction algorithm If there is no video image compression, all 169 frames are Key Frames. 171 3. Transport Related End System Metrics 173 3.1. Burst/Gap Loss Summary Statistics Metrics Block 175 This Block extends packet loss and discard metrics defined in section 176 4.7.1 of RFC3611. The metrics described here are intended to be used 177 as described in this section, in conjunction with information from 178 the Measurement Information block [RFC6776] (which MUST be present in 179 the same RTCP packet as the Burst/Gap Loss block) and also with the 180 metric "cumulative number of packets lost" provided in standard RTCP 181 [RFC3550]. Instances of this Metrics Block refer by Synchronization 182 source (SSRC) to the separate auxiliary Measurement Information block 183 [RFC6776] which describes measurement periods in use (see [RFC6776] 184 section 4.2). This Metrics Block relies on the measurement period in 185 the Measurement Information block indicating the span of the report 186 and SHOULD be sent in the same compound RTCP packet as the 187 measurement information block. If the measurement period is not 188 received in the same compound RTCP packet as this Metrics Block, this 189 metrics block MUST be discarded. 191 The metrics carried in this Metrics Block provide information 192 relevant to statistical parameters, including burst loss rate, gap 193 loss rate, burst duration mean, burst duration variance and are 194 measured at the receiving end of the RTP stream using burst gap loss 195 metrics defined in [BGLOSS] and other information which is sent 196 together with this report block. 198 3.1.1. Report Block Structure 200 0 1 2 3 201 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 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | BT=BGLSS | I | Reserved | block length | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | SSRC of Source | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | Burst Loss Rate | Gap Loss Rate | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | Burst duration Mean | Burst duration Variance | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 3.1.2. Definition of Fields in Loss Summary Statistics Block 214 Block Type (BT): 8 bits 216 Burst/Gap Loss Summary Statistics Block is identified by the 217 constant . 219 Interval Metric Flag (I): 2 bits 221 This field is used to indicate whether the Burst/Gap Loss Summary 222 Statistics metrics are Sampled, Interval or Cumulative metrics: 224 I=10: Interval Duration - the reported value applies to the 225 most recent measurement interval duration between successive 226 metrics reports. 227 I=11: Cumulative Duration - the reported value applies to the 228 accumulation period characteristic of cumulative measurements. 229 I=01: Sampled Value - the reported value is a sampled 230 instantaneous value. 232 In this document, the value I=00 is the reserved value and MUST 233 NOT be used. 235 Reserved: 6 bits 237 This field is reserved for future definition. In the absence of 238 such a definition, the bits in this field MUST be set to zero and 239 ignored by the receiver (See RFC6709 section 4.2). 241 Block Length: 16 bits 243 The constant 3, in accordance with the definition of this field in 244 Section 3 of RFC 3611 [RFC3611]. 246 SSRC of Source: 32 bits 248 As defined in Section 4.1 of RFC3611 [RFC3611]. 250 Burst Loss Rate: 16 bits 252 The fraction of packets lost during bursts since the beginning of 253 reception, expressed as a fixed point number with the binary point 254 immediately after the left-most bit. This value is calculated by 255 dividing Packets Lost in Bursts by Total Packets Expected in 256 Bursts, multiplying the result of the division by 32768 257 (0x8000),and keeping only the integer part. The maximum value is 258 thus 0x8000. Representing this as a formula: 260 integer-part( (Packets Lost in Bursts / Total Packets Expected in 261 Bursts) * 0x8000 ) 263 If the measurement is unavailable, the value 0xFFFF MUST be 264 reported. 266 Gap Loss Rate: 16 bits 268 The fraction of packets lost during gaps since the beginning of 269 reception expressed as a fixed point number with the binary point 270 immediately after the left-most bit. This value is calculated by 271 dividing the difference between number of packets lost and Packets 272 lost in Bursts by the difference between Packets Expected and 273 Total Packets expected in Bursts, multiplying the result of the 274 division by 32768 (0x8000),and keeping only the integer part. The 275 maximum value is thus 0x8000. Representing this as a formula: 277 integer-part ( (number of packets lost - Packets Lost in Bursts)/ 278 (Packets Expected - Total Packets expected in Bursts) * 0x8000 ) 280 where "number of packets lost" is obtained from standard RTCP 281 [RFC3550] and Packets Expected is calculated as the difference 282 between "extended last sequence number" and "extended first 283 sequence number" (Interval or Cumulative) provided in the 284 Measurement Identity and Information block [RFC6776]. 286 If the measurement is unavailable, the value 0xFFFF MUST be 287 reported. 289 Note that if the metric is to be calculated on an Interval basis, 290 a difference must be taken between the current and preceding 291 values of "cumulative number of packets lost" in RTCP, to obtain 292 the "number of packets lost" for the reporting interval. 294 Burst Duration Mean:16bits 296 The mean burst duration is obtained as the quotient: 298 mean = Sum of Burst Durations / Number of Bursts 300 where "Sum of Burst Durations" and "Number of Bursts" is obtained 301 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 303 If the measurement is unavailable, the value 0xFFFF MUST be 304 reported. 306 Burst Duration Variance:16bits 308 The variance of the burst duration is obtained using the standard 309 result: 311 var = ( Sum of Squares of Burst Durations - Number of Bursts * 312 mean^2 ) / (Number of Bursts - 1) 314 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 315 obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 317 If the measurement is unavailable, the value 0xFFFF MUST be 318 reported. 320 3.2. Burst/Gap Discard Summary Statistics Metrics Block 322 This Block extends packet loss and discard metrics defined in section 323 4.7.1 of RFC3611. The metrics described here are intended to be used 324 as described in this section, in conjunction with information from 325 the Measurement Identity block [RFC6776] (which MUST be present in 326 the same RTCP packet as the Burst/Gap Discard Summary Statistics 327 block) . 329 These metrics provide information relevant to statistical parameters, 330 including burst discard rate, gap discard rate and are measured at 331 the receiving end of the RTP stream using burst gap discard metrics 332 defined in [BGDISCARD] and other information which is sent together 333 with this report block. 335 Instances of this Metrics Block refer by Synchronization source 336 (SSRC) to the separate auxiliary Measurement Information block 337 [RFC6776] which describes measurement periods in use (see [RFC6776] 338 section 4.2). This metrics block relies on the measurement period in 339 the Measurement Information block indicating the span of the report 340 and SHOULD be sent in the same compound RTCP packet as the 341 measurement information block. If the measurement period is not 342 received in the same compound RTCP packet as this Metrics Block, this 343 Metrics Block MUST be discarded. 345 3.2.1. Report Block Structure 347 0 1 2 3 348 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 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | BT=BGDSS | I | Reserved | block length | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | SSRC of Source | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | Burst Discard Rate | Gap Discard Rate | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 358 Block 360 Block Type (BT): 8 bits 362 Burst/Gap Discard Summary Statistics Block is identified by the 363 constant . 365 Interval Metric Flag (I): 2 bits 367 This field is used to indicate whether the Burst/Gap Discard 368 Summary Statistics metrics are Sampled, Interval or Cumulative 369 metrics: 371 I=10: Interval Duration - the reported value applies to the 372 most recent measurement interval duration between successive 373 metrics reports. 374 I=11: Cumulative Duration - the reported value applies to the 375 accumulation period characteristic of cumulative measurements. 376 I=01: Sampled Value - the reported value is a sampled 377 instantaneous value. 379 In this document, the value I=00 is the reserved value and MUST 380 NOT be used. 382 Reserved: 6 bits 384 This field is reserved for future definition. In the absence of 385 such a definition, the bits in this field MUST be set to zero and 386 ignored by the receiver (See RFC6709 section 4.2). 388 Block Length: 16 bits 390 The constant 2, in accordance with the definition of this field in 391 Section 3 of RFC 3611 [RFC3611]. 393 SSRC of Source: 32 bits 395 As defined in Section 4.1 of RFC3611 [RFC3611]. 397 Burst Discard Rate: 16 bits 399 The fraction of packets discarded during bursts since the 400 beginning of reception, expressed as a fixed point number with the 401 binary point immediately after the left-most bit. This value is 402 calculated by dividing Packets Discarded in Bursts by Total 403 Packets expected in Bursts, multiplying the result of the division 404 by 32768 (0x8000), and keeping only the integer part, according to 405 the formula: 407 integer-part( (Packets Discarded in Bursts / Total Packets 408 expected in Bursts) * 0x8000 ) 410 If the measurement is unavailable, the value 0xFFFF MUST be 411 reported. 413 Gap Discard Rate: 16 bits 415 The fraction of packets discarded during gaps since the beginning 416 of reception expressed as a fixed point number with the binary 417 point immediately after the left-most bit. This value is 418 calculated by dividing the difference between number of packets 419 discarded and Packets Discarded in Bursts by the difference 420 between Packets Expected and Total Packets expected in Bursts, 421 multiplying the result of the division by 32768 (0x8000), and 422 keeping only the integer part. The maximum value is thus 0x8000. 423 Representing this as a formula: 425 integer-part( (number of packets discarded - Packets Discarded in 426 Bursts) /(Packets Expected - Total Packets expected in Bursts) * 427 0x8000 ) 429 where "number of packets discarded" is obtained from the RTCP XR 430 Discard Count Block [DISCARD] and filled with the sum of packets 431 discarded due to early arrival (DT=1) and packets discarded due to 432 late arrival(DT=2) and Packets Expected is calculated as the 433 difference between "extended last sequence number" and "extended 434 first sequence number" (Interval or Cumulative) provided in the 435 Measurement Information block [RFC6776]. In order for the Burst/ 436 Gap Discard Summary Statistics Block to be meaningful, 2 instances 437 of the Discard Count block with DT=1 and DT=2 MUST be included in 438 the same RTCP XR packet as the Burst/Gap Discard Summary 439 Statistics Block. 441 If the measurement is unavailable, the value 0xFFFF MUST be 442 reported. 444 4. Application Level Metrics 446 4.1. Frame Impairment Statistics Summary Metrics Block 448 This block extends statistics summary report mechanism defined in 449 section 4.6 of RFC3611 and reports statistics on which frame type 450 were affected beyond the information carried in the Statistics 451 Summary Report Block RTCP packet specified in the section 4.6 of RFC 452 3611 [RFC3611]. Information is measured at the receiving end of the 453 RTP stream and recorded about the number of frames received, lost 454 frames, duplicated frames and lost partial frames. Such information 455 can be useful for network management and video quality monitoring. 457 4.1.1. Report Block Structure 459 0 1 2 3 460 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 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | BT=FISS |T| Reserved | block length | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 | SSRC of Source | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | begin_seq | end_seq | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 468 | Discarded_frames | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 | Dup_frames | 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | Full_lost_frames | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 | Partial_lost_frames | 475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 478 Block 480 Block type (BT): 8 bits 482 Frame Impairment Statistics Summary Block is identified by the 483 constant . 485 Frame type indicator (T): 1 bit 487 This field is used to indicate the frame type to be reported. The 488 bit is set to 0 if the full_lost_frames, partial_lost_frames, 489 dup_frames,discarded_frames and Number of frames received fields 490 contain Key frame (reference frame) counts or 1 if they contain 491 Derived frame counts. Note that if both the Key frame and 492 Derivation frame report are sent, they should be sent in the same 493 RTCP compound packet using two Frame Impairment Summary Statistics 494 Blocks. 496 Reserved: 7 bits 498 This field is reserved for future definition. In the absence of 499 such a definition, the bits in this field MUST be set to zero and 500 ignored by the receiver (See RFC6709 section 4.2). 502 Block Length: 16 bits 504 The constant 6, in accordance with the definition of this field in 505 Section 3 of RFC 3611 [RFC3611]. 507 SSRC of Source: 32 bits 509 As defined in Section 4.1 of RFC3611 [RFC3611]. 511 begin_seq: 16 bits 513 As defined in Section 4.1 of RFC 3611 [RFC3611]. 515 end_seq: 16 bits 517 As defined in Section 4.1 of RFC 3611 [RFC3611]. 519 Number of discarded frames (discarded_frames): 32 bits 521 Number of frames discarded in the above sequence number interval. 523 Number of duplicate frames (dup_frames): 32 bits 525 Number of duplicate frames received in the above sequence number 526 interval. 528 Number of full lost frames (full_lost_frames): 32 bits 530 A frame is either split across multiple packets or carried in only 531 one packet.If the whole frame or all the packets of the frame is 532 lost, this frame is regarded as one full_lost_frame. The 533 full_lost_frames can be inferred from packet(s) that comprise the 534 frame. The full_lost_ frames is equivalent to the number of full 535 lost frames in the above sequence number interval. 537 Number of partial lost frames (partial_lost_frames): 32 bits 539 When a frame is split across multiple packets and some packets of 540 the frame are lost, this frame is regarded as one 541 partial_lost_frame. The partial_lost_frames can be inferred from 542 packets that comprise the frame. The value of the 543 partial_lost_frames field is equivalent to the number of partial 544 lost frames in the above sequence number interval. 546 5. SDP Signaling 548 RFC 3611 defines the use of SDP (Session Description Protocol) 549 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 550 be used without prior signaling (see section 5 of RFC3611). 552 5.1. SDP rtcp-xr-attrib Attribute Extension 554 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 555 in Section 5.1 of RFC 3611 by providing three additional values of 556 "xr-format" to signal the use of the report block defined in this 557 document. 559 xr-format = / xr-bglss-block 560 / xr-bgdss-block 561 / xr-fiss-block 562 xr-bglss-block= "burst-gap-loss-stat" 563 xr-bgdss-block = "burst-gap-discard-stat" 564 xr-fiss-block= "frame-impairment-stat" 566 5.2. Offer/Answer Usage 568 When SDP is used in offer-answer context, the SDP Offer/Answer usage 569 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 570 applies. For detailed usage of Offer/Answer for unilateral 571 parameter, refer to section 5.2 of [RFC3611]. 573 6. IANA Considerations 575 New block types for RTCP XR are subject to IANA registration. For 576 general guidelines on IANA considerations for RTCP XR, refer to RFC 577 3611. 579 6.1. New RTCP XR Block Type values 581 This document assigns three new block type value in the "RTP Control 582 Protocol (RTCP) Extended Report (XR) Block Type Registry" : 584 Name: BGLSS 585 Long Name: Burst/Gap Loss Summary Statistics Block 586 Value 587 Reference: Section 3.1 589 Name: BGDSS 590 Long Name: Burst/Gap Discard Summary Statistics Block 591 Value 592 Reference: Section 3.2 594 Name: FISS 595 Long Name: Frame Impairment Statistics Summary 596 Value 597 Reference: Section 4.1 599 6.2. New RTCP XR SDP Parameters 601 This document also registers three new SDP [RFC4566] parameters for 602 the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended 603 Report (XR) SDP Parameters Registry ": 605 * "burst-gap-loss-stat" 606 * "burst-gap-discard-stat" 607 * "frame-impairment-stat" 609 6.3. Contact information for registrations 611 The contact information for the registrations is: 613 Qin Wu (sunseawq@huawei.com) 614 101 Software Avenue, Yuhua District 615 Nanjing, Jiangsu 210012 616 China 618 7. Security Considerations 620 The new RTCP XR report blocks proposed in this document introduces no 621 new security considerations beyond those described in RFC 3611. 623 8. Acknowledgements 625 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 626 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 627 Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton 628 Jr., Alfred, Klaas Wierenga, Barry Leiba, Robert Sparks, Ralph Droms 629 and Benoit Claise for their valuable comments and suggestions on this 630 document. 632 9. References 634 9.1. Normative References 636 [BGDISCARD] 637 Clark, A., Huang, R., and W. Wu, "RTP Control 638 Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 639 Discard metric Reporting", 640 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in 641 progress), December 2012. 643 [BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control 644 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 645 Loss metric Reporting", 646 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in 647 progress), December 2012. 649 [DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol 650 (RTCP) Extended Report (XR) Block for Discard Count metric 651 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 652 progress), October 2012. 654 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 655 Requirement Levels", BCP 14, RFC 2119, March 1997. 657 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 658 Jacobson, "RTP: A Transport Protocol for Real-Time 659 Applications", STD 64, RFC 3550, July 2003. 661 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 662 Protocol Extended Reports (RTCP XR)", RFC 3611, 663 November 2003. 665 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 666 Description Protocol", RFC 4566, July 2006. 668 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 669 using SDES item and XR Block", RFC 6776, August 2012. 671 9.2. Informative References 673 [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New 674 Performance Metric Development", RFC 6390, October 2011. 676 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 677 Considerations for Protocol Extensions", RFC 6709, 678 September 2012. 680 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 681 for RTP", RFC 6792, November 2012. 683 Appendix A. Metrics represented using RFC6390 Template 685 RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC 686 number, when assigned. 688 a. Burst Loss Rate Metric 690 * Metric Name: RTP Burst Loss Rate 692 * Metric Description: The fraction of packets lost during bursts 693 since the beginning of reception for RTP traffic. 695 * Method of Measurement or Calculation: See section 3.1.2, Burst 696 Loss Rate definition [RFCXXXX]. 698 * Units of Measurement: See section 3.1.2, Burst Loss Rate 699 definition [RFCXXXX]. 701 * Measurement Point(s) with Potential Measurement Domain: See 702 section 3.1, 2nd paragraph [RFCXXXX]. 704 * Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] 705 for measurement timing and section 3.1.2 [RFCXXXX] for 706 Interval Metric flag. 708 * Use and applications: See section 1.4 [RFCXXXX]. 710 * Reporting model: See RFC3611. 712 b. Gap Loss Rate Metric 714 * Metric Name: RTP Gap Loss Rate 716 * Metric Description: The fraction of packets lost during gaps 717 since the beginning of reception for RTP traffic. 719 * Method of Measurement or Calculation: See section 3.1.2, Gap 720 Loss Rate definition [RFCXXXX]. 722 * Units of Measurement: See section 3.1.2, Gap Loss Rate 723 definition [RFCXXXX]. 725 * Measurement Point(s) with Potential Measurement Domain: See 726 section 3.1, 2nd paragraph [RFCXXXX]. 728 * Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] 729 for measurement timing and section 3.1.2 [RFCXXXX] for 730 Interval Metric flag. 732 * Use and applications: See section 1.4 [RFCXXXX]. 734 * Reporting model: See RFC3611. 736 c. Burst duration Mean Metric 738 * Metric Name: RTP Burst duration Mean 740 * Metric Description: The mean duration of the burst periods 741 that have occurred since the beginning of reception for RTP 742 traffic. 744 * Method of Measurement or Calculation: See section 3.1.2, Burst 745 Loss Rate definition [RFCXXXX]. 747 * Units of Measurement: This metric is expressed in 748 milliseconds. 750 * Measurement Point(s) with Potential Measurement Domain: See 751 section 3.1, 2nd paragraph [RFCXXXX]. 753 * Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] 754 for measurement timing and section 3.1.2 [RFCXXXX] for 755 Interval Metric flag. 757 * Use and applications: See section 1.4 [RFCXXXX]. 759 * Reporting model: See RFC3611. 761 d. Burst duration variance Metric 763 * Metric Name: RTP Burst duration variance 765 * Metric Description: The variance duration of the burst periods 766 that have occurred since the beginning of reception for RTP 767 traffic. 769 * Method of Measurement or Calculation: See section 4.1.2, Gap 770 Loss Rate definition [RFCXXXX]. 772 * Units of Measurement: See section 3.1.2, Burst Duration 773 Variance definition [RFCXXXX]. 775 * Measurement Point(s) with Potential Measurement Domain: See 776 section 4.1, 2nd paragraph [RFCXXXX]. 778 * Measurement Timing: See section 4.1, 1st paragraph [RFCXXXX] 779 for measurement timing and section 3.1.2 [RFCXXXX] for 780 Interval Metric flag. 782 * Use and applications: See section 1.4 [RFCXXXX]. 784 * Reporting model: See RFC3611. 786 e. Burst Discard metric 788 * Metric Name: RTP Burst Discard Rate 790 * Metric Description: The fraction of packets discarded during 791 bursts since the beginning of reception for RTP traffic. 793 * Method of Measurement or Calculation: See section 3.2.2, Burst 794 Discard Rate definition [RFCXXXX]. 796 * Units of Measurement: See section 3.2.2, Burst Discard Rate 797 definition [RFCXXXX]. 799 * Measurement Point(s) with Potential Measurement Domain: See 800 section 3.2, 2nd paragraph [RFCXXXX]. 802 * Measurement Timing: See section 3.2, 3rd paragraph [RFCXXXX] 803 for measurement timing and section 3.1.2 [RFCXXXX] for 804 Interval Metric flag. 806 * Use and applications: See section 1.4 [RFCXXXX]. 808 * Reporting model: See RFC3611. 810 f. Gap Discard Rate metric 812 * Metric Name: RTP Gap Discard Rate 814 * Metric Description: The fraction of packets discarded during 815 gaps since the beginning of reception for RTP traffic. 817 * Method of Measurement or Calculation: See section 3.2.2, Gap 818 Discard Rate definition [RFCXXXX]. 820 * Units of Measurement: See section 3.2.2, Gap Discard Rate 821 definition [RFCXXXX]. 823 * Measurement Point(s) with Potential Measurement Domain: See 824 section 3.2, 2nd paragraph [RFCXXXX]. 826 * Measurement Timing: See section 3.2, 3rd paragraph [RFCXXXX] 827 for measurement timing and section 3.1.2 [RFCXXXX] for 828 Interval Metric flag. 830 * Use and applications: See section 1.4 [RFCXXXX]. 832 * Reporting model: See RFC3611. 834 g. Number of discarded frames metric 836 * Metric Name: Number of discarded frames in RTP 838 * Metric Description: Number of frames discarded in a certain 839 sequence number interval for RTP traffic. 841 * Method of Measurement or Calculation: See section 4.1.2, 842 Number of discarded frames definition [RFCXXXX]. This metric 843 is directly measured and can be inferred from packet(s) that 844 comprise the frame. 846 * Units of Measurement: This metric is expressed as 32-bit 847 unsigned integer value. 849 * Measurement Point(s) with Potential Measurement Domain: See 850 section 4.1, 1st paragraph [RFCXXXX]. 852 * Measurement Timing: See section 4.1 [RFCXXXX], Number of 853 discarded frames definition, this metric relies on sequence 854 number interval and RTCP RR packet of RFC3550 to determine 855 measurement timing. 857 * Use and applications: See section 1.4 [RFCXXXX]. 859 * Reporting model: See RFC3611. 861 h. Number of duplicate frames metric 863 * Metric Name: Number of duplicate frames in RTP 865 * Metric Description: Number of frames duplicated in a certain 866 sequence number interval for RTP traffic. 868 * Method of Measurement or Calculation: See section 4.1.2, 869 Number of discarded frames definition [RFCXXXX], This metric 870 is directly measured and can be inferred from packet(s) that 871 comprise the frame. 873 * Units of Measurement: This metric is expressed as 32-bit 874 unsigned integer value. 876 * Measurement Point(s) with Potential Measurement Domain: See 877 section 4.1, 1st paragraph [RFCXXXX]. 879 * Measurement Timing: See section 4.1 [RFCXXXX], Number of 880 duplicate frames definition, this metric relies on sequence 881 number interval to determine measurement timing. 883 * Use and applications: See section 1.4 [RFCXXXX]. 885 * Reporting model: See RFC3611. 887 i. Number of full lost frames metric 889 * Metric Name: Number of full lost frames in RTP 891 * Metric Description: A frame is either split across multiple 892 RTP packets or carried in only one RTP packet.If the whole 893 frame or all the packets of the frame is lost, this frame is 894 regarded as one full_lost_frame. 896 * Method of Measurement or Calculation: See section 4.1.2, 897 Number of discarded frames definition [RFCXXXX]. 899 * Units of Measurement: This metric is expressed as 32-bit 900 unsigned integer value. 902 * Measurement Point(s) with Potential Measurement Domain: See 903 section 4.1, 1st paragraph [RFCXXXX]. 905 * Measurement Timing: See section 4.1 [RFCXXXX], Number of full 906 lost frames definition [RFCXXXX], this metric relies on 907 sequence number interval to determine measurement timing. 909 * Use and applications: See section 1.4 [RFCXXXX]. 911 * Reporting model: See RFC3611. 913 j. Number of partial lost frames metric 915 * Metric Name: Number of partial lost frames in RTP 917 * Metric Description: When a frame is split across multiple RTP 918 packets and some RTP packets of the frame are lost, this frame 919 is regarded as one partial_lost_frame. 921 * Method of Measurement or Calculation: See section 4.1.2, 922 Number of partial lost frames definition [RFCXXXX]. 924 * Units of Measurement: This metric is expressed as 32-bit 925 unsigned integer value. 927 * Measurement Point(s) with Potential Measurement Domain: See 928 section 4.1, 1st paragraph [RFCXXXX]. 930 * Measurement Timing: See section 4.1 [RFCXXXX], Number of 931 partial lost frames definition, this metric relies on sequence 932 number interval to determine measurement timing. 934 * Use and applications: See section 1.4 [RFCXXXX]. 936 * Reporting model: See RFC3611. 938 Appendix B. Change Log 940 Note to the RFC-Editor: please remove this section prior to 941 publication as an RFC. 943 B.1. draft-ietf-xrblock-rtcp-xr-summary-stat-11 945 The following are the major changes compared to 10: 946 o Incorporate the last proposed change by Barry when his DISCUSS was 947 cleared. 949 B.2. draft-ietf-xrblock-rtcp-xr-summary-stat-10 951 The following are the major changes compared to 09: 952 o Add appendix to apply RFC6390 template to metrics in this draft. 954 B.3. draft-ietf-xrblock-rtcp-xr-summary-stat-09 956 The following are the major changes compared to 08: 957 o Address comments in the IESG Review. 959 B.4. draft-ietf-xrblock-rtcp-xr-summary-stat-08 961 The following are the major changes compared to 07: 962 o Address comments raised in Sec-DIR review. 964 B.5. draft-ietf-xrblock-rtcp-xr-summary-stat-07 966 The following are the major changes compared to 06: 967 o Add comments raised in PM-DIR review by Al. 969 B.6. draft-ietf-xrblock-rtcp-xr-summary-stat-06 971 The following are the major changes compared to 05: 972 o Move RFC6709 to informative reference. 974 B.7. draft-ietf-xrblock-rtcp-xr-summary-stat-05 976 The following are the major changes compared to 04: 977 o Editorial changes to get in line with Delay and Burst Gap related 978 drafts. 980 Authors' Addresses 982 Glen Zorn 983 Network Zen 984 227/358 Thanon Sanphawut 985 Bang Na, Bangkok 10260 986 Thailand 988 Phone: +66 (0) 909-201060 989 Email: glenzorn@gmail.com 991 Roland Schott 992 Deutsche Telekom 993 Deutsche-Telekom-Allee 7 994 Darmstadt 64295 995 Germany 997 Email: Roland.Schott@telekom.de 999 Qin Wu (editor) 1000 Huawei 1001 101 Software Avenue, Yuhua District 1002 Nanjing, Jiangsu 210012 1003 China 1005 Email: sunseawq@huawei.com 1007 Rachel Huang 1008 Huawei 1009 101 Software Avenue, Yuhua District 1010 Nanjing 210012 1011 China 1013 Email: Rachel@huawei.com