idnits 2.17.1 draft-zorn-xrblock-rtcp-xr-al-stat-04.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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 19, 2012) is 4480 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: 'I-D.ietf-avt-rtp-svc' is defined on line 504, but no explicit reference was found in the text == Unused Reference: 'RFC2250' is defined on line 519, but no explicit reference was found in the text == Unused Reference: 'RFC3357' is defined on line 523, but no explicit reference was found in the text == Unused Reference: 'RFC5234' is defined on line 537, but no explicit reference was found in the text == Unused Reference: 'DSLF' is defined on line 542, but no explicit reference was found in the text == Unused Reference: 'PMOL' is defined on line 549, but no explicit reference was found in the text -- No information found for draft-ietf-rtcp-xr-discard - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'DISCARD' == Outdated reference: A later version (-10) exists of draft-ietf-xrblock-rtcp-xr-meas-identity-01 ** Downref: Normative reference to an Informational RFC: RFC 3357 ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) == Outdated reference: A later version (-22) exists of draft-ietf-avtcore-monarch-00 == Outdated reference: A later version (-12) exists of draft-ietf-pmol-metrics-framework-08 Summary: 2 errors (**), 0 flaws (~~), 11 warnings (==), 3 comments (--). 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: July 22, 2012 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 January 19, 2012 11 RTCP XR for Summary Statistics Metrics Reporting 12 draft-zorn-xrblock-rtcp-xr-al-stat-04 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 July 22, 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 This document may contain material from IETF Documents or IETF 53 Contributions published or made publicly available before November 54 10, 2008. The person(s) controlling the copyright in some of this 55 material may not have granted the IETF Trust the right to allow 56 modifications of such material outside the IETF Standards Process. 57 Without obtaining an adequate license from the person(s) controlling 58 the copyright in such materials, this document may not be modified 59 outside the IETF Standards Process, and derivative works of it may 60 not be created outside the IETF Standards Process, except to format 61 it for publication as an RFC or to translate it into languages other 62 than English. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1.1. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 70 3. Transport Layer Metrics . . . . . . . . . . . . . . . . . . . 4 71 3.1. Burst/Gap Loss Summsary Statistics Block . . . . . . . . . 4 72 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 5 73 3.1.2. Definition of Fields in Loss Summary Statistics 74 Block . . . . . . . . . . . . . . . . . . . . . . . . 5 75 3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 7 76 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7 77 3.2.2. Definition of Fields in Discard Summary Statistics 78 Block . . . . . . . . . . . . . . . . . . . . . . . . 7 79 4. Application Layer Metrics . . . . . . . . . . . . . . . . . . 8 80 4.1. Application Layer Loss/Duplication Statistics Summary 81 Block . . . . . . . . . . . . . . . . . . . . . . . . . . 9 82 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9 83 4.1.2. Definition of Fields in Loss/Duplication Summary 84 Statistics Block . . . . . . . . . . . . . . . . . . . 9 85 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 86 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 87 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 88 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12 89 6.3. Contact information for registrations . . . . . . . . . . 12 90 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 91 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 92 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 93 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 94 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 95 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 98 1. Introduction 100 RFC 3611 [RFC3611] defines seven report block formats for network 101 management and quality monitoring. However, some of these metrics 102 are mostly for multicast inference of network characteristics (MINC) 103 or voice over IP (VoIP) monitoring and not widely applicable to other 104 applications, e.g., video quality monitoring. This document focuses 105 on specifying new additional report block types used to convey loss, 106 duplication and discard summary statistics that are generically 107 designed for use in audio and video services. 109 The metrics belong to both the class of application layer metrics and 110 transport layer metrics defined in [MONARCH] (work in progress). 112 1.1. Applicability 114 The Report Blocks defined in this document can be applied to any 115 real-time applications that convey loss, duplication and discard 116 summary statistics. 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 compose of 131 the key-frame and the Derivation frame. 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 The Derivation frame is derived from Key-frame using prediction 135 from the reference frame. 137 3. Transport Layer Metrics 139 3.1. Burst/Gap Loss Summsary 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 (which MUST be present in the same RTCP packet as 144 the Burst/Gap Loss block) and also with the metric "cumulative number 145 of packets lost" provided in standard RTCP [RFC3550]. 147 3.1.1. Report Block Structure 149 0 1 2 3 150 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 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | BT=TBD |I| rsv. | block length | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | SSRC of Source | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | Burst Loss Rate | Gap Loss Rate | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | Burst duration Mean | Burst duration Varianc | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 3.1.2. Definition of Fields in Loss Summary Statistics Block 163 block type (BT): 8 bits 165 Burst/Gap Loss Summsary Statistics Block is identified by the 166 constant . 168 Interval Metric flag (I): 1 bit 170 This field is used to indicate whether the metrics block is an 171 Interval or a Cumulative report, 173 reserved: 7 bits 175 This field is reserved for future definition. In the absence of 176 such a definition, the bits in this field MUST be set to zero and 177 MUST be ignored by the receiver. 179 block length: 16 bits 181 The constant 2, in accordance with the definition of this field in 182 Section 3 of RFC 3611 [RFC3611]. 184 SSRC of source: 32 bits 186 As defined in Section 4.1 of RFC3611 [RFC3611]. 188 Burst Loss Rate: 16 bits 190 The fraction of packets lost during bursts since the beginning of 191 reception, expressed as a fixed point number with the binary point 192 at the left edge of the field. This value is calculated by 193 dividing Packets Discarded in Bursts by Total Packets expected in 194 Bursts as follows: 196 Packets Loss in Bursts / Total Packets expected in Bursts 198 Gap Loss Rate: 16 bits 200 The fraction of packets lost during gaps since the beginning of 201 reception expressed as a fixed point number with the binary point 202 at the left edge of the field. This value is calculated by 203 dividing the difference between number of packets lost and Packets 204 lost in Bursts by the difference between Packets Expected and 205 Total Packets expected in Bursts as follows: 207 (number of packets lost - Packets Lost in Bursts) / (Packets 208 Expected - Total Packets expected in Bursts) 210 where "number of packets lost" is obtained from standard RTCP 211 [RFC3550] and Packets Expected is calculated as the difference 212 between "extended last sequence number" and "extended first 213 sequence number" (Interval or Cumulative) provided in the 214 Measurement Identity and Information block [MEASIDENT]. 216 Note that if the metric is to be calculated on an Interval basis, 217 a difference must be taken between the current and preceding 218 values of "cumulative number of packets lost" in RTCP, to obtain 219 the "number of packets lost" for the reporting interval. 221 Burst duration Mean:16bits 223 The mean burst duration is obtained as the quotient: 225 mean = Sum of Burst Durations / Number of Bursts 227 where " Sum of Burst Durations " and "Number of Bursts"is obtained 228 from the RTCP XR Burst/Gap Discard Block. 230 Burst Duration Variance:16bits 232 The variance of the burst duration is obtained using the standard 233 result: 235 var = ( Sum of Squares of Burst Durations - Number of Bursts * 236 mean^2 ) / (Number of Bursts - 1) 238 where " Sum of Squares of Burst Durations " and "Number of 239 Bursts"is obtained from the RTCP XR Burst/Gap Discard Block. 241 3.2. Burst/Gap Discard Summary Statistics Block 243 The metrics described here are intended to be used as described in 244 this section, in conjunction with information from the Measurement 245 Identity block (which MUST be present in the same RTCP packet as the 246 Burst/Gap Discard block) and also with the metric "number of packets 247 discarded" provided in the RTCP XR Discard Block [DISCARD]. The RTCP 248 XR Discard Block SHOULD be sent if the Burst/Gap Discard block is 249 sent, but the converse does not apply. 251 3.2.1. Report Block Structure 253 0 1 2 3 254 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 255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 | BT=TBD |I| Rsv. | block length | 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | SSRC of Source | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 | Burst Discard Rate | Gap Discard Rate | 261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 263 3.2.2. Definition of Fields in Discard Summary Statistics Block 265 block type (BT): 8 bits 267 Burst/Gap Discard Summary Statistics Block is identified by the 268 constant . 270 reserved: 8 bits 272 This field is reserved for future definition. In the absence of 273 such a definition, the bits in this field MUST be set to zero and 274 MUST be ignored by the receiver. 276 Interval Metric flag (I): 1 bit 278 This field is used to indicate whether the metrics block is an 279 Interval or a Cumulative report, 281 reserved: 7 bits 283 This field is reserved for future definition. In the absence of 284 such a definition, the bits in this field MUST be set to zero and 285 MUST be ignored by the receiver. 287 block length: 16 bits 289 The constant 3, in accordance with the definition of this field in 290 Section 3 of RFC 3611 [RFC3611]. 292 SSRC of source: 32 bits 294 As defined in Section 4.1 of RFC3611 [RFC3611]. 296 Burst Discard Rate: 16 bits 298 The fraction of packets discarded during bursts since the 299 beginning of reception, expressed as a fixed point number with the 300 binary point at the left edge of the field. This value is 301 calculated by dividing Packets Discarded in Bursts by Total 302 Packets expected in Bursts as follows: 304 Packets Discarded in Bursts / Total Packets expected in Bursts 306 Gap Discard Rate: 16 bits 308 The fraction of packets discarded during gaps since the beginning 309 of reception expressed as a fixed point number with the binary 310 point at the left edge of the field. This value is calculated by 311 dividing the difference between number of packets discarded and 312 Packets Discarded in Bursts by the difference between Packets 313 Expected and Total Packets expected in Bursts as follows: 315 (number of packets discarded - Packets Discarded in Bursts) / 316 (Packets Expected - Total Packets expected in Bursts) 318 where "number of packets discarded" is obtained from the RTCP XR 319 Discard Block [DISCARD] and Packets Expected is calculated as the 320 difference between "extended last sequence number" and "extended 321 first sequence number" (Interval or Cumulative) provided in the 322 Measurement Information block [MEASIDENT]. 324 4. Application Layer Metrics 325 4.1. Application Layer Loss/Duplication Statistics Summary Block 327 This block reports statistics beyond the information carried in the 328 Statistics Summary Report Block RTCP packet specified in the section 329 4.6 of RFC 3611 [RFC3611]. Information is recorded about lost frames 330 ,duplicated frames, lost partial frames. Such information can be 331 useful for network management and video quality monitoring. 333 4.1.1. Report Block Structure 335 0 1 2 3 336 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 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | BT=TBD | |T|P| rsv. | block length | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | SSRC of Source | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | begin_seq | end_seq | 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | Number of frames expected | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | lost_full_frames | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | dup_frames | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | lost_partial_frames | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 4.1.2. Definition of Fields in Loss/Duplication Summary Statistics 354 Block 356 Block type (BT): 8 bits 358 Application Layer Loss/Duplication Statistics Summary Bloc is 359 identified by the constant . 361 Picture type indicator (T): 1 bit 363 Picture types used in the different video algorithms compose of 364 key-frame and derivation frame. This field is used to indicate 365 the frame type to be reported. Bits set to 0 if the lost_frames 366 field or dup_frames field contain a key_frame report or reference 367 frame report, 1 if the lost_frames field and dup_frames field 368 contain other derivation frame report. 370 P: 1 bit 372 Bit set to 1 if the partial_lost_frames field or the partial_dup_ 373 frames field contains a report, 0 otherwise. 375 Rsv.: 6 bits 377 This field is reserved for future definition. In the absence of 378 such a definition, the bits in this field MUST be set to zero and 379 MUST be ignored by the receiver. 381 Block length: 16 bits 383 The constant 6, in accordance with the definition of this field in 384 Section 3 of RFC 3611 [RFC3611]. 386 SSRC of source: 32 bits 388 As defined in Section 4.1 of RFC3611 [RFC3611]. 390 begin_seq: 16 bits 392 As defined in Section 4.1 of RFC 3611 [RFC3611]. 394 end_seq: 16 bits 396 As defined in Section 4.1 of RFC 3611 [RFC3611]. 398 number of frames expected:32bits 400 A count of the number of frames expected, estimated if necessary. 401 If no frames have been received then this count shall be set to 402 Zero. 404 lost_full_frames: 32 bits 406 If one frame is completely lost, this frame is regarded as one 407 lost full_frame. The lost_full_frames is equivalent to the number 408 of lost_full_frames in the above sequence number interval. 410 dup_frames: 32 bits 412 Number of dup_frames in the above sequence number interval. 414 lost_partial_frames: 32 bits 416 If one frame is partially lost, this frame is regarded as one lost 417 fractional frame. The lost_partial_frames is equivalent to the 418 number of lost_partial_frames in the above sequence number 419 interval. 421 5. SDP Signaling 423 [RFC3611] defines the use of SDP (Session Description Protocol) 424 [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used 425 without prior signaling. 427 This section augments the SDP [RFC4566] attribute "rtcp-xr" defined 428 in [RFC3611] by providing three additional value of "xr-format" to 429 signal the use of the report block defined in this document. 431 rtcp-xr-attrib = "a=rtcp-xr:" 432 [xr-format *(SP xr-format)] CRLF 433 xr-format = 434 / burst-gap-loss-stat 435 / burst-gap-discard-stat 436 / application-loss-dup-stat 438 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 439 and the full syntax of the "rtcp-xr" attribute. 441 6. IANA Considerations 443 New block types for RTCP XR are subject to IANA registration. For 444 general guidelines on IANA considerations for RTCP XR, refer 445 to[RFC3611] . 447 6.1. New RTCP XR Block Type values 449 This document assigns three new block type value in the RTCP XR Block 450 Type Registry: 452 Name: BGLSS 453 Long Name: Burst/Gap Loss Summsary Statistics Block 454 Value 455 Reference: Section 5.1 457 Name: BGDSS 458 Long Name: Burst/Gap Discard Summary Statistics Block 459 Value 460 Reference: Section 5.2 462 Name: ALDSS 463 Long Name: Application Layer Loss/Duplication Statistics Summary 464 Value 465 Reference: Section 6.1 467 6.2. New RTCP XR SDP Parameters 469 This document also registers three new SDP [RFC4566] parameters for 470 the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 472 * " burst-gap-loss-stat " 473 * " burst-gap-discard-stat " 474 * "application-loss-dup-stat " 476 6.3. Contact information for registrations 478 The contact information for the registrations is: 480 Glen Zorn 481 Network Zen 482 227/358 Thanon Sanphawut 483 Bang Na, Bangkok 10110 484 Thailand 486 7. Security Considerations 488 The new RTCP XR report blocks proposed in this document introduces no 489 new security considerations beyond those described in [RFC3611]. 491 8. Acknowledgements 493 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 494 Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and Yinliang 495 Hu for their valuable comments and suggestions on this document. 497 9. References 499 9.1. Normative References 501 [DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric 502 Reporting", ID draft-ietf-rtcp-xr-discard-02, May 2009. 504 [I-D.ietf-avt-rtp-svc] 505 Wenger, S., Wang, Y., Schierl, T., and A. Eleftheriadis, 506 "RTP Payload Format for Scalable Video Coding", 507 draft-ietf-avt-rtp-svc-27 (work in progress), 508 February 2011. 510 [MEASIDENT] 511 Wu, Q., "Measurement Identity and information Reporting 512 using SDES item and XR Block", 513 ID draft-ietf-xrblock-rtcp-xr-meas-identity-01, 514 October 2011. 516 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 517 Requirement Levels", BCP 14, RFC 2119, March 1997. 519 [RFC2250] Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar, 520 "RTP Payload Format for MPEG1/MPEG2 Video", RFC 2250, 521 January 1998. 523 [RFC3357] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample 524 Metrics", RFC 3357, August 2002. 526 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 527 Jacobson, "RTP: A Transport Protocol for Real-Time 528 Applications", STD 64, RFC 3550, July 2003. 530 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 531 Protocol Extended Reports (RTCP XR)", RFC 3611, 532 November 2003. 534 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 535 Description Protocol", RFC 4566, July 2006. 537 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 538 Specifications: ABNF", STD 68, RFC 5234, January 2008. 540 9.2. Informative References 542 [DSLF] Rahrer, T., Ed., Fiandra, Ed., and Wright, Ed., "Triple- 543 play Services Quality of Experience (QoE) Requirements", 544 DSL Forum Technical Report TR-126, December 2006. 546 [MONARCH] Wu, Q., "Monitoring Architectures for RTP", 547 ID draft-ietf-avtcore-monarch-00, April 2011. 549 [PMOL] Clark, A., "Framework for Performance Metric Development", 550 ID draft-ietf-pmol-metrics-framework-08, 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