idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-02.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 (October 22, 2012) is 4204 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) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-14) exists of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06 == Outdated reference: A later version (-12) exists of draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 == Outdated reference: A later version (-15) exists of draft-ietf-xrblock-rtcp-xr-discard-09 Summary: 1 error (**), 0 flaws (~~), 4 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: April 25, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 October 22, 2012 11 RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary 12 Statistics Metrics Reporting 13 draft-ietf-xrblock-rtcp-xr-summary-stat-02 15 Abstract 17 This document defines three RTP Control Protcol (RTCP) Extended 18 Report (XR) Blocks and associated SDP parameters that allow the 19 reporting of loss, duplication and discard summary statistics metrics 20 in a range of RTP applications. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 25, 2013. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 59 3. Transport Related End System Metrics . . . . . . . . . . . . . 4 60 3.1. Burst/Gap Loss Summary Statistics Block . . . . . . . . . 4 61 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 4 62 3.1.2. Definition of Fields in Loss Summary Statistics 63 Block . . . . . . . . . . . . . . . . . . . . . . . . 4 64 3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 6 65 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7 66 3.2.2. Definition of Fields inBurst/Gap Discard Summary 67 Statistics Block . . . . . . . . . . . . . . . . . . . 7 68 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 8 69 4.1. Frame Impairment Statistics Summary Block . . . . . . . . 9 70 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9 71 4.1.2. Definition of Fields in Frame Impairment Summary 72 Statistics Block . . . . . . . . . . . . . . . . . . . 9 73 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 74 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 75 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 77 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 78 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12 79 6.3. Contact information for registrations . . . . . . . . . . 12 80 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 81 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 82 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 83 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 84 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 85 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 86 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-01 . . . . . . . . 14 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 89 1. Introduction 91 This draft defines three new block types to augment those defined in 92 Freidman, et al. [RFC3611] for use in a range of RTP applications. 94 The first two block types support the reporting of burst gap loss/ 95 discard summary statistics including packet loss/discard proportion, 96 mean and variance and belong to the class of transport-related end 97 system metrics defined in Wu, Hunt & Arden 98 [I-D.ietf-avtcore-monarch]. These two blocks are intended to be used 99 in conjunction with information from the Burst Gap Loss metric block 100 or Burst Gap Discard metric block, and on which these two block 101 therefore depend. The metrics in the Burst Gap Loss block or Burst 102 Gap Discard metric block can be used independently of the metrics 103 defined in the first two blocks, however. These two blocks reflect 104 transient IP problems that affect user experience and can be used to 105 influence sender strategies to mitigate the problem. 107 To form an accurate assessment of users' quality of experience, it is 108 therefore necessary to know not just overall rates of packet loss/ 109 discard, but also which frame types were affected. The third block 110 supports the reporting of detailed statistics for each frame type, 111 including the number of frames received, lost and discarded of each 112 frame type in the Group of Pictures (GOP) and additional data 113 allowing the calculation of statistical parameters (e.g.,the 114 proportion of each frame type impaired by packet loss and discard). 115 The metrics defined in this block belong to the class of application 116 layer metrics defined in Wu, Hunt & Arden [I-D.ietf-avtcore-monarch]. 118 2. Terminology 120 2.1. Standards Language 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 In addition, the following terms are defined: 128 Picture Type 130 Picture Types used in the different video algorithms are composed 131 of the Key frame and Derived frames. The Key frame is also called 132 a reference frame and used as a reference for predicting other 133 pictures. It is coded without prediction from other pictures. 134 Derived frames are derived from a Key frame using a prediction 135 algorithm. 137 3. Transport Related End System Metrics 139 3.1. Burst/Gap Loss Summary Statistics Block 141 The metrics described here are intended to be used as described in 142 this section, in conjunction with information from the Measurement 143 Information block [I-D.ietf-xrblock-rtcp-xr-meas-identity] (which 144 MUST be present in the same RTCP packet as the Burst/Gap Loss block) 145 and also with the metric "cumulative number of packets lost" provided 146 in standard RTCP [RFC3550]. 148 These metrics provide information relevant to statistical parameters, 149 including burst loss rate, gap loss rate, burst duration mean, burst 150 duration variance and are calculated using burst gap loss metrics 151 defined in [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss] and other 152 information which is sent together with this report block. 154 3.1.1. Report Block Structure 156 0 1 2 3 157 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 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | BT=BGLSS | I | Reserved | block length | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | SSRC of Source | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | Burst Loss Rate | Gap Loss Rate | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Burst duration Mean | Burst duration Variance | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 3.1.2. Definition of Fields in Loss Summary Statistics Block 170 Block Type (BT): 8 bits 172 Burst/Gap Loss Summary Statistics Block is identified by the 173 constant . 175 Interval Metric flag (I): 2 bits 177 This field is used to indicate whether the Burst/Gap Loss Summary 178 Statistics metrics are Sampled, Interval or Cumulative metrics, 179 that is, whether the reported values apply to the most recent 180 measurement interval duration between successive metrics reports 181 (I=10) (the Interval Duration) or to the accumulation period 182 characteristic of cumulative measurements (I=11) (the Cumulative 183 Duration) or is a sampled instantaneous value (I=01) (Sampled 184 Value). 186 Reserved: 6 bits 188 This field is reserved for future definition. In the absence of 189 such a definition, the bits in this field MUST be set to zero and 190 SHOULD be ignored by the receiver. 192 Block Length: 16 bits 194 The constant 3, in accordance with the definition of this field in 195 Section 3 of RFC 3611 [RFC3611]. 197 SSRC of Source: 32 bits 199 As defined in Section 4.1 of RFC3611 [RFC3611]. 201 Burst Loss Rate: 16 bits 203 The fraction of packets lost during bursts since the beginning of 204 reception, expressed as a fixed point number with the binary point 205 at the left edge of the field. This value is calculated by 206 dividing Packets Loss in Bursts by Total Packets expected in 207 Bursts as follows: 209 Packets Loss in Bursts / Total Packets expected in Bursts 211 Gap Loss Rate: 16 bits 213 The fraction of packets lost during gaps since the beginning of 214 reception expressed as a fixed point number with the binary point 215 at the left edge of the field. This value is calculated by 216 dividing the difference between number of packets lost and Packets 217 lost in Bursts by the difference between Packets Expected and 218 Total Packets expected in Bursts as follows: 220 (number of packets lost - Packets Lost in Bursts) / (Packets 221 Expected - Total Packets expected in Bursts) 223 where "number of packets lost" is obtained from standard RTCP 224 [RFC3550] and Packets Expected is calculated as the difference 225 between "extended last sequence number" and "extended first 226 sequence number" (Interval or Cumulative) provided in the 227 Measurement Identity and Information block 228 [I-D.ietf-xrblock-rtcp-xr-meas-identity]. 230 Note that if the metric is to be calculated on an Interval basis, 231 a difference must be taken between the current and preceding 232 values of "cumulative number of packets lost" in RTCP, to obtain 233 the "number of packets lost" for the reporting interval. 235 Burst Duration Mean:16bits 237 The mean burst duration is obtained as the quotient: 239 mean = Sum of Burst Durations / Number of Bursts 241 where "Sum of Burst Durations" and "Number of Bursts" is obtained 242 from the RTCP XR Burst/Gap Loss Block 243 [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss]. 245 Burst Duration Variance:16bits 247 The variance of the burst duration is obtained using the standard 248 result: 250 var = ( Sum of Squares of Burst Durations - Number of Bursts * 251 mean^2 ) / (Number of Bursts - 1) 253 where "Sum of Squares of Burst Durations" and "Number of Bursts"is 254 obtained from the RTCP XR Burst/Gap Loss Block 255 [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss]. 257 3.2. Burst/Gap Discard Summary Statistics Block 259 The metrics described here are intended to be used as described in 260 this section, in conjunction with information from the Measurement 261 Identity block [I-D.ietf-xrblock-rtcp-xr-meas-identity] (which MUST 262 be present in the same RTCP packet as the Burst/Gap Discard Summary 263 Statistics block) and also with the metric "number of packets 264 discarded" provided in the RTCP XR Discard Block 265 [I-D.ietf-xrblock-rtcp-xr-discard]. The RTCP XR Discard Block SHOULD 266 be sent if the Burst/Gap Discard Summary Statistics block is sent, 267 but the converse does not apply. 269 These metrics provide information relevant to statistical parameters, 270 including burst discard rate, gap discard rate and are calculated 271 using burst gap loss metrics defined in 272 [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] and other information 273 which is sent together with this report block. 275 3.2.1. Report Block Structure 277 0 1 2 3 278 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 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | BT=BGDSS | I | Reserved | block length | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | SSRC of Source | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | Burst Discard Rate | Gap Discard Rate | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 3.2.2. Definition of Fields inBurst/Gap Discard Summary Statistics 288 Block 290 Block Type (BT): 8 bits 292 Burst/Gap Discard Summary Statistics Block is identified by the 293 constant . 295 Interval Metric Type (I): 2 bits 297 This field is used to indicate whether the Burst/Gap Discard 298 Summary Statistics metrics are Sampled, Interval or Cumulative 299 metrics, that is, whether the reported values applies to the most 300 recent measurement interval duration between successive metrics 301 reports (I=10) (the Interval Duration) or to the accumulation 302 period characteristic of cumulative measurements (I=11) (the 303 Cumulative Duration) or is a sampled instantaneous value (I=01) 304 (Sampled Value). 306 Reserved: 6 bits 308 This field is reserved for future definition. In the absence of 309 such a definition, the bits in this field MUST be set to zero and 310 SHOULD be ignored by the receiver. 312 Block Length: 16 bits 314 The constant 2, in accordance with the definition of this field in 315 Section 3 of RFC 3611 [RFC3611]. 317 SSRC of Source: 32 bits 319 As defined in Section 4.1 of RFC3611 [RFC3611]. 321 Burst Discard Rate: 16 bits 323 The fraction of packets discarded during bursts since the 324 beginning of reception, expressed as a fixed point number with the 325 binary point at the left edge of the field. This value is 326 calculated by dividing Packets Discarded in Bursts by Total 327 Packets expected in Bursts as follows: 329 Packets Discarded in Bursts / Total Packets expected in Bursts 331 Gap Discard Rate: 16 bits 333 The fraction of packets discarded during gaps since the beginning 334 of reception expressed as a fixed point number with the binary 335 point at the left edge of the field. This value is calculated by 336 dividing the difference between number of packets discarded and 337 Packets Discarded in Bursts by the difference between Packets 338 Expected and Total Packets expected in Bursts as follows: 340 (number of packets discarded - Packets Discarded in Bursts) / 341 (Packets Expected - Total Packets expected in Bursts) 343 where "number of packets discarded" is obtained from the RTCP XR 344 Discard Count Block [I-D.ietf-xrblock-rtcp-xr-discard] and Packets 345 Expected is calculated as the difference between "extended last 346 sequence number" and "extended first sequence number" (Interval or 347 Cumulative) provided in the Measurement Information block 348 [I-D.ietf-xrblock-rtcp-xr-meas-identity]. In order for the Burst/ 349 Gap Discard Summary Statistics Block to be meaningful either 351 1. a single instance of the Discard Count block with DT=3 or 352 2. exactly 2 instances of the Discard Count block with DT=1 and 353 DT=2, respectively 355 MUST be included in the same RTCP compound packet. If a Discard 356 Count block with DT=3 is received, "the number of packet 357 discarded" is be filled with the number of packets discarded due 358 to both early and late arrival; otherwise, "the number of packet 359 discarded" is calculated as the sum of packet discards due to 360 early arrival (DT=1) and packet discards due to late arrival 361 (DT=2). 363 4. Application Level Metrics 364 4.1. Frame Impairment Statistics Summary Block 366 This block reports statistics on which frame type were affected 367 beyond the information carried in the Statistics Summary Report Block 368 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 369 Information is recorded about thenumber of frames received, lost 370 frames, duplicated frames and lost partial frames. Such information 371 can be useful for network management and video quality monitoring. 373 4.1.1. Report Block Structure 375 0 1 2 3 376 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 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | BT=FISS |I| Reserved | block length | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | SSRC of Source | 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 | Begin_seq | End_seq | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | Number of frames received | 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 386 | Discarded_frames | 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 | Dup_frames | 389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 390 | Lost_full_frames | 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | Lost_partial_frames | 393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 395 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 396 Block 398 Block type (BT): 8 bits 400 Frame Impairment Statistics Summary Block is identified by the 401 constant . 403 Picture type indicator (I): 1 bit 405 This field is used to indicate the frame type to be reported. The 406 bit is set to 0 if the lost_full_frames, lost_partial_frames and 407 dup_frames fields contain Key frame (reference frame) counts or 1 408 if they contain Derivation frame counts. Note that if both the 409 Key frame and Derivation frame report are sent, they should be 410 sent in the same RTCP compound packet using two Frame Impairment 411 Summary Statistics Blocks. 413 Reserved: 7 bits 415 This field is reserved for future definition. In the absence of 416 such a definition, the bits in this field MUST be set to zero and 417 SHOULD be ignored by the receiver. 419 Block Length: 16 bits 421 The constant 7, in accordance with the definition of this field in 422 Section 3 of RFC 3611 [RFC3611]. 424 SSRC of Source: 32 bits 426 As defined in Section 4.1 of RFC3611 [RFC3611]. 428 Begin_seq: 16 bits 430 As defined in Section 4.1 of RFC 3611 [RFC3611]. 432 end_seq: 16 bits 434 As defined in Section 4.1 of RFC 3611 [RFC3611]. 436 Number of frames received:32 bits 438 A count of the number of frames received in the above sequence 439 number interval, estimated if necessary. If no frames have been 440 received then this count SHALL be set to zero. 442 Number of discarded frames (discarded_frames): 32 bits 444 Number of frames discarded in the above sequence number interval. 446 Number of duplicate frames (dup_frames): 32 bits 448 Number of duplicate frames received in the above sequence number 449 interval. 451 Number of full frames lost (lost_full_frames): 32 bits 453 If one frame is completely lost, this frame is regarded as one 454 lost full frame. The lost_full_frames is equivalent to the number 455 of full frames lost in the above sequence number interval. 457 Number of partial frames lost (lost_partial_frames): 32 bits 459 If one frame is partially lost, this frame is regarded as one lost 460 fractional frame. The value of the lost_partial_frames field is 461 equivalent to the number of partial frames lost in the above 462 sequence number interval. 464 5. SDP Signaling 466 RFC 3611 defines the use of SDP (Session Description Protocol) 467 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 468 without prior signaling. 470 5.1. SDP rtcp-xr-attrib Attribute Extension 472 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 473 in Section 5.1 of RFC 3611 by providing three additional values of 474 "xr-format" to signal the use of the report block defined in this 475 document. 477 xr-format = / burst-gap-loss-stat 478 / burst-gap-discard-stat 479 / frame-impairment-stat 480 Burst-gap-loss-stat ="burst gap loss summary statistics" 481 Burst-gap-discard-stat="burst gap discard summary statistics" 482 Frame-impairment-stat="frame impairment summary statistics" 484 5.2. Offer/Answer Usage 486 When SDP is used in offer-answer context, the SDP Offer/Answer usage 487 defined in Section 5.2 of RFC 3611 applies. 489 6. IANA Considerations 491 New block types for RTCP XR are subject to IANA registration. For 492 general guidelines on IANA considerations for RTCP XR, refer to RFC 493 3611. 495 6.1. New RTCP XR Block Type values 497 This document assigns three new block type value in the RTCP XR Block 498 Type Registry: 500 Name: BGLSS 501 Long Name: Burst/Gap Loss Summsary Statistics Block 502 Value 503 Reference: Section 3.1 505 Name: BGDSS 506 Long Name: Burst/Gap Discard Summary Statistics Block 507 Value 508 Reference: Section 3.2 510 Name: FISS 511 Long Name: Frame Impairment Statistics Summary 512 Value 513 Reference: Section 4.1 515 6.2. New RTCP XR SDP Parameters 517 This document also registers three new SDP [RFC4566] parameters for 518 the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 520 * " burst-gap-loss-stat " 521 * " burst-gap-discard-stat " 522 * " frame-impairment-stat " 524 6.3. Contact information for registrations 526 The contact information for the registrations is: 528 Glen Zorn 529 Network Zen 530 227/358 Thanon Sanphawut 531 Bang Na, Bangkok 10260 532 Thailand 534 7. Security Considerations 536 The new RTCP XR report blocks proposed in this document introduces no 537 new security considerations beyond those described in RFC 3611. 539 8. Acknowledgements 541 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 542 Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang 543 Hu, Jing Zhao and Ray van Brandenburg for their valuable comments and 544 suggestions on this document. 546 9. References 548 9.1. Normative References 550 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 551 Requirement Levels", BCP 14, RFC 2119, March 1997. 553 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 554 Jacobson, "RTP: A Transport Protocol for Real-Time 555 Applications", STD 64, RFC 3550, July 2003. 557 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 558 Protocol Extended Reports (RTCP XR)", RFC 3611, 559 November 2003. 561 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 562 Description Protocol", RFC 4566, July 2006. 564 9.2. Informative References 566 [I-D.ietf-avtcore-monarch] 567 Wu, W., Hunt, G., and P. Arden, "Guidelines for Use of the 568 RTP Monitoring Framework", draft-ietf-avtcore-monarch-22 569 (work in progress), September 2012. 571 [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] 572 Clark, A., Huang, R., and W. Wu, "RTP Control 573 Protocol(RTCP) Extended Report (XR) Block for Discard 574 Count metric Reporting", 575 draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06 (work in 576 progress), October 2012. 578 [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss] 579 Clark, A., Zhang, S., Zhao, J., and W. Wu, "RTP Control 580 Protocol (RTCP) Extended Report (XR) Block for Burst/Gap 581 Loss metric Reporting", 582 draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 (work in 583 progress), October 2012. 585 [I-D.ietf-xrblock-rtcp-xr-discard] 586 Clark, A., Zorn, G., and W. Wu, "RTP Control Protocol 587 (RTCP) Extended Report (XR) Block for Discard Count metric 588 Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in 589 progress), October 2012. 591 [I-D.ietf-xrblock-rtcp-xr-meas-identity] 592 Clark, A. and W. Wu, "Measurement Identity and information 593 Reporting using SDES item and XR Block", 594 draft-ietf-xrblock-rtcp-xr-meas-identity-10 (work in 595 progress), August 2012. 597 Appendix A. Change Log 599 Note to the RFC-Editor: please remove this section prior to 600 publication as an RFC. 602 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-01 604 The following are the major changes compared to 00: 605 o Outdated Reference update 606 o Add text to clarify the selection of discard count based on 607 discard count metric block. 608 o Revise Interval metric flag defintion for consistency. 609 o SDP text restructure 610 o Other editorial changes based on comments on the list. 612 Authors' Addresses 614 Glen Zorn (editor) 615 Network Zen 616 227/358 Thanon Sanphawut 617 Bang Na, Bangkok 10260 618 Thailand 620 Phone: +66 (0) 909-201060 621 Email: glenzorn@gmail.com 623 Roland Schott 624 Deutsche Telekom 625 Deutsche-Telekom-Allee 7 626 Darmstadt 64295 627 Germany 629 Email: Roland.Schott@telekom.de 630 Qin Wu 631 Huawei 632 101 Software Avenue, Yuhua District 633 Nanjing, Jiangsu 210012 634 China 636 Email: sunseawq@huawei.com 638 Rachel Huang 639 Huawei 640 101 Software Avenue, Yuhua District 641 Nanjing 210012 642 China 644 Email: Rachel@huawei.com