| Audio/Video Transport Working Group | G. Hunt |
| Internet-Draft | Unaffiliated |
| Intended status: Standards Track | A. Clark |
| Expires: January 12, 2013 | Telchemy |
| Q. Wu | |
| Huawei | |
| July 13, 2012 |
Measurement Identity and information Reporting using SDES item and XR Block
draft-ietf-xrblock-rtcp-xr-meas-identity-09.txt
This document defines an RTP Control Protocol (RTCP) Source Description (SDES) item and an RTCP Extended Report (XR) Block carrying parameters that identify and describe a measurement period, to which one or more other RTCP XR Report Blocks may refer.
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 12, 2013.
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 described in the Simplified BSD License.
This document defines one new RTP Control Protocol (RTCP) Source Description (SDES) [RFC3550] item, and one new Extended Report (XR) Report Block carrying parameters that identify and describe a measurement period, to which one or more other RTCP XR Report Blocks may refer.
The SDES item provides a field for an application specific auxiliary identifier. This identifier may be used to correlate data in XR Blocks within an RTP session with data from a non-RTP session.
A RTCP Measurement Identity SDES packet may be associated with a set of RTCP XR metrics blocks which share the same application specific measurement identifier.
The XR Report Block does not contain any measurement results (metrics). Instead, it provides information relevant to a measurement reported in one or more other block types, including:
The method for calculation of the extended RTP sequence number is provide in Real-time Transport Protocol (RTP) [RFC3550].
The RTCP XR Report Block containing the measurement information is intended to provide a single copy of the information necessary to relate measurement data in the RTCP XR blocks to the stream, and measurement period, to which they refer. Commonly, multiple other small metric blocks contain measurement data for the same stream and period, and it would be a large overhead if all of these metric blocks carried duplicated data for measurement identification.
The RTCP XR Report Block may be associated with a set of RTCP XR metrics blocks which share the same information relevant to a reported measurement. There may be several such sets in an RTCP packet, in which each set share the same information relevant to a reported measurement. There may also be RTCP XR blocks in the packet which are not associated with a Measurement Information block, for example blocks which were defined before the Measurement Identity and information mechanism was introduced by this document.
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] defines 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].
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 SDES item and XR Block described in this document are in accordance with [RFC6390] and [MONARCH].
The RTCP SDES item and the RTCP XR block defined in this document provides information relevant to the measurements for members of a family of RTCP XR metrics blocks which are designed to use it. To use the mechanism defined here, the RTCP XR block containing measurement information is not required to be in the same RTCP packet as the SDES item containing measurement identity.
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].
This section defines the format of the Measurement Identity SDES item. The SDES item is carried in the RTCP SDES packet. The packet format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. Each SDES packet is composed of a header with fixed-length fields for version, source count, packet type (PT), and length, followed by zero of more SDES items. In the SDES packet, the PT field is set to SDES (202).
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APSI=TBD | length |application specific identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ....
+-+-+-+-+-+-+-+-+
Application specific identifier is an additional identifier which is useful in the context of a specific application, e.g. an MPEG-2 transport identifier [MPEG2]. This item MUST be ignored by applications that are not configured to make use of it. The identifier is variable length. Its length is described by the length field. The value of the length field does not include the two octet SDES item header.
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=NMI | Reserved | block length = 7 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of stream source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | first sequence number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | extended first sequence number of interval | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | extended last sequence number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Measurement Duration (Interval) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Measurement Duration (Cumulative) - Seconds (bit 0-31) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Measurement Duration (Cumulative) - Fraction (bit 0-31) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
New SDES types for RTCP SDES are subject to IANA registration. For general guidelines on IANA considerations for RTCP SDES, refer to [RFC3550].
abbrev. name value APSI: Application Specific Identifier TBD
This document assigns one additional SDES type in the IANA "RTCP XR Block Type Registry" to the Measurement Identity SDES items as follow:
[Note to RFC Editor: please replace APSI with the IANA provided RTCP SDES type for the SDES item.]
This document assigns the block type value NMI in the IANA "RTCP XR Block Type Registry" to the "Measurement Information Block".
[Note to RFC Editor: please replace NMI with the IANA provided RTCP XR block type for this block.]
The contact information for the registrations is: Qin Wu (sunseawq@huawei.com) 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
RTCP reports can contain sensitive information, including information about the nature and duration of a session established between two or more endpoints. Therefore, the use of security mechanisms with RTP, as documented in Section 9 of [RFC3550] applies.
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", March 1997. |
| [RFC5905] | Mills, D., Matin, J., Burbank, J. and W. Kasch, "Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, June 2010. |
| [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. |
| [MONARCH] | Wu, Q., Hunt, G., "Monitoring Architectures for RTP", ID draft-ietf-avtcore-monarch-17, June 2012. |
| [MPEG2] | ISO/IEC, "Standard 13818-1"", December 2000. | , "
| [RFC6390] | Clark, A. and B. Claise, "Framework for Performance Metric Development", RFC 6390, October 2011. |
Note to the RFC-Editor: please remove this section prior to publication as an RFC.
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-08:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-07:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-06:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-05:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-04:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-03:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-02:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-01:
The following are the major changes to draft-ietf-xrblock-xr-rtcp-meas-identity-00:
The following are the major changes to draft-ietf-avt-rtcp-xr-meas-identity-02: