draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track S. Zhang, Ed. Intended status: Standards Track S. Zhang
Expires: September 22, 2013 J. Zhao Expires: October 13, 2013 J. Zhao
STTRI STTRI
Q. Wu Q. Wu, Ed.
Huawei Huawei
March 21, 2013 April 11, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Loss metric Reporting Loss metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09.txt draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10.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 This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 September 22, 2013. This Internet-Draft will expire on October 13, 2013.
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 35 skipping to change at page 2, line 35
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13
6.3. Contact information for registrations . . . . . . . . . . 13 6.3. Contact information for registrations . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 18 Appendix A. Metrics represented using RFC6390 Template . . . . . 18
A.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 . . . . . . . 18 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 23
A.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 18 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10 . . . . . . . 23
A.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 18 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 . . . . . . . 23
A.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 18 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 23
A.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 18 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 23
B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
1.1. Burst and Gap Loss Report Block 1.1. Burst and Gap Loss Report Block
This draft defines a new block type to augment those defined in This document defines a new block type to augment those defined in
[RFC3611] for use in a range of RTP applications. The new block type [RFC3611] for use in a range of RTP applications. The new block type
supports the reporting of the proportion of packets 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
skipping to change at page 4, line 8 skipping to change at page 4, line 8
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 RTP
Monitoring Architectures [RFC6792] provides guideline for reporting Monitoring Architectures [RFC6792] provides guideline for reporting
block format using RTCP XR. The Metrics Block described in this block format using RTCP XR. The Metrics Block described in this
document are in accordance with the guidelines in [RFC6390] and document are in accordance with the guidelines in [RFC6390] and
[RFC6792]. [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 which
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 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].
skipping to change at page 6, line 14 skipping to change at page 6, line 14
3. Burst/Gap Loss Block 3. Burst/Gap Loss 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 are made at the
receiving end of the RTP stream. Instances of this Metrics Block receiving end of the RTP stream. Instances of this Metrics Block
refer by Synchronization source (SSRC) to the separate auxiliary refer by Synchronization source (SSRC) to the separate auxiliary
Measurement Information block [RFC6776] which describes measurement Measurement Information block [RFC6776] which describes measurement
periods in use(see RFC6776 section 4.2). This Metrics Block relies periods in use(see RFC6776 section 4.2). This Metrics Block relies
on the measurement period in the Measurement Information block on the measurement period in the Measurement Information block
indicating the span of the report and SHOULD be sent in the same indicating the span of the report and MUST be sent in the same
compound RTCP packet as the measurement information block. If the compound RTCP packet as the measurement information block. If the
measurement period is not received in the same compound RTCP packet measurement period is not received in the same compound RTCP packet
as this Metrics Block, this Metrics Block MUST be discarded. as this Metrics Block, this Metrics Block MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
Burst/Gap Loss metrics block Burst/Gap Loss metrics block
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
skipping to change at page 7, line 22 skipping to change at page 7, line 22
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. Accordingly, the value definite intervals, and cannot be sampled. Accordingly, the value
I=01, indicating a sampled value, MUST NOT be used. In addition, I=01, indicating a sampled value, MUST NOT be sent, and MUST be
the value I=00 is reserved and also MUST NOT be used. The block discarded when received. In addition, the value I=00 is reserved
MUST be discarded if the value I=01 or I=00 is received. and also MUST NOT be sent, and MUST be discarded when received.
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 MUST be set to '1' if the loss/discard RTCP packet. The value is set to '1' if the loss/discard report
report and the burst gap loss report are combined. Otherwise, the and the burst gap loss report are combined. Otherwise, the value
value MUST be set to '0'. If the burst gap discard is not sent is set to '0'. If the 'C' flag is set to 1 but the burst gap
with the burst gap loss, then the receiver MUST discard the burst discard was not sent, the receiver MUST discard the burst gap
gap loss with 'C' flag set to 1. If the 'C' flag is set to 0, loss.
then receiver MUST NOT discard the burst gap loss Metrics Block
when the burst gap discard is not received.
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 block, the block length is equal to 5. The
skipping to change at page 8, line 22 skipping to change at page 8, line 22
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 Gmin Calculation defined in section 4.7.2 of RFC3611.
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).
If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
measurement is unavailable, the value 0xFFFFFF MUST be reported. an over-range measurement. If the measurement is unavailable, the
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.
If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
measurement is unavailable, the value 0xFFFFFF MUST be reported. an over-range measurement. If the measurement is unavailable, the
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).
If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate
measurement is unavailable, the value 0xFFFFFF MUST be reported. an over-range measurement. If the measurement is unavailable, the
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).
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
measurement is unavailable, the value 0xFFFF MUST be reported. over-range measurement. If the measurement is unavailable, the
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) over 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.
If the measured value exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE The measured value is unsigned value. If the measured value
MUST be reported to indicate an over-range measurement. If the exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE MUST be reported to
measurement is unavailable, the value 0xFFFFFFFFF MUST be indicate an over-range measurement. If the measurement is
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] (which MUST be present in the same RTCP Information block [RFC6776] (which MUST be present in the same RTCP
packet as the Burst/Gap Loss block) and also with the metric packet as the Burst/Gap Loss block (see section 3,1st paragraph) )
"cumulative number of packets lost" provided in standard RTCP and also with the metric "cumulative number of packets lost" provided
[RFC3550]. 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
skipping to change at page 11, line 20 skipping to change at page 11, line 20
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 during which the loss rate is high enough to cause noticeable call
quality degradation (generally over 5 percent loss rate), and gaps, quality degradation (generally over 5 percent loss rate), and gaps,
which are periods during which lost packets are infrequent and hence which are periods during which lost packets are infrequent and hence
call quality is generally acceptable. call quality is generally acceptable.
If Voice Activity Detection is used the Burst and Gap Duration shall If Voice Activity Detection is used the Burst and Gap Duration shall
be determined as if silence packets had been sent, i.e. a period of be determined as if silence packets had been sent, i.e. a period of
silence in excess of Gmin packets MUST terminate a burst condition. silence in excess of Gmin packets must terminate a burst condition.
The recommended value for the threshold Gmin in [RFC3611] results in The recommended value for the threshold Gmin in [RFC3611] results in
a Burst being a period of time during which the call quality is a Burst being a period of time during which the call quality is
degraded to a similar extent to a typical Pulse-Code Modulation(PCM) degraded to a similar extent to a typical Pulse-Code Modulation(PCM)
Severely Errored Second. Severely Errored Second.
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
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.
xr-format =/ xr-bgl-block xr-format =/ xr-bgl-block
xr-bgl-block = "brst-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 offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral applies. For detailed usage in Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameter, refer to section 5.2 of [RFC3611].
6. IANA Considerations 6. IANA Considerations
skipping to change at page 13, line 22 skipping to change at page 13, line 22
This document assigns the block type value NBGL in the IANA " RTP This document assigns the block type value NBGL 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 [Note to RFC Editor: please replace NBGL with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
6.2. New RTCP XR SDP Parameter 6.2. New RTCP XR SDP Parameter
This document also registers a new parameter "brst-gap-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
It is believed that this proposed RTCP XR report block introduces no This block does not provide per-packet statistics, so the risk to
new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply. However the gaps indicated within this block could
be used to detect the timing of other events on the path between the
sender and receiver. For example, a competing multimedia stream
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.
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
believed that this proposed RTCP XR report block introduces no other
new security considerations beyond those described in [RFC3611].
8. Contributors 8. Contributors
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 and Alfred C.,Morton Jr. Dan Romascanu,Chris Lonvick, Alfred C.,Morton Jr., Pete Resnick, Ted
Lemon, Stephen Farrell, Richard Barnes, 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", March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
skipping to change at page 17, line 51 skipping to change at page 17, line 51
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] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, October 2012. using SDES item and XR Block", RFC 6776, October 2012.
[RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792, [RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792,
November 2012. November 2012.
[SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics [SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics
Reporting", ID draft-ietf-xrblock-rtcp-xr-summary-stat-05, Reporting", ID draft-ietf-xrblock-rtcp-xr-summary-stat-11,
December 2012. March 2013.
Appendix A. Change Log Appendix A. Metrics represented using RFC6390 Template
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC
number, when assigned.
a. Threshold Metric
* Metric Name: Threshold in RTP
* Metric Description: The Threshold is equivalent to Gmin in
[RFC3611], i.e. the number of successive RTP packets that must
be received prior to and following a lost RTP packet in order
for this lost RTP packet to be regarded as part of a gap.
* Method of Measurement or Calculation: See section 3.2,
Threshold definition [RFCXXXX].
* Units of Measurement: See section 3.2, Threshold definition
[RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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.
b. Sum of Burst Durations Metric
* Metric Name: Sum of Burst Durations in RTP
* Metric Description: The total duration of bursts of lost RTP
packets in the period of the report.
* Method of Measurement or Calculation: See section 3.2, Sum of
Burst Durations definition [RFCXXXX].
* Units of Measurement: See section 3.2, Sum of Burst Durations
definition [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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.
c. Packets lost in bursts Metric
* Metric Name: RTP Packets lost in bursts
* Metric Description: The total number of RTP packets lost
during loss bursts.
* Method of Measurement or Calculation: See section 3.2, Packets
lost in bursts definition [RFCXXXX].
* Units of Measurement: See section 3.2, Packets lost in bursts
definition [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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.
d. Total packets expected in bursts Metric
* Metric Name: Total RTP packets expected in bursts
* Metric Description: The total number of RTP packets expected
during loss bursts (that is, the sum of received RTP packets
and lost RTP packets).
* Method of Measurement or Calculation: See section 3.2, Total
packets expected in bursts definition [RFCXXXX].
* Units of Measurement: See section 3.2, Total packets expected
in bursts definition [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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.
e. Number of bursts Metric
* Metric Name: Number of bursts in RTP
* Metric Description: The total duration of bursts of lost RTP
packets in the period of the report.
* Method of Measurement or Calculation: See section 3.2, Number
of bursts definition [RFCXXXX].
* Units of Measurement: See section 3.2, Number of bursts
definition [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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.
f. Sum of Squares of Burst Durations Metric
* Metric Name: Sum of Squares of Burst Durations in RTP
* Metric Description: The sum of the squares of burst durations
(where individual burst durations are expressed in ms) over in
the period of the report.
* Method of Measurement or Calculation: See section 3.2, Sum of
Squares of Burst Durations definition [RFCXXXX].
* Units of Measurement: See section 3.2, Sum of Squares of Burst
Durations definition [RFCXXXX].
* Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX].
* Measurement Timing: See section 3, 1st 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 Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 B.1. 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.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o IETF LC comments are addressed together with AD's comment on o IETF LC comments are addressed together with AD's comment on
Normative language in this version. Normative language in this version.
A.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Move RFC6709 as one informative reference. o Move RFC6709 as one informative reference.
A.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Editorial changes based on comments in the WGLC. o Editorial changes based on comments in the WGLC.
A.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o SDP update based on SDP Directorate Review. o SDP update based on SDP Directorate Review.
o Add some texts to get consistent with RFC6798 and Delay draft. o Add some texts to get consistent with RFC6798 and Delay draft.
A.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Outdated reference update. o Outdated reference update.
o Editorial changes based on comments that applied to PDV and Delay o Editorial changes based on comments that applied to PDV and Delay
drafts. 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 (editor) 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 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. 32 change blocks. 
64 lines changed or deleted 234 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/