draft-ietf-xrblock-rtcp-xr-meas-identity-02.txt   draft-ietf-xrblock-rtcp-xr-meas-identity-03.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: July 15, 2012 Telchemy Expires: September 30, 2012 Telchemy
Q. Wu Q. Wu
Huawei Huawei
January 12, 2012 March 29, 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-02.txt draft-ietf-xrblock-rtcp-xr-meas-identity-03.txt
Abstract Abstract
This document defines a RTCP SDES item and a RTCP XR Block carrying This document defines an RTCP SDES item and an RTCP XR Block carrying
parameters which identify a measurement, to which one or more other parameters that identify and describe a measurement period, to which
RTCP XR Report Blocks may refer. one or more other 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 15, 2012. This Internet-Draft will expire on September 30, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
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
A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 12 A.3. draft-ietf-xrblock-xr-rtcp-meas-identity-02 . . . . . . . 12
A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-03 . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 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 carrying parameters that identify and describe a measurement period,
of RTP applications. The XR Report Block and the SDES item do not to which one or more other RTCP XR Report Blocks may refer.
contain any measurement results (metrics). However, the XR Report
Block provides information relevant to a measurement reported in one The SDES item provides a field for an application specific auxiliary
or more other block types, including 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). Rather, it provide information relevant to a measurement
reported in one or more other block types, including:
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 The RTCP XR Report Block containing the measurement information is
more other block types, i.e.,a field for incorporation of an intended to provide a single copy of the information necessary to
application-specific auxiliary identifier, relate measurement data in the RTCP XR blocks to the stream, and
measurement period, to which they refer. Commonly, multiple other
The RTCP SDES item containing the measurement identity is intended to small metric blocks contain measurement data for the same stream and
provide information to relate RTP to a non-RTP session while the RTCP period, and it would be a large overhead if all of these metric
XR Report Block containing the measurement information is intended to blocks carried duplicated data for measurement identification.
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.
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 RTCP XR Report Block MAY be associated with a set of RTCP XR The RTCP XR Report Block MAY be associated with a set of RTCP XR
metrics blocks which share the same information relevant to a metrics blocks which share the same information relevant to a
reported measurement. There MAY be several such sets in an RTCP reported measurement. There MAY be several such sets in an RTCP
packet, in which each set share the same information relevant to a packet, in which each set share the same information relevant to a
reported measurement. There MAY also be RTCP XR blocks in the packet reported measurement. There MAY also be RTCP XR blocks in the packet
which are not associated with a Measurement Information block, for which are not associated with a Measurement Information block, for
example blocks which were defined before the Measurement Identity and example blocks which were defined before the Measurement Identity and
information mechanism was introduced by this document. information mechanism was introduced by this document.
skipping to change at page 4, line 18 skipping to change at page 4, line 17
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 [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on 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 the SDES item described in block format using RTCP XR . The SDES item and XR Block described in
this draft either reference external definitions or define metrics this draft are in accordance with [RFC6390] and [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 measurements 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 to be in the same RTCP packet measurement information is not required to be in the same RTCP packet
as the SDES item containing 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 the Measurement Identity SDES
The SDES item is carried in the RTCP SDES packet. The packet format item. The SDES item is carried in the RTCP SDES packet. The packet
for the RTCP SDES is defined in Section 6.5 of [RFC3550]. Each SDES format for the RTCP SDES is defined in Section 6.5 of [RFC3550].
packet is composed of a header with fixed-length fields for version, Each SDES packet is composed of a header with fixed-length fields for
source count, packet type (PT), and length, followed by zero of more version, source count, packet type (PT), and length, followed by zero
SDES items. In the SDES packet, the PT field is set to SDES (202). of more 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]. The identifier is variable length. transport identifier [MPEG2]. This item MUST be ignored by
Its length is described by the length field. The value of the length applications that are not configured to make use of it. The
field does not include the two octet SDES item header. If no identifier is variable length. Its length is described by the length
identifier is provided, the length field MUST be set to zero. This field. The value of the length field does not include the two octet
item MUST be ignored by applications that are not configured to make SDES item header. If no identifier is provided, the length field
use of it. MUST be set to zero.
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 | Reserved | block length = 6 | | BT=NMI | Reserved | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 41 skipping to change at page 7, line 41
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.]
Reserved.: 8 bits Reserved.: 8 bits
This field is reserved for future definition. In the absence of These bits are reserved. They MUST be set to zero by senders and
such a definition, the bits in this field MUST be set to zero and ignored by receivers.
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 6. 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 set to zero by senders and
MUST be set to zero by senders. ignored by receivers.
First sequence number: 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
skipping to change at page 8, line 34 skipping to change at page 8, line 34
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 The value of this field can be calculated by the receiver of the
example, based on received RTP media packets or using RTCP method RTP media stream, for example, based on received RTP media packets
described in [RFC3550]. 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 The value of this field can be calculated by the receiver of the
example, based on received RTP media packets or using RTCP method RTP media stream, for example, based on received RTP media packets
described in [RFC3550]. 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 one additional SDES type in the IANA "RTCP XR This document assigns one additional SDES type in the IANA "RTCP XR
skipping to change at page 10, line 7 skipping to change at page 10, line 7
The contact information for the registrations is: The contact information for the registrations is:
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, including information
information about the nature and duration of a session established about the nature and duration of a session established between two or
between two or more endpoints. Therefore, the use of security more endpoints. Therefore, the use of security mechanisms with RTP,
mechanisms with RTP documented in Section 9 of [RFC3550] should as 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.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
[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., Hunt, G., and P. , "Monitoring Architectures for
ID draft-ietf-avtcore-monarch-04, August 2011. RTP", ID draft-ietf-avtcore-monarch-11, March 2012.
[MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000. [MPEG2] "ISO/IEC, "Standard 13818-1"", December 2000.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 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.
skipping to change at page 14, line 5 skipping to change at page 13, line 9
o Relocating information that belong to SDES item and XR Block o Relocating information that belong to SDES item and XR Block
respectively in the section 1. respectively in the section 1.
o Rephrasing the text that describes SDES packet composition. o Rephrasing the text that describes SDES packet composition.
o Rephrasing identifier description. o Rephrasing identifier description.
o Other Editorial changes. o Other Editorial changes.
A.4. draft-ietf-xrblock-xr-rtcp-meas-identity-03
The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-02:
o The 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. 19 change blocks. 
63 lines changed or deleted 68 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/