draft-ietf-xrblock-rtcp-xr-delay-10.txt   draft-ietf-xrblock-rtcp-xr-delay-11.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track K. Gross Intended status: Standards Track K. Gross
Expires: April 11, 2013 AVA Networks Expires: May 20, 2013 AVA Networks
Q. Wu Q. Wu
Huawei Huawei
October 8, 2012 November 16, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay metric RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay metric
Reporting Reporting
draft-ietf-xrblock-rtcp-xr-delay-10.txt draft-ietf-xrblock-rtcp-xr-delay-11.txt
Abstract Abstract
This document defines an RTP Control Protocol(RTCP) Extended Report This document defines an RTP Control Protocol(RTCP) Extended Report
(XR) Block that allows the reporting of Delay metrics for use in a (XR) Block that allows the reporting of Delay metrics for use in a
range of Real-time Transport Protocol applications. range of Real-time Transport Protocol 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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 April 11, 2013. This Internet-Draft will expire on May 20, 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 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Packet Delay Metrics Block . . . . . . . . . . . . . . . . 3 1.1. Packet Delay Metrics Block . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
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. Delay Block . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Delay Block . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Delay Metrics Report Block . . . . 5 3.2. Definition of Fields in Delay Metrics Report Block . . . . 5
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
5.3. Contact information for registrations . . . . . . . . . . 9 5.3. Contact information for registrations . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-delay-10 . . . . . . . . . . . 14 A.1. draft-ietf-xrblock-rtcp-xr-delay-11 . . . . . . . . . . . 15
A.2. draft-ietf-xrblock-rtcp-xr-delay-09 . . . . . . . . . . . 14 A.2. draft-ietf-xrblock-rtcp-xr-delay-10 . . . . . . . . . . . 15
A.3. draft-ietf-xrblock-rtcp-xr-delay-08 . . . . . . . . . . . 14 A.3. draft-ietf-xrblock-rtcp-xr-delay-09 . . . . . . . . . . . 15
A.4. draft-ietf-xrblock-rtcp-xr-delay-07 . . . . . . . . . . . 14 A.4. draft-ietf-xrblock-rtcp-xr-delay-08 . . . . . . . . . . . 15
A.5. draft-ietf-xrblock-rtcp-xr-delay-06 . . . . . . . . . . . 14 A.5. draft-ietf-xrblock-rtcp-xr-delay-07 . . . . . . . . . . . 15
A.6. draft-ietf-xrblock-rtcp-xr-delay-05 . . . . . . . . . . . 14 A.6. draft-ietf-xrblock-rtcp-xr-delay-06 . . . . . . . . . . . 15
A.7. draft-ietf-xrblock-rtcp-xr-delay-04 . . . . . . . . . . . 15 A.7. draft-ietf-xrblock-rtcp-xr-delay-05 . . . . . . . . . . . 16
A.8. draft-ietf-xrblock-rtcp-xr-delay-03 . . . . . . . . . . . 15 A.8. draft-ietf-xrblock-rtcp-xr-delay-04 . . . . . . . . . . . 16
A.9. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 15 A.9. draft-ietf-xrblock-rtcp-xr-delay-03 . . . . . . . . . . . 16
A.10. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 15 A.10. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 16
A.11. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 15 A.11. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 A.12. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
1.1. Packet Delay Metrics Block 1.1. Packet Delay Metrics Block
This draft defines a new block type to augment those defined in This document defines a new block type to augment those defined in
[RFC3611] for use in a range of RTP applications. The new block type [RFC3611] for use in a range of RTP applications. The new block type
supports the reporting of the mean, minimum and maximum values of the supports the reporting of the mean, minimum and maximum values of the
network round-trip delay between RTP interfaces in peer RTP end network round-trip delay between RTP interfaces in peer RTP end
systems as measured, for example, using the RTCP method described in systems as measured, for example, using the RTCP method described in
[RFC3550]. It also supports reporting of the component of the round- [RFC3550]. It also supports reporting of the component of the round-
trip delay internal to the local RTP system. trip delay internal to the local RTP system.
The network metrics belong to the class of transport metrics defined The network metrics belong to the class of transport metrics defined
in [MONARCH]. in [MONARCH].
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This draft defines a new Extended Report block for use Report (XR). This document defines a new Extended Report block for
with[RFC3550] and [RFC3611]. use with[RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [MONARCH] provides guideline for reporting Monitoring Architectures [MONARCH] provides guideline for reporting
block format using RTCP XR. The Metrics Block described in this block format using RTCP XR. The Metrics Block described in this
document are in accordance with the guidelines in [RFC6390] and document are in accordance with the guidelines in [RFC6390] and
[MONARCH]. [MONARCH].
skipping to change at page 5, line 12 skipping to change at page 5, line 12
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Delay Block 3. Delay Block
Metrics in this block report on packet delay in the stream arriving Metrics in this block report on packet delay in the stream arriving
at the RTP system. The measurement of these metrics are made either at the RTP system. The measurement of these metrics are made either
at the receiving end of the RTP stream or at the sending end of the at the receiving end of the RTP stream or at the sending end of the
RTP stream. Instances of this Metrics Block refer by Synchronization RTP stream. 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
[MEASI] which contains measurement intervals. This metric block [RFC6776] which contains measurement periods (see RFC6776 section
relies on the measurement interval in the Measurement Information 4.2). This metric block relies on the measurement period in the
block indicating the span of the report and SHOULD be sent in the Measurement Information block indicating the span of the report and
same compound RTCP packet as the measurement information block. If SHOULD be sent in the same compound RTCP packet as the measurement
the measurement interval is not received in the same compound RTCP information block. If the measurement period is not received in the
packet as this metric block, this metric block MUST be discarded. same compound RTCP packet as this metric block, this metric block
MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
Delay metrics block Delay metrics block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NDEL | I | resv. | block length = 6 | | BT=NDEL | I | resv. | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 8 skipping to change at page 6, line 8
Block type (BT): 8 bits Block type (BT): 8 bits
A Delay Report Block is identified by the constant NDEL. A Delay Report Block is identified by the constant NDEL.
[Note to RFC Editor: please replace NDEL with the IANA provided [Note to RFC Editor: please replace NDEL with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Delay metrics are This field is used to indicate whether the Delay metrics are
Sampled, Interval or Cumulative metrics, that is, whether the Sampled, Interval or Cumulative metrics:
reported values applies to the most recent measurement interval
duration between successive metrics reports (I=10) (the Interval I=10: Interval Duration - the reported value applies to the
Duration) or to the accumulation period characteristic of most recent measurement interval duration between successive
cumulative measurements (I=11) (the Cumulative Duration) or is a metrics reports.
sampled instantaneous value (I=01) (Sampled Value).
I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled
instantaneous value.
Reserved (resv): 6 bits Reserved (resv): 6 bits
These bits are reserved. They MUST be set to zero by senders and These bits are reserved. They MUST be set to zero by senders and
SHOULD be ignored by receivers. SHOULD be ignored by receivers (See RFC6709 section 4.2).
block length: 16 bits block length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the Delay block, the block length is equal to 6. the Delay block, the block length is equal to 6.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
Mean Network Round Trip Delay: 32 bits Mean Network Round Trip Delay: 32 bits
The Mean Network Round Trip Delay is the mean value of the RTP-to- The Mean Network Round Trip Delay is the mean value of the RTP-to-
RTP interface round trip delay over the measurement period, RTP interface round trip delay over the measurement period,
expressed in units of 1/65536 seconds. This value is typically expressed in units of 1/65536 seconds. This value is typically
determined using RTCP SR/RR (See RFC 3550 section 6.4.1). It also determined using NTP timestamp field in the RTCP SR and LSR field
can be determined using RTCP Receiver Reference Time Report Block and DLSR field in the RTCP RR (See RFC 3550 section 6.4.1 and
and DLRR Report Block (See RFC3611 section 4.5). figure 2). It also can be determined using NTP timestamp field in
the RTCP Receiver Reference Time Report Block and LRR field and
DLRR field in the DLRR Report Block (See RFC3611 section 4.5).
If only one measurement of Round Trip Delay is available for the If only one measurement of Round Trip Delay is available for the
timespan of the report (i.e.,the measurement period) (whether timespan of the report (i.e.,the measurement period) (whether
Interval or Cumulative), this single value SHOULD be reported as Interval or Cumulative), this single value SHOULD be reported as
the mean value. the mean value.
If the measurement is unavailable, the value of this field with If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported. all bits set to 1 MUST be reported.
Min Network Round Trip Delay: 32 bits Min Network Round Trip Delay: 32 bits
The Min Network Round Trip Delay is the minimum value of the RTP- The Min Network Round Trip Delay is the minimum value of the RTP-
to-RTP interface round trip delay over the measurement period, to-RTP interface round trip delay over the measurement period,
expressed in units of 1/65536 seconds. This value is typically expressed in units of 1/65536 seconds. This value is typically
determined using RTCP SR/RR. It also can be determined using RTCP determined using NTP timestamp field in the RTCP SR and LSR field
Receiver Reference Time Report Block and DLRR Report Block. and DLSR field in the RTCP RR. It also can be determined using
NTP timestamp field in the RTCP Receiver Reference Time Report
Block and LRR field and DLRR field in the DLRR Report Block.
If only one measurement of Round Trip Delay is available for the If only one measurement of Round Trip Delay is available for the
timespan of the report (i.e.,the measurement period) (whether timespan of the report (i.e.,the measurement period) (whether
Interval or Cumulative), this single value SHOULD be reported as Interval or Cumulative), this single value SHOULD be reported as
the minimum value. the minimum value.
If the measurement is unavailable, the value of this field with If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported. all bits set to 1 MUST be reported.
Max Network Round Trip Delay: 32 bits Max Network Round Trip Delay: 32 bits
The Max Network Round Trip Delay is the maximum value of the RTP- The Max Network Round Trip Delay is the maximum value of the RTP-
to-RTP interface round trip delay over the measurement period, to-RTP interface round trip delay over the measurement period,
expressed in units of 1/65536 seconds. This value is typically expressed in units of 1/65536 seconds. This value is typically
determined using RTCP SR/RR. It also can be determined using RTCP determined using NTP timestamp field in the RTCP SR and LSR field
Receiver Reference Time Report Block and DLRR Report Block. and DLSR field in the RTCP RR. It also can be determined using
NTP timestamp field in the RTCP Receiver Reference Time Report
Block and LRR field and DLRR field in the DLRR Report Block.
If only one measurement of Round Trip Delay is available for the If only one measurement of Round Trip Delay is available for the
timespan of the report (i.e.,the measurement period) (whether timespan of the report (i.e.,the measurement period) (whether
Interval or Cumulative), this single value SHOULD be reported as Interval or Cumulative), this single value SHOULD be reported as
the maximum value. the maximum value.
If the measurement is unavailable, the value of this field with If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported. all bits set to 1 MUST be reported.
End System Delay: 64 bits End System Delay: 64 bits
skipping to change at page 12, line 14 skipping to change at page 13, line 14
8. Acknowledgments 8. Acknowledgments
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Jing Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Jing
Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida
Schubert. Schubert,Barry Leiba,Sean Turner,Robert Sparks,Benoit Claise,Stephen
Farrell.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
skipping to change at page 13, line 27 skipping to change at page 14, line 27
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
[RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network [RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network
Time Protocol Version 4: Protocol and Algorithms Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, June 2010. Specification", RFC 5905, June 2010.
9.2. Informative References 9.2. Informative References
[MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-10,
August 2012.
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-22, September 2012. ID draft-ietf-avtcore-monarch-22, September 2012.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 2011.
[RFC6776] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, October 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-delay-10 A.1. draft-ietf-xrblock-rtcp-xr-delay-11
The following are the major changes to previous version :
o Editorial changes based on IESG reviews.
A.2. draft-ietf-xrblock-rtcp-xr-delay-10
The following are the major changes to previous version : The following are the major changes to previous version :
o Editorial changes based on SDP directorate Review. o Editorial changes based on SDP directorate Review.
A.2. draft-ietf-xrblock-rtcp-xr-delay-09 A.3. draft-ietf-xrblock-rtcp-xr-delay-09
The following are the major changes to previous version : The following are the major changes to previous version :
o Editorial changes based on comments that are applied to PDV draft. o Editorial changes based on comments that are applied to PDV draft.
A.3. draft-ietf-xrblock-rtcp-xr-delay-08 A.4. draft-ietf-xrblock-rtcp-xr-delay-08
The following are the major changes to previous version : The following are the major changes to previous version :
o Move Geoff Hunt from author list to Contributors section based on o Move Geoff Hunt from author list to Contributors section based on
his suggestion. his suggestion.
A.4. draft-ietf-xrblock-rtcp-xr-delay-07 A.5. draft-ietf-xrblock-rtcp-xr-delay-07
The following are the major changes to previous version : The following are the major changes to previous version :
o Editorial changes. o Editorial changes.
o Reference updates. o Reference updates.
A.5. draft-ietf-xrblock-rtcp-xr-delay-06 A.6. draft-ietf-xrblock-rtcp-xr-delay-06
The following are the major changes to previous version : The following are the major changes to previous version :
o Editorial changes. o Editorial changes.
A.6. draft-ietf-xrblock-rtcp-xr-delay-05 A.7. draft-ietf-xrblock-rtcp-xr-delay-05
The following are the major changes to previous version : The following are the major changes to previous version :
o One typo fixed. o One typo fixed.
A.7. draft-ietf-xrblock-rtcp-xr-delay-04 A.8. draft-ietf-xrblock-rtcp-xr-delay-04
The following are the major changes to previous version : The following are the major changes to previous version :
o Revise the definition of sampled metric to get alignment with o Revise the definition of sampled metric to get alignment with
MONARCH. MONARCH.
o Clarify sending the metric block in the same RTCP compound packet o Clarify sending the metric block in the same RTCP compound packet
as the measurement information block. as the measurement information block.
A.8. draft-ietf-xrblock-rtcp-xr-delay-03 A.9. draft-ietf-xrblock-rtcp-xr-delay-03
The following are the major changes to previous version : The following are the major changes to previous version :
o Allocate 64 bit for end system delay and represent it using 64 bit o Allocate 64 bit for end system delay and represent it using 64 bit
NTP-Timestamp. NTP-Timestamp.
o Other editorial changes. o Other editorial changes.
A.9. draft-ietf-xrblock-rtcp-xr-delay-02 A.10. draft-ietf-xrblock-rtcp-xr-delay-02
The following are the major changes to previous version : The following are the major changes to previous version :
o Allocate 32bits for each metrics and change unit for each metric o Allocate 32bits for each metrics and change unit for each metric
from ms to 1/65536 seconds. from ms to 1/65536 seconds.
A.10. draft-ietf-xrblock-rtcp-xr-delay-01 A.11. draft-ietf-xrblock-rtcp-xr-delay-01
The following are the major changes to previous version : The following are the major changes to previous version :
o Updated references. o Updated references.
o Allocate one more bit for Interval metric flag to indicate sampled o Allocate one more bit for Interval metric flag to indicate sampled
metric can be used. metric can be used.
o add a few clarification text for failure mode. o add a few clarification text for failure mode.
A.11. draft-ietf-xrblock-rtcp-xr-delay-00 A.12. draft-ietf-xrblock-rtcp-xr-delay-00
The following are the major changes to previous version : The following are the major changes to previous version :
o Changed BNF for SDP following Christian Groves' and Tom Taylor's o Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009). comments (4th and 5th May 2009).
o Updated references. o Updated references.
Authors' Addresses Authors' Addresses
 End of changes. 27 change blocks. 
70 lines changed or deleted 88 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/