idnits 2.17.1 draft-zorn-xrblock-rtcp-xr-al-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 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 (May 16, 2011) is 4729 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 527, but no explicit reference was found in the text == Unused Reference: 'RFC2250' is defined on line 536, but no explicit reference was found in the text == Unused Reference: 'RFC3550' is defined on line 543, but no explicit reference was found in the text == Unused Reference: 'RFC6051' is defined on line 557, but no explicit reference was found in the text == Unused Reference: 'PMOL' is defined on line 574, but no explicit reference was found in the text ** 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 (~~), 9 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: November 17, 2011 Deutsche Telekom 6 Q. Wu 7 R. Huang 8 Huawei 9 May 16, 2011 11 RTCP XR for Application Layer Statistics Metrics Reporting 12 draft-zorn-xrblock-rtcp-xr-al-stat-00 14 Abstract 16 This document defines an RTCP XR Report Block and associated SDP 17 parameters that allows the reporting of application layer summary, 18 loss discard and burst metrics for use in a range of RTP 19 applications. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on November 17, 2011. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 70 3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3 71 4. Application Layer Metrics . . . . . . . . . . . . . . . . . . 3 72 4.1. Application Layer Statistics Summary Report Block . . . . 4 73 4.2. Application Layer Loss and Discard Metrics Block . . . . . 6 74 4.3. Application Layer Burst Metrics Block . . . . . . . . . . 8 75 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 78 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 79 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 80 9.1. Normative References . . . . . . . . . . . . . . . . . . . 12 81 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 82 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 85 1. Introduction 87 RFC 3611 [RFC3611] defines seven report block formats for network 88 management and quality monitoring. However, some of these metrics 89 are mostly for multicast inference of network characteristics (MINC) 90 or voice over IP (VoIP) monitoring and not widely applicable to other 91 applications, e.g., video quality monitoring. This document focuses 92 on specifying new additional report block types used to convey video 93 related parameters at application layer that are genericly designed 94 for use in voice, audio and video services. 96 The metrics belong to the class of transport level metrics defined in 97 [MONARCH] (work in progress). 99 2. Terminology 101 2.1. Standards Language 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119 [RFC2119]. 107 In addition, the following terms are defined: 109 Picture Type 111 Picture types used in the different video algorithms compose of 112 the key-frame and the Derivation frame. Key-frame is also called 113 a reference frame and used as a reference for predicting other 114 pictures. It is coded without prediction from other pictures. 115 The Derivation frame is derived from Key-frame using prediction 116 from the reference frame. 118 3. Applicability 120 The Metric Block defined in this document can be applied to any real 121 time applications that convey video related parameters at application 122 layer. 124 4. Application Layer Metrics 125 4.1. Application Layer Statistics Summary Report Block 127 This block reports statistics beyond the information carried in the 128 Statistics Summary Report Block RTCP packet specified in the section 129 4.6 of RFC 3611 [RFC3611]. Information is recorded about lost frame 130 packets, duplicated frame packets, lost layered component packets, 131 duplicated layered component packets. Such information can be useful 132 for network management and video quality monitoring. 134 The report block contents are dependent upon a series of flag bits 135 carried in the first part of the header. Not all parameters need to 136 be reported in each block. Flags indicate which parameters are 137 reported and which are not. The fields corresponding to unreported 138 parameters MUST be present, but are set to zero. The receiver MUST 139 ignore any Video Statistics Summary Report Block with a non-zero 140 value in any field flagged as unreported. 142 The Application Layer Statistics Summary Report Block has the 143 following format: 145 0 1 2 3 146 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 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 148 | BT=TBD |I| tag |T|P|rsd| block length | 149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 150 | begin_seq | end_seq | 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | lost_frames | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | dup frames | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | partial_lost_frames | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | partial_dup_frames | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | key frames impairement proportion | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 Block type (BT): 8 bits 165 The Application Layer Statistics Summary Report Block is 166 identified by the 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 Measurement Identifier association (tag): 3 bits 175 This field is used to identify the Measurement Identifier block 176 [MEASIDENT] which describes this measurement. 178 Picture type indicator (T): 1 bits 180 Picture types used in the different video algorithms compose of 181 key-frame and derivation frame. This field is used to indicate 182 the frame type to be reported. Bits set to 0 if the lost_frames 183 field or dup_frames field contain a key_frame report or reference 184 frame report, 1 if the lost_frames field and dup_frames field 185 contain other derivation frame report. 187 P: 1 bit 189 Bit set to 1 if the partial_lost_frames field or the partial_dup_ 190 frames field contains a report, 0 otherwise. 192 Rsd.: 2 bits 194 This field is reserved for future definition. In the absence of 195 such a definition, the bits in this field MUST be set to zero and 196 MUST be ignored by the receiver. 198 Block length: 16 bits 200 The constant 5, in accordance with the definition of this field in 201 Section 3 of RFC 3611 [RFC3611]. 203 begin_seq: 16 bits 205 As defined in Section 4.1 of RFC 3611 [RFC3611]. 207 end_seq: 16 bits 209 As defined in Section 4.1 of RFC 3611 [RFC3611]. 211 lost_frames: 32 bits 213 Number of lost_frames in the above sequence number interval. 215 dup_frames: 32 bits 217 Number of dup_frames in the above sequence number interval. 219 partial lost_frames: 32 bits 221 Number of partial lost_frames in the above sequence number 222 interval. 224 partial dup_frames: 32 bits 226 Number of partial_dup_frames in the above sequence number 227 interval. 229 key frames impairment proportion:32bits 231 The proportion of key frame impaired by packet loss,discard and 232 duplication. 234 4.2. Application Layer Loss and Discard Metrics Block 236 This block reports Loss and Discard metrics statistics beyond the 237 information carried in the standard RTCP packet format. The block 238 reports separately on packets lost on the IP channel, and those that 239 have been received but then discarded by the receiving jitter buffer. 241 It is very useful to distinguish between packets lost by the network 242 and those discarded due to jitter. Both have equal effect on the 243 quality of the video stream, however, having separate counts helps 244 identify the source of quality degradation. These fields MUST be 245 populated, and MUST be set to zero if no packets have been received. 247 Implementations MUST provide values for all the fields defined here. 248 For certain metrics, if the value is undefined or unknown, then the 249 specified default or unknown field value MUST be provided. 251 The block is encoded as six 32-bit words: 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| tag |T| rsv.| block length | 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | Loss rate | Discard rate | 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 block type (BT): 8 bits 263 A Application Layer Metrics Report Block is identified by the 264 constant . 266 Interval Metric flag (I): 1 bit 268 This field is used to indicate whether the metrics block is an 269 Interval or a Cumulative report, 271 Measurement Identifier association (tag): 3 bits 273 This field is used to identify the Measurement Identifier block 274 [MEASIDENT] which describes this measurement. 276 Picture type indicator (T): 1 bits 278 Picture types used in the different video algorithms compose of 279 key-frame and derivation frame. This field is used to indicate 280 the picture type to be reported. Bits set to 0 if the Loss rate 281 field and discard rate field contain a Key_frame report or 282 reference frame report, 1 if the Loss rate field and discard rate 283 field contain other derivation frame reports. 285 reserved: 3 bits 287 This field is reserved for future definition. In the absence of 288 such a definition, the bits in this field MUST be set to zero and 289 MUST be ignored by the receiver. 291 block length: 16 bits 293 The constant 1, in accordance with the definition of this field in 294 Section 3 of RFC 3611 [RFC3611]. 296 Loss rate: 8 bits 298 The fraction of RTP data packets from the source lost 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 the total number of lost packets containing 302 specified frame (e.g., Key frame) (after the effects of applying 303 any error protection such as FEC) by the total number of packets 304 expected, multiplying the result of the division by 256, limiting 305 the maximum value to 255 (to avoid overflow), and taking the 306 integer part. The numbers of duplicated packets and discarded 307 packets do not enter into this calculation. Since receivers 308 cannot be required to maintain unlimited buffers, a receiver MAY 309 categorize late-arriving packets as lost. The degree of lateness 310 that triggers a loss SHOULD be significantly greater than that 311 which triggers a discard. 313 Discard rate: 8 bits 315 The fraction of RTP data packets from the source that have been 316 discarded since the beginning of reception, due to late or early 317 arrival, under-run or overflow at the receiving jitter buffer. 318 This value is expressed as a fixed point number with the binary 319 point at the left edge of the field. It is calculated by dividing 320 the total number of discarded packets containing specified frame 321 (e.g., Key Frame) (excluding duplicate packet discards) by the 322 total number of packets expected, multiplying the result of the 323 division by 256, limiting the maximum value to 255 (to avoid 324 overflow), and taking the integer part. 326 4.3. Application Layer Burst Metrics Block 328 This block reports Burst metrics statistics beyond the information 329 carried in the standard RTCP packet format. It reports on the 330 combined effect of losses and discards, as both have equal effect on 331 video quality. 333 In order to properly assess the quality of a video stream, it is 334 desirable to consider the degree of burstiness of packet loss RFC 335 3357 [RFC3357]. Following the one-way loss pattern sample metrics 336 discussed in [RFC3357], a measure of the spacing between consecutive 337 network packet loss or error events, is a "loss distance". The loss 338 distance metric captures the spacing between the loss periods. The 339 duration of a loss or error event (e.g. and how many packets are lost 340 in that duration) is a "loss period", the loss period metric captures 341 the frequency and length (burstiness) of loss once it starts. Delay 342 reports include the transit delay between RTP end points and the end 343 system processing delays, both of which contribute to the user 344 perceived delay. 346 Implementations MUST provide values for all the fields defined here. 347 For certain metrics, if the value is undefined or unknown, then the 348 specified default or unknown field value MUST be provided. 350 The block is encoded as three 32-bit words: 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=TBD |I| tag | Rsv. | block length | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 | Loss Distance | Loss Period | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | Max Loss Duration | Reserved. | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 362 block type (BT): 8 bits 364 Appliation Layer Metrics Report Block is identified by the 365 constant . 367 reserved: 8 bits 369 This field is reserved for future definition. In the absence of 370 such a definition, the bits in this field MUST be set to zero and 371 MUST be ignored by the receiver. 373 Interval Metric flag (I): 1 bit 375 This field is used to indicate whether the metrics block is an 376 Interval or a Cumulative report, 378 Measurement Identifier association (tag): 3 bits 380 This field is used to identify the Measurement Identifier block 381 [MEASIDENT] which describes this measurement. 383 reserved: 4 bits 385 This field is reserved for future definition. In the absence of 386 such a definition, the bits in this field MUST be set to zero and 387 MUST be ignored by the receiver. 389 block length: 16 bits 391 The constant 2, in accordance with the definition of this field in 392 Section 3 of RFC 3611 [RFC3611]. 394 Loss Distance: 16 bits 396 The mean duration, expressed in milliseconds, of the loss 397 intervals that have occurred since the beginning of reception 398 [DSLF]. The duration of each loss distance is calculated based 399 upon the frames that mark the beginning and end of that period. 400 It is equal to the timestamp of the end frame, plus the duration 401 of the end frame, minus the timestamp of the beginning frame. If 402 the actual values are not available, estimated values MUST be 403 used. If there have been no burst periods, the burst duration 404 value MUST be zero. 406 Loss Period: 16 bits 408 The mean duration, expressed in milliseconds, of the burst loss 409 periods that have occurred since the beginning of reception 410 [DSLF]. The duration of each period is calculated based upon the 411 frame that marks the end of the prior burst loss and the frame 412 that marks the beginning of the subsequent burst loss. It is 413 equal to the timestamp of the subsequent burst frame, minus the 414 timestamp of the prior burst packet, plus the duration of the 415 prior burst packet. If the actual values are not available, 416 estimated values MUST be used. In the case of a gap that occurs 417 at the beginning of reception, the sum of the timestamp of the 418 prior burst packet and the duration of the prior burst packet are 419 replaced by the reception start time. In the case of a gap that 420 occurs at the end of reception, the timestamp of the subsequent 421 burst packet is replaced by the reception end time. If there have 422 been no gap periods, the gap duration value MUST be zero. 424 Max Loss Duration of a single error: 16 bits 426 The maximum loss duration, expressed in milliseconds, of the loss 427 periods that have occurred since the beginning of reception. The 428 recommended max loss duration is specified as less than 16 ms in 429 [DSLF], which provides a balance between interleaver depth 430 protection from xDSL errors induced by impulse noise, delay added 431 to other applications and video service QoE requirements to reduce 432 visible impairments. 434 Reserved: 16 bits 436 All bits SHALL be set to 0 by the sender and SHALL be ignored on 437 reception. 439 block length: 16 bits 441 The constant 2, in accordance with the definition of this field in 442 Section 3 of RFC 3611 [RFC3611]. 444 5. SDP Signaling 446 Three new parameter is defined for the six report blocks defined in 447 this document to be used with Session Description Protocol (SDP) 448 [RFC4566] using the Augmented Backus-Naur Form (ABNF) [RFC5234]. 449 They have the following syntax within the "rtcp-xr" attribute 450 [RFC3611]: 452 rtcp-xr-attrib = "a=rtcp-xr:" 453 [xr-format *(SP xr-format)] CRLF 454 xr-format = 455 / application-loss-metrics 456 / application-burst-metrics 457 / application-stat-summary 459 application-burst-metrics = " application-burst-metrics" 460 ["=" max-size] 461 max-size = 1*DIGIT ; maximum block size in octets 463 application--loss-metrics = " application-loss-metrics" 464 ["=" stat-flag *("," stat-flag)] 465 stat-flag = "key Frame loss and duplication" 466 / "derivation Frame loss and duplication" 468 application-stat-summary = "application-stat-summary" 469 ["=" stat-flag *("," stat-flag)] 470 stat-flag = "key Frame loss and duplication" 471 / "derivation Frame loss and duplication" 473 Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description 474 and the full syntax of the "rtcp-xr" attribute. 476 6. IANA Considerations 478 New report block types for RTCP XR are subject to IANA registration. 479 For general guidelines on IANA allocations for RTCP XR, refer to 480 Section 6.2 of [RFC3611]. 482 This document assigns three new block type value in the RTCP XR Block 483 Type Registry: 485 Name: ALSS 486 Long Name: Application Layer Statistics Summary 487 Value 488 Reference: Section 4.1 490 Name: ALLDM 491 Long Name: Application Layer Loss and Discard Metrics 492 Value 493 Reference: Section 4.2 494 Name: ALBM 495 Long Name: Application Layer Burst Metrics 496 Value 497 Reference: Section 4.3 498 This document also registers three new SDP [RFC4566] parameters for 499 the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: 501 * "application-layer-loss-metrics" 502 * "application-layer -burst-metrics" 503 * "application-layer -stat-summary" 505 The contact information for the registrations is: 507 Qin Wu 508 sunseawq@huawei.com 509 101 Software Avenue, Yuhua District 510 Nanjing, JiangSu 210012 China 512 7. Security Considerations 514 The new RTCP XR report blocks proposed in this document introduces no 515 new security considerations beyond those described in [RFC3611]. 517 8. Acknowledgements 519 The authors would like to thank Bill Ver Steeg, David R Oran, Ali 520 Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and Yinliang 521 Hu for their valuable comments and suggestions on this document. 523 9. References 525 9.1. Normative References 527 [I-D.ietf-avt-rtp-svc] 528 Wenger, S., Wang, Y., Schierl, T., and A. Eleftheriadis, 529 "RTP Payload Format for Scalable Video Coding", 530 draft-ietf-avt-rtp-svc-27 (work in progress), 531 February 2011. 533 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 534 Requirement Levels", BCP 14, RFC 2119, March 1997. 536 [RFC2250] Hoffman, D., Fernando, G., Goyal, V., and M. Civanlar, 537 "RTP Payload Format for MPEG1/MPEG2 Video", RFC 2250, 538 January 1998. 540 [RFC3357] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample 541 Metrics", RFC 3357, August 2002. 543 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 544 Jacobson, "RTP: A Transport Protocol for Real-Time 545 Applications", STD 64, RFC 3550, July 2003. 547 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control 548 Protocol Extended Reports (RTCP XR)", RFC 3611, 549 November 2003. 551 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 552 Description Protocol", RFC 4566, July 2006. 554 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 555 Specifications: ABNF", STD 68, RFC 5234, January 2008. 557 [RFC6051] Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP 558 Flows", RFC 6051, November 2010. 560 9.2. Informative References 562 [DSLF] Rahrer, T., Ed., Fiandra, Ed., and Wright, Ed., "Triple- 563 play Services Quality of Experience (QoE) Requirements", 564 DSL Forum Technical Report TR-126, December 2006. 566 [MEASIDENT] 567 Hunt, G. and A. Clark, "RTCP XR Measurement Identifier 568 Block", ID draft-ietf-avt-rtcp-xr-meas-identity-02, 569 May 2009. 571 [MONARCH] Wu, Q., "Monitoring Architectures for RTP", 572 ID draft-ietf-avtcore-monarch-00, April 2011. 574 [PMOL] Clark, A., "Framework for Performance Metric Development", 575 ID draft-ietf-pmol-metrics-framework-08, January 2011. 577 Appendix A. Change Log 579 This document is separated from 580 draft-wu-xrblock-rtcp-xr-quality-monitoring-01 with a few editorial 581 changes and focuses on application layer summary, loss, discard, and 582 burst metrics. 584 Authors' Addresses 586 Glen Zorn 587 Network Zen 588 77/440 Soi Phoomjit, Rama IV Road 589 Phra Khanong, Khlong Toie 590 Bangkok 10110 591 Thailand 593 Phone: +66 (0) 87 502 4274 594 Email: gwz@net-zen.net 596 Roland Schott 597 Deutsche Telekom 598 Deutsche-Telekom-Allee 7 599 Darmstadt 64295 600 Germany 602 Email: Roland.Schott@telekom.de 604 Qin Wu 605 Huawei 606 101 Software Avenue, Yuhua District 607 Nanjing, Jiangsu 210012 608 China 610 Email: sunseawq@huawei.com 612 Rachel Huang 613 Huawei 614 101 Software Avenue, Yuhua District 615 Nanjing 210012 616 China 618 Email: Rachel@huawei.com