draft-ietf-xrblock-rtcp-xr-summary-stat-04.txt   draft-ietf-xrblock-rtcp-xr-summary-stat-05.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track R. Schott Intended status: Standards Track R. Schott
Expires: June 17, 2013 Deutsche Telekom Expires: June 22, 2013 Deutsche Telekom
Q. Wu Q. Wu
R. Huang R. Huang
Huawei Huawei
December 14, 2012 December 19, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary
Statistics Metrics Reporting Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-summary-stat-04 draft-ietf-xrblock-rtcp-xr-summary-stat-05
Abstract Abstract
This document defines three RTP Control Protcol (RTCP) Extended This document defines three RTP Control Protocol (RTCP) Extended
Report (XR) Blocks that allow the reporting of loss, duplication and Report (XR) Blocks that allow the reporting of loss, duplication and
discard summary statistics metrics in a range of RTP applications. discard summary statistics metrics in a range of RTP applications.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 17, 2013. This Internet-Draft will expire on June 22, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 24 skipping to change at page 2, line 24
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Transport Related End System Metrics . . . . . . . . . . . . . 4 3. Transport Related End System Metrics . . . . . . . . . . . . . 4
3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 4 3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 4
3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 5 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 5
3.1.2. Definition of Fields in Loss Summary Statistics 3.1.2. Definition of Fields in Loss Summary Statistics
Block . . . . . . . . . . . . . . . . . . . . . . . . 5 Block . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7 3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7
3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7
3.2.2. Definition of Fields inBurst/Gap Discard Summary 3.2.2. Definition of Fields in Burst/Gap Discard Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 8 Statistics Block . . . . . . . . . . . . . . . . . . . 8
4. Application Level Metrics . . . . . . . . . . . . . . . . . . 9 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 9
4.1. Frame Impairment Statistics Summary Metrics Block . . . . 9 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 9
4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10
4.1.2. Definition of Fields in Frame Impairment Summary 4.1.2. Definition of Fields in Frame Impairment Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 10 Statistics Block . . . . . . . . . . . . . . . . . . . 10
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 12 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 12
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13
6.3. Contact information for registrations . . . . . . . . . . 13 6.3. Contact information for registrations . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-04 . . . . . . . . 15 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
1.1. Summary Statistics Metrics 1.1. Summary Statistics Metrics
This draft defines three new block types to augment those defined in This draft defines three new block types to augment those defined in
[RFC3611] for use in a range of RTP applications. [RFC3611] for use in a range of RTP applications.
The first two block types support the reporting of burst gap loss/ The first two block types support the reporting of burst gap loss/
discard summary statistics including packet loss/discard proportion, discard summary statistics including packet loss/discard proportion,
mean and variance and belong to the class of transport-related end mean and variance and belong to the class of transport-related end
system metrics defined in [RFC6792]. These two blocks are intended system metrics defined in [RFC6792]. These two blocks are intended
to be used in conjunction with information from the Burst Gap Loss to be used in conjunction with information from the Burst Gap Loss
metric block or Burst Gap Discard metric block, and on which these Metrics Block or Burst Gap Discard Metrics Block, and on which these
two block therefore depend. The metrics in the Burst Gap Loss block two block therefore depend. The metrics in the Burst Gap Loss block
or Burst Gap Discard metric block can be used independently of the or Burst Gap Discard Metrics Block can be used independently of the
metrics defined in the first two blocks, however. metrics defined in the first two blocks.
The third block supports the reporting of detailed statistics for The third block supports the reporting of detailed statistics for
each frame type, including the number of frames received, lost and each frame type, including the number of frames received, lost and
discarded of each frame type in the Group of Pictures (GOP) and discarded of each frame type in the Group of Pictures (GOP) and
additional data allowing the calculation of statistical parameters additional data allowing the calculation of statistical parameters
(e.g.,the proportion of each frame type impaired by packet loss and (e.g.,the proportion of each frame type impaired by packet loss and
discard). The metrics defined in this block belong to the class of discard). The metrics defined in this block belong to the class of
application layer metrics defined in [RFC6792]. application layer metrics defined in [RFC6792].
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
skipping to change at page 4, line 35 skipping to change at page 4, line 35
3.1. Burst/Gap Loss Summary Statistics Metrics Block 3.1. Burst/Gap Loss Summary Statistics Metrics Block
The metrics described here are intended to be used as described in The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement this section, in conjunction with information from the Measurement
Information block [RFC6776] (which MUST be present in the same RTCP Information block [RFC6776] (which MUST be present in the same RTCP
packet as the Burst/Gap Loss block) and also with the metric packet as the Burst/Gap Loss block) and also with the metric
"cumulative number of packets lost" provided in standard RTCP "cumulative number of packets lost" provided in standard RTCP
[RFC3550]. Instances of this Metrics Block refer by Synchronization [RFC3550]. Instances of this Metrics Block refer by Synchronization
source (SSRC) to the separate auxiliary Measurement Information block source (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which contains measurement periods (see [RFC6776] section [RFC6776] which describes measurement periods in use (see [RFC6776]
4.2). This metrics block relies on the measurement period in the section 4.2). This Metrics Block relies on the measurement period in
Measurement Information block indicating the span of the report and the Measurement Information block indicating the span of the report
SHOULD be sent in the same compound RTCP packet as the measurement and SHOULD be sent in the same compound RTCP packet as the
information block. If the measurement period is not received in the measurement information block. If the measurement period is not
same compound RTCP packet as this metric block, this metrics block received in the same compound RTCP packet as this Metrics Block, this
MUST be discarded. metrics block MUST be discarded.
The metrics carried in this metrics block provide information The metrics carried in this Metrics Block provide information
relevant to statistical parameters, including burst loss rate, gap relevant to statistical parameters, including burst loss rate, gap
loss rate, burst duration mean, burst duration variance and are loss rate, burst duration mean, burst duration variance and are
calculated at the receiving end of the RTP stream using burst gap calculated at the receiving end of the RTP stream using burst gap
loss metrics defined in [BGLOSS] and other information which is sent loss metrics defined in [BGLOSS] and other information which is sent
together with this report block. together with this report block.
3.1.1. Report Block Structure 3.1.1. Report Block Structure
0 1 2 3 0 1 2 3
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 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
skipping to change at page 7, line 31 skipping to change at page 7, line 31
packet as the Burst/Gap Discard Summary Statistics block) . packet as the Burst/Gap Discard Summary Statistics block) .
These metrics provide information relevant to statistical parameters, These metrics provide information relevant to statistical parameters,
including burst discard rate, gap discard rate and are calculated at including burst discard rate, gap discard rate and are calculated at
the receiving end of the RTP stream using burst gap discard metrics the receiving end of the RTP stream using burst gap discard metrics
defined in [BGDISCARD] and other information which is sent together defined in [BGDISCARD] and other information which is sent together
with this report block. with this report block.
Instances of this Metrics Block refer by Synchronization source Instances of this Metrics Block refer by Synchronization source
(SSRC) to the separate auxiliary Measurement Information block (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which contains measurement periods (see [RFC6776] section [RFC6776] which describes measurement periods in use (see [RFC6776]
4.2). This metrics block relies on the measurement period in the section 4.2). This metrics block relies on the measurement period in
Measurement Information block indicating the span of the report and the Measurement Information block indicating the span of the report
SHOULD be sent in the same compound RTCP packet as the measurement and SHOULD be sent in the same compound RTCP packet as the
information block. If the measurement period is not received in the measurement information block. If the measurement period is not
same compound RTCP packet as this metric block, this metrics block received in the same compound RTCP packet as this Metrics Block, this
MUST be discarded. Metrics Block MUST be discarded.
3.2.1. Report Block Structure 3.2.1. Report Block Structure
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=BGDSS | I | Reserved | block length | | BT=BGDSS | I | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Discard Rate | Gap Discard Rate | | Burst Discard Rate | Gap Discard Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2.2. Definition of Fields inBurst/Gap Discard Summary Statistics 3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics
Block Block
Block Type (BT): 8 bits Block Type (BT): 8 bits
Burst/Gap Discard Summary Statistics Block is identified by the Burst/Gap Discard Summary Statistics Block is identified by the
constant <BGDSS>. constant <BGDSS>.
Interval Metric Flag (I): 2 bits Interval Metric Flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Discard This field is used to indicate whether the Burst/Gap Discard
skipping to change at page 9, line 28 skipping to change at page 9, line 28
where "number of packets discarded" is obtained from the RTCP XR where "number of packets discarded" is obtained from the RTCP XR
Discard Count Block [DISCARD] and filled with the sum of packets Discard Count Block [DISCARD] and filled with the sum of packets
discarded due to early arrival (DT=1) and packets discarded due to discarded due to early arrival (DT=1) and packets discarded due to
late arrival(DT=2) and Packets Expected is calculated as the late arrival(DT=2) and Packets Expected is calculated as the
difference between "extended last sequence number" and "extended difference between "extended last sequence number" and "extended
first sequence number" (Interval or Cumulative) provided in the first sequence number" (Interval or Cumulative) provided in the
Measurement Information block [RFC6776]. In order for the Burst/ Measurement Information block [RFC6776]. In order for the Burst/
Gap Discard Summary Statistics Block to be meaningful, 2 instances Gap Discard Summary Statistics Block to be meaningful, 2 instances
of the Discard Count block with DT=1 and DT=2 MUST be included in of the Discard Count block with DT=1 and DT=2 MUST be included in
the same RTCP compound packet as the Burst/Gap Discard Summary the same RTCP XR packet as the Burst/Gap Discard Summary
Statistics Block. Statistics Block.
4. Application Level Metrics 4. Application Level Metrics
4.1. Frame Impairment Statistics Summary Metrics Block 4.1. Frame Impairment Statistics Summary Metrics Block
This block reports statistics on which frame type were affected This block reports statistics on which frame type were affected
beyond the information carried in the Statistics Summary Report Block beyond the information carried in the Statistics Summary Report Block
RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611].
Information is measured at the receiving end of the RTP stream and Information is measured at the receiving end of the RTP stream and
recorded about thenumber of frames received, lost frames, duplicated recorded about the number of frames received, lost frames, duplicated
frames and lost partial frames. Such information can be useful for frames and lost partial frames. Such information can be useful for
network management and video quality monitoring. network management and video quality monitoring.
4.1.1. Report Block Structure 4.1.1. Report Block Structure
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=FISS |T| Reserved | block length | | BT=FISS |T| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 8 skipping to change at page 12, line 8
Number of partial frames lost (lost_partial_frames): 32 bits Number of partial frames lost (lost_partial_frames): 32 bits
If one frame is partially lost, this frame is regarded as one lost If one frame is partially lost, this frame is regarded as one lost
fractional frame. The value of the lost_partial_frames field is fractional frame. The value of the lost_partial_frames field is
equivalent to the number of partial frames lost in the above equivalent to the number of partial frames lost in the above
sequence number interval. sequence number interval.
5. SDP Signaling 5. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) RFC 3611 defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. However XR blocks MAY
without prior signaling. be used without prior signaling (see section 5 of RFC3611).
5.1. SDP rtcp-xr-attrib Attribute Extension 5.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in Section 5.1 of RFC 3611 by providing three additional values of in Section 5.1 of RFC 3611 by providing three additional values of
"xr-format" to signal the use of the report block defined in this "xr-format" to signal the use of the report block defined in this
document. document.
xr-format = / burst-gap-loss-stat xr-format = / burst-gap-loss-stat
/ burst-gap-discard-stat / burst-gap-discard-stat
/ frame-impairment-stat / frame-impairment-stat
Burst-gap-loss-stat ="burst gap loss summary statistics" Burst-gap-loss-stat ="burst gap loss summary statistics"
Burst-gap-discard-stat="burst gap discard summary statistics" Burst-gap-discard-stat="burst gap discard summary statistics"
Frame-impairment-stat="frame impairment summary statistics" Frame-impairment-stat="frame impairment summary statistics"
5.2. Offer/Answer Usage 5.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameter, refer to section 5.2 of [RFC3611].
6. IANA Considerations 6. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to RFC general guidelines on IANA considerations for RTCP XR, refer to RFC
3611. 3611.
6.1. New RTCP XR Block Type values 6.1. New RTCP XR Block Type values
This document assigns three new block type value in the RTCP XR Block This document assigns three new block type value in the "RTP Control
Type Registry: Protocol (RTCP) Extended Report (XR) Block Type Registry" :
Name: BGLSS Name: BGLSS
Long Name: Burst/Gap Loss Summary Statistics Block Long Name: Burst/Gap Loss Summary Statistics Block
Value <BGLSS> Value <BGLSS>
Reference: Section 3.1 Reference: Section 3.1
Name: BGDSS Name: BGDSS
Long Name: Burst/Gap Discard Summary Statistics Block Long Name: Burst/Gap Discard Summary Statistics Block
Value <BGDSS> Value <BGDSS>
Reference: Section 3.2 Reference: Section 3.2
Name: FISS Name: FISS
Long Name: Frame Impairment Statistics Summary Long Name: Frame Impairment Statistics Summary
Value <FISS> Value <FISS>
Reference: Section 4.1 Reference: Section 4.1
6.2. New RTCP XR SDP Parameters 6.2. New RTCP XR SDP Parameters
This document also registers three new SDP [RFC4566] parameters for This document also registers three new SDP [RFC4566] parameters for
the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended
Report (XR) SDP Parameters Registry ":
* " burst-gap-loss-stat " * " burst-gap-loss-stat "
* " burst-gap-discard-stat " * " burst-gap-discard-stat "
* " frame-impairment-stat " * " frame-impairment-stat "
6.3. Contact information for registrations 6.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com) Qin Wu (sunseawq@huawei.com)
skipping to change at page 14, line 41 skipping to change at page 14, line 41
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003. November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709,
September 2012.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012. using SDES item and XR Block", RFC 6776, August 2012.
9.2. Informative References 9.2. Informative References
[RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures
for RTP", RFC 6792, November 2012. for RTP", RFC 6792, November 2012.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-04 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-05
The following are the major changes compared to 03: The following are the major changes compared to 04:
o Editorial changes to get in line with Delay and Burst Gap related o Editorial changes to get in line with Delay and Burst Gap related
drafts. drafts.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) Glen Zorn (editor)
Network Zen Network Zen
227/358 Thanon Sanphawut 227/358 Thanon Sanphawut
Bang Na, Bangkok 10260 Bang Na, Bangkok 10260
Thailand Thailand
 End of changes. 22 change blocks. 
37 lines changed or deleted 42 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/