draft-ietf-xrblock-rtcp-xr-delay-02.txt   draft-ietf-xrblock-rtcp-xr-delay-03.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: October 8, 2012 Telchemy Expires: October 23, 2012 Telchemy
K. Gross K. Gross
AVA Networks AVA Networks
Q. Wu Q. Wu
Huawei Huawei
April 6, 2012 April 21, 2012
RTCP XR Report Block for Delay metric Reporting RTCP XR Report Block for Delay metric Reporting
draft-ietf-xrblock-rtcp-xr-delay-02.txt draft-ietf-xrblock-rtcp-xr-delay-03.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of Delay metrics for use in a range of RTP applications. reporting of Delay metrics for use 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.
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 October 8, 2012. This Internet-Draft will expire on October 23, 2012.
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 25 skipping to change at page 2, line 25
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 . . . . . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
5.3. Contact information for registrations . . . . . . . . . . 9 5.3. Contact information for registrations . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13
A.1. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 13 A.1. draft-ietf-xrblock-rtcp-xr-delay-03 . . . . . . . . . . . 13
A.2. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13 A.2. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 13
A.3. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 13 A.3. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13
A.4. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
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 draft 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
skipping to change at page 3, line 37 skipping to change at page 3, line 37
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. Metrics definition and specification of performance metrics. Metrics
described in this draft either reference external definitions or described in this draft either reference external definitions or
define metrics generally in accordance with the guidelines in define metrics generally in accordance with the guidelines in
[RFC6390]. [RFC6390].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a range of RTP applications. These metrics are applicable to a range of RTP applications in which
this report block would be useful, such as multimedia conferencing
and streaming audio and video.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"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. Instances of this Metrics Block refer by SSRC to at the RTP system. Instances of this Metrics Block refer by SSRC to
the separate auxiliary Measurement Information block [MEASI] which the separate auxiliary Measurement Information block [MEASI] which
contains measurement intervals. This metric block relies on the contains measurement intervals. This metric block relies on the
measurement interval in the Measurement Information block indicating measurement interval in the Measurement Information block indicating
the span of the report. If the measurement interval is not received the span of the report. If the measurement interval is not received
for this metric block, this metric block should be discarded. in the same compound RTCP packet as this metric block, this metric
block should 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 = 5 | | BT=NDEL | I | resv. | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean Network Round Trip Delay | | Mean Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| End System Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Network Round Trip Delay | | Min Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Network Round Trip Delay | | Max Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| End System Delay - Seconds (bit 0-31) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| End System Delay - Fraction (bit 0-31) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Delay Metrics Report Block 3.2. Definition of Fields in Delay Metrics Report Block
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 Basic Loss/Discard This field is used to indicate whether the Delay metrics are
metrics are sampled, Interval or Cumulative metrics, that is, Sampled, Interval or Cumulative metrics, that is, whether the
whether the reported values applies to the most recent measurement reported values applies to the most recent measurement interval
interval duration between successive metrics reports (I=10) (the duration between successive metrics reports (I=10) (the Interval
Interval Duration) or to the accumulation period characteristic of Duration) or to the accumulation period characteristic of
cumulative measurements (I=11) (the Cumulative Duration) or to the cumulative measurements (I=11) (the Cumulative Duration) or to the
value of a continuously measured or calculated that has been value of a continuously measured or calculated that has been
sampled at end of the interval (I=01) (Sampled Value). sampled at end of the interval (I=01) (Sampled Value).
Reserved (resv): 6 bits Reserved (resv): 6 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They MUST be set to zero by senders and
and MUST be ignored by receivers. SHOULD be ignored by receivers.
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 5. 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. determined using RTCP SR/RR.
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 (whether Interval or Cumulative), this timespan of the report (whether Interval or Cumulative), this
single value should be reported as the mean value. single value should be reported as the mean value.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measurement is unavailable, the value 0xFFFFFFFF SHOULD be
reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported.
End System Delay: 32 bits
The End System Delay is the internal round trip delay within the
reporting endpoint, expressed in units of 1/65536 seconds. This
value is calculated using the nominal value of the jitter buffer
delay plus the accumulation/ encoding and decoding / playout delay
associated with the codec being used.
If the measured or estimated value exceeds 0xFFFD, the value
0xFFFE SHOULD be reported to indicate an over-range measurement.
If the measurement is unavailable, the value 0xFFFF SHOULD be
reported. 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. determined using RTCP SR/RR.
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 (whether Interval or Cumulative), this timespan of the report (whether Interval or Cumulative), this
single value should be reported as the minimum value. single value should be reported as the minimum value.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measurement is unavailable, the value 0xFFFFFFFF SHOULD be
reported to indicate an over-range measurement. If the reported.
measurement is unavailable, the value 0xFFFF SHOULD 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. determined using RTCP SR/RR.
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 (whether Interval or Cumulative), this timespan of the report (whether Interval or Cumulative), this
single value should be reported as the maximum value. single value should be reported as the maximum value.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measurement is unavailable, the value 0xFFFFFFFF SHOULD be
reported to indicate an over-range measurement. If the reported.
measurement is unavailable, the value 0xFFFF SHOULD be reported.
End System Delay: 64 bits
The End System Delay is the internal round trip delay within the
reporting endpoint, calculated using the nominal value of the
jitter buffer delay plus the accumulation/encoding and decoding/
playout delay associated with the codec being used. The value of
this field is represented using a 64-bit NTP-format timestamp as
defined in [RFC5905], which is 64-bit unsigned fixed-point number
with the integer part in the first 32 bits and the fractional part
in the last 32 bits.
If the measurement is unavailable, the value 0xFFFFFFFF SHOULD be
reported.
4. SDP Signaling 4. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] 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. XR blocks MAY be used
without prior signaling. without prior signaling.
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Kingdom Kingdom
6. Security Considerations 6. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply.
7. Contributors 7. 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. Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
8. References 8. References
skipping to change at page 12, line 21 skipping to change at page 12, line 21
[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.
[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)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
[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
Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, June 2010.
8.2. Informative References 8.2. Informative References
[MEASI] Hunt, G., "Measurement Identity and information Reporting [MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block", using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-measu-identity-01, ID draft-ietf-xrblock-rtcp-xr-meas-identity-06,
October 2011. April 2012.
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-04, August 2011. ID draft-ietf-avtcore-monarch-12, April 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.
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-00 A.1. 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 Changed BNF for SDP following Christian Groves' and Tom Taylor's o Allocate 64 bit for end system delay and represent it using 64 bit
comments (4th and 5th May 2009). NTP-Timestamp.
o Updated references. o Other editorial changes.
A.2. draft-ietf-xrblock-rtcp-xr-delay-01 A.2. draft-ietf-xrblock-rtcp-xr-delay-02
The following are the major changes to previous version :
o Allocate 32bits for each metrics and change unit for each metric
from ms to 1/65536 seconds.
A.3. 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.3. draft-ietf-xrblock-rtcp-xr-delay-02 A.4. 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 Allocate 32bits for each metrics and change unit for each metric o Changed BNF for SDP following Christian Groves' and Tom Taylor's
from ms to 1/65536 seconds. comments (4th and 5th May 2009).
o Updated references.
Authors' Addresses Authors' Addresses
Geoff Hunt Geoff Hunt
Unaffiliated Unaffiliated
Email: r.geoff.hunt@gmail.com Email: r.geoff.hunt@gmail.com
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
 End of changes. 27 change blocks. 
54 lines changed or deleted 71 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/