idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-06.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 (January 16, 2013) is 4119 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 624, 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: July 20, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 January 16, 2013 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-06 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 July 20, 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 . . . . . . . . . . . . . . . . 7 69 3.2.2. Definition of Fields in Burst/Gap Discard Summary 70 Statistics Block . . . . . . . . . . . . . . . . . . . 8 71 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 9 72 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 9 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 . . . . . . . . . . . . . . . . . . . . 12 79 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 80 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 12 81 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13 82 6.3. Contact information for registrations . . . . . . . . . . 13 83 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 84 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 85 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 87 9.2. Informative References . . . . . . . . . . . . . . . . . . 14 88 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 89 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 15 90 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 15 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 93 1. Introduction 95 1.1. Summary Statistics Metrics 97 This draft defines three new block types to augment those defined in 98 [RFC3611] for use in a range of RTP applications. 100 The first two block types support the reporting of burst gap loss/ 101 discard summary statistics including packet loss/discard proportion, 102 mean and variance and belong to the class of transport-related end 103 system metrics defined in [RFC6792]. These two blocks are intended 104 to be used in conjunction with information from the Burst Gap Loss 105 Metrics Block or Burst Gap Discard Metrics Block, and on which these 106 two block therefore depend. The metrics in the Burst Gap Loss block 107 or Burst Gap Discard Metrics Block can be used independently of the 108 metrics defined in the first two blocks. 110 The third block supports the reporting of detailed statistics for 111 each frame type, including the number of frames received, lost and 112 discarded of each frame type in the Group of Pictures (GOP) and 113 additional data allowing the calculation of statistical parameters 114 (e.g.,the proportion of each frame type impaired by packet loss and 115 discard). The metrics defined in this block belong to the class of 116 application layer metrics defined in [RFC6792]. 118 1.2. RTCP and RTCP XR Reports 120 The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] 121 defined an extensible structure for reporting using an RTCP Extended 122 Report (XR). This document defines a new Extended Report block for 123 use with [RFC3550] and [RFC3611]. 125 1.3. Performance Metrics Framework 127 The RTP Monitoring Architectures [RFC6792] provides guideline for 128 reporting block format using RTCP XR. Metrics described in this 129 draft are in accordance with the guidelines in [RFC6792]. 131 1.4. Applicability 133 These metrics are applicable to a wide range of RTP applications and 134 reflect transient IP problems that affect user experience. They can 135 be used to form an accurate assessment of users' quality of 136 experience and influence sender strategies to mitigate the problem. 138 2. Terminology 140 2.1. Standards Language 142 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 143 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 144 document are to be interpreted as described in RFC 2119 [RFC2119]. 146 In addition, the following terms are defined: 148 Picture Type 150 Picture Types used in the different video algorithms are composed 151 of the Key frame and Derived frames. The Key frame is also called 152 a reference frame and used as a reference for predicting other 153 pictures. It is coded without prediction from other pictures. 154 Derived frames are derived from a Key frame using a prediction 155 algorithm. 157 3. Transport Related End System Metrics 159 3.1. Burst/Gap Loss Summary Statistics Metrics Block 161 The metrics described here are intended to be used as described in 162 this section, in conjunction with information from the Measurement 163 Information block [RFC6776] (which MUST be present in the same RTCP 164 packet as the Burst/Gap Loss block) and also with the metric 165 "cumulative number of packets lost" provided in standard RTCP 166 [RFC3550]. Instances of this Metrics Block refer by Synchronization 167 source (SSRC) to the separate auxiliary Measurement Information block 168 [RFC6776] which describes measurement periods in use (see [RFC6776] 169 section 4.2). This Metrics Block relies on the measurement period in 170 the Measurement Information block indicating the span of the report 171 and SHOULD be sent in the same compound RTCP packet as the 172 measurement information block. If the measurement period is not 173 received in the same compound RTCP packet as this Metrics Block, this 174 metrics block MUST be discarded. 176 The metrics carried in this Metrics Block provide information 177 relevant to statistical parameters, including burst loss rate, gap 178 loss rate, burst duration mean, burst duration variance and are 179 calculated at the receiving end of the RTP stream using burst gap 180 loss metrics defined in [BGLOSS] and other information which is sent 181 together with this report block. 183 3.1.1. Report Block Structure 185 0 1 2 3 186 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 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | BT=BGLSS | I | Reserved | block length | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | SSRC of Source | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 | Burst Loss Rate | Gap Loss Rate | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | Burst duration Mean | Burst duration Variance | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 3.1.2. Definition of Fields in Loss Summary Statistics Block 199 Block Type (BT): 8 bits 201 Burst/Gap Loss Summary Statistics Block is identified by the 202 constant . 204 Interval Metric Flag (I): 2 bits 206 This field is used to indicate whether the Burst/Gap Loss Summary 207 Statistics metrics are Sampled, Interval or Cumulative metrics: 209 I=10: Interval Duration - the reported value applies to the 210 most recent measurement interval duration between successive 211 metrics reports. 212 I=11: Cumulative Duration - the reported value applies to the 213 accumulation period characteristic of cumulative measurements. 214 I=01: Sampled Value - the reported value is a sampled 215 instantaneous value. 216 In this document, the value I=00 is the reserved value and MUST 217 NOT be used. 219 Reserved: 6 bits 221 This field is reserved for future definition. In the absence of 222 such a definition, the bits in this field MUST be set to zero and 223 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 225 Block Length: 16 bits 227 The constant 3, in accordance with the definition of this field in 228 Section 3 of RFC 3611 [RFC3611]. 230 SSRC of Source: 32 bits 232 As defined in Section 4.1 of RFC3611 [RFC3611]. 234 Burst Loss Rate: 16 bits 236 The fraction of packets lost during bursts since the beginning of 237 reception, expressed as a fixed point number with the binary point 238 at the left edge of the field. This value is calculated by 239 dividing Packets Loss in Bursts by Total Packets expected in 240 Bursts as follows: 242 Packets Loss in Bursts / Total Packets expected in Bursts 244 Gap Loss Rate: 16 bits 246 The fraction of packets lost during gaps 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 the difference between number of packets lost and Packets 250 lost in Bursts by the difference between Packets Expected and 251 Total Packets expected in Bursts as follows: 253 (number of packets lost - Packets Lost in Bursts) / (Packets 254 Expected - Total Packets expected in Bursts) 256 where "number of packets lost" is obtained from standard RTCP 257 [RFC3550] and Packets Expected is calculated as the difference 258 between "extended last sequence number" and "extended first 259 sequence number" (Interval or Cumulative) provided in the 260 Measurement Identity and Information block [RFC6776]. 262 Note that if the metric is to be calculated on an Interval basis, 263 a difference must be taken between the current and preceding 264 values of "cumulative number of packets lost" in RTCP, to obtain 265 the "number of packets lost" for the reporting interval. 267 Burst Duration Mean:16bits 269 The mean burst duration is obtained as the quotient: 271 mean = Sum of Burst Durations / Number of Bursts 273 where "Sum of Burst Durations" and "Number of Bursts" is obtained 274 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 276 Burst Duration Variance:16bits 278 The variance of the burst duration is obtained using the standard 279 result: 281 var = ( Sum of Squares of Burst Durations - Number of Bursts * 282 mean^2 ) / (Number of Bursts - 1) 284 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 285 obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 287 3.2. Burst/Gap Discard Summary Statistics Metrics Block 289 The metrics described here are intended to be used as described in 290 this section, in conjunction with information from the Measurement 291 Identity block [RFC6776] (which MUST be present in the same RTCP 292 packet as the Burst/Gap Discard Summary Statistics block) . 294 These metrics provide information relevant to statistical parameters, 295 including burst discard rate, gap discard rate and are calculated at 296 the receiving end of the RTP stream using burst gap discard metrics 297 defined in [BGDISCARD] and other information which is sent together 298 with this report block. 300 Instances of this Metrics Block refer by Synchronization source 301 (SSRC) to the separate auxiliary Measurement Information block 302 [RFC6776] which describes measurement periods in use (see [RFC6776] 303 section 4.2). This metrics block relies on the measurement period in 304 the Measurement Information block indicating the span of the report 305 and SHOULD be sent in the same compound RTCP packet as the 306 measurement information block. If the measurement period is not 307 received in the same compound RTCP packet as this Metrics Block, this 308 Metrics Block MUST be discarded. 310 3.2.1. Report Block Structure 312 0 1 2 3 313 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 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | BT=BGDSS | I | Reserved | block length | 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 | SSRC of Source | 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 | Burst Discard Rate | Gap Discard Rate | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 323 Block 325 Block Type (BT): 8 bits 327 Burst/Gap Discard Summary Statistics Block is identified by the 328 constant . 330 Interval Metric Flag (I): 2 bits 332 This field is used to indicate whether the Burst/Gap Discard 333 Summary Statistics metrics are Sampled, Interval or Cumulative 334 metrics: 336 I=10: Interval Duration - the reported value applies to the 337 most recent measurement interval duration between successive 338 metrics reports. 339 I=11: Cumulative Duration - the reported value applies to the 340 accumulation period characteristic of cumulative measurements. 341 I=01: Sampled Value - the reported value is a sampled 342 instantaneous value. 344 In this document, the value I=00 is the reserved value and MUST 345 NOT be used. 347 Reserved: 6 bits 349 This field is reserved for future definition. In the absence of 350 such a definition, the bits in this field MUST be set to zero and 351 SHOULD be ignored by the receiver (See RFC6709 section 4.2). 353 Block Length: 16 bits 355 The constant 2, in accordance with the definition of this field in 356 Section 3 of RFC 3611 [RFC3611]. 358 SSRC of Source: 32 bits 360 As defined in Section 4.1 of RFC3611 [RFC3611]. 362 Burst Discard Rate: 16 bits 364 The fraction of packets discarded during bursts since the 365 beginning of reception, expressed as a fixed point number with the 366 binary point at the left edge of the field. This value is 367 calculated by dividing Packets Discarded in Bursts by Total 368 Packets expected in Bursts as follows: 370 Packets Discarded in Bursts / Total Packets expected in Bursts 372 Gap Discard Rate: 16 bits 374 The fraction of packets discarded during gaps since the beginning 375 of reception expressed as a fixed point number with the binary 376 point at the left edge of the field. This value is calculated by 377 dividing the difference between number of packets discarded and 378 Packets Discarded in Bursts by the difference between Packets 379 Expected and Total Packets expected in Bursts as follows: 381 (number of packets discarded - Packets Discarded in Bursts) / 382 (Packets Expected - Total Packets expected in Bursts) 384 where "number of packets discarded" is obtained from the RTCP XR 385 Discard Count Block [DISCARD] and filled with the sum of packets 386 discarded due to early arrival (DT=1) and packets discarded due to 387 late arrival(DT=2) and Packets Expected is calculated as the 388 difference between "extended last sequence number" and "extended 389 first sequence number" (Interval or Cumulative) provided in the 390 Measurement Information block [RFC6776]. In order for the Burst/ 391 Gap Discard Summary Statistics Block to be meaningful, 2 instances 392 of the Discard Count block with DT=1 and DT=2 MUST be included in 393 the same RTCP XR packet as the Burst/Gap Discard Summary 394 Statistics Block. 396 4. Application Level Metrics 398 4.1. Frame Impairment Statistics Summary Metrics Block 400 This block reports statistics on which frame type were affected 401 beyond the information carried in the Statistics Summary Report Block 402 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 403 Information is measured at the receiving end of the RTP stream and 404 recorded about the number of frames received, lost frames, duplicated 405 frames and lost partial frames. Such information can be useful for 406 network management and video quality monitoring. 408 4.1.1. Report Block Structure 410 0 1 2 3 411 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 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | BT=FISS |T| Reserved | block length | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | SSRC of Source | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Begin_seq | End_seq | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | Number of frames received | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Discarded_frames | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Dup_frames | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | Lost_full_frames | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Lost_partial_frames | 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 431 Block 433 Block type (BT): 8 bits 435 Frame Impairment Statistics Summary Block is identified by the 436 constant . 438 Picture type indicator (T): 1 bit 440 This field is used to indicate the frame type to be reported. The 441 bit is set to 0 if the lost_full_frames, lost_partial_frames and 442 dup_frames fields contain Key frame (reference frame) counts or 1 443 if they contain Derived frame counts. Note that if both the Key 444 frame and Derivation frame report are sent, they should be sent in 445 the same RTCP compound packet using two Frame Impairment Summary 446 Statistics Blocks. 448 Reserved: 7 bits 450 This field is reserved for future definition. In the absence of 451 such a definition, the bits in this field MUST be set to zero and 452 SHOULD be ignored by the receiver. 454 Block Length: 16 bits 456 The constant 7, in accordance with the definition of this field in 457 Section 3 of RFC 3611 [RFC3611]. 459 SSRC of Source: 32 bits 461 As defined in Section 4.1 of RFC3611 [RFC3611]. 463 Begin_seq: 16 bits 465 As defined in Section 4.1 of RFC 3611 [RFC3611]. 467 end_seq: 16 bits 469 As defined in Section 4.1 of RFC 3611 [RFC3611]. 471 Number of frames received:32 bits 473 A count of the number of frames received in the above sequence 474 number interval, estimated if necessary. If no frames have been 475 received then this count SHALL be set to zero. 477 Number of discarded frames (discarded_frames): 32 bits 479 Number of frames discarded in the above sequence number interval. 481 Number of duplicate frames (dup_frames): 32 bits 483 Number of duplicate frames received in the above sequence number 484 interval. 486 Number of full frames lost (lost_full_frames): 32 bits 488 If one frame is completely lost, this frame is regarded as one 489 lost full frame. The lost_full_frames is equivalent to the number 490 of full frames lost in the above sequence number interval. 492 Number of partial frames lost (lost_partial_frames): 32 bits 494 If one frame is partially lost, this frame is regarded as one lost 495 fractional frame. The value of the lost_partial_frames field is 496 equivalent to the number of partial frames lost in the above 497 sequence number interval. 499 5. SDP Signaling 501 RFC 3611 defines the use of SDP (Session Description Protocol) 502 [RFC4566] for signaling the use of XR blocks. However XR blocks MAY 503 be used without prior signaling (see section 5 of RFC3611). 505 5.1. SDP rtcp-xr-attrib Attribute Extension 507 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 508 in Section 5.1 of RFC 3611 by providing three additional values of 509 "xr-format" to signal the use of the report block defined in this 510 document. 512 xr-format = / burst-gap-loss-stat 513 / burst-gap-discard-stat 514 / frame-impairment-stat 515 Burst-gap-loss-stat ="burst gap loss summary statistics" 516 Burst-gap-discard-stat="burst gap discard summary statistics" 517 Frame-impairment-stat="frame impairment summary statistics" 519 5.2. Offer/Answer Usage 521 When SDP is used in offer-answer context, the SDP Offer/Answer usage 522 defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters 523 applies. For detailed usage of Offer/Answer for unilateral 524 parameter, refer to section 5.2 of [RFC3611]. 526 6. IANA Considerations 528 New block types for RTCP XR are subject to IANA registration. For 529 general guidelines on IANA considerations for RTCP XR, refer to RFC 530 3611. 532 6.1. New RTCP XR Block Type values 534 This document assigns three new block type value in the "RTP Control 535 Protocol (RTCP) Extended Report (XR) Block Type Registry" : 537 Name: BGLSS 538 Long Name: Burst/Gap Loss Summary Statistics Block 539 Value 540 Reference: Section 3.1 542 Name: BGDSS 543 Long Name: Burst/Gap Discard Summary Statistics Block 544 Value 545 Reference: Section 3.2 547 Name: FISS 548 Long Name: Frame Impairment Statistics Summary 549 Value 550 Reference: Section 4.1 552 6.2. New RTCP XR SDP Parameters 554 This document also registers three new SDP [RFC4566] parameters for 555 the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended 556 Report (XR) SDP Parameters Registry ": 558 * " burst-gap-loss-stat " 559 * " burst-gap-discard-stat " 560 * " frame-impairment-stat " 562 6.3. Contact information for registrations 564 The contact information for the registrations is: 566 Qin Wu (sunseawq@huawei.com) 567 101 Software Avenue, Yuhua District 568 Nanjing, Jiangsu 210012 569 China 571 7. Security Considerations 573 The new RTCP XR report blocks proposed in this document introduces no 574 new security considerations beyond those described in RFC 3611. 576 8. Acknowledgements 578 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 579 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 580 Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu for 581 their valuable comments and suggestions on this document. 583 9. References 585 9.1. Normative References 587 [BGDISCARD] 588 Clark, A., Huang, R., and W. Wu, "RTP Control 589 Protocol(RTCP) Extended Report (XR) Block for Burst/Gap 590 Discard metric Reporting", 591 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in 592 progress), December 2012. 594 [BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control 595 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 596 Loss metric Reporting", 597 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in 598 progress), December 2012. 600 [DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol 601 (RTCP) Extended Report (XR) Block for Discard Count metric 602 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 603 progress), October 2012. 605 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 606 Requirement Levels", BCP 14, RFC 2119, March 1997. 608 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 609 Jacobson, "RTP: A Transport Protocol for Real-Time 610 Applications", STD 64, RFC 3550, July 2003. 612 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 613 Protocol Extended Reports (RTCP XR)", RFC 3611, 614 November 2003. 616 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 617 Description Protocol", RFC 4566, July 2006. 619 [RFC6776] Wu, Q., "Measurement Identity and information Reporting 620 using SDES item and XR Block", RFC 6776, August 2012. 622 9.2. Informative References 624 [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design 625 Considerations for Protocol Extensions", RFC 6709, 626 September 2012. 628 [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures 629 for RTP", RFC 6792, November 2012. 631 Appendix A. Change Log 633 Note to the RFC-Editor: please remove this section prior to 634 publication as an RFC. 636 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-06 638 The following are the major changes compared to 05: 639 o Move RFC6709 to informative reference. 641 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-05 643 The following are the major changes compared to 04: 644 o Editorial changes to get in line with Delay and Burst Gap related 645 drafts. 647 Authors' Addresses 649 Glen Zorn (editor) 650 Network Zen 651 227/358 Thanon Sanphawut 652 Bang Na, Bangkok 10260 653 Thailand 655 Phone: +66 (0) 909-201060 656 Email: glenzorn@gmail.com 658 Roland Schott 659 Deutsche Telekom 660 Deutsche-Telekom-Allee 7 661 Darmstadt 64295 662 Germany 664 Email: Roland.Schott@telekom.de 666 Qin Wu 667 Huawei 668 101 Software Avenue, Yuhua District 669 Nanjing, Jiangsu 210012 670 China 672 Email: sunseawq@huawei.com 673 Rachel Huang 674 Huawei 675 101 Software Avenue, Yuhua District 676 Nanjing 210012 677 China 679 Email: Rachel@huawei.com