draft-ietf-xrblock-rtcp-xr-delay-05.txt   draft-ietf-xrblock-rtcp-xr-delay-06.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: November 15, 2012 Telchemy Expires: November 30, 2012 Telchemy
K. Gross K. Gross
AVA Networks AVA Networks
Q. Wu Q. Wu
Huawei Huawei
May 14, 2012 May 29, 2012
RTCP XR Report Block for Delay metric Reporting RTCP XR Report Block for Delay metric Reporting
draft-ietf-xrblock-rtcp-xr-delay-05.txt draft-ietf-xrblock-rtcp-xr-delay-06.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 November 15, 2012. This Internet-Draft will expire on November 30, 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 30 skipping to change at page 2, line 30
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. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 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-05 . . . . . . . . . . . 13 A.1. draft-ietf-xrblock-rtcp-xr-delay-06 . . . . . . . . . . . 13
A.2. draft-ietf-xrblock-rtcp-xr-delay-04 . . . . . . . . . . . 13 A.2. draft-ietf-xrblock-rtcp-xr-delay-05 . . . . . . . . . . . 13
A.3. draft-ietf-xrblock-rtcp-xr-delay-03 . . . . . . . . . . . 13 A.3. draft-ietf-xrblock-rtcp-xr-delay-04 . . . . . . . . . . . 13
A.4. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 13 A.4. draft-ietf-xrblock-rtcp-xr-delay-03 . . . . . . . . . . . 13
A.5. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13 A.5. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 13
A.6. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 14 A.6. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13
A.7. draft-ietf-xrblock-rtcp-xr-delay-00 . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
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 30 skipping to change at page 3, line 30
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 that Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611]. MUST be used as defined in [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. Metrics definition and specification of performance metrics. The RTP
described in this draft either reference external definitions or Monitoring Architectures [MONARCH] provides guideline for reporting
define metrics generally in accordance with the guidelines in block format using RTCP XR. The Metrics Block described in this
[RFC6390]. document are in accordance with the guidelines in [RFC6390] and
[MONARCH].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a range of RTP applications in which These metrics are applicable to a range of RTP applications in which
this report block would be useful, such as multimedia conferencing this report block would be useful, such as multimedia conferencing
and streaming audio and video. 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
the separate auxiliary Measurement Information block [MEASI] which Synchronization source (SSRC) to the separate auxiliary Measurement
contains measurement intervals. This metric block relies on the Information block [MEASI] which contains measurement intervals. This
measurement interval in the Measurement Information block indicating metric block relies on the measurement interval in the Measurement
the span of the report and should be sent in the same compound RTCP Information block indicating the span of the report and SHOULD be
packet as the measurement information block. If the measurement sent in the same compound RTCP packet as the measurement information
interval is not received in the same compound RTCP packet as this block. If the measurement interval is not received in the same
metric block, this metric block should be discarded. 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 = 6 | | BT=NDEL | I | resv. | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 37 skipping to change at page 6, line 37
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 (i.e.,the measurement period) (whether
single value should be reported as the mean value. Interval or Cumulative), this single value SHOULD be reported as
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 SHOULD 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. 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 (i.e.,the measurement period) (whether
single value should be reported as the minimum value. Interval or Cumulative), this single value SHOULD be reported as
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 SHOULD 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. 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 (i.e.,the measurement period) (whether
single value should be reported as the maximum value. Interval or Cumulative), this single value SHOULD be reported as
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 SHOULD be reported. all bits set to 1 MUST be reported.
End System Delay: 64 bits End System Delay: 64 bits
The End System Delay is the internal round trip delay within the The End System Delay is the internal round trip delay within the
reporting endpoint, calculated using the nominal value of the reporting endpoint, calculated using the nominal value of the
jitter buffer delay plus the accumulation/encoding and decoding/ jitter buffer delay plus the accumulation/encoding and decoding/
playout delay associated with the codec being used. The value of playout delay associated with the codec being used. The value of
this field is represented using a 64-bit NTP-format timestamp as this field is represented using a 64-bit NTP-format timestamp as
defined in [RFC5905], which is 64-bit unsigned fixed-point number defined in [RFC5905], which is 64-bit unsigned fixed-point number
with the integer part in the first 32 bits and the fractional part with the integer part in the first 32 bits and the fractional part
in the last 32 bits. in the last 32 bits.
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 SHOULD be reported. all bits set to 1 MUST 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 12 skipping to change at page 11, line 12
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. Acknowledgments 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,Jing
Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida
Schubert.
8. References 8. References
8.1. Normative References 8.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 10 skipping to change at page 13, line 10
ID draft-ietf-avtcore-monarch-13, May 2012. ID draft-ietf-avtcore-monarch-13, May 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-05 A.1. draft-ietf-xrblock-rtcp-xr-delay-06
The following are the major changes to previous version :
o Editorial changes.
A.2. 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.2. draft-ietf-xrblock-rtcp-xr-delay-04 A.3. 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.3. draft-ietf-xrblock-rtcp-xr-delay-03 A.4. 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.4. draft-ietf-xrblock-rtcp-xr-delay-02 A.5. 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.5. draft-ietf-xrblock-rtcp-xr-delay-01 A.6. 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.6. draft-ietf-xrblock-rtcp-xr-delay-00 A.7. 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. 21 change blocks. 
39 lines changed or deleted 53 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/