draft-ietf-xrblock-rtcp-xr-pdv-06.txt   draft-ietf-xrblock-rtcp-xr-pdv-07.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 Q. Wu Intended status: Standards Track Q. Wu
Expires: March 18, 2013 Huawei Expires: March 25, 2013 Huawei
September 14, 2012 September 21, 2012
RTCP XR Report Block for Packet Delay Variation Metric Reporting RTP Control Protocol (RTCP) Extended Report (XR) Block for Packet Delay
draft-ietf-xrblock-rtcp-xr-pdv-06.txt Variation Metric Reporting
draft-ietf-xrblock-rtcp-xr-pdv-07.txt
Abstract Abstract
This document defines a Real-Time Control Protocol (RTCP) Extended This document defines an RTP Control Protocol (RTCP) Extended Report
Report (XR) block that allows the reporting of Packet Delay Variation (XR) block that allows the reporting of Packet Delay Variation
metrics for a range of Real-time Transport Protocol (RTP) metrics for a range of RTP applications.
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.
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 March 18, 2013. This Internet-Draft will expire on March 25, 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 3, line 38 skipping to change at page 3, line 38
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 XR Block described in this document block format using RTCP XR. The XR Block described in this document
are in accordance with the guidelines in [RFC6390] and [MONARCH]. are in accordance with the guidelines in [RFC6390] and [MONARCH].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a wide range of RTP applications in These metrics are applicable to a wide range of RTP applications in
which the application streams are sensitive to delay variation. which the application streams are sensitive to delay
Application designers can know the range of delay variation they must variation[RFC5481]. For example, applications could use the
accommodate, whether they are designing fixed or adaptive buffer measurements of these metrics to help adjust the size of adaptive
systems. Network manager also can constrain delay variation to jitter buffers to improve performance. Network managers can use
ensure the quality of real-time applications, and monitor this metric these metrics to compare actual delay variation to targets (i.e., a
(possibly to compare with a numerical objective or Service Level numerical objective or Service Level Agreement) to help ensure the
Agreement) [RFC5481]. quality of real-time application performance.
2. Terminology 2. Terminology
This document uses ABNF from [RFC5234] as a terminology statement.
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].
2.2. Notations 2.2. Notations
This report block makes use of binary fractions. The terminology This report block makes use of binary fractions. The terminology
used is used is
skipping to change at page 5, line 17 skipping to change at page 5, line 17
Metrics in this block report on packet delay variation in the stream Metrics in this block report on packet delay variation in the stream
arriving at the RTP system. The measurement of these metrics are arriving at the RTP system. The measurement of these metrics are
made at the receiving end of the RTP stream. Instances of this made at the receiving end of the RTP stream. Instances of this
Metrics Block refer by Synchronization source (SSRC) to the separate Metrics Block refer by Synchronization source (SSRC) to the separate
auxiliary Measurement Information block [MEASI] which contains auxiliary Measurement Information block [MEASI] which contains
measurement intervals. This metric block relies on the measurement measurement intervals. This metric block relies on the measurement
interval in the Measurement Information block indicating the span of interval in the Measurement Information block indicating the span of
the report and SHOULD be sent in the same compound RTCP packet as the the report and SHOULD be sent in the same compound RTCP packet as the
measurement information block. If the measurement interval is not measurement information block. If the measurement interval is not
received for this metric block, this metric block MUST be discarded ( received for this metric block, this metric block MUST be discarded (
See timing details in section 5.4 of[MONARCH]). See section 5.4 of[MONARCH]for timing details).
3.1. Report Block Structure 3.1. Report Block Structure
PDV metrics block PDV 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=NPDV | I |pdvtyp |Rsv| block length=4 | | BT=NPDV | I |pdvtyp |Rsv| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 End of changes. 7 change blocks. 
19 lines changed or deleted 17 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/