RTP Control Protocol (RTCP) Extended Report (XR) Block for Independent Reporting of Burst/Gap Discard Metric
draft-ietf-xrblock-independent-burst-gap-discard-01
Audio/Video Transport Working Group V. Singh
Internet-Draft callstats.io
Intended status: Standards Track C. Perkins
Expires: September 22, 2016 University of Glasgow
A. Clark
Telchemy
R. Huang
Huawei
March 21, 2016
RTP Control Protocol (RTCP) Extended Report (XR) Block for Independent
Reporting of Burst/Gap Discard Metric
draft-ietf-xrblock-independent-burst-gap-discard-01
Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of burst and gap discard metrics
independently of the burst and gap loss 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 September 22, 2016.
Copyright Notice
Copyright (c) 2016 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
Singh, et al. Expires September 22, 2016 [Page 1]
Internet-Draft RTCP XR Burst/Gap Discard March 2016
carefully, as they describe your rights and restrictions with respect
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Burst-Gap Discard Metrics Block . . . . . . . . . . . . . 2
1.2. RTCP and RTCP Extended Reports . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Burst/Gap Discard Metrics Block . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Burst/Gap Discard Metrics Block . 5
3.3. Derived Metrics Based on the Reported Metrics . . . . . . 7
4. Considerations for Voice-over-IP Applications . . . . . . . . 8
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . 8
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . . 9
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Metrics Represented Using the Template from RFC 6390 13
1. Introduction
1.1. Burst-Gap Discard Metrics Block
This document defines a new block type that extends the metrics
defined in [RFC7003]. The new block type reports the proportion of
packets discarded in a burst by the dejitter buffer at the receiver.
The number of packets discarded depends on the dejitter buffer
algorithm implemented by the endpoint.
The new report block defined in this document is different from the
one defined in [RFC7003]. The metrics in [RFC7003] depends on the
Show full document text