idnits 2.17.1 draft-zorn-xrblock-rtcp-xr-al-stat-05.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 28, 2012) is 4440 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: 'PMOL' is defined on line 549, 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: August 31, 2012 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 February 28, 2012 11 RTCP XR for Summary Statistics Metrics Reporting 12 draft-zorn-xrblock-rtcp-xr-al-stat-05 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 August 31, 2012. 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 Summsary 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 . . . . . . . . . . . . . . . . . . . . . . . . 6 66 4. Application Layer Metrics . . . . . . . . . . . . . . . . . . 8 67 4.1. Frame Impairment Statistics Summary Block . . . . . . . . 8 68 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 8 69 4.1.2. Definition of Fields in Frame Impairment Summary 70 Statistics Block . . . . . . . . . . . . . . . . . . . 9 71 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 73 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 74 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 11 75 6.3. Contact information for registrations . . . . . . . . . . 11 76 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 77 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 78 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 79 9.1. Normative References . . . . . . . . . . . . . . . . . . . 12 80 9.2. Informative References . . . . . . . . . . . . . . . . . . 12 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 Summsary 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=TBD |I| rsv. | block length | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 153 | SSRC of Source | 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Burst Loss Rate | Gap Loss Rate | 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Burst duration Mean | Burst duration Varianc | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 3.1.2. Definition of Fields in Loss Summary Statistics Block 162 Block Type (BT): 8 bits 164 Burst/Gap Loss Summsary Statistics Block is identified by the 165 constant . 167 Interval Metric flag (I): 1 bit 169 This field is used to indicate whether the metrics block is an 170 Interval or a Cumulative report, 172 Reserved: 7 bits 174 This field is reserved for future definition. In the absence of 175 such a definition, the bits in this field MUST be set to zero and 176 MUST be ignored by the receiver. 178 Block Length: 16 bits 180 The constant 2, in accordance with the definition of this field in 181 Section 3 of RFC 3611 [RFC3611]. 183 SSRC of Source: 32 bits 185 As defined in Section 4.1 of RFC3611 [RFC3611]. 187 Burst Loss Rate: 16 bits 189 The fraction of packets lost during bursts since the beginning of 190 reception, expressed as a fixed point number with the binary point 191 at the left edge of the field. This value is calculated by 192 dividing Packets Discarded in Bursts by Total Packets expected in 193 Bursts as follows: 195 Packets Loss in Bursts / Total Packets expected in Bursts 197 Gap Loss Rate: 16 bits 199 The fraction of packets lost during gaps since the beginning of 200 reception expressed as a fixed point number with the binary point 201 at the left edge of the field. This value is calculated by 202 dividing the difference between number of packets lost and Packets 203 lost in Bursts by the difference between Packets Expected and 204 Total Packets expected in Bursts as follows: 206 (number of packets lost - Packets Lost in Bursts) / (Packets 207 Expected - Total Packets expected in Bursts) 209 where "number of packets lost" is obtained from standard RTCP 210 [RFC3550] and Packets Expected is calculated as the difference 211 between "extended last sequence number" and "extended first 212 sequence number" (Interval or Cumulative) provided in the 213 Measurement Identity and Information block [MEASIDENT]. 215 Note that if the metric is to be calculated on an Interval basis, 216 a difference must be taken between the current and preceding 217 values of "cumulative number of packets lost" in RTCP, to obtain 218 the "number of packets lost" for the reporting interval. 220 Burst Duration Mean:16bits 222 The mean burst duration is obtained as the quotient: 224 mean = Sum of Burst Durations / Number of Bursts 225 where " Sum of Burst Durations " and "Number of Bursts"is obtained 226 from the RTCP XR Burst/Gap Discard Block. 228 Burst Duration Variance:16bits 230 The variance of the burst duration is obtained using the standard 231 result: 233 var = ( Sum of Squares of Burst Durations - Number of Bursts * 234 mean^2 ) / (Number of Bursts - 1) 236 where " Sum of Squares of Burst Durations " and "Number of 237 Bursts"is obtained from the RTCP XR Burst/Gap Discard Block. 239 3.2. Burst/Gap Discard Summary Statistics Block 241 The metrics described here are intended to be used as described in 242 this section, in conjunction with information from the Measurement 243 Identity block [MEASIDENT] (which MUST be present in the same RTCP 244 packet as the Burst/Gap Discard block) and also with the metric 245 "number of packets discarded" provided in the RTCP XR Discard Block 246 [DISCARD]. The RTCP XR Discard Block SHOULD be sent if the Burst/Gap 247 Discard block is sent, but the converse does not apply. 249 These metrics provide information relevant to statistical parameters, 250 including burst discard rate, gap discard rate and are calculated 251 using burst gap loss metrics defined in [BGDISCARD] and other 252 information which is sent together with this report block. 254 3.2.1. Report Block Structure 256 0 1 2 3 257 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 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | BT=TBD |I| Rsv. | block length | 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 | SSRC of Source | 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 263 | Burst Discard Rate | Gap Discard Rate | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 3.2.2. Definition of Fields in Discard Summary Statistics Block 267 Block Type (BT): 8 bits 269 Burst/Gap Discard Summary Statistics Block is identified by the 270 constant . 272 Reserved: 8 bits 274 This field is reserved for future definition. In the absence of 275 such a definition, the bits in this field MUST be set to zero and 276 MUST be ignored by the receiver. 278 Interval Metric flag (I): 1 bit 280 This field is used to indicate whether the metrics block is an 281 Interval or a Cumulative report, 283 Reserved: 7 bits 285 This field is reserved for future definition. In the absence of 286 such a definition, the bits in this field MUST be set to zero and 287 MUST be ignored by the receiver. 289 block length: 16 bits 291 The constant 3, in accordance with the definition of this field in 292 Section 3 of RFC 3611 [RFC3611]. 294 SSRC of Source: 32 bits 296 As defined in Section 4.1 of RFC3611 [RFC3611]. 298 Burst Discard Rate: 16 bits 300 The fraction of packets discarded during bursts since the 301 beginning of reception, expressed as a fixed point number with the 302 binary point at the left edge of the field. This value is 303 calculated by dividing Packets Discarded in Bursts by Total 304 Packets expected in Bursts as follows: 306 Packets Discarded in Bursts / Total Packets expected in Bursts 308 Gap Discard Rate: 16 bits 310 The fraction of packets discarded during gaps since the beginning 311 of reception expressed as a fixed point number with the binary 312 point at the left edge of the field. This value is calculated by 313 dividing the difference between number of packets discarded and 314 Packets Discarded in Bursts by the difference between Packets 315 Expected and Total Packets expected in Bursts as follows: 317 (number of packets discarded - Packets Discarded in Bursts) / 318 (Packets Expected - Total Packets expected in Bursts) 320 where "number of packets discarded" is obtained from the RTCP XR 321 Discard Block [DISCARD] and Packets Expected is calculated as the 322 difference between "extended last sequence number" and "extended 323 first sequence number" (Interval or Cumulative) provided in the 324 Measurement Information block [MEASIDENT]. 326 4. Application Layer Metrics 328 4.1. Frame Impairment Statistics Summary Block 330 This block reports statistics on which frame type were affected 331 beyond the information carried in the Statistics Summary Report Block 332 RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. 333 Information is recorded about umber of frames received, lost frames 334 ,duplicated frames, lost partial frames. Such information can be 335 useful for network management and video quality monitoring. 337 4.1.1. Report Block Structure 339 0 1 2 3 340 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 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | BT=TBD | |T| rsv. | block length | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | SSRC of Source | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | begin_seq | end_seq | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | Number of frames received | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | dicarded_frames | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | dup_frames | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | lost_full_frames | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | lost_partial_frames | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 4.1.2. Definition of Fields in Frame Impairment Summary Statistics 360 Block 362 Block type (BT): 8 bits 364 Frame Impairment Statistics Summary Block is identified by the 365 constant . 367 Picture type indicator (T): 1 bit 369 Picture types used in the different video algorithms compose of 370 key-frame and derivation frame. This field is used to indicate 371 the frame type to be reported. Bits set to 0 if the lost_frames 372 field or dup_frames field contain a key_frame report or reference 373 frame report, 1 if the lost_frames field and dup_frames field 374 contain other derivation frame report. Note that if both the key 375 frame report and derivation frame are sent, they should be sent in 376 the same RTCP compound packet using two XR Blocks. 378 Rsv.: 6 bits 380 This field is reserved for future definition. In the absence of 381 such a definition, the bits in this field MUST be set to zero and 382 MUST be ignored by the receiver. 384 Block Length: 16 bits 386 The constant 7, in accordance with the definition of this field in 387 Section 3 of RFC 3611 [RFC3611]. 389 SSRC of Source: 32 bits 391 As defined in Section 4.1 of RFC3611 [RFC3611]. 393 begin_seq: 16 bits 395 As defined in Section 4.1 of RFC 3611 [RFC3611]. 397 end_seq: 16 bits 399 As defined in Section 4.1 of RFC 3611 [RFC3611]. 401 number of frames received:32bits 403 A count of the number of frames received, estimated if necessary. 404 If no frames have been received then this count shall be set to 405 Zero. 407 lost_full_frames: 32 bits 409 If one frame is completely lost, this frame is regarded as one 410 lost full_frame. The lost_full_frames is equivalent to the number 411 of lost_full_frames in the above sequence number interval. 413 discarded_frames: 32 bits 415 Number of frames discarded in the above sequence number interval. 417 dup_frames: 32 bits 419 Number of duplicated frames in the above sequence number interval. 421 lost_partial_frames: 32 bits 423 If one frame is partially lost, this frame is regarded as one lost 424 fractional frame. The lost_partial_frames is equivalent to the 425 number of lost_partial_frames in the above sequence number 426 interval. 428 5. SDP Signaling 430 [RFC3611] defines the use of SDP (Session Description Protocol) 431 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 432 without prior signaling. 434 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 435 in [RFC3611] by providing three additional value of "xr-format" to 436 signal the use of the report block defined in this document. 438 rtcp-xr-attrib = "a=rtcp-xr:" 439 [xr-format *(SP xr-format)] CRLF 440 xr-format = 441 / burst-gap-loss-stat 442 / burst-gap-discard-stat 443 / frame-impairment-stat 445 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 446 and the full syntax of the "rtcp-xr" attribute. 448 6. IANA Considerations 450 New block types for RTCP XR are subject to IANA registration. For 451 general guidelines on IANA considerations for RTCP XR, refer 452 to[RFC3611] . 454 6.1. New RTCP XR Block Type values 456 This document assigns three new block type value in the RTCP XR Block 457 Type Registry: 459 Name: BGLSS 460 Long Name: Burst/Gap Loss Summsary Statistics Block 461 Value 462 Reference: Section 5.1 464 Name: BGDSS 465 Long Name: Burst/Gap Discard Summary Statistics Block 466 Value 467 Reference: Section 5.2 469 Name: FISS 470 Long Name: Frame Impairment Statistics Summary 471 Value 472 Reference: Section 6.1 474 6.2. New RTCP XR SDP Parameters 476 This document also registers three new SDP [RFC4566] parameters for 477 the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 479 * " burst-gap-loss-stat " 480 * " burst-gap-discard-stat " 481 * " frame-impairment-stat " 483 6.3. Contact information for registrations 485 The contact information for the registrations is: 487 Glen Zorn 488 Network Zen 489 227/358 Thanon Sanphawut 490 Bang Na, Bangkok 10110 491 Thailand 493 7. Security Considerations 495 The new RTCP XR report blocks proposed in this document introduces no 496 new security considerations beyond those described in [RFC3611]. 498 8. Acknowledgements 500 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 501 Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu, Yinliang 502 Hu,Jing Zhao and Brandenburg, R. (Ray) van for their valuable 503 comments and suggestions on this document. 505 9. References 507 9.1. Normative References 509 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 510 Requirement Levels", BCP 14, RFC 2119, March 1997. 512 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 513 Jacobson, "RTP: A Transport Protocol for Real-Time 514 Applications", STD 64, RFC 3550, July 2003. 516 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 517 Protocol Extended Reports (RTCP XR)", RFC 3611, 518 November 2003. 520 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 521 Description Protocol", RFC 4566, July 2006. 523 9.2. Informative References 525 [BGDISCARD] 526 Hunt, G., "RTCP XR Report Block for Burst Gap Discard 527 metric Reporting", 528 ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02, 529 January 2012. 531 [BGLOSS] Hunt, G., "RTCP XR Report Block for Burst Gap Loss metric 532 Reporting", 533 ID draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01, 534 January 2012. 536 [DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric 537 Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-01, 538 December 2011. 540 [MEASIDENT] 541 Wu, Q., "Measurement Identity and information Reporting 542 using SDES item and XR Block", 543 ID draft-ietf-xrblock-rtcp-xr-meas-identity-02, 544 January 2012. 546 [MONARCH] Wu, Q., "Monitoring Architecture for RTP", 547 ID draft-ietf-avtcore-monarch-10, February 2012. 549 [PMOL] Clark, A., "Framework for Performance Metric Development", 550 RFC 6390, January 2011. 552 Appendix A. Change Log 554 This document is separated from 555 draft-wu-xrblock-rtcp-xr-quality-monitoring-01 with a few editorial 556 changes and focuses on loss,duplication, discard, and summary 557 statistics metrics. 559 Authors' Addresses 561 Glen Zorn 562 Network Zen 563 77/440 Soi Phoomjit, Rama IV Road 564 Phra Khanong, Khlong Toie 565 Bangkok 10110 566 Thailand 568 Phone: +66 (0) 87 502 4274 569 Email: gwz@net-zen.net 571 Roland Schott 572 Deutsche Telekom 573 Deutsche-Telekom-Allee 7 574 Darmstadt 64295 575 Germany 577 Email: Roland.Schott@telekom.de 579 Qin Wu 580 Huawei 581 101 Software Avenue, Yuhua District 582 Nanjing, Jiangsu 210012 583 China 585 Email: sunseawq@huawei.com 586 Rachel Huang 587 Huawei 588 101 Software Avenue, Yuhua District 589 Nanjing 210012 590 China 592 Email: Rachel@huawei.com