draft-ietf-xrblock-rtcp-xr-delay-01.txt   draft-ietf-xrblock-rtcp-xr-delay-02.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: June 9, 2012 Telchemy Expires: October 8, 2012 Telchemy
K. Gross K. Gross
AVA Networks AVA Networks
Q. Wu Q. Wu
Huawei Huawei
December 7, 2011 April 6, 2012
RTCP XR Report Block for Delay metric Reporting RTCP XR Report Block for Delay metric Reporting
draft-ietf-xrblock-rtcp-xr-delay-01.txt draft-ietf-xrblock-rtcp-xr-delay-02.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 June 9, 2012. This Internet-Draft will expire on October 8, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 32 skipping to change at page 2, line 32
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. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 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-00 . . . . . . . . . . . 13
A.2. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13 A.2. draft-ietf-xrblock-rtcp-xr-delay-01 . . . . . . . . . . . 13
A.3. draft-ietf-xrblock-rtcp-xr-delay-02 . . . . . . . . . . . 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 5, line 22 skipping to change at page 5, line 22
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. for 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 = 3 | | BT=NDEL | I | resv. | block length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean Network Round Trip Delay | End System Delay | | Mean Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Network Round Trip Delay | Max Network Round Trip Delay | | End System Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Network Round Trip Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 Basic Loss/Discard
metrics are sampled,Interval or Cumulative metrics, that is, metrics are sampled, Interval or Cumulative metrics, that is,
whether the reported values applies to the most recent measurement whether the reported values applies to the most recent measurement
interval duration between successive metrics reports (I=10) (the interval duration between successive metrics reports (I=10) (the
Interval Duration) or to the accumulation period characteristic of Interval 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 SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST 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 3. the Delay block, the block length is equal to 5.
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 (ms): 16 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 in ms over the measurement period, RTP interface round trip delay over the measurement period,
typically determined using RTCP SR/RR. expressed in units of 1/65536 seconds. This value is typically
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 measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
End System Delay (ms): 16 bits End System Delay: 32 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, expressed in units of 1/65536 seconds. This
jitter buffer delay plus the accumulation/ encoding and decoding / value is calculated using the nominal value of the jitter buffer
playout delay associated with the codec being used. 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 If the measured or estimated value exceeds 0xFFFD, the value
0xFFFE SHOULD be reported to indicate an over-range measurement. 0xFFFE SHOULD be reported to indicate an over-range measurement.
If the measurement is unavailable, the value 0xFFFF SHOULD be If the measurement is unavailable, the value 0xFFFF SHOULD be
reported. reported.
Min Network Round Trip Delay (ms): 16 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 in ms over the measurement to-RTP interface round trip delay over the measurement period,
period, typically determined using RTCP SR/RR. expressed in units of 1/65536 seconds. This value is typically
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 measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
Max Network Round Trip Delay (ms): 16 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 in ms over the measurement to-RTP interface round trip delay over the measurement period,
period, typically determined using RTCP SR/RR. expressed in units of 1/65536 seconds. This value is typically
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 measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
4. SDP Signaling 4. SDP Signaling
skipping to change at page 14, line 5 skipping to change at page 13, line 30
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
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.
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
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
 End of changes. 20 change blocks. 
23 lines changed or deleted 39 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/