idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-08.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 (February 6, 2013) is 4096 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) == Unused Reference: 'RFC6709' is defined on line 666, 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 (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn, Ed. 3 Internet-Draft Network Zen 4 Intended status: Standards Track R. Schott 5 Expires: August 10, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 February 6, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-08 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 August 10, 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. Summary Statistics Metrics . . . . . . . . . . . . . . . . 3 57 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 58 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 59 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 62 3. Transport Related End System Metrics . . . . . . . . . . . . . 4 63 3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 4 64 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 5 65 3.1.2. Definition of Fields in Loss Summary Statistics 66 Block . . . . . . . . . . . . . . . . . . . . . . . . 5 67 3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7 68 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 8 69 3.2.2. Definition of Fields in Burst/Gap Discard Summary 70 Statistics Block . . . . . . . . . . . . . . . . . . . 8 71 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 10 72 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 10 73 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10 74 4.1.2. Definition of Fields in Frame Impairment Summary 75 Statistics Block . . . . . . . . . . . . . . . . . . . 10 76 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 77 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 78 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 13 79 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 80 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 13 81 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13 82 6.3. Contact information for registrations . . . . . . . . . . 14 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 84 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 87 9.2. Informative References . . . . . . . . . . . . . . . . . . 15 88 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 89 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 15 90 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 15 91 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 15 92 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 16 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 95 1. Introduction 97 1.1. Summary Statistics Metrics 99 This draft defines three new block types to augment those defined in 100 [RFC3611] for use in a range of RTP applications. 102 o Burst/Gap Loss Summary Statistics Metrics Block 103 o Burst/Gap Discard Summary Statistics Metrics Block 104 o Frame Impairment Statistics Summary Metrics Block 106 The first two block types support the reporting of burst gap loss/ 107 discard summary statistics including packet loss/discard proportion, 108 mean and variance and belong to the class of transport-related end 109 system metrics defined in [RFC6792]. These two blocks are intended 110 to be used in conjunction with information from the Burst Gap Loss 111 Metrics Block [BGLOSS] or Burst Gap Discard Metrics Block 112 [BGDISCARD], and on which these two blocks therefore depend. The 113 metrics in the Burst Gap Loss Metrics block or Burst Gap Discard 114 Metrics Block are consistent with the definitions of Burst, Gap, Loss 115 and Discard in RTCP XR [RFC3611]. 117 The third block supports the reporting of detailed video statistics 118 for each frame type, including the number of frames received, lost 119 and discarded of each frame type in the Group of Pictures (GOP) and 120 additional data allowing the calculation of statistical parameters 121 (e.g.,the proportion of each frame type impaired by packet loss and 122 discard). The metrics defined in this block belong to the class of 123 application layer metrics defined in [RFC6792]. 125 1.2. RTCP and RTCP XR Reports 127 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 128 defined an extensible structure for reporting using an RTCP Extended 129 Report (XR). This document defines a new Extended Report block for 130 use with [RFC3550] and [RFC3611]. 132 1.3. Performance Metrics Framework 134 The RTP Monitoring Architectures [RFC6792] provides guideline for 135 reporting block format using RTCP XR. Metrics described in this 136 draft are in accordance with the guidelines in [RFC6792]. 138 1.4. Applicability 140 These metrics are applicable to a wide range of RTP applications and 141 reflect transient IP problems that affect user experience. They can 142 be used to form an accurate assessment of users' quality of 143 experience and influence sender strategies to mitigate the problem. 145 2. Terminology 147 2.1. Standards Language 149 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 150 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 151 document are to be interpreted as described in RFC 2119 [RFC2119]. 153 In addition, the following terms are defined: 155 Frame Type 157 A video frame is compressed using different algorithms. Frame 158 type is used to identify different algorithms for video frames. 159 Two frame Types used in the different video algorithms are the Key 160 frame and Derived frames. The Key frame is independently coded 161 without prediction from other pictures and used as a reference 162 frame for predicting other pictures. Derived frames are 163 predicatively coded and derived from a Key frame using a 164 prediction algorithm. 166 3. Transport Related End System Metrics 168 3.1. Burst/Gap Loss Summary Statistics Metrics Block 170 The metrics described here are intended to be used as described in 171 this section, in conjunction with information from the Measurement 172 Information block [RFC6776] (which MUST be present in the same RTCP 173 packet as the Burst/Gap Loss block) and also with the metric 174 "cumulative number of packets lost" provided in standard RTCP 175 [RFC3550]. Instances of this Metrics Block refer by Synchronization 176 source (SSRC) to the separate auxiliary Measurement Information block 177 [RFC6776] which describes measurement periods in use (see [RFC6776] 178 section 4.2). This Metrics Block relies on the measurement period in 179 the Measurement Information block indicating the span of the report 180 and SHOULD be sent in the same compound RTCP packet as the 181 measurement information block. If the measurement period is not 182 received in the same compound RTCP packet as this Metrics Block, this 183 metrics block MUST be discarded. 185 The metrics carried in this Metrics Block provide information 186 relevant to statistical parameters, including burst loss rate, gap 187 loss rate, burst duration mean, burst duration variance and are 188 calculated at the receiving end of the RTP stream using burst gap 189 loss metrics defined in [BGLOSS] and other information which is sent 190 together with this report block. 192 3.1.1. Report Block Structure 194 0 1 2 3 195 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 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | BT=BGLSS | I | Reserved | block length | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | SSRC of Source | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | Burst Loss Rate | Gap Loss Rate | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | Burst duration Mean | Burst duration Variance | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 3.1.2. Definition of Fields in Loss Summary Statistics Block 208 Block Type (BT): 8 bits 210 Burst/Gap Loss Summary Statistics Block is identified by the 211 constant . 213 Interval Metric Flag (I): 2 bits 215 This field is used to indicate whether the Burst/Gap Loss Summary 216 Statistics metrics are Sampled, Interval or Cumulative metrics: 218 I=10: Interval Duration - the reported value applies to the 219 most recent measurement interval duration between successive 220 metrics reports. 221 I=11: Cumulative Duration - the reported value applies to the 222 accumulation period characteristic of cumulative measurements. 223 I=01: Sampled Value - the reported value is a sampled 224 instantaneous value. 226 In this document, the value I=00 is the reserved value and MUST 227 NOT be used. 229 Reserved: 6 bits 231 This field is reserved for future definition. In the absence of 232 such a definition, the bits in this field MUST be set to zero and 233 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 235 Block Length: 16 bits 237 The constant 3, in accordance with the definition of this field in 238 Section 3 of RFC 3611 [RFC3611]. 240 SSRC of Source: 32 bits 242 As defined in Section 4.1 of RFC3611 [RFC3611]. 244 Burst Loss Rate: 16 bits 246 The fraction of packets lost during bursts since the beginning of 247 reception, expressed as a fixed point number with the binary point 248 at the left edge of the field. This value is calculated by 249 dividing Packets Loss in Bursts by Total Packets expected in 250 Bursts, multiplying the result of the division by 7FFF, with the 251 maximum value 7FFF, and taking the integer part as follows: 253 Packets Loss in Bursts / Total Packets expected in Bursts 255 If the measurement is unavailable, the value 0x8000 MUST be 256 reported. 258 Gap Loss Rate: 16 bits 260 The fraction of packets lost during gaps since the beginning of 261 reception expressed as a fixed point number with the binary point 262 at the left edge of the field. This value is calculated by 263 dividing the difference between number of packets lost and Packets 264 lost in Bursts by the difference between Packets Expected and 265 Total Packets expected in Bursts, multiplying the result of the 266 division by 7FFF, with the maximum value 7FFF, and taking the 267 integer part as follows: 269 (number of packets lost - Packets Lost in Bursts) / (Packets 270 Expected - Total Packets expected in Bursts) 272 where "number of packets lost" is obtained from standard RTCP 273 [RFC3550] and Packets Expected is calculated as the difference 274 between "extended last sequence number" and "extended first 275 sequence number" (Interval or Cumulative) provided in the 276 Measurement Identity and Information block [RFC6776]. 278 If the measurement is unavailable, the value 0x8000 MUST be 279 reported. 281 Note that if the metric is to be calculated on an Interval basis, 282 a difference must be taken between the current and preceding 283 values of "cumulative number of packets lost" in RTCP, to obtain 284 the "number of packets lost" for the reporting interval. 286 Burst Duration Mean:16bits 288 The mean burst duration is obtained as the quotient: 290 mean = Sum of Burst Durations / Number of Bursts 292 where "Sum of Burst Durations" and "Number of Bursts" is obtained 293 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 295 If the measurement is unavailable, the value 0xFFFF MUST be 296 reported. 298 Burst Duration Variance:16bits 300 The variance of the burst duration is obtained using the standard 301 result: 303 var = ( Sum of Squares of Burst Durations - Number of Bursts * 304 mean^2 ) / (Number of Bursts - 1) 306 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 307 obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 309 If the measurement is unavailable, the value 0xFFFF MUST be 310 reported. 312 3.2. Burst/Gap Discard Summary Statistics Metrics Block 314 The metrics described here are intended to be used as described in 315 this section, in conjunction with information from the Measurement 316 Identity block [RFC6776] (which MUST be present in the same RTCP 317 packet as the Burst/Gap Discard Summary Statistics block) . 319 These metrics provide information relevant to statistical parameters, 320 including burst discard rate, gap discard rate and are calculated at 321 the receiving end of the RTP stream using burst gap discard metrics 322 defined in [BGDISCARD] and other information which is sent together 323 with this report block. 325 Instances of this Metrics Block refer by Synchronization source 326 (SSRC) to the separate auxiliary Measurement Information block 327 [RFC6776] which describes measurement periods in use (see [RFC6776] 328 section 4.2). This metrics block relies on the measurement period in 329 the Measurement Information block indicating the span of the report 330 and SHOULD be sent in the same compound RTCP packet as the 331 measurement information block. If the measurement period is not 332 received in the same compound RTCP packet as this Metrics Block, this 333 Metrics Block MUST be discarded. 335 3.2.1. Report Block Structure 337 0 1 2 3 338 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 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | BT=BGDSS | I | Reserved | block length | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | SSRC of Source | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | Burst Discard Rate | Gap Discard Rate | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 348 Block 350 Block Type (BT): 8 bits 352 Burst/Gap Discard Summary Statistics Block is identified by the 353 constant . 355 Interval Metric Flag (I): 2 bits 357 This field is used to indicate whether the Burst/Gap Discard 358 Summary Statistics metrics are Sampled, Interval or Cumulative 359 metrics: 361 I=10: Interval Duration - the reported value applies to the 362 most recent measurement interval duration between successive 363 metrics reports. 364 I=11: Cumulative Duration - the reported value applies to the 365 accumulation period characteristic of cumulative measurements. 366 I=01: Sampled Value - the reported value is a sampled 367 instantaneous value. 369 In this document, the value I=00 is the reserved value and MUST 370 NOT be used. 372 Reserved: 6 bits 374 This field is reserved for future definition. In the absence of 375 such a definition, the bits in this field MUST be set to zero and 376 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 378 Block Length: 16 bits 380 The constant 2, in accordance with the definition of this field in 381 Section 3 of RFC 3611 [RFC3611]. 383 SSRC of Source: 32 bits 385 As defined in Section 4.1 of RFC3611 [RFC3611]. 387 Burst Discard Rate: 16 bits 389 The fraction of packets discarded during bursts since the 390 beginning of reception, expressed as a fixed point number with the 391 binary point at the left edge of the field. This value is 392 calculated by dividing Packets Discarded in Bursts by Total 393 Packets expected in Bursts, multiplying the result of the division 394 by 7FFF, with the maximum value 7FFF, and taking the integer part 395 as follows: 397 Packets Discarded in Bursts / Total Packets expected in Bursts 399 If the measurement is unavailable, the value 0x8000 MUST be 400 reported. 402 Gap Discard Rate: 16 bits 404 The fraction of packets discarded during gaps since the beginning 405 of reception expressed as a fixed point number with the binary 406 point at the left edge of the field. This value is calculated by 407 dividing the difference between number of packets discarded and 408 Packets Discarded in Bursts by the difference between Packets 409 Expected and Total Packets expected in Bursts, multiplying the 410 result of the division by 7FFF, with the maximum value 7FFF, and 411 taking the integer part as follows: 413 (number of packets discarded - Packets Discarded in Bursts) / 414 (Packets Expected - Total Packets expected in Bursts) 416 where "number of packets discarded" is obtained from the RTCP XR 417 Discard Count Block [DISCARD] and filled with the sum of packets 418 discarded due to early arrival (DT=1) and packets discarded due to 419 late arrival(DT=2) and Packets Expected is calculated as the 420 difference between "extended last sequence number" and "extended 421 first sequence number" (Interval or Cumulative) provided in the 422 Measurement Information block [RFC6776]. In order for the Burst/ 423 Gap Discard Summary Statistics Block to be meaningful, 2 instances 424 of the Discard Count block with DT=1 and DT=2 MUST be included in 425 the same RTCP XR packet as the Burst/Gap Discard Summary 426 Statistics Block. 428 If the measurement is unavailable, the value 0x8000 MUST be 429 reported. 431 4. Application Level Metrics 433 4.1. Frame Impairment Statistics Summary Metrics Block 435 This block reports statistics on which frame type were affected 436 beyond the information carried in the Statistics Summary Report Block 437 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 438 Information is measured at the receiving end of the RTP stream and 439 recorded about the number of frames received, lost frames, duplicated 440 frames and lost partial frames. Such information can be useful for 441 network management and video quality monitoring. 443 4.1.1. Report Block Structure 445 0 1 2 3 446 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 447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 448 | BT=FISS |T| Reserved | block length | 449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 450 | SSRC of Source | 451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 452 | begin_seq | end_seq | 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Number of frames received | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | Discarded_frames | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | Dup_frames | 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | Full_lost_frames | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Partial_lost_frames | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 466 Block 468 Block type (BT): 8 bits 470 Frame Impairment Statistics Summary Block is identified by the 471 constant . 473 Frame type indicator (T): 1 bit 475 This field is used to indicate the frame type to be reported. The 476 bit is set to 0 if the full_lost_frames, partial_lost_frames, 477 dup_frames,discarded_frames and Number of frames received fields 478 contain Key frame (reference frame) counts or 1 if they contain 479 Derived frame counts. Note that if both the Key frame and 480 Derivation frame report are sent, they should be sent in the same 481 RTCP compound packet using two Frame Impairment Summary Statistics 482 Blocks. 484 Reserved: 7 bits 486 This field is reserved for future definition. In the absence of 487 such a definition, the bits in this field MUST be set to zero and 488 SHOULD be ignored by the receiver. 490 Block Length: 16 bits 492 The constant 7, in accordance with the definition of this field in 493 Section 3 of RFC 3611 [RFC3611]. 495 SSRC of Source: 32 bits 497 As defined in Section 4.1 of RFC3611 [RFC3611]. 499 begin_seq: 16 bits 501 As defined in Section 4.1 of RFC 3611 [RFC3611]. 503 end_seq: 16 bits 505 As defined in Section 4.1 of RFC 3611 [RFC3611]. 507 Number of frames received:32 bits 509 A count of the number of frames received in the above sequence 510 number interval, estimated if necessary. If no frames have been 511 received then this count SHALL be set to zero. 513 Number of discarded frames (discarded_frames): 32 bits 515 Number of frames discarded in the above sequence number interval. 517 Number of duplicate frames (dup_frames): 32 bits 519 Number of duplicate frames received in the above sequence number 520 interval. 522 Number of full lost frames (full_lost_frames): 32 bits 524 A frame is either split across multiple packets or carried in only 525 one packet.If the whole frame or all the packets of the frame is 526 lost, this frame is regarded as one full lost frame. The 527 full_lost-frames can be inferred from packet(s) that comprise the 528 frame. The full lost_ frames is equivalent to the number of full 529 lost frames in the above sequence number interval. 531 Number of partial lost frames (partial_lost_frames): 32 bits 533 When a frame is split across multiple packets and some packets of 534 the frame are lost, this frame is regarded as one partially lost 535 frame. The partial_lost-frames can be inferred from packets that 536 comprise the frame. The value of the partial_lost_frames field is 537 equivalent to the number of partial lost frames in the above 538 sequence number interval. 540 5. SDP Signaling 542 RFC 3611 defines the use of SDP (Session Description Protocol) 543 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 544 be used without prior signaling (see section 5 of RFC3611). 546 5.1. SDP rtcp-xr-attrib Attribute Extension 548 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 549 in Section 5.1 of RFC 3611 by providing three additional values of 550 "xr-format" to signal the use of the report block defined in this 551 document. 553 xr-format = / xr-bglss-block 554 / xr-bgdss-block 555 / xr-fiss-block 556 xr-bglss-block=" burst-gap-loss-stat " 557 xr-bgdss-block =" burst-gap-discard-stat " 558 xr-fiss-block=" frame-impairment-stat " 560 5.2. Offer/Answer Usage 562 When SDP is used in offer-answer context, the SDP Offer/Answer usage 563 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 564 applies. For detailed usage of Offer/Answer for unilateral 565 parameter, refer to section 5.2 of [RFC3611]. 567 6. IANA Considerations 569 New block types for RTCP XR are subject to IANA registration. For 570 general guidelines on IANA considerations for RTCP XR, refer to RFC 571 3611. 573 6.1. New RTCP XR Block Type values 575 This document assigns three new block type value in the "RTP Control 576 Protocol (RTCP) Extended Report (XR) Block Type Registry" : 578 Name: BGLSS 579 Long Name: Burst/Gap Loss Summary Statistics Block 580 Value 581 Reference: Section 3.1 583 Name: BGDSS 584 Long Name: Burst/Gap Discard Summary Statistics Block 585 Value 586 Reference: Section 3.2 588 Name: FISS 589 Long Name: Frame Impairment Statistics Summary 590 Value 591 Reference: Section 4.1 593 6.2. New RTCP XR SDP Parameters 595 This document also registers three new SDP [RFC4566] parameters for 596 the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended 597 Report (XR) SDP Parameters Registry ": 599 * " burst-gap-loss-stat " 600 * " burst-gap-discard-stat " 601 * " frame-impairment-stat " 603 6.3. Contact information for registrations 605 The contact information for the registrations is: 607 Qin Wu (sunseawq@huawei.com) 608 101 Software Avenue, Yuhua District 609 Nanjing, Jiangsu 210012 610 China 612 7. Security Considerations 614 The new RTCP XR report blocks proposed in this document introduces no 615 new security considerations beyond those described in RFC 3611. 617 8. Acknowledgements 619 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 620 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 621 Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton 622 Jr., Alfred and Klaas Wierenga for their valuable comments and 623 suggestions on this document. 625 9. References 627 9.1. Normative References 629 [BGDISCARD] 630 Clark, A., Huang, R., and W. Wu, "RTP Control 631 Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 632 Discard metric Reporting", 633 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in 634 progress), December 2012. 636 [BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control 637 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 638 Loss metric Reporting", 639 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in 640 progress), December 2012. 642 [DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol 643 (RTCP) Extended Report (XR) Block for Discard Count metric 644 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 645 progress), October 2012. 647 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 648 Requirement Levels", BCP 14, RFC 2119, March 1997. 650 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 651 Jacobson, "RTP: A Transport Protocol for Real-Time 652 Applications", STD 64, RFC 3550, July 2003. 654 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 655 Protocol Extended Reports (RTCP XR)", RFC 3611, 656 November 2003. 658 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 659 Description Protocol", RFC 4566, July 2006. 661 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 662 using SDES item and XR Block", RFC 6776, August 2012. 664 9.2. Informative References 666 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 667 Considerations for Protocol Extensions", RFC 6709, 668 September 2012. 670 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 671 for RTP", RFC 6792, November 2012. 673 Appendix A. Change Log 675 Note to the RFC-Editor: please remove this section prior to 676 publication as an RFC. 678 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-08 680 The following are the major changes compared to 07: 681 o Add comments raised in Sec-DIR review. 683 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-07 685 The following are the major changes compared to 06: 686 o Add comments raised in PM-DIR review by Al. 688 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-06 690 The following are the major changes compared to 05: 691 o Move RFC6709 to informative reference. 693 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-05 695 The following are the major changes compared to 04: 696 o Editorial changes to get in line with Delay and Burst Gap related 697 drafts. 699 Authors' Addresses 701 Glen Zorn (editor) 702 Network Zen 703 227/358 Thanon Sanphawut 704 Bang Na, Bangkok 10260 705 Thailand 707 Phone: +66 (0) 909-201060 708 Email: glenzorn@gmail.com 710 Roland Schott 711 Deutsche Telekom 712 Deutsche-Telekom-Allee 7 713 Darmstadt 64295 714 Germany 716 Email: Roland.Schott@telekom.de 718 Qin Wu 719 Huawei 720 101 Software Avenue, Yuhua District 721 Nanjing, Jiangsu 210012 722 China 724 Email: sunseawq@huawei.com 726 Rachel Huang 727 Huawei 728 101 Software Avenue, Yuhua District 729 Nanjing 210012 730 China 732 Email: Rachel@huawei.com