draft-ietf-xrblock-rtcp-xr-delay-00.txt   draft-ietf-xrblock-rtcp-xr-delay-01.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: April 19, 2012 Telchemy Expires: June 9, 2012 Telchemy
K. Gross K. Gross
AVA Networks AVA Networks
Q. Wu Q. Wu
Huawei Huawei
October 17, 2011 December 7, 2011
RTCP XR Report Block for Delay metric Reporting RTCP XR Report Block for Delay metric Reporting
draft-ietf-xrblock-rtcp-xr-delay-00.txt draft-ietf-xrblock-rtcp-xr-delay-01.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 April 19, 2012. This Internet-Draft will expire on June 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 31 skipping to change at page 2, line 31
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. 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
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 29 skipping to change at page 3, line 29
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 [PMOLFRAME] provides guidance on The Performance Metrics Framework [RFC6390] provides guidance on the
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
[PMOLFRAME]. [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.
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. at the RTP system. Instances of this Metrics Block refer by SSRC to
the separate auxiliary Measurement Information block [MEASI] which
contains measurement intervals. This metric block relies on the
measurement interval in the Measurement Information block indicating
the span of the report. If the measurement interval is not received
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 = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean Network Round Trip Delay | End System Delay | | Mean Network Round Trip Delay | End System Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Network Round Trip Delay | Max Network Round Trip 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 NPDV 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): 1 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Packet Delay Variation This field is used to indicate whether the Basic Loss/Discard
metrics block is an Interval or a Cumulative report, that is, metrics are sampled,Interval or Cumulative metrics, that is,
whether the reported values apply to the most recent measurement whether the reported values applies to the most recent measurement
interval duration between successive metrics reports (I=1) (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=0) (the Cumulative Duration). cumulative measurements (I=11) (the Cumulative Duration) or to the
value of a continuously measured or calculated that has been
sampled at end of the interval (I=01) (Sampled Value).
Reserved (resv): 7 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 3.
SSRC of source: 32 bits SSRC of source: 32 bits
skipping to change at page 12, line 23 skipping to change at page 12, line 23
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.
8.2. Informative References 8.2. Informative References
[MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-measu-identity-01,
October 2011.
[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-04, August 2011.
[PMOLFRAME] [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Clark, A. and B. Claise, "Framework for Performance Metric Development", RFC 6390, October 2011.
Development", ID draft-ietf-pmol-metrics-framework-12,
July 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-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.
A.2. draft-ietf-xrblock-rtcp-xr-delay-01
The following are the major changes to previous version :
o Updated references.
o Allocate one more bit for Interval metric flag to indicate sampled
metric can be used.
o add a few clarification text for failure mode.
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
Duluth, GA 30097 Duluth, GA 30097
USA USA
Email: alan.d.clark@telchemy.com Email: alan.d.clark@telchemy.com
Kevin Gross Kevin Gross
AVA Networks AVA Networks
Email: kevin.gross@comcast.net Email: kevin.gross@avanw.com
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com Email: sunseawq@huawei.com
 End of changes. 18 change blocks. 
22 lines changed or deleted 44 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/