draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt   draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-06.txt 
XR Block Working Group J. Ott XR Block Working Group J. Ott
Internet-Draft V. Singh Internet-Draft V. Singh
Intended status: Standards Track Aalto University Intended status: Standards Track Aalto University
Expires: June 22, 2013 I. Curcio Expires: January 06, 2014 I. Curcio
Nokia Research Center Nokia Research Center
December 19, 2012 July 05, 2013
RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length
Encoding (RLE) of Discarded Packets Encoding (RLE) of Discarded Packets
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05.txt draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-06.txt
Abstract Abstract
The RTP Control Protocol (RTCP) is used in conjunction with the Real- The RTP Control Protocol (RTCP) is used in conjunction with the Real-
time Transport Protocol (RTP) in to provide a variety of short-term time Transport Protocol (RTP) in to provide a variety of short-term
and long-term reception statistics. The available reporting may and long-term reception statistics. The available reporting may
include aggregate information across longer periods of time as well include aggregate information across longer periods of time as well
as individual packet reporting. This document specifies a per-packet as individual packet reporting. This document specifies a per-packet
report metric capturing individual packets discarded from the jitter report metric capturing individual packets discarded from the jitter
buffer after successful reception. buffer after successful reception.
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 June 22, 2013. This Internet-Draft will expire on January 06, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. XR Discard RLE Report Block . . . . . . . . . . . . . . . . . 4 3. XR Discard RLE Report Block . . . . . . . . . . . . . . . . . 4
4. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 5 4. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 5
5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 7 5. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 7
5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7 5.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 7
5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . 7
6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 6. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8.1. XR Report Block Registration . . . . . . . . . . . . . . . 9 8.1. XR Report Block Registration . . . . . . . . . . . . . . 8
8.2. SDP Parameter Registration . . . . . . . . . . . . . . . . 9 8.2. SDP Parameter Registration . . . . . . . . . . . . . . . 8
8.3. Contact information for IANA registrations . . . . . . . . 9 8.3. Contact information for IANA registrations . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 10 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 10
A.1. changes in A.1. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00 . . . . 10 metrics-00 . . . . . . . . . . . . . . . . . . . . . . . 10
A.2. changes in A.2. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-01 . . . . 10 metrics-01 . . . . . . . . . . . . . . . . . . . . . . . 10
A.3. changes in A.3. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-02 . . . . 11 metrics-02 . . . . . . . . . . . . . . . . . . . . . . . 10
A.4. changes in A.4. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-03 . . . . 11 metrics-03 . . . . . . . . . . . . . . . . . . . . . . . 10
A.5. changes in A.5. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-04 . . . . 11 metrics-04 . . . . . . . . . . . . . . . . . . . . . . . 10
A.6. changes in A.6. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-
draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05 . . . . 11 metrics-05 . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
RTP [RFC3550] provides a transport for real-time media flows such as RTP [RFC3550] provides a transport for real-time media flows such as
audio and video together with the RTP control protocol (RTCP) which audio and video together with the RTP control protocol (RTCP) which
provides periodic feedback about the media streams received in a provides periodic feedback about the media streams received in a
specific duration. In addition, RTCP can be used for timely feedback specific duration. In addition, RTCP can be used for timely feedback
about individual events to report (e.g., packet loss) [RFC4585]. about individual events to report (e.g., packet loss) [RFC4585].
Both long-term and short-term feedback enable a sender to adapt its Both long-term and short-term feedback enable a sender to adapt its
media transmission and/or encoding dynamically to the observed path media transmission and/or encoding dynamically to the observed path
characteristics. characteristics.
RFC3611 [RFC3611] defines RTCP Extended Reports as a detailed RFC3611 [RFC3611] defines RTCP Extended Reports as a detailed
reporting framework to provide more than just the coarse RR reporting framework to provide more than just the coarse RR
statistics. The detailed reporting may enable a sender to react more statistics. The detailed reporting may enable a sender to react more
appropriately to the observed networking conditions as these can be appropriately to the observed networking conditions as these can be
characterized better, although at the expense of extra overhead. characterized better, although at the expense of extra overhead.
Among many other report blocks, RFC3611 specifies the Loss RLE block Among many other report blocks, RFC3611 specifies the Loss Run Length
which reports runs of packets received and lost with the granularity Encoding (RLE) block which reports runs of packets received and lost
of individual packets. This can help both error recovery and path with the granularity of individual packets. This can help both error
loss characterization. In addition to lost packets, RFC3611 defines recovery and path loss characterization. In addition to lost
the notion of "discarded" packets: packets that were received but packets, RFC3611 defines the notion of "discarded" packets: packets
dropped from the jitter buffer because they were either too early that were received but dropped from the jitter buffer because they
(for buffering) or too late (for playout). The "discard rate" metric were either too early (for buffering) or too late (for playout). The
is part of the VoIP metrics report block even though it is not just "discard rate" metric is part of the VoIP metrics report block even
applicable to audio: it is specified as the fraction of discarded though it is not just applicable to audio: it is specified as the
packets since the beginning of the session. See section 4.7.1 of fraction of discarded packets since the beginning of the session.
RFC3611 [RFC3611]. See section 4.7.1 of RFC3611 [RFC3611].
Recently proposed extensions to the Extended Reports (XR) reporting
suggest enhancing this discard metric:
Recently proposed extensions to the XR reporting suggest enhancing
this discard metric:
o Reporting the number of discarded packets in a measurement o Reporting the number of discarded packets in a measurement
interval, i.e., during either the last reporting interval or since interval, i.e., during either the last reporting interval or since
the beginning of the session, as indicated by a flag in the the beginning of the session, as indicated by a flag in the
suggested XR report [I-D.ietf-xrblock-rtcp-xr-discard]. If an suggested XR report [I-D.ietf-xrblock-rtcp-xr-discard]. If an
endpoint needs to report packet discard due to other reasons than endpoint needs to report packet discard due to other reasons than
early- and late-arrival (for example, discard due to duplication, early- and late-arrival (for example, discard due to duplication,
redundancy, etc.) then it should consider using the Discarded redundancy, etc.) then it should consider using the Discarded
Packets Report Block [I-D.ietf-xrblock-rtcp-xr-discard]. Packets Report Block [I-D.ietf-xrblock-rtcp-xr-discard].
o Reporting gaps and bursts of discarded packets during a o Reporting gaps and bursts of discarded packets during a
measurement interval, i.e., the last reporting interval or the measurement interval, i.e., the last reporting interval or the
duration of the session duration of the session
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard]. [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard].
However, none of these metrics allow a receiver to report precisely However, none of these metrics allow a receiver to report precisely
which packets were discarded. While this information could in theory which packets were discarded. While this information could in theory
be derived from high-frequency reporting on the number of discarded be derived from high-frequency reporting on the number of discarded
packets [I-D.ietf-xrblock-rtcp-xr-discard] or from the gap/burst packets [I-D.ietf-xrblock-rtcp-xr-discard] or from the gap/burst
report [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard], these two report [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard], these two
skipping to change at page 4, line 34 skipping to change at page 4, line 28
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119] and indicate requirement levels for compliant [RFC2119] and indicate requirement levels for compliant
implementations. implementations.
The terminology defined in RTP [RFC3550] and in the extensions for XR The terminology defined in RTP [RFC3550] and in the extensions for XR
reporting [RFC3611] applies. reporting [RFC3611] applies.
3. XR Discard RLE Report Block 3. XR Discard RLE Report Block
The XR Discard RLE report block uses the same format as specified for The XR Discard RLE report block uses the same format as specified for
the loss and duplicate report blocks in [RFC3611]. Figure 1 recaps the loss and duplicate report blocks in [RFC3611]. Figure 1
the packet format. The fields "BT", "T", "block length", "SSRC of describes the packet format. The fields "BT", "T", "block length",
source", "begin_seq", and "end_seq" SHALL have the same semantics and "SSRC of source", "begin_seq", and "end_seq" SHALL have the same
representation as defined in [RFC3611]. The "chunks" encoding the semantics and representation as defined in [RFC3611]. The "chunks"
run length SHALL have the same representation as in RFC3611, but encoding the run length SHALL have the same representation as in
encode discarded packets. RFC3611, but encode discarded packets.
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=DRLE |rsvd |E| T | block length | | BT=DRLE |rsvd |E| T | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| chunk 1 | chunk 2 | | chunk 1 | chunk 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: ... : : ... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| chunk n-1 | chunk n | | chunk n-1 | chunk n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: XR Discard Report Block Figure 1: XR Discard Report Block
Block Type (BT, 8 bits): A Run-length encoded Discarded Packets Block Type (BT, 8 bits): A Run-length encoded Discarded Packets
Report Block is identified by the constant DRLE. Report Block is identified by the constant DRLE.
[Note to RFC Editor: please replace DRLE with the IANA provided RTCP [Note to RFC Editor: please replace DRLE with the IANA provided RTCP
XR block type for this block. Please remove this note prior to XR block type for this block. Please remove this note prior to
publication as an RFC.] publication as an RFC.]
skipping to change at page 6, line 5 skipping to change at page 5, line 35
Discard RLE Report Blocks SHOULD be sent in conjunction with an RTCP Discard RLE Report Blocks SHOULD be sent in conjunction with an RTCP
RR as a compound RTCP packet. RR as a compound RTCP packet.
4. XR Bytes Discarded Report Block 4. XR Bytes Discarded Report Block
The XR Bytes Discarded report block uses the following format which The XR Bytes Discarded report block uses the following format which
follows the model of the framework for performance metric development follows the model of the framework for performance metric development
[RFC6390]. [RFC6390].
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=BDR | I |E|reserved | block length=2 | | BT=BDR | I |E|reserved | block length=2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| number of bytes discarded | | number of bytes discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: XR Bytes Discarded Report Block Figure 2: XR Bytes Discarded Report Block
Block Type (BT, 8 bits): A Bytes Discarded Packets Report Block is Block Type (BT, 8 bits): A Bytes Discarded Packets Report Block is
identified by the constant BDR. identified by the constant BDR.
[Note to RFC Editor: please replace BDR with the IANA provided RTCP [Note to RFC Editor: please replace BDR with the IANA provided RTCP
XR block type for this block. Please remove this note prior to XR block type for this block. Please remove this note prior to
publication as an RFC.] publication as an RFC.]
The Interval Metric flag (I) (2 bits) is used to indicate whether the The Interval Metric flag (I) (2 bits) is used to indicate whether the
discard metric is Interval, or a Cumulative metric, that is, whether discard metric is Interval, or a Cumulative metric, that is, whether
the reported value applies to the most recent measurement interval the reported value applies to the most recent measurement interval
duration between successive reports (I=10, the Interval Duration) or duration between successive reports (I=10, the Interval Duration) or
to the accumulation period characteristic of cumulative measurements to the accumulation period characteristic of cumulative measurements
(I=11, the Cumulative Duration). Since the bytes discarded are not (I=11, the Cumulative Duration). Since the bytes discarded are not
measured at a particular time instance but over one or several measured at a particular time instance but over one or several
reporting intervals, the metric MUST NOT be reported as a Sampled reporting intervals, the metric MUST NOT be reported as a Sampled
Metric (I=01). Metric (I=01).
skipping to change at page 7, line 15 skipping to change at page 6, line 44
number of bytes discarded since the last RTCP XR Byte Discarded Block number of bytes discarded since the last RTCP XR Byte Discarded Block
was received. was received.
If the XR block follows a measurement identity block [RFC6776] in the If the XR block follows a measurement identity block [RFC6776] in the
same RTCP compound packet then the cumulative (I=11) or the interval same RTCP compound packet then the cumulative (I=11) or the interval
(I=10) for this report block corresponds to the values of the (I=10) for this report block corresponds to the values of the
"measurement duration" in the measurement information block. "measurement duration" in the measurement information block.
If the receiver sends the Bytes Discarded Report Block without the If the receiver sends the Bytes Discarded Report Block without the
measurement identity block then the discard block MUST be sent in measurement identity block then the discard block MUST be sent in
conjunction with an RTCP RR as a compound RTCP packet. conjunction with an RTCP Receiver Report (RR) as a compound RTCP
packet.
5. Protocol Operation 5. Protocol Operation
This section describes the behavior of the reporting (= receiver) This section describes the behavior of the reporting (= receiver)
node and the media sender. node and the media sender.
5.1. Reporting Node (Receiver) 5.1. Reporting Node (Receiver)
Transmission of RTCP XR Discard RLE Reports is up to the discretion Transmission of RTCP XR Discard RLE Reports is up to the discretion
of the receiver, as is the reporting granularity. However, it is of the receiver, as is the reporting granularity. However, it is
skipping to change at page 9, line 29 skipping to change at page 9, line 15
Description Protocol (SDP), "discard-rle" and "discard-bytes", in the Description Protocol (SDP), "discard-rle" and "discard-bytes", in the
"RTP Control Protocol Extended Reports (RTCP XR) Session Description "RTP Control Protocol Extended Reports (RTCP XR) Session Description
Protocol (SDP) Parameters Registry". Protocol (SDP) Parameters Registry".
8.3. Contact information for IANA registrations 8.3. Contact information for IANA registrations
Joerg Ott (jo@comnet.tkk.fi) Joerg Ott (jo@comnet.tkk.fi)
Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland. Aalto University Comnet, Otakaari 5A, 02150 Espoo, Finland.
9. Acknowledgements 9. Acknowledgments
Thanks to Qin Wu, Colin Perkins, Dan Romascanu, Roni Even and Dan Thanks to Qin Wu, Colin Perkins, Dan Romascanu, Roni Even and Dan
Wing for providing valuable feedback on earlier versions of this Wing for providing valuable feedback on earlier versions of this
draft draft
10. References 10. References
10.1. Normative References 10.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", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, 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)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611, November
November 2003. 2003.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control "Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, July
July 2006. 2006.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390, Performance Metric Development", BCP 170, RFC 6390,
October 2011. October 2011.
[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
Reporting Using a Source Description (SDES) Item and an Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 2012. RTCP Extended Report (XR) Block", RFC 6776, October 2012.
10.2. Informative References 10.2. Informative References
[I-D.ietf-xrblock-rtcp-xr-discard] [I-D.ietf-xrblock-rtcp-xr-discard]
Clark, A., Zorn, G., and W. Wu, "RTP Control Protocol Clark, A., Zorn, G., and W. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Discard Count metric (RTCP) Extended Report (XR) Block for Discard Count metric
Reporting", draft-ietf-xrblock-rtcp-xr-discard-11 (work in Reporting", draft-ietf-xrblock-rtcp-xr-discard-15 (work in
progress), December 2012. progress), June 2013.
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard]
Clark, A., Huang, R., and W. Wu, "RTP Control Clark, A., Huang, R., and W. Wu, "RTP Control
Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
Discard metric Reporting", Discard metric Reporting", draft-ietf-xrblock-rtcp-xr-
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in burst-gap-discard-14 (work in progress), April 2013.
progress), December 2012.
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. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00 A.1. changes in draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-00
o Changed the interval flag from 1 to 2 bits in the discarded bytes o Changed the interval flag from 1 to 2 bits in the discarded bytes
report. Also added the measurement identification tag to the report. Also added the measurement identification tag to the
 End of changes. 22 change blocks. 
94 lines changed or deleted 95 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/