Network Working Group | G. Zorn, Ed. |
Internet-Draft | Network Zen |
Intended status: Standards Track | R. Schott |
Expires: July 20, 2013 | Deutsche Telekom |
Q. Wu | |
R. Huang | |
Huawei | |
January 16, 2013 |
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-summary-stat-06
This document defines three RTP Control Protocol (RTCP) Extended Report (XR) Blocks that allow the reporting of loss, duplication and discard summary statistics metrics in a range of RTP applications.
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 July 20, 2013.
Copyright (c) 2013 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 described in the Simplified BSD License.
This draft defines three new block types to augment those defined in [RFC3611] for use in a range of RTP applications.
The first two block types support the reporting of burst gap loss/ discard summary statistics including packet loss/discard proportion, mean and variance and belong to the class of transport-related end system metrics defined in [RFC6792]. These two blocks are intended to be used in conjunction with information from the Burst Gap Loss Metrics Block or Burst Gap Discard Metrics Block, and on which these two block therefore depend. The metrics in the Burst Gap Loss block or Burst Gap Discard Metrics Block can be used independently of the metrics defined in the first two blocks.
The third block supports the reporting of detailed statistics for each frame type, including the number of frames received, lost and discarded of each frame type in the Group of Pictures (GOP) and additional data allowing the calculation of statistical parameters (e.g.,the proportion of each frame type impaired by packet loss and discard). The metrics defined in this block belong to the class of application layer metrics defined in [RFC6792].
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 for use with [RFC3550] and [RFC3611].
The RTP Monitoring Architectures [RFC6792] provides guideline for reporting block format using RTCP XR. Metrics described in this draft are in accordance with the guidelines in [RFC6792].
These metrics are applicable to a wide range of RTP applications and reflect transient IP problems that affect user experience. They can be used to form an accurate assessment of users' quality of experience and influence sender strategies to mitigate the problem.
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:
The metrics described here are intended to be used as described in this section, in conjunction with information from the Measurement Information block [RFC6776] (which MUST be present in the same RTCP packet as the Burst/Gap Loss block) and also with the metric "cumulative number of packets lost" provided in standard RTCP [RFC3550]. Instances of this Metrics Block refer by Synchronization source (SSRC) to the separate auxiliary Measurement Information block [RFC6776] which describes measurement periods in use (see [RFC6776] section 4.2). This Metrics Block relies on the measurement period in the Measurement Information block indicating the span of the report and SHOULD be sent in the same compound RTCP packet as the measurement information block. If the measurement period is not received in the same compound RTCP packet as this Metrics Block, this metrics block MUST be discarded.
The metrics carried in this Metrics Block provide information relevant to statistical parameters, including burst loss rate, gap loss rate, burst duration mean, burst duration variance and are calculated at the receiving end of the RTP stream using burst gap loss metrics defined in [BGLOSS] and other information which is sent together with this report block.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=BGLSS | I | Reserved | block length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Burst Loss Rate | Gap Loss Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Burst duration Mean | Burst duration Variance | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In this document, the value I=00 is the reserved value and MUST NOT be used.
The metrics described here are intended to be used as described in this section, in conjunction with information from the Measurement Identity block [RFC6776] (which MUST be present in the same RTCP packet as the Burst/Gap Discard Summary Statistics block) .
These metrics provide information relevant to statistical parameters, including burst discard rate, gap discard rate and are calculated at the receiving end of the RTP stream using burst gap discard metrics defined in [BGDISCARD] and other information which is sent together with this report block.
Instances of this Metrics Block refer by Synchronization source (SSRC) to the separate auxiliary Measurement Information block [RFC6776] which describes measurement periods in use (see [RFC6776] section 4.2). This metrics block relies on the measurement period in the Measurement Information block indicating the span of the report and SHOULD be sent in the same compound RTCP packet as the measurement information block. If the measurement period is not received in the same compound RTCP packet as this Metrics Block, this Metrics Block MUST be discarded.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=BGDSS | I | Reserved | block length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Burst Discard Rate | Gap Discard Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This block reports statistics on which frame type were affected beyond the information carried in the Statistics Summary Report Block RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. Information is measured at the receiving end of the RTP stream and recorded about the number of frames received, lost frames, duplicated frames and lost partial frames. Such information can be useful for network management and video quality monitoring.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=FISS |T| Reserved | block length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Begin_seq | End_seq | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of frames received | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discarded_frames | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Dup_frames | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lost_full_frames | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lost_partial_frames | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RFC 3611 defines the use of SDP (Session Description Protocol) [RFC4566] for signaling the use of XR blocks. However XR blocks MAY be used without prior signaling (see section 5 of RFC3611).
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined in Section 5.1 of RFC 3611 by providing three additional values of "xr-format" to signal the use of the report block defined in this document.
xr-format = / burst-gap-loss-stat / burst-gap-discard-stat / frame-impairment-stat Burst-gap-loss-stat ="burst gap loss summary statistics" Burst-gap-discard-stat="burst gap discard summary statistics" Frame-impairment-stat="frame impairment summary statistics"
When SDP is used in offer-answer context, the SDP Offer/Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters applies. For detailed usage of Offer/Answer for unilateral parameter, refer to section 5.2 of [RFC3611].
New block types for RTCP XR are subject to IANA registration. For general guidelines on IANA considerations for RTCP XR, refer to RFC 3611.
Name: BGLSS Long Name: Burst/Gap Loss Summary Statistics Block Value <BGLSS> Reference: Section 3.1 Name: BGDSS Long Name: Burst/Gap Discard Summary Statistics Block Value <BGDSS> Reference: Section 3.2 Name: FISS Long Name: Frame Impairment Statistics Summary Value <FISS> Reference: Section 4.1
This document assigns three new block type value in the "RTP Control Protocol (RTCP) Extended Report (XR) Block Type Registry" :
* " burst-gap-loss-stat " * " burst-gap-discard-stat " * " frame-impairment-stat "
This document also registers three new SDP [RFC4566] parameters for the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended Report (XR) SDP Parameters Registry ":
The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com) 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
The new RTCP XR report blocks proposed in this document introduces no new security considerations beyond those described in RFC 3611.
The authors would like to thank Bill Ver Steeg, David R Oran, Ali Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu for their valuable comments and suggestions on this document.
[RFC6709] | Carpenter, B., Aboba, B. and S. Cheshire, "Design Considerations for Protocol Extensions", RFC 6709, September 2012. |
[RFC6792] | Hunt, G., Wu, Q. and P. Arden, "Monitoring Architectures for RTP", RFC 6792, November 2012. |
Note to the RFC-Editor: please remove this section prior to publication as an RFC.
The following are the major changes compared to 05:
The following are the major changes compared to 04: