idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-07.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 4, 2013) is 4099 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 661, 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 8, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 February 4, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-07 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 8, 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-07 . . . . . . . . 15 90 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 15 91 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 15 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 94 1. Introduction 96 1.1. Summary Statistics Metrics 98 This draft defines three new block types to augment those defined in 99 [RFC3611] for use in a range of RTP applications. 101 o Burst/Gap Loss Summary Statistics Metrics Block 102 o Burst/Gap Discard Summary Statistics Metrics Block 103 o Frame Impairment Statistics Summary Metrics Block 105 The first two block types support the reporting of burst gap loss/ 106 discard summary statistics including packet loss/discard proportion, 107 mean and variance and belong to the class of transport-related end 108 system metrics defined in [RFC6792]. These two blocks are intended 109 to be used in conjunction with information from the Burst Gap Loss 110 Metrics Block [BGLOSS] or Burst Gap Discard Metrics Block 111 [BGDISCARD], and on which these two blocks therefore depend. The 112 metrics in the Burst Gap Loss Metrics block or Burst Gap Discard 113 Metrics Block are consistent with the definitions of Burst, Gap, Loss 114 and Discard in RTCP XR [RFC3611]. 116 The third block supports the reporting of detailed video statistics 117 for each frame type, including the number of frames received, lost 118 and discarded of each frame type in the Group of Pictures (GOP) and 119 additional data allowing the calculation of statistical parameters 120 (e.g.,the proportion of each frame type impaired by packet loss and 121 discard). The metrics defined in this block belong to the class of 122 application layer metrics defined in [RFC6792]. 124 1.2. RTCP and RTCP XR Reports 126 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 127 defined an extensible structure for reporting using an RTCP Extended 128 Report (XR). This document defines a new Extended Report block for 129 use with [RFC3550] and [RFC3611]. 131 1.3. Performance Metrics Framework 133 The RTP Monitoring Architectures [RFC6792] provides guideline for 134 reporting block format using RTCP XR. Metrics described in this 135 draft are in accordance with the guidelines in [RFC6792]. 137 1.4. Applicability 139 These metrics are applicable to a wide range of RTP applications and 140 reflect transient IP problems that affect user experience. They can 141 be used to form an accurate assessment of users' quality of 142 experience and influence sender strategies to mitigate the problem. 144 2. Terminology 146 2.1. Standards Language 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 149 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 150 document are to be interpreted as described in RFC 2119 [RFC2119]. 152 In addition, the following terms are defined: 154 Picture Type 156 Picture Types used in the different video algorithms are composed 157 of the Key frame and Derived frames. The Key frame is 158 independently coded without prediction from other pictures and 159 used as a reference frame for predicting other pictures. Derived 160 frames are predicatively coded and derived from a Key frame using 161 a prediction algorithm. 163 3. Transport Related End System Metrics 165 3.1. Burst/Gap Loss Summary Statistics Metrics Block 167 The metrics described here are intended to be used as described in 168 this section, in conjunction with information from the Measurement 169 Information block [RFC6776] (which MUST be present in the same RTCP 170 packet as the Burst/Gap Loss block) and also with the metric 171 "cumulative number of packets lost" provided in standard RTCP 172 [RFC3550]. Instances of this Metrics Block refer by Synchronization 173 source (SSRC) to the separate auxiliary Measurement Information block 174 [RFC6776] which describes measurement periods in use (see [RFC6776] 175 section 4.2). This Metrics Block relies on the measurement period in 176 the Measurement Information block indicating the span of the report 177 and SHOULD be sent in the same compound RTCP packet as the 178 measurement information block. If the measurement period is not 179 received in the same compound RTCP packet as this Metrics Block, this 180 metrics block MUST be discarded. 182 The metrics carried in this Metrics Block provide information 183 relevant to statistical parameters, including burst loss rate, gap 184 loss rate, burst duration mean, burst duration variance and are 185 calculated at the receiving end of the RTP stream using burst gap 186 loss metrics defined in [BGLOSS] and other information which is sent 187 together with this report block. 189 3.1.1. Report Block Structure 191 0 1 2 3 192 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 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | BT=BGLSS | I | Reserved | block length | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | SSRC of Source | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 | Burst Loss Rate | Gap Loss Rate | 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | Burst duration Mean | Burst duration Variance | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 3.1.2. Definition of Fields in Loss Summary Statistics Block 205 Block Type (BT): 8 bits 207 Burst/Gap Loss Summary Statistics Block is identified by the 208 constant . 210 Interval Metric Flag (I): 2 bits 212 This field is used to indicate whether the Burst/Gap Loss Summary 213 Statistics metrics are Sampled, Interval or Cumulative metrics: 215 I=10: Interval Duration - the reported value applies to the 216 most recent measurement interval duration between successive 217 metrics reports. 218 I=11: Cumulative Duration - the reported value applies to the 219 accumulation period characteristic of cumulative measurements. 220 I=01: Sampled Value - the reported value is a sampled 221 instantaneous value. 222 In this document, the value I=00 is the reserved value and MUST 223 NOT be used. 225 Reserved: 6 bits 227 This field is reserved for future definition. In the absence of 228 such a definition, the bits in this field MUST be set to zero and 229 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 231 Block Length: 16 bits 233 The constant 3, in accordance with the definition of this field in 234 Section 3 of RFC 3611 [RFC3611]. 236 SSRC of Source: 32 bits 238 As defined in Section 4.1 of RFC3611 [RFC3611]. 240 Burst Loss Rate: 16 bits 242 The fraction of packets lost during bursts since the beginning of 243 reception, expressed as a fixed point number with the binary point 244 at the left edge of the field. This value is calculated by 245 dividing Packets Loss in Bursts by Total Packets expected in 246 Bursts, multiplying the result of the division by 7FFF, with the 247 maximum value 7FFF, and taking the integer part as follows: 249 Packets Loss in Bursts / Total Packets expected in Bursts 251 If the measurement is unavailable, the value 0x8000 MUST be 252 reported. 254 Gap Loss Rate: 16 bits 256 The fraction of packets lost during gaps since the beginning of 257 reception expressed as a fixed point number with the binary point 258 at the left edge of the field. This value is calculated by 259 dividing the difference between number of packets lost and Packets 260 lost in Bursts by the difference between Packets Expected and 261 Total Packets expected in Bursts, multiplying the result of the 262 division by 7FFF, with the maximum value 7FFF, and taking the 263 integer part as follows: 265 (number of packets lost - Packets Lost in Bursts) / (Packets 266 Expected - Total Packets expected in Bursts) 268 where "number of packets lost" is obtained from standard RTCP 269 [RFC3550] and Packets Expected is calculated as the difference 270 between "extended last sequence number" and "extended first 271 sequence number" (Interval or Cumulative) provided in the 272 Measurement Identity and Information block [RFC6776]. 274 If the measurement is unavailable, the value 0x8000 MUST be 275 reported. 277 Note that if the metric is to be calculated on an Interval basis, 278 a difference must be taken between the current and preceding 279 values of "cumulative number of packets lost" in RTCP, to obtain 280 the "number of packets lost" for the reporting interval. 282 Burst Duration Mean:16bits 284 The mean burst duration is obtained as the quotient: 286 mean = Sum of Burst Durations / Number of Bursts 288 where "Sum of Burst Durations" and "Number of Bursts" is obtained 289 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 291 If the measurement is unavailable, the value 0xFFFF MUST be 292 reported. 294 Burst Duration Variance:16bits 296 The variance of the burst duration is obtained using the standard 297 result: 299 var = ( Sum of Squares of Burst Durations - Number of Bursts * 300 mean^2 ) / (Number of Bursts - 1) 302 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 303 obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 305 If the measurement is unavailable, the value 0xFFFF MUST be 306 reported. 308 3.2. Burst/Gap Discard Summary Statistics Metrics Block 310 The metrics described here are intended to be used as described in 311 this section, in conjunction with information from the Measurement 312 Identity block [RFC6776] (which MUST be present in the same RTCP 313 packet as the Burst/Gap Discard Summary Statistics block) . 315 These metrics provide information relevant to statistical parameters, 316 including burst discard rate, gap discard rate and are calculated at 317 the receiving end of the RTP stream using burst gap discard metrics 318 defined in [BGDISCARD] and other information which is sent together 319 with this report block. 321 Instances of this Metrics Block refer by Synchronization source 322 (SSRC) to the separate auxiliary Measurement Information block 323 [RFC6776] which describes measurement periods in use (see [RFC6776] 324 section 4.2). This metrics block relies on the measurement period in 325 the Measurement Information block indicating the span of the report 326 and SHOULD be sent in the same compound RTCP packet as the 327 measurement information block. If the measurement period is not 328 received in the same compound RTCP packet as this Metrics Block, this 329 Metrics Block MUST be discarded. 331 3.2.1. Report Block Structure 333 0 1 2 3 334 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 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | BT=BGDSS | I | Reserved | block length | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | SSRC of Source | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | Burst Discard Rate | Gap Discard Rate | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 344 Block 346 Block Type (BT): 8 bits 348 Burst/Gap Discard Summary Statistics Block is identified by the 349 constant . 351 Interval Metric Flag (I): 2 bits 353 This field is used to indicate whether the Burst/Gap Discard 354 Summary Statistics metrics are Sampled, Interval or Cumulative 355 metrics: 357 I=10: Interval Duration - the reported value applies to the 358 most recent measurement interval duration between successive 359 metrics reports. 360 I=11: Cumulative Duration - the reported value applies to the 361 accumulation period characteristic of cumulative measurements. 362 I=01: Sampled Value - the reported value is a sampled 363 instantaneous value. 365 In this document, the value I=00 is the reserved value and MUST 366 NOT be used. 368 Reserved: 6 bits 370 This field is reserved for future definition. In the absence of 371 such a definition, the bits in this field MUST be set to zero and 372 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 374 Block Length: 16 bits 376 The constant 2, in accordance with the definition of this field in 377 Section 3 of RFC 3611 [RFC3611]. 379 SSRC of Source: 32 bits 381 As defined in Section 4.1 of RFC3611 [RFC3611]. 383 Burst Discard Rate: 16 bits 385 The fraction of packets discarded during bursts since the 386 beginning of reception, expressed as a fixed point number with the 387 binary point at the left edge of the field. This value is 388 calculated by dividing Packets Discarded in Bursts by Total 389 Packets expected in Bursts, multiplying the result of the division 390 by 7FFF, with the maximum value 7FFF, and taking the integer part 391 as follows: 393 Packets Discarded in Bursts / Total Packets expected in Bursts 395 If the measurement is unavailable, the value 0x8000 MUST be 396 reported. 398 Gap Discard Rate: 16 bits 400 The fraction of packets discarded during gaps since the beginning 401 of reception expressed as a fixed point number with the binary 402 point at the left edge of the field. This value is calculated by 403 dividing the difference between number of packets discarded and 404 Packets Discarded in Bursts by the difference between Packets 405 Expected and Total Packets expected in Bursts, multiplying the 406 result of the division by 7FFF, with the maximum value 7FFF, and 407 taking the integer part as follows: 409 (number of packets discarded - Packets Discarded in Bursts) / 410 (Packets Expected - Total Packets expected in Bursts) 412 where "number of packets discarded" is obtained from the RTCP XR 413 Discard Count Block [DISCARD] and filled with the sum of packets 414 discarded due to early arrival (DT=1) and packets discarded due to 415 late arrival(DT=2) and Packets Expected is calculated as the 416 difference between "extended last sequence number" and "extended 417 first sequence number" (Interval or Cumulative) provided in the 418 Measurement Information block [RFC6776]. In order for the Burst/ 419 Gap Discard Summary Statistics Block to be meaningful, 2 instances 420 of the Discard Count block with DT=1 and DT=2 MUST be included in 421 the same RTCP XR packet as the Burst/Gap Discard Summary 422 Statistics Block. 424 If the measurement is unavailable, the value 0x8000 MUST be 425 reported. 427 4. Application Level Metrics 429 4.1. Frame Impairment Statistics Summary Metrics Block 431 This block reports statistics on which frame type were affected 432 beyond the information carried in the Statistics Summary Report Block 433 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 434 Information is measured at the receiving end of the RTP stream and 435 recorded about the number of frames received, lost frames, duplicated 436 frames and lost partial frames. Such information can be useful for 437 network management and video quality monitoring. 439 4.1.1. Report Block Structure 441 0 1 2 3 442 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 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 | BT=FISS |T| Reserved | block length | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | SSRC of Source | 447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 448 | begin_seq | end_seq | 449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 450 | Number of frames received | 451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 452 | Discarded_frames | 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Dup_frames | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | Full_lost_frames | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | Partial_lost_frames | 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 462 Block 464 Block type (BT): 8 bits 466 Frame Impairment Statistics Summary Block is identified by the 467 constant . 469 Picture type indicator (T): 1 bit 471 This field is used to indicate the frame type to be reported. The 472 bit is set to 0 if the lost_full_frames, lost_partial_frames and 473 dup_frames fields contain Key frame (reference frame) counts or 1 474 if they contain Derived frame counts. Note that if both the Key 475 frame and Derivation frame report are sent, they should be sent in 476 the same RTCP compound packet using two Frame Impairment Summary 477 Statistics Blocks. 479 Reserved: 7 bits 481 This field is reserved for future definition. In the absence of 482 such a definition, the bits in this field MUST be set to zero and 483 SHOULD be ignored by the receiver. 485 Block Length: 16 bits 487 The constant 7, in accordance with the definition of this field in 488 Section 3 of RFC 3611 [RFC3611]. 490 SSRC of Source: 32 bits 492 As defined in Section 4.1 of RFC3611 [RFC3611]. 494 begin_seq: 16 bits 496 As defined in Section 4.1 of RFC 3611 [RFC3611]. 498 end_seq: 16 bits 500 As defined in Section 4.1 of RFC 3611 [RFC3611]. 502 Number of frames received:32 bits 504 A count of the number of frames received in the above sequence 505 number interval, estimated if necessary. If no frames have been 506 received then this count SHALL be set to zero. 508 Number of discarded frames (discarded_frames): 32 bits 510 Number of frames discarded in the above sequence number interval. 512 Number of duplicate frames (dup_frames): 32 bits 514 Number of duplicate frames received in the above sequence number 515 interval. 517 Number of full lost frames (full_lost_frames): 32 bits 519 A frame is either split across multiple packets or carried in only 520 one packet.If the whole frame or all the packets of the frame is 521 lost, this frame is regarded as one full lost frame. The 522 full_lost-frames can be inferred from packet(s) that comprise the 523 frame. The full lost_ frames is equivalent to the number of full 524 lost frames in the above sequence number interval. 526 Number of partial lost frames (partial_lost_frames): 32 bits 528 When a frame is split across multiple packets and some packets of 529 the frame are lost, this frame is regarded as one partially lost 530 frame. The partial_lost-frames can be inferred from packets that 531 comprise the frame. The value of the partial_lost_frames field is 532 equivalent to the number of partial lost frames in the above 533 sequence number interval. 535 5. SDP Signaling 537 RFC 3611 defines the use of SDP (Session Description Protocol) 538 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 539 be used without prior signaling (see section 5 of RFC3611). 541 5.1. SDP rtcp-xr-attrib Attribute Extension 543 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 544 in Section 5.1 of RFC 3611 by providing three additional values of 545 "xr-format" to signal the use of the report block defined in this 546 document. 548 xr-format = / xr-bglss-block 549 / xr-bgdss-block 550 / xr-fiss-block 551 xr-bglss-block=" burst-gap-loss-stat " 552 xr-bgdss-block =" burst-gap-discard-stat " 553 xr-fiss-block=" frame-impairment-stat " 555 5.2. Offer/Answer Usage 557 When SDP is used in offer-answer context, the SDP Offer/Answer usage 558 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 559 applies. For detailed usage of Offer/Answer for unilateral 560 parameter, refer to section 5.2 of [RFC3611]. 562 6. IANA Considerations 564 New block types for RTCP XR are subject to IANA registration. For 565 general guidelines on IANA considerations for RTCP XR, refer to RFC 566 3611. 568 6.1. New RTCP XR Block Type values 570 This document assigns three new block type value in the "RTP Control 571 Protocol (RTCP) Extended Report (XR) Block Type Registry" : 573 Name: BGLSS 574 Long Name: Burst/Gap Loss Summary Statistics Block 575 Value 576 Reference: Section 3.1 578 Name: BGDSS 579 Long Name: Burst/Gap Discard Summary Statistics Block 580 Value 581 Reference: Section 3.2 583 Name: FISS 584 Long Name: Frame Impairment Statistics Summary 585 Value 586 Reference: Section 4.1 588 6.2. New RTCP XR SDP Parameters 590 This document also registers three new SDP [RFC4566] parameters for 591 the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended 592 Report (XR) SDP Parameters Registry ": 594 * " burst-gap-loss-stat " 595 * " burst-gap-discard-stat " 596 * " frame-impairment-stat " 598 6.3. Contact information for registrations 600 The contact information for the registrations is: 602 Qin Wu (sunseawq@huawei.com) 603 101 Software Avenue, Yuhua District 604 Nanjing, Jiangsu 210012 605 China 607 7. Security Considerations 609 The new RTCP XR report blocks proposed in this document introduces no 610 new security considerations beyond those described in RFC 3611. 612 8. Acknowledgements 614 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 615 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 616 Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton 617 Jr., Alfred for their valuable comments and suggestions on this 618 document. 620 9. References 622 9.1. Normative References 624 [BGDISCARD] 625 Clark, A., Huang, R., and W. Wu, "RTP Control 626 Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 627 Discard metric Reporting", 628 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in 629 progress), December 2012. 631 [BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control 632 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 633 Loss metric Reporting", 634 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in 635 progress), December 2012. 637 [DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol 638 (RTCP) Extended Report (XR) Block for Discard Count metric 639 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 640 progress), October 2012. 642 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 643 Requirement Levels", BCP 14, RFC 2119, March 1997. 645 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 646 Jacobson, "RTP: A Transport Protocol for Real-Time 647 Applications", STD 64, RFC 3550, July 2003. 649 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 650 Protocol Extended Reports (RTCP XR)", RFC 3611, 651 November 2003. 653 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 654 Description Protocol", RFC 4566, July 2006. 656 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 657 using SDES item and XR Block", RFC 6776, August 2012. 659 9.2. Informative References 661 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 662 Considerations for Protocol Extensions", RFC 6709, 663 September 2012. 665 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 666 for RTP", RFC 6792, November 2012. 668 Appendix A. Change Log 670 Note to the RFC-Editor: please remove this section prior to 671 publication as an RFC. 673 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-07 675 The following are the major changes compared to 05: 676 o Add comments raised in PM-DIR review by Al. 678 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-06 680 The following are the major changes compared to 05: 681 o Move RFC6709 to informative reference. 683 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-05 685 The following are the major changes compared to 04: 686 o Editorial changes to get in line with Delay and Burst Gap related 687 drafts. 689 Authors' Addresses 691 Glen Zorn (editor) 692 Network Zen 693 227/358 Thanon Sanphawut 694 Bang Na, Bangkok 10260 695 Thailand 697 Phone: +66 (0) 909-201060 698 Email: glenzorn@gmail.com 700 Roland Schott 701 Deutsche Telekom 702 Deutsche-Telekom-Allee 7 703 Darmstadt 64295 704 Germany 706 Email: Roland.Schott@telekom.de 708 Qin Wu 709 Huawei 710 101 Software Avenue, Yuhua District 711 Nanjing, Jiangsu 210012 712 China 714 Email: sunseawq@huawei.com 716 Rachel Huang 717 Huawei 718 101 Software Avenue, Yuhua District 719 Nanjing 210012 720 China 722 Email: Rachel@huawei.com