RTCP XR Report Block for One Way Delay metric Reporting
draft-wu-xrblock-rtcp-xr-one-way-delay-01
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2012-07-02
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Audio/Video Transport Working Group R. Brandenburg
Internet-Draft TNO
Intended status: Standards Track K. Gross
Expires: January 4, 2013 AVA Networks
Q. Wu
Huawei
F. Boronat
M. Montagud
UPVLC
July 3, 2012
RTCP XR Report Block for One Way Delay metric Reporting
draft-wu-xrblock-rtcp-xr-one-way-delay-01.txt
Abstract
This document defines an RTCP XR Report Block that allows the
reporting of One Way Delay metrics for use in a range of RTP
applications.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Brandenburg, et al. Expires January 4, 2013 [Page 1]
Internet-Draft One Way Delay July 2012
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Packet One Way Delay Metrics Block . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. One Way Delay Block . . . . . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in One Way Delay Metrics Report
Block . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Clock synchronization for one way delay metrics . . . . . . . 7
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
6.3. Contact information for registrations . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Brandenburg, et al. Expires January 4, 2013 [Page 2]
Internet-Draft One Way Delay July 2012
1. Introduction
1.1. Packet One Way Delay Metrics Block
[I-D.ietf-xrblock-rtcp-xr-delay] defines the new block type
supporting the reporting of the mean, minimum and maximum values of
the network round-trip delay between media source(source) and media
receiver(destination). However none of these metrics allow a
receiver to report one way delay from source to destination or the
other way around. As described in [RFC2679], the path from a source
to a destination may be different than the path from the destination
back to the source. Even when the two paths are symmetric, they may
have radically different performance characteristics. Therefore the
Show full document text