idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-09.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 22, 2013) is 4081 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 670, 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 3 Internet-Draft Network Zen 4 Intended status: Standards Track R. Schott 5 Expires: August 26, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 February 22, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-09 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 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 . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . 11 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-09 . . . . . . . . 15 90 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 15 91 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 15 92 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 16 93 A.5. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 16 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 96 1. Introduction 98 1.1. Summary Statistics Metrics 100 This draft defines three new block types to augment those defined in 101 [RFC3611] for use in a range of RTP applications. 103 o Burst/Gap Loss Summary Statistics Metrics Block 104 o Burst/Gap Discard Summary Statistics Metrics Block 105 o Frame Impairment Statistics Summary Metrics Block 107 The first two block types support the reporting of burst gap loss/ 108 discard summary statistics including packet loss/discard proportion, 109 mean and variance and belong to the class of transport-related end 110 system metrics defined in [RFC6792]. These two blocks are intended 111 to be used in conjunction with information from the Burst Gap Loss 112 Metrics Block [BGLOSS] or Burst Gap Discard Metrics Block 113 [BGDISCARD], and on which these two blocks therefore depend. The 114 metrics in the Burst Gap Loss Metrics block or Burst Gap Discard 115 Metrics Block are consistent with the definitions of Burst, Gap, Loss 116 and Discard in RTCP XR [RFC3611]. 118 The third block supports the reporting of detailed video statistics 119 for each frame type, including the number of frames received, lost 120 and discarded of each frame type in the Group of Pictures (GOP) and 121 additional data allowing the calculation of statistical parameters 122 (e.g.,the proportion of each frame type impaired by packet loss and 123 discard). The metrics defined in this block belong to the class of 124 application layer metrics defined in [RFC6792]. 126 1.2. RTCP and RTCP XR Reports 128 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 129 defined an extensible structure for reporting using an RTCP Extended 130 Report (XR). This document defines a new Extended Report block for 131 use with [RFC3550] and [RFC3611]. 133 1.3. Performance Metrics Framework 135 The RTP Monitoring Architectures [RFC6792] provides guideline for 136 reporting block format using RTCP XR. Metrics described in this 137 draft are in accordance with the guidelines in [RFC6792]. 139 1.4. Applicability 141 These metrics are applicable to a wide range of RTP applications and 142 reflect transient IP problems that affect user experience. They can 143 be used to form an accurate assessment of users' quality of 144 experience and influence sender strategies to mitigate the problem. 146 2. Terminology 148 2.1. Standards Language 150 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 151 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 152 document are to be interpreted as described in RFC 2119 [RFC2119]. 154 In addition, the following terms are defined: 156 Frame Type 158 In many cases, a video frame is compressed using different 159 algorithms. Frame type is used to identify different algorithms 160 for video frames. Two frame Types used in the different video 161 algorithms are the Key frame and Derived frames. The Key frame is 162 independently coded without prediction from other pictures and 163 used as a reference frame for predicting other pictures. Derived 164 frames are predicatively coded and derived from a Key frame using 165 a prediction algorithm If there is no video image compression, all 166 frames are Key Frames. 168 3. Transport Related End System Metrics 170 3.1. Burst/Gap Loss Summary Statistics Metrics Block 172 This Block extends packet loss and discard metrics defined in section 173 4.7.1 of RFC3611. The metrics described here are intended to be used 174 as described in this section, in conjunction with information from 175 the Measurement Information block [RFC6776] (which MUST be present in 176 the same RTCP packet as the Burst/Gap Loss block) and also with the 177 metric "cumulative number of packets lost" provided in standard RTCP 178 [RFC3550]. Instances of this Metrics Block refer by Synchronization 179 source (SSRC) to the separate auxiliary Measurement Information block 180 [RFC6776] which describes measurement periods in use (see [RFC6776] 181 section 4.2). This Metrics Block relies on the measurement period in 182 the Measurement Information block indicating the span of the report 183 and SHOULD be sent in the same compound RTCP packet as the 184 measurement information block. If the measurement period is not 185 received in the same compound RTCP packet as this Metrics Block, this 186 metrics block MUST be discarded. 188 The metrics carried in this Metrics Block provide information 189 relevant to statistical parameters, including burst loss rate, gap 190 loss rate, burst duration mean, burst duration variance and are 191 calculated at the receiving end of the RTP stream using burst gap 192 loss metrics defined in [BGLOSS] and other information which is sent 193 together with this report block. 195 3.1.1. Report Block Structure 197 0 1 2 3 198 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 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | BT=BGLSS | I | Reserved | block length | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | SSRC of Source | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | Burst Loss Rate | Gap Loss Rate | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | Burst duration Mean | Burst duration Variance | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 3.1.2. Definition of Fields in Loss Summary Statistics Block 211 Block Type (BT): 8 bits 213 Burst/Gap Loss Summary Statistics Block is identified by the 214 constant . 216 Interval Metric Flag (I): 2 bits 218 This field is used to indicate whether the Burst/Gap Loss Summary 219 Statistics metrics are Sampled, Interval or Cumulative metrics: 221 I=10: Interval Duration - the reported value applies to the 222 most recent measurement interval duration between successive 223 metrics reports. 224 I=11: Cumulative Duration - the reported value applies to the 225 accumulation period characteristic of cumulative measurements. 226 I=01: Sampled Value - the reported value is a sampled 227 instantaneous value. 229 In this document, the value I=00 is the reserved value and MUST 230 NOT be used. 232 Reserved: 6 bits 234 This field is reserved for future definition. In the absence of 235 such a definition, the bits in this field MUST be set to zero and 236 ignored by the receiver (See RFC6709 section 4.2). 238 Block Length: 16 bits 240 The constant 3, in accordance with the definition of this field in 241 Section 3 of RFC 3611 [RFC3611]. 243 SSRC of Source: 32 bits 245 As defined in Section 4.1 of RFC3611 [RFC3611]. 247 Burst Loss Rate: 16 bits 249 The fraction of packets lost during bursts since the beginning of 250 reception, expressed as a fixed point number with the binary point 251 immediately after the left-most bit. This value is calculated by 252 dividing Packets Lost in Bursts by Total Packets Expected in 253 Bursts, multiplying the result of the division by 32768 254 (0x8000),and keeping only the integer part. The maximum value is 255 thus 0x8000. Representing this as a formula: 257 integer-part( (Packets Lost in Bursts / Total Packets Expected in 258 Bursts) * 0x8000 ) 260 If the measurement is unavailable, the value 0xFFFF MUST be 261 reported. 263 Gap Loss Rate: 16 bits 265 The fraction of packets lost during gaps since the beginning of 266 reception expressed as a fixed point number with the binary point 267 immediately after the left-most bit. This value is calculated by 268 dividing the difference between number of packets lost and Packets 269 lost in Bursts by the difference between Packets Expected and 270 Total Packets expected in Bursts, multiplying the result of the 271 division by 32768 (0x8000),and keeping only the integer part. The 272 maximum value is thus 0x8000. Representing this as a formula: 274 integer-part ( (number of packets lost - Packets Lost in Bursts)/ 275 (Packets Expected - Total Packets expected in Bursts) * 0x8000 ) 277 where "number of packets lost" is obtained from standard RTCP 278 [RFC3550] and Packets Expected is calculated as the difference 279 between "extended last sequence number" and "extended first 280 sequence number" (Interval or Cumulative) provided in the 281 Measurement Identity and Information block [RFC6776]. 283 If the measurement is unavailable, the value 0xFFFF MUST be 284 reported. 286 Note that if the metric is to be calculated on an Interval basis, 287 a difference must be taken between the current and preceding 288 values of "cumulative number of packets lost" in RTCP, to obtain 289 the "number of packets lost" for the reporting interval. 291 Burst Duration Mean:16bits 293 The mean burst duration is obtained as the quotient: 295 mean = Sum of Burst Durations / Number of Bursts 297 where "Sum of Burst Durations" and "Number of Bursts" is obtained 298 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 300 If the measurement is unavailable, the value 0xFFFF MUST be 301 reported. 303 Burst Duration Variance:16bits 305 The variance of the burst duration is obtained using the standard 306 result: 308 var = ( Sum of Squares of Burst Durations - Number of Bursts * 309 mean^2 ) / (Number of Bursts - 1) 311 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 312 obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 314 If the measurement is unavailable, the value 0xFFFF MUST be 315 reported. 317 3.2. Burst/Gap Discard Summary Statistics Metrics Block 319 This Block extends packet loss and discard metrics defined in section 320 4.7.1 of RFC3611. The metrics described here are intended to be used 321 as described in this section, in conjunction with information from 322 the Measurement Identity block [RFC6776] (which MUST be present in 323 the same RTCP packet as the Burst/Gap Discard Summary Statistics 324 block) . 326 These metrics provide information relevant to statistical parameters, 327 including burst discard rate, gap discard rate and are calculated at 328 the receiving end of the RTP stream using burst gap discard metrics 329 defined in [BGDISCARD] and other information which is sent together 330 with this report block. 332 Instances of this Metrics Block refer by Synchronization source 333 (SSRC) to the separate auxiliary Measurement Information block 334 [RFC6776] which describes measurement periods in use (see [RFC6776] 335 section 4.2). This metrics block relies on the measurement period in 336 the Measurement Information block indicating the span of the report 337 and SHOULD be sent in the same compound RTCP packet as the 338 measurement information block. If the measurement period is not 339 received in the same compound RTCP packet as this Metrics Block, this 340 Metrics Block MUST be discarded. 342 3.2.1. Report Block Structure 344 0 1 2 3 345 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 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | BT=BGDSS | I | Reserved | block length | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | SSRC of Source | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Burst Discard Rate | Gap Discard Rate | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 355 Block 357 Block Type (BT): 8 bits 359 Burst/Gap Discard Summary Statistics Block is identified by the 360 constant . 362 Interval Metric Flag (I): 2 bits 364 This field is used to indicate whether the Burst/Gap Discard 365 Summary Statistics metrics are Sampled, Interval or Cumulative 366 metrics: 368 I=10: Interval Duration - the reported value applies to the 369 most recent measurement interval duration between successive 370 metrics reports. 371 I=11: Cumulative Duration - the reported value applies to the 372 accumulation period characteristic of cumulative measurements. 373 I=01: Sampled Value - the reported value is a sampled 374 instantaneous value. 376 In this document, the value I=00 is the reserved value and MUST 377 NOT be used. 379 Reserved: 6 bits 381 This field is reserved for future definition. In the absence of 382 such a definition, the bits in this field MUST be set to zero and 383 ignored by the receiver (See RFC6709 section 4.2). 385 Block Length: 16 bits 387 The constant 2, in accordance with the definition of this field in 388 Section 3 of RFC 3611 [RFC3611]. 390 SSRC of Source: 32 bits 392 As defined in Section 4.1 of RFC3611 [RFC3611]. 394 Burst Discard Rate: 16 bits 396 The fraction of packets discarded during bursts since the 397 beginning of reception, expressed as a fixed point number with the 398 binary point at the left edge of the field. This value is 399 calculated by dividing Packets Discarded in Bursts by Total 400 Packets expected in Bursts, multiplying the result of the division 401 by 32768 (0x8000), and keeping only the integer part, according to 402 the formula: 404 integer-part( (Packets Discarded in Bursts / Total Packets 405 expected in Bursts) * 0x8000 ) 407 If the measurement is unavailable, the value 0xFFFF MUST be 408 reported. 410 Gap Discard Rate: 16 bits 412 The fraction of packets discarded during gaps since the beginning 413 of reception expressed as a fixed point number with the binary 414 point immediately after the left-most bit. This value is 415 calculated by dividing the difference between number of packets 416 discarded and Packets Discarded in Bursts by the difference 417 between Packets Expected and Total Packets expected in Bursts, 418 multiplying the result of the division by 32768 (0x8000), and 419 keeping only the integer part. The maximum value is thus 0x8000. 420 Representing this as a formula: 422 integer-part( (number of packets discarded - Packets Discarded in 423 Bursts) /(Packets Expected - Total Packets expected in Bursts) * 424 0x8000 ) 426 where "number of packets discarded" is obtained from the RTCP XR 427 Discard Count Block [DISCARD] and filled with the sum of packets 428 discarded due to early arrival (DT=1) and packets discarded due to 429 late arrival(DT=2) and Packets Expected is calculated as the 430 difference between "extended last sequence number" and "extended 431 first sequence number" (Interval or Cumulative) provided in the 432 Measurement Information block [RFC6776]. In order for the Burst/ 433 Gap Discard Summary Statistics Block to be meaningful, 2 instances 434 of the Discard Count block with DT=1 and DT=2 MUST be included in 435 the same RTCP XR packet as the Burst/Gap Discard Summary 436 Statistics Block. 438 If the measurement is unavailable, the value 0xFFFF MUST be 439 reported. 441 4. Application Level Metrics 443 4.1. Frame Impairment Statistics Summary Metrics Block 445 This block extends statistics summary report mechanism defined in 446 section 4.6 of RFC3611 and reports statistics on which frame type 447 were affected beyond the information carried in the Statistics 448 Summary Report Block RTCP packet specified in the section 4.6 of RFC 449 3611 [RFC3611]. Information is measured at the receiving end of the 450 RTP stream and recorded about the number of frames received, lost 451 frames, duplicated frames and lost partial frames. Such information 452 can be useful for network management and video quality monitoring. 454 4.1.1. Report Block Structure 456 0 1 2 3 457 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 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 | BT=FISS |T| Reserved | block length | 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 | SSRC of Source | 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | begin_seq | end_seq | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 | Discarded_frames | 466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 | Dup_frames | 468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 | Full_lost_frames | 470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 471 | Partial_lost_frames | 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 475 Block 477 Block type (BT): 8 bits 479 Frame Impairment Statistics Summary Block is identified by the 480 constant . 482 Frame type indicator (T): 1 bit 484 This field is used to indicate the frame type to be reported. The 485 bit is set to 0 if the full_lost_frames, partial_lost_frames, 486 dup_frames,discarded_frames and Number of frames received fields 487 contain Key frame (reference frame) counts or 1 if they contain 488 Derived frame counts. Note that if both the Key frame and 489 Derivation frame report are sent, they should be sent in the same 490 RTCP compound packet using two Frame Impairment Summary Statistics 491 Blocks. 493 Reserved: 7 bits 495 This field is reserved for future definition. In the absence of 496 such a definition, the bits in this field MUST be set to zero and 497 ignored by the receiver (See RFC6709 section 4.2). 499 Block Length: 16 bits 501 The constant 6, in accordance with the definition of this field in 502 Section 3 of RFC 3611 [RFC3611]. 504 SSRC of Source: 32 bits 506 As defined in Section 4.1 of RFC3611 [RFC3611]. 508 begin_seq: 16 bits 510 As defined in Section 4.1 of RFC 3611 [RFC3611]. 512 end_seq: 16 bits 514 As defined in Section 4.1 of RFC 3611 [RFC3611]. 516 Number of discarded frames (discarded_frames): 32 bits 518 Number of frames discarded in the above sequence number interval. 520 Number of duplicate frames (dup_frames): 32 bits 522 Number of duplicate frames received in the above sequence number 523 interval. 525 Number of full lost frames (full_lost_frames): 32 bits 527 A frame is either split across multiple packets or carried in only 528 one packet.If the whole frame or all the packets of the frame is 529 lost, this frame is regarded as one full_lost_frame. The 530 full_lost_frames can be inferred from packet(s) that comprise the 531 frame. The full_lost_ frames is equivalent to the number of full 532 lost frames in the above sequence number interval. 534 Number of partial lost frames (partial_lost_frames): 32 bits 536 When a frame is split across multiple packets and some packets of 537 the frame are lost, this frame is regarded as one 538 partial_lost_frame. The partial_lost_frames can be inferred from 539 packets that comprise the frame. The value of the 540 partial_lost_frames field is equivalent to the number of partial 541 lost frames in the above sequence number interval. 543 5. SDP Signaling 545 RFC 3611 defines the use of SDP (Session Description Protocol) 546 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 547 be used without prior signaling (see section 5 of RFC3611). 549 5.1. SDP rtcp-xr-attrib Attribute Extension 551 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 552 in Section 5.1 of RFC 3611 by providing three additional values of 553 "xr-format" to signal the use of the report block defined in this 554 document. 556 xr-format = / xr-bglss-block 557 / xr-bgdss-block 558 / xr-fiss-block 559 xr-bglss-block= "burst-gap-loss-stat" 560 xr-bgdss-block = "burst-gap-discard-stat" 561 xr-fiss-block= "frame-impairment-stat" 563 5.2. Offer/Answer Usage 565 When SDP is used in offer-answer context, the SDP Offer/Answer usage 566 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 567 applies. For detailed usage of Offer/Answer for unilateral 568 parameter, refer to section 5.2 of [RFC3611]. 570 6. IANA Considerations 572 New block types for RTCP XR are subject to IANA registration. For 573 general guidelines on IANA considerations for RTCP XR, refer to RFC 574 3611. 576 6.1. New RTCP XR Block Type values 578 This document assigns three new block type value in the "RTP Control 579 Protocol (RTCP) Extended Report (XR) Block Type Registry" : 581 Name: BGLSS 582 Long Name: Burst/Gap Loss Summary Statistics Block 583 Value 584 Reference: Section 3.1 586 Name: BGDSS 587 Long Name: Burst/Gap Discard Summary Statistics Block 588 Value 589 Reference: Section 3.2 591 Name: FISS 592 Long Name: Frame Impairment Statistics Summary 593 Value 594 Reference: Section 4.1 596 6.2. New RTCP XR SDP Parameters 598 This document also registers three new SDP [RFC4566] parameters for 599 the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended 600 Report (XR) SDP Parameters Registry ": 602 * "burst-gap-loss-stat" 603 * "burst-gap-discard-stat" 604 * "frame-impairment-stat" 606 6.3. Contact information for registrations 608 The contact information for the registrations is: 610 Qin Wu (sunseawq@huawei.com) 611 101 Software Avenue, Yuhua District 612 Nanjing, Jiangsu 210012 613 China 615 7. Security Considerations 617 The new RTCP XR report blocks proposed in this document introduces no 618 new security considerations beyond those described in RFC 3611. 620 8. Acknowledgements 622 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 623 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 624 Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton 625 Jr., Alfred, Klaas Wierenga, Barry Leiba, Robert Sparks, Ralph Droms 626 and Benoit Claise for their valuable comments and suggestions on this 627 document. 629 9. References 631 9.1. Normative References 633 [BGDISCARD] 634 Clark, A., Huang, R., and W. Wu, "RTP Control 635 Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 636 Discard metric Reporting", 637 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in 638 progress), December 2012. 640 [BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control 641 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 642 Loss metric Reporting", 643 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in 644 progress), December 2012. 646 [DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol 647 (RTCP) Extended Report (XR) Block for Discard Count metric 648 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 649 progress), October 2012. 651 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 652 Requirement Levels", BCP 14, RFC 2119, March 1997. 654 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 655 Jacobson, "RTP: A Transport Protocol for Real-Time 656 Applications", STD 64, RFC 3550, July 2003. 658 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 659 Protocol Extended Reports (RTCP XR)", RFC 3611, 660 November 2003. 662 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 663 Description Protocol", RFC 4566, July 2006. 665 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 666 using SDES item and XR Block", RFC 6776, August 2012. 668 9.2. Informative References 670 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 671 Considerations for Protocol Extensions", RFC 6709, 672 September 2012. 674 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 675 for RTP", RFC 6792, November 2012. 677 Appendix A. Change Log 679 Note to the RFC-Editor: please remove this section prior to 680 publication as an RFC. 682 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-09 684 The following are the major changes compared to 08: 685 o Address comments in the IESG Review. 687 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-08 689 The following are the major changes compared to 07: 690 o Address comments raised in Sec-DIR review. 692 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-07 694 The following are the major changes compared to 06: 695 o Add comments raised in PM-DIR review by Al. 697 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-06 699 The following are the major changes compared to 05: 700 o Move RFC6709 to informative reference. 702 A.5. draft-ietf-xrblock-rtcp-xr-summary-stat-05 704 The following are the major changes compared to 04: 705 o Editorial changes to get in line with Delay and Burst Gap related 706 drafts. 708 Authors' Addresses 710 Glen Zorn 711 Network Zen 712 227/358 Thanon Sanphawut 713 Bang Na, Bangkok 10260 714 Thailand 716 Phone: +66 (0) 909-201060 717 Email: glenzorn@gmail.com 719 Roland Schott 720 Deutsche Telekom 721 Deutsche-Telekom-Allee 7 722 Darmstadt 64295 723 Germany 725 Email: Roland.Schott@telekom.de 727 Qin Wu 728 Huawei 729 101 Software Avenue, Yuhua District 730 Nanjing, Jiangsu 210012 731 China 733 Email: sunseawq@huawei.com 734 Rachel Huang 735 Huawei 736 101 Software Avenue, Yuhua District 737 Nanjing 210012 738 China 740 Email: Rachel@huawei.com