draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt   draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: April 15, 2012 Telchemy Expires: July 15, 2012 Telchemy
Q. Wu Q. Wu
Huawei Huawei
October 13, 2011 January 12, 2012
Measurement Identity and information Reporting using SDES item and XR Measurement Identity and information Reporting using SDES item and XR
Block Block
draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt
Abstract Abstract
This document defines a RTCP SDES item and a RTCP XR Block carrying This document defines a RTCP SDES item and a RTCP XR Block carrying
parameters which identify a measurement, to which one or more other parameters which identify a measurement, to which one or more other
RTCP XR Report Blocks may refer. RTCP XR Report Blocks may refer.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 15, 2012. This Internet-Draft will expire on July 15, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 32 skipping to change at page 2, line 32
5.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 9 5.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 9
5.2. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 5.2. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9
5.3. Contact information for registrations . . . . . . . . . . 9 5.3. Contact information for registrations . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12
A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 12 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 12
A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 12 A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
This draft defines one new RTCP SDES item and one new XR Report Block This draft defines one new RTCP SDES item and one new XR Report Block
to carry parameters which identify a measurement for use in a range to carry parameters which identify a measurement for use in a range
of RTP applications. The SDES item and the XR Report Block do not of RTP applications. The XR Report Block and the SDES item do not
itself contain any measurement results (metrics).However, they contain any measurement results (metrics). However, the XR Report
provide information relevant to a measurement reported in one or more Block provides information relevant to a measurement reported in one
other block types, including or more other block types, including
o a field for incorporation of an application-specific auxiliary
identifier,
o the sequence number of the first packet of the RTP session, o the sequence number of the first packet of the RTP session,
o the extended sequence numbers of the first packet of the current o the extended sequence numbers of the first packet of the current
measurement interval, and the last packet included in the measurement interval, and the last packet included in the
measurement, measurement,
o the duration of the most recent measurement interval and o the duration of the most recent measurement interval and
o the duration of the interval applicable to cumulative measurements o the duration of the interval applicable to cumulative measurements
(which may be the duration of the RTP session to date). (which may be the duration of the RTP session to date).
The method for calculation of the extended RTP sequence number is The method for calculation of the extended RTP sequence number is
provide in [RFC3550]. provide in [RFC3550].
And the SDES item provides a measurement identity reported in one or
more other block types, i.e.,a field for incorporation of an
application-specific auxiliary identifier,
The RTCP SDES item containing the measurement identity is intended to The RTCP SDES item containing the measurement identity is intended to
provide information to relate RTP to a non-RTP session while the RTCP provide information to relate RTP to a non-RTP session while the RTCP
XR Report Block containing the measurement information is intended to XR Report Block containing the measurement information is intended to
provide a single copy of the information necessary to relate provide a single copy of the information necessary to relate
measurement data in the RTCP XR blocks to the stream, and measurement measurement data in the RTCP XR blocks to the stream, and measurement
period, to which they refer. Commonly, multiple other small metric period, to which they refer. Commonly, multiple other small metric
blocks contain measurement data for the same stream and period, and blocks contain measurement data for the same stream and period, and
it would be a large overhead if all of these metric blocks carried it would be a large overhead if all of these metric blocks carried
duplicated data for measurement identification. duplicated data for measurement identification.
skipping to change at page 4, line 14 skipping to change at page 4, line 15
1.1. RTCP and RTCP XR Reports 1.1. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611]. MUST be used as defined in [RFC3550] and [RFC3611].
1.2. Performance Metrics Framework 1.2. Performance Metrics Framework
The Performance Metrics Framework [PMOLFRAME] provides guidance on The Performance Metrics Framework [RFC6390] provides guidance on the
the definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures[MONARCH] provides guideline for reporting Monitoring Architectures[MONARCH] provides guideline for reporting
block format using RTCP XR . Metrics or SDES item described in this block format using RTCP XR . Metrics or the SDES item described in
draft either reference external definitions or define metrics this draft either reference external definitions or define metrics
generally in accordance with [PMOLFRAME][MONARCH]. generally in accordance with [RFC6390] and [MONARCH].
1.3. Applicability 1.3. Applicability
The RTCP SDES item and the RTCP XR block defined in this document The RTCP SDES item and the RTCP XR block defined in this document
provides information relevant to the measurement for members of a provides information relevant to the measurement for members of a
family of RTCP XR metrics blocks which are designed to use it. To family of RTCP XR metrics blocks which are designed to use it. To
use the mechanism defined here, the RTCP XR block containing use the mechanism defined here, the RTCP XR block containing
measurement information is not required in the same RTCP packet as measurement information is not required to be in the same RTCP packet
the SDES item contain measurement identity. as the SDES item containing measurement identity.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119] document are to be interpreted as described in RFC 2119 [RFC2119]
3. Measurement Identity SDES Item 3. Measurement Identity SDES Item
This section defines the format of Measurement Identity SDES item. This section defines the format of Measurement Identity SDES item.
The SDES item is carried in the RTCP SDES packet. The packet format 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 for the RTCP SDES is defined in Section 6.5 of [RFC3550]. Each SDES
packet has a fixed-length field for version, source count, packet packet is composed of a header with fixed-length fields for version,
type (PT), length as well as a variable-length field for the SDES source count, packet type (PT), and length, followed by zero of more
item. In the SDES packet, the PT field is set to SDES (202). SDES items. In the SDES packet, the PT field is set to SDES (202).
3.1. APSI: Application Specific Identifier SDES Item 3.1. APSI: Application Specific Identifier SDES Item
0 1 2 3 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 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 | APSI=TBD | length |application specific identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .... | ....
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Application specific identifier is an additional identifier which is Application specific identifier is an additional identifier which is
useful in the context of a specific application, e.g. an MPEG-2 useful in the context of a specific application, e.g. an MPEG-2
transport identifier [MPEG2]. Where the identifier is less than 32 transport identifier [MPEG2]. The identifier is variable length.
bits, the identifier SHOULD be mapped into the most significant bits Its length is described by the length field. The value of the length
of the field. If no additional identifier is provided, all bits of field does not include the two octet SDES item header. If no
the field MUST be set to zero. This item MUST be ignored by identifier is provided, the length field MUST be set to zero. This
applications which are not configured to make use of it. item MUST be ignored by applications that are not configured to make
use of it.
4. Measurement Information XR Block 4. Measurement Information XR Block
4.1. Report Block Structure 4.1. Report Block Structure
0 1 2 3 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 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 | Rsv. | block length = 6 | | BT=NMI | Reserved | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of stream source | | SSRC of stream source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | first seq num | | Reserved | first sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended first sequence number of interval | | extended first sequence number of interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended last sequence number | | extended last sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Cumulative) (ms) | | Measurement Duration (Cumulative) (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Interval) (ms) | | Measurement Duration (Interval) (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 39 skipping to change at page 7, line 39
4.2. Definition of Fields in Measurement Information Report Block 4.2. Definition of Fields in Measurement Information Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Measurement Information Report Block is identified by the A Measurement Information Report Block is identified by the
constant NMI. constant NMI.
[Note to RFC Editor: please replace NMI with the IANA provided [Note to RFC Editor: please replace NMI with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Rsv.: 8 bits Reserved.: 8 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
MUST be ignored by the receiver. MUST be ignored by the receiver.
Block Length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words minus one. For The length of this report block in 32-bit words minus one. For
the Measurement Information block, the block length is equal to 7. the Measurement Information block, the block length is equal to 6.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
Reserved: 16 bits Reserved: 16 bits
These bits are reserved. They MUST be ignored by receivers. They These bits are reserved. They MUST be ignored by receivers. They
MUST be set to zero by senders. MUST be set to zero by senders.
First seq num: 16 bits First sequence number: 16 bits
The RTP sequence number of the first received RTP packet of the The RTP sequence number of the first received RTP packet of the
session, used to determine the number of packets contributing to session, used to determine the number of packets contributing to
cumulative measurements. cumulative measurements.
Extended first sequence number of interval: 32 bits Extended first sequence number of interval: 32 bits
The extended RTP sequence number of the first received RTP packet The extended RTP sequence number of the first received RTP packet
of the current measurement interval. of the current measurement interval.
Extended last sequence number: 32 bits Extended last sequence number: 32 bits
The extended RTP sequence number of the last received RTP packet The extended RTP sequence number of the last received RTP packet
which contributed to this measurement. which contributed to this measurement.
Measurement Duration (Cumulative) (ms): 32 bits Measurement Duration (Cumulative) (ms): 32 bits
The duration in ms of the reporting interval applicable to The duration in ms of the reporting interval applicable to
Cumulative reports which use this Measurement Information block. Cumulative reports which use this Measurement Information block.
The value of this field can be calculated by receiver, for
example, based on received RTP media packets or using RTCP method
described in [RFC3550].
Measurement Duration (Interval) (ms): 32 bits Measurement Duration (Interval) (ms): 32 bits
The duration in ms of the reporting interval applicable to The duration in ms of the reporting interval applicable to
Interval reports which use this Measurement Information block. Interval reports which use this Measurement Information block.
The value of this field can be calculated by receiver, for
example, based on received RTP media packets or using RTCP method
described in [RFC3550].
5. IANA Considerations 5. IANA Considerations
New SDES types for RTCP SDES are subject to IANA registration. For New SDES types for RTCP SDES are subject to IANA registration. For
general guidelines on IANA considerations for RTCP SDES, refer to general guidelines on IANA considerations for RTCP SDES, refer to
[RFC3550]. [RFC3550].
5.1. New RTCP SDES Type value 5.1. New RTCP SDES Type value
This document assigns additional five SDES types in the IANA "RTCP XR This document assigns one additional SDES type in the IANA "RTCP XR
Block Type Registry" to the Measurement Identity SDES items as Block Type Registry" to the Measurement Identity SDES items as
follow: follow:
abbrev. name value abbrev. name value
APSI: Application Specific Identifier TBD APSI: Application Specific Identifier TBD
[Note to RFC Editor: please replace APSI with the IANA provided RTCP [Note to RFC Editor: please replace APSI with the IANA provided RTCP
SDES type for the SDES item.] SDES type for the SDES item.]
5.2. New RTCP XR Block Type value 5.2. New RTCP XR Block Type value
skipping to change at page 10, line 9 skipping to change at page 10, line 9
Qin Wu (sunseawq@huawei.com) Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
6. Security Considerations 6. Security Considerations
RTCP reports can contain sensitive information since they can provide RTCP reports can contain sensitive information since they can provide
information about the nature and duration of a session established information about the nature and duration of a session established
between two or more endpoints.Therefore, the use of security between two or more endpoints. Therefore, the use of security
mechanisms with RTP documented in Section 9 of [RFC3550] should mechanisms with RTP documented in Section 9 of [RFC3550] should
apply. apply.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
skipping to change at page 11, line 25 skipping to change at page 11, line 25
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
7.2. Informative References 7.2. Informative References
[MONARCH] Wu, Q., "Monitoring Architectures for RTP", [MONARCH] Wu, Q., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-04, August 2011. ID draft-ietf-avtcore-monarch-04, August 2011.
[MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000.
[PMOLFRAME] [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Clark, A. and B. Claise, "Framework for Performance Metric Development", RFC 6390, October 2011.
Development", ID draft-ietf-pmol-metrics-framework-12,
July 2011.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00
The following are the major changes to The following are the major changes to
draft-ietf-avt-rtcp-xr-meas-identity-02: draft-ietf-avt-rtcp-xr-meas-identity-02:
skipping to change at page 13, line 5 skipping to change at page 12, line 42
o Add Section 1.2 to make SDES item and XR Report be compliant with o Add Section 1.2 to make SDES item and XR Report be compliant with
RFC3550 and RFC3611 RFC3550 and RFC3611
o Add Section 1.3 to make SDES item and XR Report follow Performance o Add Section 1.3 to make SDES item and XR Report follow Performance
Metrics Framework and RTP Monitoring Architecture. Metrics Framework and RTP Monitoring Architecture.
o Add section5.2 to register the new RTCP XR Block Type value. o Add section5.2 to register the new RTCP XR Block Type value.
o Remove RTCP SDES Type values that are needed. o Remove RTCP SDES Type values that are needed.
A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02
The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-01:
o Relocating information that belong to SDES item and XR Block
respectively in the section 1.
o Rephrasing the text that describes SDES packet composition.
o Rephrasing identifier description.
o Other Editorial changes.
Authors' Addresses Authors' Addresses
Geoff Hunt Geoff Hunt
Unaffiliated Unaffiliated
Email: r.geoff.hunt@gmail.com Email: r.geoff.hunt@gmail.com
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
 End of changes. 24 change blocks. 
39 lines changed or deleted 60 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/