draft-ietf-xrblock-rtcp-xr-burst-gap-discard-03.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.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: October 20, 2012 Telchemy Expires: January 11, 2013 Telchemy
R. Huang R. Huang
Q. Wu, Ed. Q. Wu, Ed.
Huawei Huawei
April 18, 2012 July 10, 2012
RTCP XR Report Block for Burst/Gap Discard metric Reporting RTCP XR Report Block for Burst/Gap Discard metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-03.txt draft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of Burst and Gap Discard metrics for use in a range of RTP reporting of Burst and Gap Discard metrics for use in a range of RTP
applications. applications.
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 October 20, 2012. This Internet-Draft will expire on January 11, 2013.
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 13 skipping to change at page 2, line 13
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. Burst and Gap Discard Report Block . . . . . . . . . . . . 3 1.1. Burst and Gap Discard Report Block . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Burst/Gap Discard Block . . . . . . . . . . . . . . . . . . . 6 3. Burst/Gap Discard Block . . . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Burst/Gap Discard Report Block . . 6 3.2. Definition of Fields in Burst/Gap Discard Report Block . . 5
3.3. Derived metrics based on reported metrics . . . . . . . . 8 3.3. Derived metrics based on reported metrics . . . . . . . . 7
4. Considerations for Voice-over-IP applications . . . . . . . . 9 4. Considerations for Voice-over-IP applications . . . . . . . . 8
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
6.3. Contact information for registrations . . . . . . . . . . 11 6.3. Contact information for registrations . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
9. Changes from previous version . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
1.1. Burst and Gap Discard Report Block 1.1. Burst and Gap Discard Report Block
This draft defines a new block type to augment those defined in This document defines a new block type to augment those defined in
[RFC3611] for use in a range of RTP applications. The new block type [RFC3611] for use in a range of RTP applications. The new block type
supports the reporting of the proportion of packets discarded by the supports the reporting of the proportion of packets discarded by the
receiver due to jitter. The discards during discard bursts are receiver due to jitter. The discards during discard bursts are
reported, together with the number of bursts and additional data reported, together with the number of bursts. This block is intended
allowing the calculation of statistical parameters (mean and to be used in conjunction with [DISCARD] which provides the total
variance) of the distribution of burst lengths. This block is packets discarded, and on which this block therefore depends.
intended to be used in conjunction with [DISCARD] which provides the
total packets discarded, and on which this block therefore depends.
However the metric in [DISCARD] may be used independently of the However the metric in [DISCARD] may be used independently of the
metrics in this block. metrics in this block.
This block provides information on transient IP problems. Burst/Gap This block provides information on transient IP problems. Burst/Gap
metrics are typically used in Cumulative reports however MAY be used metrics are typically used in Cumulative reports however MAY be used
in Interval reports. The burstiness of packet discard affects user in Interval reports. The burstiness of packet discard affects user
experience, may influence any sender strategies to mitigate the experience, may influence any sender strategies to mitigate the
problem, and may also have diagnostic value. problem, and may also have diagnostic value.
The metric belongs to the class of transport-related terminal metrics The metric belongs to the class of transport-related terminal metrics
defined in [MONARCH] (work in progress). defined in [MONARCH] .
The definitions of Burst, Gap, Loss and Discard are consistent with The definitions of Burst, Gap, Loss and Discard are consistent with
definitions in [RFC3611]. To accommodate the range of jitter buffer definitions in [RFC3611]. To accommodate the range of jitter buffer
algorithms and packet discard logic that may be used by implementors, algorithms and packet discard logic that may be used by implementors,
the method used to distinguish between bursts and gaps may be an the method used to distinguish between bursts and gaps may be an
equivalent method to that defined in[RFC3611] . equivalent method to that defined in[RFC3611] .
1.2. RTCP and RTCP XR Reports 1.2. 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 document defines a new Extended Report block. The
MUST be used as defined in [RFC3550] and [RFC3611]. use of Extended Report blocks is defined by [RFC3611].
1.3. Performance Metrics Framework 1.3. 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. Metrics definition and specification of performance metrics. Metrics
described in this draft either reference external definitions or described in this draft either reference external definitions or
define metrics generally in accordance with the guidelines in define metrics generally in accordance with the guidelines in
[RFC6390]. [RFC6390].
1.4. Applicability 1.4. Applicability
skipping to change at page 5, line 19 skipping to change at page 4, line 19
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].
In addition, the following terms are defined: In addition, the following terms are defined:
Received, Lost and Discarded Received, Lost and Discarded
A packet shall be regarded as lost if it fails to arrive within an A packet shall be regarded as lost if it fails to arrive within an
implementation-specific time window. A packet that arrives within implementation-specific time window. A packet that arrives within
this time window but is too early or late to be played out shall this time window but is too early or late to be played out or
be regarded as discarded. A packet shall be classified as one of thrown away before playout (e.g., packet duplication or
received (or OK), discarded or lost. redundancy) shall be regarded as discarded. A packet shall be
classified as one of received (or OK), discarded or lost.
Bursts and Gaps Bursts and Gaps
The terms Burst and Gap are used in a manner consistent with that The terms Burst and Gap are used in a manner consistent with that
of RTCP XR [RFC3611]. RTCP XR views a RTP stream as being divided of RTCP XR [RFC3611]. RTCP XR views a RTP stream as being divided
into bursts, which are periods during which the discard rate is into bursts, which are periods during which the discard rate is
high enough to cause noticeable quality degradation (generally high enough to cause noticeable quality degradation (generally
over 5 percent discard rate), and gaps, which are periods during over 5 percent discard rate), and gaps, which are periods during
which discarded packets are infrequent and hence quality is which discarded packets are infrequent and hence quality is
generally acceptable. generally acceptable.
skipping to change at page 6, line 17 skipping to change at page 5, line 17
Metrics in this block report on Burst/Gap Discard in the stream Metrics in this block report on Burst/Gap Discard in the stream
arriving at the RTP system. arriving at the RTP system.
3.1. Report Block Structure 3.1. Report Block Structure
Burst/Gap Discard metrics block Burst/Gap Discard metrics block
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=NBGD |I| resv. | block length = 3 | | BT=NBGD | I | resv. | block length = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Packets Discarded in Bursts | | Threshold | Packets Discarded in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Total Packets expected in bursts | Reserved. | | Total Packets expected in bursts | Reserved. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Burst/Gap Discard Report Block 3.2. Definition of Fields in Burst/Gap Discard Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Burst/Gap Discard Report Block is identified by the constant A Burst/Gap Discard Report Block is identified by the constant
NBGD. NBGD.
[Note to RFC Editor: please replace NBGD with the IANA provided [Note to RFC Editor: please replace NBGD with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 1 bit Interval Metric flag (I): 2 bits
This field is used to indicate whether the Packet Delay Variation This field is used to indicate whether the Burst/Gap Discard
metrics block is an Interval or a Cumulative report, that is, metrics are Sampled, Interval or Cumulative metrics, that is,
whether the reported values apply to the most recent measurement whether the reported values applies to the most recent measurement
interval duration between successive metrics reports (I=1) (the interval duration between successive metrics reports (I=10) (the
Interval Duration) or to the accumulation period characteristic of Interval Duration) or to the accumulation period characteristic of
cumulative measurements (I=0) (the Cumulative Duration). cumulative measurements (I=11) (the Cumulative Duration) or is a
sampled instantaneous value (I=01) (Sampled Value).
Reserved (resv): 7 bits Reserved (resv): 6 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
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 Delay block, the block length is equal to 3. the Delay block, the block length is equal to 3.
SSRC of source: 32 bits SSRC of source: 32 bits
skipping to change at page 8, line 7 skipping to change at page 7, line 7
be reported to indicate an over-range measurement. If the be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFFFF SHOULD be reported.
Reserved (resv): 8 bits Reserved (resv): 8 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
3.3. Derived metrics based on reported metrics 3.3. Derived metrics based on reported metrics
The metrics described here are intended to be used as described in The metrics described here are intended to be used in conjunction
this section, in conjunction with information from the Measurement with information from the Measurement Information block [MEASID],
Information block [MEASID], discard block [DISCARD] (which MUST be discard block [DISCARD] (which MUST be present in the same RTCP
present in the same RTCP packet as the Burst/Gap Discard block). packet as the Burst/Gap Discard block).
These metrics provides the following information relevant to These metrics provides the following information relevant to
statistical parameters, including: statistical parameters, including:
o The fraction of packets discarded during bursts (burst discard o The fraction of packets discarded during bursts (burst discard
rate in [SUMSTAT]) rate in [SUMSTAT])
o The fraction of packets discarded during gaps (gap discard rate in o The fraction of packets discarded during gaps (gap discard rate in
[SUMSTAT]) [SUMSTAT])
skipping to change at page 9, line 18 skipping to change at page 8, line 18
Where the metric is used with a Voice-overIP (VoIP) application, the Where the metric is used with a Voice-overIP (VoIP) application, the
following considerations apply. following considerations apply.
RTCP XR views a call as being divided into bursts, which are periods RTCP XR views a call as being divided into bursts, which are periods
during which the discard rate is high enough to cause noticeable call during which the discard rate is high enough to cause noticeable call
quality degradation (generally over 5 percent discard rate), and quality degradation (generally over 5 percent discard rate), and
gaps, which are periods during which discarded packets are infrequent gaps, which are periods during which discarded packets are infrequent
and hence call quality is generally acceptable. and hence call quality is generally acceptable.
If Voice Activity Detection is used the Burst and Gap Duration shall If Voice Activity Detection is used the Burst and Gap Duration shall
be determined as if silence frames had been sent, i.e. a period of be determined as if silence packets had been sent, i.e. a period of
silence in excess of Gmin frames MUST terminate a burst condition. silence in excess of Gmin packets MUST terminate a burst condition.
The recommended value for the threshold Gmin in [RFC3611] results in The recommended value for the threshold Gmin in [RFC3611] results in
a Burst being a period of time during which the call quality is a Burst being a period of time during which the call quality is
degraded to a similar extent to a typical PCM Severely Errored Second degraded to a similar extent to a typical PCM Severely Errored Second
[PSES]. [PSES].
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
skipping to change at page 11, line 13 skipping to change at page 10, line 13
xr-bgd-block = "brst-gap-dscrd" xr-bgd-block = "brst-gap-dscrd"
6. IANA Considerations 6. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611]. [RFC3611].
6.1. New RTCP XR Block Type value 6.1. New RTCP XR Block Type value
This document assigns the block type value NDEL in the IANA "RTCP XR This document assigns the block type value NBGD in the IANA "RTCP XR
Block Type Registry" to the "Burst/Gap Discard Metrics Block". Block Type Registry" to the "Burst/Gap Discard Metrics Block".
[Note to RFC Editor: please replace NBGD with the IANA provided RTCP [Note to RFC Editor: please replace NBGD with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
6.2. New RTCP XR SDP Parameter 6.2. New RTCP XR SDP Parameter
This document also registers a new parameter "brst-gap-dscrd" in the This document also registers a new parameter "brst-gap-dscrd" in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
6.3. Contact information for registrations 6.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Geoff Hunt (r.geoff.hunt@gmail.com) Qin Wu (sunseawq@huawei.com)
Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United 101 Software Avenue, Yuhua District
Kingdom Nanjing, Jiangsu 210012
China
7. Security Considerations 7. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply.
8. Contributors 8. Acknowledgments
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
9. Changes from previous version 9. References
Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009), now aligned with RFC 5234 section
3.3 "Incremental Alternatives".
Updated references.
10. References
10.1. Normative References 9.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.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
10.2. Informative References 9.2. Informative References
[DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric [DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric
Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-02, Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-02,
April 2012. April 2012.
[MEASID] Wu, Q., "Measurement Identity and information Reporting [MEASID] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-05, ID draft-ietf-xrblock-rtcp-xr-meas-identity-05,
April 2012. April 2012.
 End of changes. 24 change blocks. 
66 lines changed or deleted 58 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/