idnits 2.17.1 draft-ietf-xrblock-rtcp-xr-summary-stat-00.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 (July 30, 2012) is 4259 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: 'RFC6390' is defined on line 562, but no explicit reference was found in the text ** 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-02 == Outdated reference: A later version (-12) exists of draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01 == Outdated reference: A later version (-15) exists of draft-ietf-xrblock-rtcp-xr-discard-01 == Outdated reference: A later version (-10) exists of draft-ietf-xrblock-rtcp-xr-meas-identity-02 == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-10 Summary: 1 error (**), 0 flaws (~~), 7 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: January 31, 2013 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 July 30, 2012 11 RTCP XR for Summary Statistics Metrics Reporting 12 draft-ietf-xrblock-rtcp-xr-summary-stat-00 14 Abstract 16 This document defines three RTCP XR Report Blocks and associated SDP 17 parameters that allows the reporting of loss, duplication and discard 18 summary statistics metrics for use in a range of RTP applications. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on January 31, 2013. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 57 3. Transport Layer Metrics . . . . . . . . . . . . . . . . . . . 4 58 3.1. Burst/Gap Loss Summary Statistics Block . . . . . . . . . 4 59 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 4 60 3.1.2. Definition of Fields in Loss Summary Statistics 61 Block . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 6 63 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 6 64 3.2.2. Definition of Fields in Discard Summary Statistics 65 Block . . . . . . . . . . . . . . . . . . . . . . . . 7 66 4. Application Layer Metrics . . . . . . . . . . . . . . . . . . 8 67 4.1. Frame Impairment Statistics Summary Block . . . . . . . . 8 68 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9 69 4.1.2. Definition of Fields in Frame Impairment Summary 70 Statistics Block . . . . . . . . . . . . . . . . . . . 9 71 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 73 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 74 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12 75 6.3. Contact information for registrations . . . . . . . . . . 12 76 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 77 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 78 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 79 9.1. Normative References . . . . . . . . . . . . . . . . . . . 12 80 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 81 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 84 1. Introduction 86 This draft defines three new block types to augment those defined in 87 [RFC3611] for use in a range of RTP applications. 89 The first two block types support the reporting of burst gap loss/ 90 discard, summary statistics including packet loss/discard proportion, 91 mean and variance and belong to the class of transport layer metrics 92 defined in [MONARCH]. These two blocks are intended to be used in 93 conjunction with information from the Burst Gap Loss metric block or 94 burst gap discard metric block, and on which these two block 95 therefore depends. However the metrics in the Burst Gap Loss block 96 or burst gap discard block may be used independently of the metrics 97 defined in the first two blocks. 99 To form an accurate assessment of user quality of experience, it is 100 therefore necessary to know not just overall rates of packet loss/ 101 discard, but also which frame type were affected. The third block 102 supports the reporting of detailed statistics for each frame type, 103 including the number of received, lost and discarded of each frame 104 type in the Group of Pictures and additional data allowing the 105 calculation of statistical parameters (e.g.,the proportion of each 106 frame type impaired by packet loss and discard). The metrics defined 107 in this block belong to the class of application layer metrics 108 defined in [MONARCH]. 110 2. Terminology 112 2.1. Standards Language 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in RFC 2119 [RFC2119]. 118 In addition, the following terms are defined: 120 Picture Type 122 Picture types used in the different video algorithms compose of 123 the key-frame and the Derivation frame. Key-frame is also called 124 a reference frame and used as a reference for predicting other 125 pictures. It is coded without prediction from other pictures. 126 The Derivation frame is derived from Key-frame using prediction 127 from the reference frame. 129 3. Transport Layer Metrics 131 3.1. Burst/Gap Loss Summary Statistics Block 133 The metrics described here are intended to be used as described in 134 this section, in conjunction with information from the Measurement 135 Information block [MEASIDENT] (which MUST be present in the same RTCP 136 packet as the Burst/Gap Loss block) and also with the metric 137 "cumulative number of packets lost" provided in standard RTCP 138 [RFC3550]. 140 These metrics provide information relevant to statistical parameters, 141 including burst loss rate, gap loss rate, burst duration mean, burst 142 duration variance and are calculated using burst gap loss metrics 143 defined in [BGLOSS] and other information which is sent together with 144 this report block. 146 3.1.1. Report Block Structure 148 0 1 2 3 149 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 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | BT=BGLSS | I | rsv. | block length | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 153 | SSRC of Source | 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Burst Loss Rate | Gap Loss Rate | 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Burst duration Mean | Burst duration Variance | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 3.1.2. Definition of Fields in Loss Summary Statistics Block 162 Block Type (BT): 8 bits 164 Burst/Gap Loss Summary Statistics Block is identified by the 165 constant . 167 Interval Metric flag (I): 2 bits 169 This field is used to indicate whether the Burst/Gap Loss Summary 170 Statistics metrics are Sampled, Interval or Cumulative metrics, 171 that is, whether the reported values applies to the most recent 172 measurement interval duration between successive metrics reports 173 (I=10) (the Interval Duration) or to the accumulation period 174 characteristic of cumulative measurements (I=11) (the Cumulative 175 Duration) or is a sampled instantaneous value (I=01) (Sampled 176 Value). 178 Reserved: 6 bits 180 This field is reserved for future definition. In the absence of 181 such a definition, the bits in this field MUST be set to zero and 182 MUST be ignored by the receiver. 184 Block Length: 16 bits 186 The constant 3, in accordance with the definition of this field in 187 Section 3 of RFC 3611 [RFC3611]. 189 SSRC of Source: 32 bits 191 As defined in Section 4.1 of RFC3611 [RFC3611]. 193 Burst Loss Rate: 16 bits 195 The fraction of packets lost during bursts since the beginning of 196 reception, expressed as a fixed point number with the binary point 197 at the left edge of the field. This value is calculated by 198 dividing Packets Loss in Bursts by Total Packets expected in 199 Bursts as follows: 201 Packets Loss in Bursts / Total Packets expected in Bursts 203 Gap Loss Rate: 16 bits 205 The fraction of packets lost during gaps since the beginning of 206 reception expressed as a fixed point number with the binary point 207 at the left edge of the field. This value is calculated by 208 dividing the difference between number of packets lost and Packets 209 lost in Bursts by the difference between Packets Expected and 210 Total Packets expected in Bursts as follows: 212 (number of packets lost - Packets Lost in Bursts) / (Packets 213 Expected - Total Packets expected in Bursts) 215 where "number of packets lost" is obtained from standard RTCP 216 [RFC3550] and Packets Expected is calculated as the difference 217 between "extended last sequence number" and "extended first 218 sequence number" (Interval or Cumulative) provided in the 219 Measurement Identity and Information block [MEASIDENT]. 221 Note that if the metric is to be calculated on an Interval basis, 222 a difference must be taken between the current and preceding 223 values of "cumulative number of packets lost" in RTCP, to obtain 224 the "number of packets lost" for the reporting interval. 226 Burst Duration Mean:16bits 228 The mean burst duration is obtained as the quotient: 230 mean = Sum of Burst Durations / Number of Bursts 232 where " Sum of Burst Durations " and "Number of Bursts"is obtained 233 from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 235 Burst Duration Variance:16bits 237 The variance of the burst duration is obtained using the standard 238 result: 240 var = ( Sum of Squares of Burst Durations - Number of Bursts * 241 mean^2 ) / (Number of Bursts - 1) 243 where " Sum of Squares of Burst Durations " and "Number of 244 Bursts"is obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. 246 3.2. Burst/Gap Discard Summary Statistics Block 248 The metrics described here are intended to be used as described in 249 this section, in conjunction with information from the Measurement 250 Identity block [MEASIDENT] (which MUST be present in the same RTCP 251 packet as the Burst/Gap Discard block) and also with the metric 252 "number of packets discarded" provided in the RTCP XR Discard Block 253 [DISCARD]. The RTCP XR Discard Block SHOULD be sent if the Burst/Gap 254 Discard block is sent, but the converse does not apply. 256 These metrics provide information relevant to statistical parameters, 257 including burst discard rate, gap discard rate and are calculated 258 using burst gap loss metrics defined in [BGDISCARD] and other 259 information which is sent together with this report block. 261 3.2.1. Report Block Structure 263 0 1 2 3 264 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 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | BT=BGDSS | I | Rsv. | block length | 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | SSRC of Source | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Burst Discard Rate | Gap Discard Rate | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 3.2.2. Definition of Fields in Discard Summary Statistics Block 275 Block Type (BT): 8 bits 277 Burst/Gap Discard Summary Statistics Block is identified by the 278 constant . 280 Reserved: 8 bits 282 This field is reserved for future definition. In the absence of 283 such a definition, the bits in this field MUST be set to zero and 284 MUST be ignored by the receiver. 286 Interval Metric flag (I): 2 bits 288 This field is used to indicate whether the metrics block is an 289 Interval or a Cumulative report, 291 Reserved: 6 bits 293 This field is used to indicate whether the Burst/Gap Discard 294 Summary Statistics metrics are Sampled, Interval or Cumulative 295 metrics, that is, whether the reported values applies to the most 296 recent measurement interval duration between successive metrics 297 reports (I=10) (the Interval Duration) or to the accumulation 298 period characteristic of cumulative measurements (I=11) (the 299 Cumulative Duration) or is a sampled instantaneous value (I=01) 300 (Sampled Value). 302 block length: 16 bits 304 The constant 2, in accordance with the definition of this field in 305 Section 3 of RFC 3611 [RFC3611]. 307 SSRC of Source: 32 bits 309 As defined in Section 4.1 of RFC3611 [RFC3611]. 311 Burst Discard Rate: 16 bits 313 The fraction of packets discarded during bursts since the 314 beginning of reception, expressed as a fixed point number with the 315 binary point at the left edge of the field. This value is 316 calculated by dividing Packets Discarded in Bursts by Total 317 Packets expected in Bursts as follows: 319 Packets Discarded in Bursts / Total Packets expected in Bursts 321 Gap Discard Rate: 16 bits 323 The fraction of packets discarded during gaps since the beginning 324 of reception expressed as a fixed point number with the binary 325 point at the left edge of the field. This value is calculated by 326 dividing the difference between number of packets discarded and 327 Packets Discarded in Bursts by the difference between Packets 328 Expected and Total Packets expected in Bursts as follows: 330 (number of packets discarded - Packets Discarded in Bursts) / 331 (Packets Expected - Total Packets expected in Bursts) 333 where "number of packets discarded" is obtained from the RTCP XR 334 Discard Block [DISCARD] and Packets Expected is calculated as the 335 difference between "extended last sequence number" and "extended 336 first sequence number" (Interval or Cumulative) provided in the 337 Measurement Information block [MEASIDENT]. 339 4. Application Layer Metrics 341 4.1. Frame Impairment Statistics Summary Block 343 This block reports statistics on which frame type were affected 344 beyond the information carried in the Statistics Summary Report Block 345 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 346 Information is recorded about umber of frames received, lost frames 347 ,duplicated frames, lost partial frames. Such information can be 348 useful for network management and video quality monitoring. 350 4.1.1. Report Block Structure 352 0 1 2 3 353 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 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | BT=FISS |T| rsv. | block length | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | SSRC of Source | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | begin_seq | end_seq | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Number of frames received | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | dicarded_frames | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | dup_frames | 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 | lost_full_frames | 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 369 | lost_partial_frames | 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 373 Block 375 Block type (BT): 8 bits 377 Frame Impairment Statistics Summary Block is identified by the 378 constant . 380 Picture type indicator (T): 1 bit 382 Picture types used in the different video algorithms compose of 383 key-frame and derivation frame. This field is used to indicate 384 the frame type to be reported. Bits set to 0 if the lost_frames 385 field or dup_frames field contain a key_frame report or reference 386 frame report, 1 if the lost_frames field and dup_frames field 387 contain other derivation frame report. Note that if both the key 388 frame report and derivation frame are sent, they should be sent in 389 the same RTCP compound packet using two XR Blocks. 391 Rsv.: 7 bits 393 This field is reserved for future definition. In the absence of 394 such a definition, the bits in this field MUST be set to zero and 395 MUST be ignored by the receiver. 397 Block Length: 16 bits 399 The constant 7, in accordance with the definition of this field in 400 Section 3 of RFC 3611 [RFC3611]. 402 SSRC of Source: 32 bits 404 As defined in Section 4.1 of RFC3611 [RFC3611]. 406 begin_seq: 16 bits 408 As defined in Section 4.1 of RFC 3611 [RFC3611]. 410 end_seq: 16 bits 412 As defined in Section 4.1 of RFC 3611 [RFC3611]. 414 number of frames received:32bits 416 A count of the number of frames received, estimated if necessary. 417 If no frames have been received then this count shall be set to 418 Zero. 420 lost_full_frames: 32 bits 422 If one frame is completely lost, this frame is regarded as one 423 lost full_frame. The lost_full_frames is equivalent to the number 424 of lost_full_frames in the above sequence number interval. 426 discarded_frames: 32 bits 428 Number of frames discarded in the above sequence number interval. 430 dup_frames: 32 bits 432 Number of duplicated frames in the above sequence number interval. 434 lost_partial_frames: 32 bits 436 If one frame is partially lost, this frame is regarded as one lost 437 fractional frame. The lost_partial_frames is equivalent to the 438 number of lost_partial_frames in the above sequence number 439 interval. 441 5. SDP Signaling 443 [RFC3611] defines the use of SDP (Session Description Protocol) 444 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 445 without prior signaling. 447 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 448 in [RFC3611] by providing three additional value of "xr-format" to 449 signal the use of the report block defined in this document. 451 rtcp-xr-attrib = "a=rtcp-xr:" 452 [xr-format *(SP xr-format)] CRLF 453 xr-format = 454 / burst-gap-loss-stat 455 / burst-gap-discard-stat 456 / frame-impairment-stat 458 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 459 and the full syntax of the "rtcp-xr" attribute. 461 6. IANA Considerations 463 New block types for RTCP XR are subject to IANA registration. For 464 general guidelines on IANA considerations for RTCP XR, refer 465 to[RFC3611] . 467 6.1. New RTCP XR Block Type values 469 This document assigns three new block type value in the RTCP XR Block 470 Type Registry: 472 Name: BGLSS 473 Long Name: Burst/Gap Loss Summsary Statistics Block 474 Value 475 Reference: Section 5.1 477 Name: BGDSS 478 Long Name: Burst/Gap Discard Summary Statistics Block 479 Value 480 Reference: Section 5.2 482 Name: FISS 483 Long Name: Frame Impairment Statistics Summary 484 Value 485 Reference: Section 6.1 487 6.2. New RTCP XR SDP Parameters 489 This document also registers three new SDP [RFC4566] parameters for 490 the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 492 * " burst-gap-loss-stat " 493 * " burst-gap-discard-stat " 494 * " frame-impairment-stat " 496 6.3. Contact information for registrations 498 The contact information for the registrations is: 500 Glen Zorn 501 Network Zen 502 227/358 Thanon Sanphawut 503 Bang Na, Bangkok 10110 504 Thailand 506 7. Security Considerations 508 The new RTCP XR report blocks proposed in this document introduces no 509 new security considerations beyond those described in [RFC3611]. 511 8. Acknowledgements 513 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 514 Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu, Yinliang 515 Hu,Jing Zhao and Brandenburg, R. (Ray) van for their valuable 516 comments and suggestions on this document. 518 9. References 520 9.1. Normative References 522 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 523 Requirement Levels", BCP 14, RFC 2119, March 1997. 525 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 526 Jacobson, "RTP: A Transport Protocol for Real-Time 527 Applications", STD 64, RFC 3550, July 2003. 529 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 530 Protocol Extended Reports (RTCP XR)", RFC 3611, 531 November 2003. 533 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 534 Description Protocol", RFC 4566, July 2006. 536 9.2. Informative References 538 [BGDISCARD] 539 Hunt, G., "RTCP XR Report Block for Burst Gap Discard 540 metric Reporting", 541 ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02, 542 January 2012. 544 [BGLOSS] Hunt, G., "RTCP XR Report Block for Burst Gap Loss metric 545 Reporting", 546 ID draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01, 547 January 2012. 549 [DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric 550 Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-01, 551 December 2011. 553 [MEASIDENT] 554 Wu, Q., "Measurement Identity and information Reporting 555 using SDES item and XR Block", 556 ID draft-ietf-xrblock-rtcp-xr-meas-identity-02, 557 January 2012. 559 [MONARCH] Wu, Q., "Monitoring Architecture for RTP", 560 ID draft-ietf-avtcore-monarch-10, February 2012. 562 [RFC6390] Clark, A., "Framework for Performance Metric Development", 563 RFC 6390, January 2011. 565 Appendix A. Change Log 567 This document is separated from 568 draft-wu-xrblock-rtcp-xr-quality-monitoring-01 with a few editorial 569 changes and focuses on loss,duplication, discard, and summary 570 statistics metrics. 572 Authors' Addresses 574 Glen Zorn 575 Network Zen 576 77/440 Soi Phoomjit, Rama IV Road 577 Phra Khanong, Khlong Toie 578 Bangkok 10110 579 Thailand 581 Phone: +66 (0) 87 502 4274 582 Email: gwz@net-zen.net 584 Roland Schott 585 Deutsche Telekom 586 Deutsche-Telekom-Allee 7 587 Darmstadt 64295 588 Germany 590 Email: Roland.Schott@telekom.de 592 Qin Wu 593 Huawei 594 101 Software Avenue, Yuhua District 595 Nanjing, Jiangsu 210012 596 China 598 Email: sunseawq@huawei.com 600 Rachel Huang 601 Huawei 602 101 Software Avenue, Yuhua District 603 Nanjing 210012 604 China 606 Email: Rachel@huawei.com