draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt   rfc6958.txt 
Audio/Video Transport Working Group A. Clark Internet Engineering Task Force (IETF) A. Clark
Internet-Draft Telchemy Request for Comments: 6958 Telchemy
Intended status: Standards Track S. Zhang Category: Standards Track S. Zhang
Expires: October 17, 2013 J. Zhao ISSN: 2070-1721 J. Zhao
STTRI STTRI
Q. Wu, Ed. Q. Wu, Ed.
Huawei Huawei
April 15, 2013 May 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap RTP Control Protocol (RTCP) Extended Report (XR) Block for
Loss metric Reporting Burst/Gap Loss Metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt
Abstract Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) Block that allows the reporting of Burst and Gap Loss metrics (XR) Block that allows the reporting of burst and gap loss metrics
for use in a range of RTP applications. for use in a range of RTP applications.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on October 17, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6958.
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
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
1.1. Burst and Gap Loss Report Block . . . . . . . . . . . . . 3 1.1. Burst/Gap Loss Metrics Block . . . . . . . . . . . . . . 2
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 3. Burst/Gap Loss Metrics Block . . . . . . . . . . . . . . . . 4
3. Burst/Gap Loss Block . . . . . . . . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.2. Definition of Fields in Burst/Gap Loss Metrics Block . . 5
3.2. Definition of Fields in Burst/Gap Loss Report Block . . . 6 3.3. Derived Metrics Based on Reported Metrics . . . . . . . . 7
3.3. Derived metrics based on reported metrics . . . . . . . . 9 4. Considerations for Voice-over-IP Applications . . . . . . . . 8
4. Considerations for Voice-over-IP applications . . . . . . . . 11 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 9
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 9
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6.1. New RTCP XR Block Type Value . . . . . . . . . . . . . . 9
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13 6.3. Contact Information for Registrations . . . . . . . . . . 10
6.3. Contact information for registrations . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 17 Appendix A. Metrics Represented Using the Template from RFC 6390 13
Appendix A. Metrics represented using RFC6390 Template . . . . . 18
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 23
B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-11 . . . . . . . 23
B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10 . . . . . . . 23
B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 . . . . . . . 23
B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 23
B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 23
B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 23
B.7. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
1.1. Burst and Gap Loss Report Block 1.1. Burst/Gap Loss Metrics Block
This document 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 lost by the supports the reporting of the proportion of packets lost by the
network. The losses during loss bursts are reported, together with network. The losses during loss bursts are reported, together with
the number of bursts and additional data allowing the calculation of the number of bursts and additional data, allowing the calculation of
statistical parameters (mean and variance) of the distribution of statistical parameters (mean and variance) of the distribution of
burst lengths. Some uses of these metrics depend on the availability burst lengths. Some uses of these metrics depend on the availability
of the metric "cumulative number of packets lost" from RTCP of the metric "cumulative number of packets lost" from RTCP
[RFC3550]. [RFC3550].
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 they also metrics are typically used in Cumulative reports; however, they also
may be used in Interval reports. The burstiness of packet loss may be used in Interval reports. The burstiness of packet loss
affects user experience, may influence any sender strategies to affects user experience, may influence any sender strategies to
mitigate the problem, and may also have diagnostic value. mitigate the problem, and may also have diagnostic value.
The metric belongs to the class of transport-related end system The metric belongs to the class of transport-related end system
metrics defined in [RFC6792]. metrics defined in [RFC6792].
The definitions of Burst, Gap, Loss and Discard are consistent with The definitions of "burst", "gap", "loss", and "discard" are
definitions in [RFC3611]. To accommodate the range of jitter buffer consistent with definitions in [RFC3611]. To accommodate the range
algorithms and packet discard logic that may be used by implementors, of jitter buffer algorithms and packet discard logic that may be used
the method used to distinguish between bursts and gaps may be an by implementors, the method used to distinguish between bursts and
equivalent method to that defined in [RFC3611]. The method used gaps may be an equivalent method to that defined in [RFC3611]. The
should produce the same result as that defined in [RFC3611] for method used should produce the same result as that defined in
conditions of burst packet loss, but may produce different results [RFC3611] for conditions of burst packet loss but may produce
for conditions of time varying jitter. different results for conditions of time-varying jitter.
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 defines an extensible structure for reporting by using an RTCP
Report (XR). This document defines a new Extended Report block for Extended Report (XR). This document defines a new Extended Report
use with [RFC3550] and [RFC3611]. block for use with [RFC3550] and [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. The RTP definition and specification of performance metrics. The "Guidelines
Monitoring Architectures [RFC6792] provides guideline for reporting for Use of the RTP Monitoring Framework" [RFC6792] provides
block format using RTCP XR. The Metrics Block described in this guidelines for reporting block format using RTCP XR. The Metrics
document are in accordance with the guidelines in [RFC6390] and Block described in this document is in accordance with the guidelines
[RFC6792]. in [RFC6390] and [RFC6792].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a range of RTP applications which These metrics are applicable to a range of RTP applications that
contain jitter buffers and don't use stream repair means, e.g., contain jitter buffers and don't use stream repair means, e.g.,
Forward Error Correction (FEC) [RFC5109] and/or retransmission Forward Error Correction (FEC) [RFC5109] and/or retransmission
[RFC4588]. [RFC4588].
2. Terminology 2. Terminology
2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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 or this time window but is too early or late to be played out or
thrown away before playout due to packet duplication or redundancy thrown away before playout due to packet duplication or redundancy
shall be regarded as discarded. A packet shall be classified as shall be regarded as discarded. A packet shall be classified as
one of received (or OK), discarded or lost. The metric one of received (or OK), discarded, or lost. The metric
"cumulative number of packets lost" defined in [RFC3550] reports a "cumulative number of packets lost" defined in [RFC3550] reports a
count of packets lost from the media stream (single SSRC within count of packets lost from the media stream (single
single RTP session). Similarly the metric "number of packets Synchronization Source (SSRC) within a single RTP session).
discarded" defined in [DISCARD] reports a count of packets Similarly, the metric "number of packets discarded" defined in
discarded from the media stream (single SSRC within single RTP [DISCARD] reports a count of packets discarded from the media
session) arriving at the receiver. Another metric defined in stream (single SSRC within single RTP session) arriving at the
[RFC5725] is available to report on packets which are not receiver. The post-repair Loss RLE metric, which is defined in
recovered by any repair techniques which may be in use. [RFC5725], can be used to report the number of packets that are
not recovered by any repair techniques that are in use.
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
of RTCP XR [RFC3611]. RTCP XR views a RTP stream as being divided that of RTCP XR [RFC3611]. RTCP XR views an RTP stream as being
into bursts, which are periods during which the loss rate is high divided into bursts, which are periods when the loss rate is high
enough to cause noticeable quality degradation (generally over 5 enough to cause noticeable quality degradation (generally over 5
percent loss rate), and gaps, which are periods during which lost percent loss rate) and gaps, which are periods when lost packets
packets are infrequent and hence quality is generally acceptable. are infrequent and hence quality is generally acceptable.
3. Burst/Gap Loss Block 3. Burst/Gap Loss Metrics Block
Metrics in this block report on Burst/Gap Loss in the stream arriving Metrics in this block report on burst/gap loss in the stream arriving
at the RTP system. The measurement of these metrics are made at the at the RTP system. The measurement of these metrics is made at the
receiving end of the RTP stream. Instances of this Metrics Block receiving end of the RTP stream. Each instance of this Metrics Block
refer by Synchronization source (SSRC) to the separate auxiliary refers by SSRC to a separate auxiliary Measurement Information Block
Measurement Information block [RFC6776] which describes measurement [RFC6776], which describes the measurement periods in use (see RFC
periods in use(see RFC6776 section 4.2). 6776, Section 4.2).
This Metrics Block relies on the measurement period in the This Metrics Block relies on the measurement period in the
Measurement Information block indicating the span of the report. Measurement Information Block indicating the span of the report.
Senders MUST send this block in the same compound RTCP packet as the Senders MUST send this block in the same compound RTCP packet as the
measurement information block. Receivers MUST verify that the Measurement Information Block. Receivers MUST verify that the
measurement period is received in the same compound RTCP packet as measurement period is received in the same compound RTCP packet as
this Metrics Block. If not, this Metrics Block MUST be discarded. this Metrics Block. If not, this Metrics Block MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
Burst/Gap Loss metrics block The structure of the Burst/Gap Loss Metrics Block is as follows.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NBGL | I |C| resv. | block length = 5 | | BT=20 | I |C| resv. | Block Length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+-+-+-+-+-+-+
| Threshold | Sum of Burst Durations (ms) | | Threshold | Sum of Burst Durations (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Lost in Bursts | Total... | | Packets Lost in Bursts | Total... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Packets expected in bursts | Number of bursts | Sum of| | ...Packets Expected in Bursts | Number of Bursts | Sum of|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Squares of Burst Durations (ms-squared) | | ...Squares of Burst Durations (ms-squared) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Burst/Gap Loss Report Block 3.2. Definition of Fields in Burst/Gap Loss Metrics Block
Block type (BT): 8 bits
A Burst/Gap Loss Report Block is identified by the constant NBGL. Block Type (BT): 8 bits
[Note to RFC Editor: please replace NBGL with the IANA provided A Burst/Gap Loss Metrics Block is identified by the constant 20.
RTCP XR block type for this block.]
Interval Metric flag (I): 2 bits Interval Metric flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Loss metrics This field is used to indicate whether the burst/gap loss metrics
are Sampled, Interval or Cumulative metrics: are Sampled, Interval, or Cumulative metrics:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value.
In this document, Burst/Gap Loss Metrics can only be measured over In this document, burst/gap loss metrics can only be measured over
definite intervals, and cannot be sampled. Also, the value I=00 definite intervals and cannot be sampled. Also, the value I=00 is
is reserved for future use. Senders MUST NOT use the values I=00 reserved for future use. Senders MUST NOT use the values I=00 or
or I=01. If a block is received with I=00 or I=01, the receiver I=01. If a block is received with I=00 or I=01, the receiver MUST
MUST discard the block. discard the block.
Loss and Discard Combination flag (C): 1 bit Loss and Discard Combination flag (C): 1 bit
The 'C' flag is used to indicate whether the loss/discard report The 'C' flag is used to indicate whether the loss/discard report
is combined with the burst gap loss report in the same compound is combined with the burst/gap loss report in the same compound
RTCP packet. The value is set to '1' if the loss/discard report RTCP packet. The value is set to '1' if the loss/discard report
and the burst gap loss report are combined. Otherwise, the value and the burst gap loss report are combined. Otherwise, the value
is set to '0'. If the 'C' flag is set to 1 but the burst gap is set to '0'. If the 'C' flag is set to '1' but the burst/gap
discard was not sent, the receiver MUST discard the burst gap discard was not sent, the receiver MUST discard the burst/gap
loss. loss.
Reserved (resv): 5 bits Reserved (resv.): 5 bits
These bits are reserved. They MUST be set to zero by senders and These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (See RFC6709 section 4.2). ignored by receivers (see [RFC6709], Section 4.2).
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 Burst/Gap Loss block, the block length is equal to 5. The the Burst/Gap Loss Metrics Block, the block length is equal to 5.
block MUST be discarded if the block length is set to a different The block MUST be discarded if the block length is set to a
value. different value.
SSRC of source: 32 bits SSRC of Source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
Threshold: 8 bits Threshold: 8 bits
The Threshold is equivalent to Gmin in [RFC3611], i.e. the number The Threshold is equivalent to Gmin in [RFC3611], i.e., the number
of successive packets that must be received prior to and following of successive packets that must be received prior to and following
a lost packet in order for this lost packet to be regarded as part a lost packet in order for this lost packet to be regarded as part
of a gap. Note that the threshold is calculated in accordance of a gap. Note that the threshold is calculated in accordance
with Gmin Calculation defined in section 4.7.2 of RFC3611. with the Gmin Calculation defined in Section 4.7.2 of RFC 3611.
Sum of Burst Durations (ms): 24 bits Sum of Burst Durations (ms): 24 bits
The total duration of bursts of lost packets in the period of the The total duration of bursts of lost packets in the period of the
report (Interval or Cumulative). report (Interval or Cumulative).
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
an over-range measurement. If the measurement is unavailable, the an over-range measurement. If the measurement is unavailable, the
value 0xFFFFFF MUST be reported. value 0xFFFFFF MUST be reported.
Packets lost in bursts: 24 bits Packets Lost in Bursts: 24 bits
The total number of packets lost during loss bursts. The total number of packets lost during loss bursts.
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
an over-range measurement. If the measurement is unavailable, the an over-range measurement. If the measurement is unavailable, the
value 0xFFFFFF MUST be reported. value 0xFFFFFF MUST be reported.
Total packets expected in bursts: 24 bits Total Packets Expected in Bursts: 24 bits
The total number of packets expected during loss bursts (that is, The total number of packets expected during loss bursts (that is,
the sum of received packets and lost packets). the sum of received packets and lost packets).
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
an over-range measurement. If the measurement is unavailable, the an over-range measurement. If the measurement is unavailable, the
value 0xFFFFFF MUST be reported. value 0xFFFFFF MUST be reported.
Number of bursts: 16 bits Number of Bursts: 16 bits
The number of bursts in the period of the report (Interval or The number of bursts in the period of the report (Interval or
Cumulative). Cumulative).
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
over-range measurement. If the measurement is unavailable, the over-range measurement. If the measurement is unavailable, the
value 0xFFFF MUST be reported. value 0xFFFF MUST be reported.
Sum of Squares of Burst Durations (ms-squared): 36 bits Sum of Squares of Burst Durations (ms-squared): 36 bits
The sum of the squares of burst durations (where individual burst The sum of the squares of burst durations (where individual burst
durations are expressed in ms) over in the period of the report durations are expressed in ms) in the period of the report
(Interval or Cumulative). The units for this quantity are (Interval or Cumulative). The units for this quantity are
milliseconds-squared. milliseconds-squared.
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE MUST be reported to exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE MUST be reported to
indicate an over-range measurement. If the measurement is indicate an over-range measurement. If the measurement is
unavailable, the value 0xFFFFFFFFF MUST be reported. unavailable, the value 0xFFFFFFFFF MUST be reported.
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 as described in
this section, in conjunction with information from the Measurement this section, in conjunction with information from the Measurement
Information block [RFC6776] and also with the metric "cumulative Information Block [RFC6776] and also with the metric "cumulative
number of packets lost" provided in standard RTCP [RFC3550]. number of packets lost" provided in standard RTCP [RFC3550].
These metrics provide information relevant to statistical parameters, These metrics provide information relevant to statistical parameters,
including: including:
o The fraction of packets lost during bursts (i.e., Burst Loss Rate o the fraction of packets lost during bursts (i.e., Burst Loss Rate
in [SUMSTAT]), which can be calculated using the metric " Packets in [SUMSTAT]), which can be calculated using the metric "Packets
Loss in Bursts " and the metric " Total Packets expected in Bursts Loss in Bursts" and the metric "Total Packets Expected in Bursts"
" provided in the Burst/Gap Loss metrics block. provided in the Burst/Gap Loss Metrics Block.
o The fraction of packets lost during gaps (i.e., Gap Loss Rate in o the fraction of packets lost during gaps (i.e., Gap Loss Rate in
[SUMSTAT]), which can be calculated using the metric " Packets [SUMSTAT]), which can be calculated using the metric "Packets Loss
Loss in Bursts " and the metric " Total Packets expected in Bursts in Bursts" and the metric "Total Packets Expected in Bursts"
" provided in the Burst/Gap Loss metrics block. provided in the Burst/Gap Loss Metrics Block.
o burst duration mean [SUMSTAT], which can be calculated using the o burst duration mean [SUMSTAT], which can be calculated using the
metric " Packets Loss in Bursts " and the metric " Total Packets metric "Packets Loss in Bursts" and the metric "Total Packets
expected in Bursts " provided in the Burst/Gap Loss metrics block. Expected in Bursts" provided in the Burst/Gap Loss Metrics Block.
o burst duration variance [SUMSTAT], which can be calculated using o burst duration variance [SUMSTAT], which can be calculated using
the metric " Packets Loss in Bursts " and the metric " Total the metric "Packets Loss in Bursts" and the metric "Total Packets
Packets expected in Bursts " provided in the Burst/Gap Loss Expected in Bursts" provided in the Burst/Gap Loss Metrics Block.
metrics block.
The details on calculation these parameters in the metrics are The details on calculation of these parameters in the metrics are
described in [SUMSTAT]. described in [SUMSTAT].
4. Considerations for Voice-over-IP applications 4. Considerations for Voice-over-IP Applications
This Metrics Block is applicable to a broad range of RTP This Metrics Block is applicable to a broad range of RTP
applications. Where the metric is used with a Voice-overIP (VoIP) applications. Where the metric is used with a Voice-over-IP (VoIP)
application and the stream repair means is not available, the application and the stream repair means is not available, 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 loss rate is high enough to cause noticeable call when the loss rate is high enough to cause noticeable call quality
quality degradation (generally over 5 percent loss rate), and gaps, degradation (generally over 5 percent loss rate), and gaps, which are
which are periods during which lost packets are infrequent and hence periods when lost packets are infrequent and hence call quality is
call quality is generally acceptable. generally acceptable.
If Voice Activity Detection is used, the Burst and Gap Duration shall If Voice Activity Detection is used, the Burst and Gap Durations
be determined as if silence packets had been sent, i.e. a period of shall be determined as if silence packets had been sent, i.e., a
silence in excess of Gmin packets will terminate a burst condition. period of silence in excess of Gmin packets will terminate a burst
condition.
The recommended value for the threshold Gmin in [RFC3611] results in The recommended value for the threshold Gmin in [RFC3611] causes a
a Burst being a period of time during which the call quality is burst during which the call quality is degraded to a similar extent
degraded to a similar extent to a typical Pulse-Code Modulation(PCM) as it would be during a typical Pulse Code Modulation (PCM) Severely
Severely Errored Second. Errored Second.
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of the Session Description Protocol (SDP)
[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
without prior signaling. without prior signaling.
5.1. SDP rtcp-xr-attrib Attribute Extension 5.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document. The
ABNF [RFC5234] syntax is below.
xr-format =/ xr-bgl-block xr-format =/ xr-bgl-block
xr-bgl-block = "burst-gap-loss" xr-bgl-block = "burst-gap-loss"
5.2. Offer/Answer Usage 5.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in the offer/answer context, the SDP Offer/Answer
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters usage defined in [RFC3611] for unilateral "rtcp-xr" attribute
applies. For detailed usage in Offer/Answer for unilateral parameters applies. For detailed usage of offer/answer for
parameter, refer to section 5.2 of [RFC3611]. unilateral parameters, refer to Section 5.2 of [RFC3611].
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 NBGL in the IANA " RTP This document assigns the block type value 20 in the IANA "RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry " to Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
the "Burst/Gap Loss Metrics Block". the "Burst/Gap Loss Metrics Block".
[Note to RFC Editor: please replace NBGL with the IANA provided RTCP
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 "burst-gap-loss" in the This document also registers a new parameter "burst-gap-loss" 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".
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:
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
7. Security Considerations 7. Security Considerations
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. However the gaps indicated within this block could does not apply. However, the gaps indicated within this block could
be used to detect the timing of other events on the path between the be used to detect the timing of other events on the path between the
sender and receiver. For example, a competing multimedia stream sender and receiver. For example, a competing multimedia stream
might cause a loss burst for the duration of the stream, allowing the might cause a loss burst for the duration of the stream, allowing the
receiver of this block to know when the competing stream was active. receiver of this block to know when the competing stream was active.
This risk is not a significant threat since the only information This risk is not a significant threat since the only information
leaked is the timing of the loss, not the cause. Besides this, it is leaked is the timing of the loss, not the cause. Besides this, it is
believed that this proposed RTCP XR report block introduces no other believed that this proposed RTCP XR report block introduces no other
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
8. Contributors 8. Contributors
skipping to change at page 16, line 13 skipping to change at page 10, line 41
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
9. Acknowledgments 9. Acknowledgments
The authors gratefully acknowledge reviews and feedback provided by The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Adam Roach, Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Adam Roach,
Dan Romascanu,Chris Lonvick, Alfred C.,Morton Jr., Pete Resnick, Ted Dan Romascanu, Chris Lonvick, Alfred C. Morton Jr., Pete Resnick, Ted
Lemon, Stephen Farrell, Richard Barnes, Benoit Claise. Lemon, Stephen Farrell, Richard Barnes, and Benoit Claise.
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", March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Applications", RFC 3550, July 2003. Jacobson, "RTP: A Transport Protocol for Real-Time
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)", November 2003. Protocol Extended Reports (RTCP XR)", RFC 3611, 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", RFC 4566, July 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE [RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE
Report Block Type for RTP Control Protocol (RTCP) Extended Report Block Type for RTP Control Protocol (RTCP) Extended
Reports (XRs)", RFC 5725, February 2020. Reports (XRs)", RFC 5725, February 2010.
10.2. Informative References 10.2. Informative References
[DISCARD] Wu, Q., "RTCP XR Report Block for Discard metric [DISCARD] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-11, Protocol (RTCP) Extended Report (XR) Block for Discard
December 2012. Count metric Reporting", Work in Progress, April 2013.
[RFC4588] Rey, J., Leon, D., , A., Varsa, V., and R. Hakenberg, "RTP [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Retransmission Payload Format", RFC 4588, July 2006. Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
July 2006.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, December 2007. Correction", RFC 5109, December 2007.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Development", RFC 6390, July 2011. Performance Metric Development", BCP 170, RFC 6390,
October 2011.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
using SDES item and XR Block", RFC 6776, October 2012. Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 2012.
[RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792, [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
November 2012. RTP Monitoring Framework", RFC 6792, November 2012.
[SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics [SUMSTAT] Zorn, G., Schott, R., Wu, Q., Ed., and R. Huang, "RTP
Reporting", ID draft-ietf-xrblock-rtcp-xr-summary-stat-11, Control Protocol (RTCP) Extended Report (XR) Blocks for
Summary Statistics Metrics Reporting", Work in Progress,
March 2013. March 2013.
Appendix A. Metrics represented using RFC6390 Template Appendix A. Metrics Represented Using the Template from RFC 6390
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC The six metrics defined in this document are described below using
number, when assigned. the template from Section 5.4.4 of RFC 6390.
a. Threshold Metric a. Threshold Metric
* Metric Name: Threshold in RTP * Metric Name: Threshold in RTP
* Metric Description: The Threshold is equivalent to Gmin in * Metric Description: The Threshold is equivalent to Gmin in
[RFC3611], i.e. the number of successive RTP packets that must [RFC3611], i.e., the number of successive RTP packets that
be received prior to and following a lost RTP packet in order must be received prior to and following a lost RTP packet in
for this lost RTP packet to be regarded as part of a gap. order for this lost RTP packet to be regarded as part of a
gap.
* Method of Measurement or Calculation: See section 3.2, * Method of Measurement or Calculation: See Section 3.2,
Threshold definition [RFCXXXX]. Threshold definition.
* Units of Measurement: See section 3.2, Threshold definition * Units of Measurement: See Section 3.2, Threshold definition.
[RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and section 3.2 [RFCXXXX] for Interval measurement timing and Section 3.2 for Interval Metric flag.
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
b. Sum of Burst Durations Metric b. Sum of Burst Durations Metric
* Metric Name: Sum of Burst Durations in RTP * Metric Name: Sum of Burst Durations in RTP
* Metric Description: The total duration of bursts of lost RTP * Metric Description: The total duration of bursts of lost RTP
packets in the period of the report. packets in the period of the report.
* Method of Measurement or Calculation: See section 3.2, Sum of * Method of Measurement or Calculation: See Section 3.2, Sum of
Burst Durations definition [RFCXXXX]. Burst Durations definition.
* Units of Measurement: See section 3.2, Sum of Burst Durations * Units of Measurement: See Section 3.2, Sum of Burst Durations
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and section 3.2 [RFCXXXX] for Interval measurement timing and Section 3.2 for Interval Metric flag.
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
c. Packets lost in bursts Metric c. Packets Lost in Bursts Metric
* Metric Name: RTP Packets lost in bursts * Metric Name: RTP Packets lost in bursts
* Metric Description: The total number of RTP packets lost * Metric Description: The total number of RTP packets lost
during loss bursts. during loss bursts.
* Method of Measurement or Calculation: See section 3.2, Packets * Method of Measurement or Calculation: See Section 3.2, Packets
lost in bursts definition [RFCXXXX]. Lost in Bursts definition.
* Units of Measurement: See section 3.2, Packets lost in bursts * Units of Measurement: See Section 3.2, Packets lost in bursts
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and section 3.2 [RFCXXXX] for Interval measurement timing and Section 3.2 for Interval Metric flag.
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
d. Total packets expected in bursts Metric d. Total Packets Expected in Bursts Metric
* Metric Name: Total RTP packets expected in bursts * Metric Name: Total RTP packets expected in bursts
* Metric Description: The total number of RTP packets expected * Metric Description: The total number of RTP packets expected
during loss bursts (that is, the sum of received RTP packets during loss bursts (that is, the sum of received RTP packets
and lost RTP packets). and lost RTP packets).
* Method of Measurement or Calculation: See section 3.2, Total * Method of Measurement or Calculation: See Section 3.2, Total
packets expected in bursts definition [RFCXXXX]. packets expected in bursts definition.
* Units of Measurement: See section 3.2, Total packets expected * Units of Measurement: See Section 3.2, Total packets expected
in bursts definition [RFCXXXX]. in bursts definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and section 3.2 [RFCXXXX] for Interval measurement timing and Section 3.2 for Interval Metric flag.
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
e. Number of bursts Metric e. Number of Bursts Metric
* Metric Name: Number of bursts in RTP * Metric Name: Number of bursts in RTP
* Metric Description: The total duration of bursts of lost RTP * Metric Description: The total duration of bursts of lost RTP
packets in the period of the report. packets in the period of the report.
* Method of Measurement or Calculation: See section 3.2, Number * Method of Measurement or Calculation: See Section 3.2, Number
of bursts definition [RFCXXXX]. of bursts definition.
* Units of Measurement: See section 3.2, Number of bursts * Units of Measurement: See Section 3.2, Number of bursts
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and section 3.2 [RFCXXXX] for Interval measurement timing and Section 3.2 for Interval Metric flag.
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
f. Sum of Squares of Burst Durations Metric f. Sum of Squares of Burst Durations Metric
* Metric Name: Sum of Squares of Burst Durations in RTP * Metric Name: Sum of Squares of Burst Durations in RTP
* Metric Description: The sum of the squares of burst durations * Metric Description: The sum of the squares of burst durations
(where individual burst durations are expressed in ms) over in (where individual burst durations are expressed in ms) over in
the period of the report. the period of the report.
* Method of Measurement or Calculation: See section 3.2, Sum of * Method of Measurement or Calculation: See Section 3.2, Sum of
Squares of Burst Durations definition [RFCXXXX]. Squares of Burst Durations definition.
* Units of Measurement: See section 3.2, Sum of Squares of Burst * Units of Measurement: See Section 3.2, Sum of Squares of Burst
Durations definition [RFCXXXX]. Durations definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* Measurement Timing: See section 3, 2nd paragraph [RFCXXXX] for
measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag.
* Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611.
Appendix B. Change Log
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-11
The following are the major changes compared to previous version:
o Incorporated Ted's proposed change during IESG review.
B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10
The following are the major changes compared to previous version:
o IESG Review comments are addressed in this version.
B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09
The following are the major changes compared to previous version:
o IETF LC comments are addressed together with AD's comment on
Normative language in this version.
B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08
The following are the major changes compared to previous version:
o Move RFC6709 as one informative reference.
B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07
The following are the major changes compared to previous version:
o Editorial changes based on comments in the WGLC.
B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06
The following are the major changes compared to previous version:
o SDP update based on SDP Directorate Review.
o Add some texts to get consistent with RFC6798 and Delay draft.
B.7. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04
The following are the major changes compared to previous version: * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and Section 3.2 for Interval Metric flag.
o Outdated reference update. * Use and Applications: See Section 1.4.
o Editorial changes based on comments that applied to PDV and Delay * Reporting Model: See RFC 3611.
drafts.
Authors' Addresses Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
Email: alan.d.clark@telchemy.com EMail: alan.d.clark@telchemy.com
Sunshine Zhang Sunshine Zhang
Shanghai Research Institute of China Telecom Corporation Limited Shanghai Research Institute of China Telecom Corporation Limited
No.1835,South Pudong Road No. 1835, South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: zhangyx@sttri.com.cn EMail: zhangyx@sttri.com.cn
Jing Zhao Jing Zhao
Shanghai Research Institute of China Telecom Corporation Limited Shanghai Research Institute of China Telecom Corporation Limited
No.1835,South Pudong Road No. 1835, South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: zhaojing@sttri.com.cn EMail: zhaojing@sttri.com.cn
Qin Wu (editor) Qin Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com EMail: sunseawq@huawei.com
 End of changes. 134 change blocks. 
349 lines changed or deleted 279 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/