RTCP XR Report Block for Discard Count metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-06
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7002.
|
|
|---|---|---|---|
| Authors | Alan Clark , Glen Zorn , Qin Wu | ||
| Last updated | 2012-08-23 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 7002 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-xrblock-rtcp-xr-discard-06
Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy
Intended status: Standards Track G. Zorn
Expires: February 25, 2013 Network Zen
Q. Wu
Huawei
August 24, 2012
RTCP XR Report Block for Discard Count metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-06.txt
Abstract
This document defines an RTCP XR Report Block that allows the
reporting of a simple discard count metric 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 February 25, 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
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
Clark, et al. Expires February 25, 2013 [Page 1]
Internet-Draft RTCP XR Discard August 2012
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Discard Count Report Block . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
3. Discard Count Metric Report Block . . . . . . . . . . . . . . 6
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6
3.2. Definition of Fields in Discard Count Metric Report
Block . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
5.3. Contact information for registrations . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Clark, et al. Expires February 25, 2013 [Page 2]
Internet-Draft RTCP XR Discard August 2012
1. Introduction
1.1. Discard Count Report Block
This document defines a new block type to augment those defined in
[RFC3611] for use in a range of RTP applications. The new block type
supports the reporting of the number of packets which are received
correctly but are never played out, typically because they arrive too
late to be played out (buffer underflow) or too early (buffer
overflow). The metric is applicable both to systems which use packet
loss repair techniques (such as forward error correction [RFC5109] or
retransmission [RFC4588]) and to those which do not.
This metric is useful for identifying the existence, and
characterising the severity, of a packet transport problem which may
affect users' perception of a service delivered over RTP.
The metric belongs to the class of transport-related terminal metrics
defined in [MONARCH].
1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block. The
use of Extended Report blocks is defined by [RFC3611].
1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP
Monitoring Architectures [MONARCH] provides guideline for reporting
block format using RTCP XR. The Metrics Block described in this
document are in accordance with the guidelines in [RFC6390] and
[MONARCH].
1.4. Applicability
This metric is believed to be applicable to a large class of RTP
applications which use a jitter buffer.
In case of Discard count metric block sent together with Burst gap
discard metric block defined in [BGDISCARD] to the media sender or
RTP based network management system, information carried in the
discard count metric block and Burst gap discard metric block allows
them calculate the some bust gap summary statistics,e.g., gap discard
rate.
Clark, et al. Expires February 25, 2013 [Page 3]
Internet-Draft RTCP XR Discard August 2012
In case of replication being kept "on", reporting duplicate packets
discards allows the media sender or network management system
determine what proportion of lost packets are being concealed by the
process and calculate the actual loss rate which is helpful to know
that there are some network issues that need to be investigated.
Clark, et al. Expires February 25, 2013 [Page 4]
Internet-Draft RTCP XR Discard August 2012
2. Terminology
2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
In addition, the following terms are defined:
Received, Lost and Discarded
A packet shall be regarded as lost if it fails to arrive within an
implementation-specific time window. A packet that arrives within
this time window but is too early or late to be played out or
thrown away before playout due to packet duplication or redundancy
shall be regarded as discarded. A packet shall be classified as
one of received (or OK), discarded or lost. The Discard Count
Metric counts only discarded packets. The metric "cumulative
number of packets lost" defined in [RFC3550] reports a count of
packets lost from the media stream (single SSRC within single RTP
session). Similarly the metric "number of packets discarded"
reports a count of packets discarded from the media stream (single
SSRC within single RTP session) arriving at the receiver. Another
metric defined in [RFC5725] is available to report on packets
which are not recovered by any repair techniques which may be in
use.
Clark, et al. Expires February 25, 2013 [Page 5]
Internet-Draft RTCP XR Discard August 2012
3. Discard Count Metric Report Block
3.1. Report Block Structure
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=PDC | I |DT | resv.| block length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| number of packets discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure
3.2. Definition of Fields in Discard Count Metric Report Block
Block type (BT): 8 bits
A Discard Count Metric Report Block is identified by the constant
PDC.
[Note to RFC Editor: please replace PDC with the IANA provided
RTCP XR block type for this block.]
Interval Metric flag (I): 2 bits
This field is used to indicate whether the Discard Count Metric is
an Interval or Cumulative metric, Sample metric [MONARCH],that is,
whether the reported values applies to the most recent measurement
interval duration between successive metrics reports (I=10) (the
Interval Duration) or to the accumulation period characteristic of
cumulative measurements (I=11) (the Cumulative Duration) or is a
sampled instantaneous value (I=01) (Sampled Value). In this
document, Discard Count Metric is not measured at a particular
time instant but over one or several reporting intervals.
Therefore Discard Count Metric MUST not be chosen as Sampled
Metric.
Discard Type (DT): 2bits
This field is used to identify the discard type used in this
report block. The discard type is defined as follows:
Clark, et al. Expires February 25, 2013 [Page 6]
Internet-Draft RTCP XR Discard August 2012
00: Report packet discarded or being thrown away before playout
due to packets duplication.
01: Report packet discarded due to too early to be played out.
10: Report packet discarded due to too late to be played out.
11: Report the total number of discarded packets due to both
early and late to be played out.
An endpoint MAY report only one of the above four discard types
blocks in an compound RTCP report in a reporting interval. It MAY
also report a combination of discard types in a compound RTCP
report but not all combinations are valid. The endpoint MAY
report duplicate packet discard (DT=0) block with any other
discard (DT=1, 2, or 3) block. Additionally, an endpoint MUST NOT
report combined discard (DT=3) block with early discard (DT=1) or
late discard (DT=2) report block.
Note that duplicating RTP packets is for robustness or error
resilience but disrupts RTCP statitics. In order to tackle this,
the mechanism described in [RTPDUP] can be used which will not
cause breakage of RTP streams or RTCP rules.
Reserved (resv): 4 bits
These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers.
block length: 16 bits
The length of this report block in 32-bit words, minus one. For
the Discard Count block, the block length is equal to 2.
SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611].
number of packets discarded: 32 bits
Number of packets discarded over the period (Interval or
Cumulative) covered by this report.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
Clark, et al. Expires February 25, 2013 [Page 7]
Internet-Draft RTCP XR Discard August 2012
MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
Note that the number of packets expected in the period associated
with this metric (whether interval or cumulative) is available
from the difference between a pair of extended sequence numbers in
the Measurement Information block [MEASI], so need not be repeated
in this block.
Clark, et al. Expires February 25, 2013 [Page 8]
Internet-Draft RTCP XR Discard August 2012
4. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling.
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611])
xr-format =/ xr-pdc-block
xr-pdc-block = "pkt-dscrd-count"
Clark, et al. Expires February 25, 2013 [Page 9]
Internet-Draft RTCP XR Discard August 2012
5. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611].
5.1. New RTCP XR Block Type value
This document assigns the block type value PDC in the IANA "RTCP XR
Block Type Registry" to the "Discard Count Metrics Block".
[Note to RFC Editor: please replace PDC with the IANA provided RTCP
XR block type for this block.]
5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "pkt-dscrd" in the "RTCP
XR SDP Parameters Registry".
5.3. Contact information for registrations
The following contact information is provided for all
registrations in this document:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Clark, et al. Expires February 25, 2013 [Page 10]
Internet-Draft RTCP XR Discard August 2012
6. Security Considerations
It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply.
Clark, et al. Expires February 25, 2013 [Page 11]
Internet-Draft RTCP XR Discard August 2012
7. Contributors
Geoff Hunt wrote the initial draft of this document.
Clark, et al. Expires February 25, 2013 [Page 12]
Internet-Draft RTCP XR Discard August 2012
8. Acknowledgments
The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Kevin
Gross, Varun Singh,Claire Bi, Roni Even, Dan Romascanu.
Clark, et al. Expires February 25, 2013 [Page 13]
Internet-Draft RTCP XR Discard August 2012
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006.
9.2. Informative References
[BGDISCARD]
Hunt, G., "RTCP XR Report Block for Burst Gap Discard
metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-05,
July 2012.
[MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-06,
April 2012.
[MONARCH] Wu, Q., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-12, April 2012.
[RFC4588] Rey, J., "RTP Retransmission Payload Format", RFC 4588,
July 2006.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, July 2006.
[RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss
metric Reporting", RFC 5725, February 2010.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011.
[RTPDUP] Begen, A. and C. Perkins, "Duplicating RTP Streams",
ID draft-ietf-avtext-rtp-duplication-00, July 2012.
Clark, et al. Expires February 25, 2013 [Page 14]
Internet-Draft RTCP XR Discard August 2012
Authors' Addresses
Alan Clark
Telchemy Incorporated
2905 Premiere Parkway, Suite 280
Duluth, GA 30097
USA
Email: alan.d.clark@telchemy.com
Glen Zorn
Network Zen
77/440 Soi Phoomjit, Rama IV Road
Phra Khanong, Khlong Toie
Bangkok 10110
Thailand
Phone: +66 (0) 87 502 4274
Email: gwz@net-zen.net
Qin Wu
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Email: sunseawq@huawei.com
Clark, et al. Expires February 25, 2013 [Page 15]