draft-ietf-xrblock-rtcp-xr-meas-identity-00.txt   draft-ietf-xrblock-rtcp-xr-meas-identity-01.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: March 29, 2012 Telchemy Expires: April 15, 2012 Telchemy
Q. Wu Q. Wu
Huawei Huawei
September 26, 2011 October 13, 2011
RTCP Source Description (SDES) items for Measurement Identity Measurement Identity and information Reporting using SDES item and XR
draft-ietf-xrblock-rtcp-xr-meas-identity-00.txt Block
draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
Abstract Abstract
This document defines RTCP SDES items carrying parameters which This document defines a RTCP SDES item and a RTCP XR Block carrying
identify a measurement, to which one or more other RTCP XR Report parameters which identify a measurement, to which one or more other
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
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 March 29, 2012. This Internet-Draft will expire on April 15, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.1. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4
2. Measurement Identity SDES Items . . . . . . . . . . . . . . . 4 1.2. Performance Metrics Framework . . . . . . . . . . . . . . 4
2.1. APSI: Application Specific Identifier SDES Item . . . . . 4 1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2.2. EXFS: extended first sequence number SDES Item . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. EXLS: extended last sequence number SDES Item . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
2.4. CUMD: Cumulative Measurement Duration SDES Item . . . . . 5 3. Measurement Identity SDES Item . . . . . . . . . . . . . . . . 6
2.5. INMD: Interval Measurement Duration SDES Item . . . . . . 5 3.1. APSI: Application Specific Identifier SDES Item . . . . . 6
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. Measurement Information XR Block . . . . . . . . . . . . . . . 7
3.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 6 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7
3.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 6 4.2. Definition of Fields in Measurement Information Report
3.3. Contact information for registrations . . . . . . . . . . 6 Block . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5.1. New RTCP SDES Type value . . . . . . . . . . . . . . . . . 9
5.1. Normative References . . . . . . . . . . . . . . . . . . . 8 5.2. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9
5.2. Informative References . . . . . . . . . . . . . . . . . . 8 5.3. Contact information for registrations . . . . . . . . . . 9
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
A.1. draft-ietf-xrblock-rtcp-sdes-meas-identity-00 . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 12
A.1. draft-ietf-xrblock-xr-rtcp-meas-identity-00 . . . . . . . 12
A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01 . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
This draft defines new RTCP SDES items to carry parameters which This draft defines one new RTCP SDES item and one new XR Report Block
identify a measurement for use in a range of RTP applications. These to carry parameters which identify a measurement for use in a range
SDES items do not itself contain any measurement results (metrics). of RTP applications. The SDES item and the XR Report Block do not
However, they provide information relevant to a measurement reported itself contain any measurement results (metrics).However, they
in one or more other block types, including provide information relevant to a measurement reported in one or more
other block types, including
o a field for incorporation of an application-specific auxiliary o a field for incorporation of an application-specific auxiliary
identifier, 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].
The RTCP SDES packet containing these item is intended to provide a The RTCP SDES item containing the measurement identity is intended to
single copy of the information necessary to relate measurement data provide information to relate RTP to a non-RTP session while the RTCP
in the RTCP XR blocks to the stream, and measurement period, to which XR Report Block containing the measurement information is intended to
they refer. Commonly, multiple other small metric blocks contain provide a single copy of the information necessary to relate
measurement data for the same stream and period, and it would be a measurement data in the RTCP XR blocks to the stream, and measurement
large overhead if all of these metric blocks carried duplicated data period, to which they refer. Commonly, multiple other small metric
for measurement identification. Other blocks make a reference to blocks contain measurement data for the same stream and period, and
this block (by SSRC). A Measurement Identity SDES packet is it would be a large overhead if all of these metric blocks carried
associated with the set of RTCP XR metrics blocks which share the duplicated data for measurement identification.
same SSRC value. There MAY be several such sets in an RTCP packet,
up to a limit of 8 arising from the use of 3-bit tags. There MAY
also be RTCP XR blocks in the packet which are not associated with a
Measurement Identity block, for example blocks which were defined
before the Measurement Identity mechanism was introduced by this
document.
1.1. Applicability 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 RTPC SDES items provide identification information for members of The RTCP XR Report Block MAY be associated with a set of RTCP XR
a family of RTCP XR metrics blocks which are designed to use it. To metrics blocks which share the same information relevant to a
use the mechanism defined here, a metrics block must be in the same reported measurement. There MAY be several such sets in an RTCP
RTCP packet as the SDES packet for Measurement Identity. 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.
2. Measurement Identity SDES Items 1.1. RTCP and RTCP XR Reports
This section defines the format of Measurement Identity SDES items. The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
These SDES items are carried in the RTCP SDES packet. The packet defined an extensible structure for reporting using an RTCP Extended
format for the RTCP SDES is defined in Section 6.5 of [RFC3550]. Report (XR). This draft defines a new Extended Report block that
Each SDES packet has a fixed-length field for version,source count, MUST be used as defined in [RFC3550] and [RFC3611].
parcket type (PT), length as well as a variable-length field for SDES
items. In the SDES packets, the PT field is set to SDES (202).
2.1. APSI: Application Specific Identifier SDES Item 1.2. Performance Metrics Framework
The Performance Metrics Framework [PMOLFRAME] provides guidance on
the definition and specification of performance metrics. The RTP
Monitoring Architectures[MONARCH] provides guideline for reporting
block format using RTCP XR . Metrics or SDES item described in this
draft either reference external definitions or define metrics
generally in accordance with [PMOLFRAME][MONARCH].
1.3. Applicability
The RTCP SDES item and the RTCP XR block defined in this document
provides information relevant to the measurement 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 in the same RTCP packet as
the SDES item contain measurement identity.
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]
3. 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
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
type (PT), length as well as a variable-length field for the SDES
item. In the SDES packet, the PT field is set to SDES (202).
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]. Where the identifier is less than 32
bits, the identifier SHOULD be mapped into the most significant bits bits, the identifier SHOULD be mapped into the most significant bits
of the field. If no additional identifier is provided, all bits of of the field. If no additional identifier is provided, all bits of
the field MUST be set to zero. This field MUST be ignored by the field MUST be set to zero. This item MUST be ignored by
applications which are not configured to make use of it. applications which are not configured to make use of it.
2.2. EXFS: extended first sequence number SDES Item 4. Measurement Information XR Block
0 1 2 3 4.1. Report Block Structure
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 | extended first sequence number
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| of interval ....
+-+-+-+-+-+-+-+-+
The RTP sequence number of the first received RTP packet of the 0 1 2 3
session, used to determine the number of packets contributing to 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
cumulative measurements. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NMI | Rsv. | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of stream source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | first seq num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended first sequence number of interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended last sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Cumulative) (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Interval) (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2.3. EXLS: extended last sequence number SDES Item Report Block Structure
0 1 2 3 4.2. Definition of Fields in Measurement Information Report Block
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 | extended last sequence number
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ....
+-+-+-+-+-+-+-+-+
The extended RTP sequence number of the last received RTP packet Block type (BT): 8 bits
which contributed to this measurement.
2.4. CUMD: Cumulative Measurement Duration SDES Item A Measurement Information Report Block is identified by the
constant NMI.
0 1 2 3 [Note to RFC Editor: please replace NMI with the IANA provided
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 RTCP XR block type for this block.]
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APSI=TBD | length | Measurement Duration (Cumulative)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (ms) ....
+-+-+-+-+-+-+-+-+
The duration in ms of the reporting interval applicable to Cumulative Rsv.: 8 bits
reports which use this Measurement Identity block.
2.5. INMD: Interval Measurement Duration SDES Item 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
MUST be ignored by the receiver.
0 1 2 3 Block Length: 16 bits
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 | Measurement Duration (Interval)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (ms) ....
+-+-+-+-+-+-+-+-+
The duration in ms of the reporting interval applicable to Interval The length of this report block in 32-bit words minus one. For
reports which use this Measurement Identity block. the Measurement Information block, the block length is equal to 7.
3. IANA Considerations SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611].
Reserved: 16 bits
These bits are reserved. They MUST be ignored by receivers. They
MUST be set to zero by senders.
First seq num: 16 bits
The RTP sequence number of the first received RTP packet of the
session, used to determine the number of packets contributing to
cumulative measurements.
Extended first sequence number of interval: 32 bits
The extended RTP sequence number of the first received RTP packet
of the current measurement interval.
Extended last sequence number: 32 bits
The extended RTP sequence number of the last received RTP packet
which contributed to this measurement.
Measurement Duration (Cumulative) (ms): 32 bits
The duration in ms of the reporting interval applicable to
Cumulative reports which use this Measurement Information block.
Measurement Duration (Interval) (ms): 32 bits
The duration in ms of the reporting interval applicable to
Interval reports which use this Measurement Information block.
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].
3.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 additional five SDES types 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
EXFS: extended first sequence number TBD
EXLS: extended last sequence number TBD
CUMD: Cumulative Measurement Duration TBD
INMD: Interval Measurement Duration TBD
[Note to RFC Editor: please replace APSI,EXF,EXLS,CUMD,INMD with the [Note to RFC Editor: please replace APSI with the IANA provided RTCP
IANA provided RTCP SDES type for these SDES items.] SDES type for the SDES item.]
3.2. New RTCP XR SDP Parameter 5.2. New RTCP XR Block Type value
This document also registers a new parameter "jitter-bfr" in the This document assigns the block type value NMI in the IANA "RTCP XR
"RTCP XR SDP Parameters Registry". Block Type Registry" to the "Measurement Information Block".
3.3. Contact information for registrations [Note to RFC Editor: please replace NMI with the IANA provided RTCP
XR block type for this block.]
5.3. Contact information for registrations
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
4. 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.
5. References 7. References
5.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.
5.2. Informative References [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003.
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] [PMOLFRAME]
Clark, A. and B. Claise, "Framework for Performance Metric Clark, A. and B. Claise, "Framework for Performance Metric
Development", ID draft-ietf-pmol-metrics-framework-12, Development", ID draft-ietf-pmol-metrics-framework-12,
July 2011. 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-rtcp-sdes-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:
o Change the use of SDES item to convey measurement identity instead o Change the use of SDES item to convey measurement identity instead
of XR Block in section 2. of XR Block in section 2.
o Update references. o Update references.
o Update security section and remove SDP signaling section. o Update security section and remove SDP signaling section.
A.2. draft-ietf-xrblock-xr-rtcp-meas-identity-01
The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-00:
o Replace SDES item containing additional measurement information
with XR Block.
o Add section 2 to describe following RFC2119 language.
o Add Section 1.2 to make SDES item and XR Report be compliant with
RFC3550 and RFC3611
o Add Section 1.3 to make SDES item and XR Report follow Performance
Metrics Framework and RTP Monitoring Architecture.
o Add section5.2 to register the new RTCP XR Block Type value.
o Remove RTCP SDES Type values that are needed.
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. 39 change blocks. 
118 lines changed or deleted 207 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/