draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-00.txt   draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01.txt 
XR Block Working Group V. Singh, Ed. XR Block Working Group V. Singh, Ed.
Internet-Draft J. Ott Internet-Draft J. Ott
Intended status: Standards Track Aalto University Intended status: Standards Track Aalto University
Expires: April 04, 2014 I. Curcio Expires: May 08, 2014 I. Curcio
Nokia Research Center Nokia Research Center
October 01, 2013 November 04, 2013
RTP Control Protocol (RTCP) Extended Report (XR) for Bytes Discarded RTP Control Protocol (RTCP) Extended Report (XR) for Bytes Discarded
Metric Metric
draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-00 draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
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 report as individual packet reporting. This document specifies a report
computing the bytes discarded from the de-jitter buffer after computing the bytes discarded from the de-jitter buffer after
successful reception. successful reception.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 04, 2014. This Internet-Draft will expire on May 08, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 4 3. XR Bytes Discarded Report Block . . . . . . . . . . . . . . . 4
4. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 6 4. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 5
4.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 6 4.1. Reporting Node (Receiver) . . . . . . . . . . . . . . . . 5
4.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Media Sender . . . . . . . . . . . . . . . . . . . . . . 6
5. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 6 5. SDP signaling . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7.1. XR Report Block Registration . . . . . . . . . . . . . . 8 7.1. XR Report Block Registration . . . . . . . . . . . . . . 7
7.2. SDP Parameter Registration . . . . . . . . . . . . . . . 8 7.2. SDP Parameter Registration . . . . . . . . . . . . . . . 7
7.3. Contact information for IANA registrations . . . . . . . 8 7.3. Contact information for IANA registrations . . . . . . . 8
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Metrics represented using RFC6390 Template . . . . . 10 Appendix A. Metrics represented using RFC6390 Template . . . . . 9
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 10 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 10
B.1. changes in draft-singh-xrblock-rtcp-xr-bytes- B.1. changes in draft-singh-xrblock-rtcp-xr-bytes-
discarded-metric-00 . . . . . . . . . . . . . . . . . . . 10 discarded-metric-00 . . . . . . . . . . . . . . . . . . . 10
B.2. changes in draft-ietf-xrblock-rtcp-xr-bytes- B.2. changes in draft-ietf-xrblock-rtcp-xr-bytes-
discarded-metric-00 . . . . . . . . . . . . . . . . . . . 11 discarded-metric-00 . . . . . . . . . . . . . . . . . . . 10
B.3. changes in draft-ietf-xrblock-rtcp-xr-bytes-
discarded-metric-01 . . . . . . . . . . . . . . . . . . . 10
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 media sender to adapt Both long-term and short-term feedback enable a media sender to adapt
skipping to change at page 3, line 28 skipping to change at page 3, line 24
beginning of the session. See section 4.7.1 of RFC3611 [RFC3611]. beginning of the session. See section 4.7.1 of RFC3611 [RFC3611].
The discard metric is believed to be applicable to a large class of The discard metric is believed to be applicable to a large class of
RTP applications which use a de-jitter buffer RFC5481 [RFC5481]. RTP applications which use a de-jitter buffer RFC5481 [RFC5481].
Recently proposed extensions to the Extended Reports (XR) reporting Recently proposed extensions to the Extended Reports (XR) reporting
suggest enhancing this discard metric: 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 [RFC7002]. If an endpoint needs to report
endpoint needs to report packet discard due to other reasons than packet discard due to other reasons than early- and late-arrival
early- and late-arrival (for example, discard due to duplication, (for example, discard due to duplication, redundancy, etc.) then
redundancy, etc.) then it should consider using the Discarded it should consider using the Discarded Packets Report Block
Packets Report Block [I-D.ietf-xrblock-rtcp-xr-discard]. [RFC7002].
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 [RFC7003].
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard].
o Reporting run-length encoding of discarded packet during a o Reporting run-length encoding of discarded packet during a
measurement interval, i.e., between a set of sequence numbers measurement interval, i.e., between a set of sequence numbers
[I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics]. [I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics].
However, none of these metrics allow a receiver to report precisely However, none of these metrics allow a receiver to report precisely
the number of bytes that were discarded. While this information the number of RTP payload bytes that were discarded. While this
could in theory be derived from high-frequency reporting on the information could in theory be derived from high-frequency reporting
number of discarded packets [I-D.ietf-xrblock-rtcp-xr-discard] or on the number of discarded packets [RFC7002] or from the Discard RLE
from the Discard RLE report report [I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics], these two
[I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics], these two mechanisms mechanisms do not appear feasible: The former would require an unduly
do not appear feasible: The former would require an unduly high high amount of reporting which still might not be sufficient due to
amount of reporting which still might not be sufficient due to the the non-deterministic scheduling of RTCP packets. The latter incurs
non-deterministic scheduling of RTCP packets. The latter incurs
significant complexity (by storing a map of sequence numbers and significant complexity (by storing a map of sequence numbers and
packet sizes) and reporting overhead. packet sizes) and reporting overhead.
An XR block is defined in this document to indicate the number of An XR block is defined in this document to indicate the number of RTP
bytes discarded, per interval or for the duration of the session, payload bytes discarded, per interval or for the duration of the
similar to other XR report blocks. session, similar to other XR report blocks.
2. Terminology 2. Terminology
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 BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
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.
skipping to change at page 4, line 44 skipping to change at page 4, line 28
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 RTP payload bytes discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: XR Bytes Discarded Report Block Figure 1: 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.]
skipping to change at page 5, line 37 skipping to change at page 5, line 19
report blocks MUST be included. report blocks MUST be included.
reserved (5 bits): This field is reserved for future definition. In reserved (5 bits): This field is reserved for future definition. In
the absence of such definition, the bits in this field MUST be set to the absence of such definition, the bits in this field MUST be set to
zero and MUST be ignored by the receiver. zero and MUST be ignored by the receiver.
block length (16 bits) MUST be set to 2, in accordance with the block length (16 bits) MUST be set to 2, in accordance with the
definition of this field in [RFC3611]. The block MUST be discarded definition of this field in [RFC3611]. The block MUST be discarded
if the block length is set to a different value. if the block length is set to a different value.
The 'number of bytes discarded' is a 32-bit unsigned integer value The 'number of RTP payload bytes discarded' is a 32-bit unsigned
indicating the total number of bytes discarded. Bytes discarded integer value indicating the total number of bytes discarded. Bytes
corresponds to the RTP payload size of every RTP packet that is discarded corresponds to the RTP payload size of every RTP packet
discarded (due to early or late arrival). Hence, the bytes discarded that is discarded (due to early or late arrival). Hence, the bytes
ignores the size of any RTP header extensions and the size of the discarded ignores the size of any RTP header extensions and the size
padding bits. Also the discarded packet is associated to the of the padding bits. Also the discarded packet is associated to the
interval in which it was discarded and not when it was expected. interval in which it was discarded and not when it was expected.
If Interval Metric flag (I=11) is set, the value in the field If Interval Metric flag (I=11) is set, the value in the field
indicates the number of bytes discarded from the start of the indicates the number of RTP payload bytes discarded from the start of
session, if Interval Metric flag (I=01) is set, it indicates the the session, if Interval Metric flag (I=01) is set, it indicates the
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
skipping to change at page 6, line 21 skipping to change at page 6, line 4
4. Protocol Operation 4. Protocol Operation
This section describes the behavior of the reporting node (= media This section describes the behavior of the reporting node (= media
receiver) and the media sender. receiver) and the media sender.
4.1. Reporting Node (Receiver) 4.1. Reporting Node (Receiver)
Transmission of RTCP XR Bytes Discarded Report is up to the Transmission of RTCP XR Bytes Discarded Report is up to the
discretion of the media receiver, as is the reporting granularity. discretion of the media receiver, as is the reporting granularity.
However, it is RECOMMENDED that the media receiver signals all However, it is RECOMMENDED that the media receiver signals all
discarded packets using the method defined in this document. If all discarded packets using the method defined in this document. If all
packets over a reporting period were discarded, the media receiver packets over a reporting period were discarded, the media receiver
MAY use the Discard Report Block [I-D.ietf-xrblock-rtcp-xr-discard] MAY use the Discard Report Block [RFC7002] instead.
instead.
The media receiver MAY send the Bytes Discard Reports as part of the The media receiver MAY send the Bytes Discard Reports as part of the
regularly scheduled RTCP packets as per RFC3550. It MAY also include regularly scheduled RTCP packets as per RFC3550. It MAY also include
Bytes Discard Reports in immediate or early feedback packets as per Bytes Discard Reports in immediate or early feedback packets as per
RFC4585. RFC4585.
4.2. Media Sender 4.2. Media Sender
The media sender MUST be prepared to operate without receiving any The media sender MUST be prepared to operate without receiving any
Bytes Discarded reports. If Bytes Discarded reports are generated by Bytes Discarded reports. If Bytes Discarded reports are generated by
skipping to change at page 9, line 21 skipping to change at page 9, line 5
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.
[I-D.ietf-xrblock-rtcp-xr-discard] [RFC7002] Clark, A., Zorn, G., and Q. 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", RFC 7002, September 2013.
Reporting", draft-ietf-xrblock-rtcp-xr-discard-15 (work in
progress), June 2013.
9.2. Informative References 9.2. Informative References
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] [RFC7003] Clark, A., Huang, R., and Q. Wu, "RTP Control Protocol
Clark, A., Huang, R., and W. Wu, "RTP Control (RTCP) Extended Report (XR) Block for Burst/Gap Discard
Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Metric Reporting", RFC 7003, September 2013.
Discard metric Reporting", draft-ietf-xrblock-rtcp-xr-
burst-gap-discard-14 (work in progress), April 2013.
[I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics] [I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics]
Ott, J., Singh, V., and I. Curcio, "RTP Control Protocol Ott, J., Singh, V., and I. Curcio, "RTP Control Protocol
(RTCP) Extended Reports (XR) for Run Length Encoding (RLE) (RTCP) Extended Reports (XR) for Run Length Encoding (RLE)
of Discarded Packets", draft-ietf-xrblock-rtcp-xr-discard- of Discarded Packets", draft-ietf-xrblock-rtcp-xr-discard-
rle-metrics-06 (work in progress), July 2013. rle-metrics-06 (work in progress), July 2013.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
skipping to change at page 10, line 19 skipping to change at page 9, line 48
[I-D.ietf-avtcore-rtp-security-options] [I-D.ietf-avtcore-rtp-security-options]
Westerlund, M. and C. Perkins, "Options for Securing RTP Westerlund, M. and C. Perkins, "Options for Securing RTP
Sessions", draft-ietf-avtcore-rtp-security-options-04 Sessions", draft-ietf-avtcore-rtp-security-options-04
(work in progress), July 2013. (work in progress), July 2013.
Appendix A. Metrics represented using RFC6390 Template Appendix A. Metrics represented using RFC6390 Template
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC
number, when assigned. number, when assigned.
a. Bytes Discarded Metric a. RTP Payload Bytes Discarded Metric
* Metric Name: Bytes Discarded Metric
* Metric Description: Total number of bytes discarded over the * Metric Name: RTP Payload Bytes Discarded Metric
period covered by this report. * Metric Description: Total number of RTP Payload bytes
discarded over the period covered by this report.
* Method of Measurement or Calculation: See section 4, number of * Method of Measurement or Calculation: See section 4, number of
bytes discarded definition [RFCXXXX]. bytes discarded definition in [RFCXXXX].
* Units of Measurement: See section 4, number of bytes discarded * Units of Measurement: See section 4, number of RTP payload
definition [RFCXXXX]. bytes discarded definition in [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4, 1st paragraph [RFCXXXX]. section 4, 1st paragraph of [RFCXXXX].
* Measurement Timing: See section 4, last three paragraphs of * Measurement Timing: See section 4, last three paragraphs of
[RFCXXXX] for measurement timing and for the Interval Metric [RFCXXXX] for measurement timing and for the Interval Metric
flag. flag.
* Use and applications: See section 1, paragraph 1 of [RFCXXXX]. * Use and applications: See section 1, paragraph 1 of [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix B. Change Log Appendix B. Change Log
skipping to change at page 11, line 9 skipping to change at page 10, line 38
B.1. changes in draft-singh-xrblock-rtcp-xr-bytes-discarded-metric-00 B.1. changes in draft-singh-xrblock-rtcp-xr-bytes-discarded-metric-00
o Bytes discarded metric split from o Bytes discarded metric split from
[I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics]. [I-D.ietf-xrblock-rtcp-xr-discard-rle-metrics].
B.2. changes in draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-00 B.2. changes in draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-00
o Submitted as a WG draft. o Submitted as a WG draft.
B.3. changes in draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
o Editorial fixes: Updated references from drafts to RFCs.
o Updated fields in the RFC6390 template.
o Changed 'number of bytes discarded' to 'number of RTP payload
bytes discarded'.
Authors' Addresses Authors' Addresses
Varun Singh (editor) Varun Singh (editor)
Aalto University Aalto University
School of Electrical Engineering School of Electrical Engineering
Otakaari 5 A Otakaari 5 A
Espoo, FIN 02150 Espoo, FIN 02150
Finland Finland
Email: varun@comnet.tkk.fi Email: varun@comnet.tkk.fi
 End of changes. 25 change blocks. 
58 lines changed or deleted 62 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/