draft-ietf-xrblock-independent-burst-gap-discard-00.txt   draft-ietf-xrblock-independent-burst-gap-discard-01.txt 
Audio/Video Transport Working Group V. Singh Audio/Video Transport Working Group V. Singh
Internet-Draft callstats.io Internet-Draft callstats.io
Intended status: Standards Track C. Perkins Intended status: Standards Track C. Perkins
Expires: June 15, 2016 University of Glasgow Expires: September 22, 2016 University of Glasgow
A. Clark A. Clark
Telchemy Telchemy
R. Huang R. Huang
Huawei Huawei
December 13, 2015 March 21, 2016
RTP Control Protocol (RTCP) Extended Report (XR) Block for Independent RTP Control Protocol (RTCP) Extended Report (XR) Block for Independent
Reporting of Burst/Gap Discard Metric Reporting of Burst/Gap Discard Metric
draft-ietf-xrblock-independent-burst-gap-discard-00 draft-ietf-xrblock-independent-burst-gap-discard-01
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 discard metrics (XR) block that allows the reporting of burst and gap discard metrics
independently of the burst and gap loss metrics for use in a range of independently of the burst and gap loss metrics for use in a range of
RTP applications. RTP applications.
Status of This Memo Status of This Memo
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 June 15, 2016. This Internet-Draft will expire on September 22, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
3.3. Derived Metrics Based on the Reported Metrics . . . . . . 7 3.3. Derived Metrics Based on the Reported Metrics . . . . . . 7
4. Considerations for Voice-over-IP Applications . . . . . . . . 8 4. Considerations for Voice-over-IP Applications . . . . . . . . 8
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . 8 5.1. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . 8
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 9 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. New RTCP XR Block Type Value . . . . . . . . . . . . . . 9 6.1. New RTCP XR Block Type Value . . . . . . . . . . . . . . 9
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
6.3. Contact Information for Registrations . . . . . . . . . . 9 6.3. Contact Information for Registrations . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . 10 10.1. Normative References . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Metrics Represented Using the Template from RFC 6390 12 Appendix A. Metrics Represented Using the Template from RFC 6390 13
1. Introduction 1. Introduction
1.1. Burst-Gap Discard Metrics Block 1.1. Burst-Gap Discard Metrics Block
This document defines a new block type that extends the metrics This document defines a new block type that extends the metrics
defined in [RFC7003], the metrics in this report block can be used in defined in [RFC7003]. The new block type reports the proportion of
a range of RTP applications. The new block type reports the packets discarded in a burst by the dejitter buffer at the receiver.
proportion of packets discarded by the jitter buffer at the receiver The number of packets discarded depends on the dejitter buffer
in a burst and number of packets discarded depends on the de-jitter algorithm implemented by the endpoint.
buffer algorithm implemented by the endpoint.
The new report block defined in this document is different from the The new report block defined in this document is different from the
one defined in [RFC7003]. The metrics in [RFC7003] depends on the one defined in [RFC7003]. The metrics in [RFC7003] depends on the
metrics in the burst-gap loss metric defined in [RFC6958]. metrics in the burst-gap loss metric defined in [RFC6958].
Consequently, an endpoint using [RFC7003] MUST report it along with Consequently, an endpoint using [RFC7003] MUST report it along with
[RFC6958] for it to be useful. The combined usage is useful when an [RFC6958] for it to be useful. The combined usage is useful when an
endpoint observes correlated packet losses and discard. However, endpoint observes correlated packet losses and discard. However,
when the burst of packet losses and discards do not occur when the burst of packet losses and discards do not occur
simultaneously, the application may prefer a concise report block simultaneously, the application may prefer a concise report block
that just reports the burst-gap of discarded packets. The report that just reports the burst-gap of discarded packets. The report
block in this document provides the complete information and does not block in this document provides the complete information and does not
require additional report blocks. That is, this block reports: the require additional report blocks. That is, this block reports: the
total number of packets discarded, the total burst duration, and the total number of packets discarded, the total burst duration, and the
total number of bursts, all of these metrics are missing in total number of bursts, all of these metrics are missing in
[RFC7003]. [RFC7003].
skipping to change at page 3, line 20 skipping to change at page 3, line 19
that just reports the burst-gap of discarded packets. The report that just reports the burst-gap of discarded packets. The report
block in this document provides the complete information and does not block in this document provides the complete information and does not
require additional report blocks. That is, this block reports: the require additional report blocks. That is, this block reports: the
total number of packets discarded, the total burst duration, and the total number of packets discarded, the total burst duration, and the
total number of bursts, all of these metrics are missing in total number of bursts, all of these metrics are missing in
[RFC7003]. [RFC7003].
This block provides information on transient network issues. Burst/ This block provides information on transient network issues. Burst/
gap metrics are typically used in cumulative reports; however, they gap metrics are typically used in cumulative reports; however, they
may also be used in interval reports (see the Interval Metric flag in may also be used in interval reports (see the Interval Metric flag in
Section 3.2). The variation in the number of packet discard in a Section 3.2). The variation in the number of packet discards in a
burst affects the user experience. Based on the metrics reported in burst affects the user experience. Based on the metrics reported in
the block, the sending endpoint may change the packetisation the block, the sending endpoint may change the packetization
interval, vary the bitrate, etc. The report may additionally be used interval, vary the bitrate, etc. The report may additionally be used
for diagnostics [RFC6792]. The metric belongs to the class of for diagnostics [RFC6792]. The metric belongs to the class of
transport-related end-system metrics defined in [RFC6792]. transport-related end-system metrics defined in [RFC6792].
The definitions of "burst", "gap", "loss", and "discard" are The definitions of "burst", "gap", "loss", and "discard" are
consistent with the definitions in [RFC3611]. To accommodate the consistent with the definitions in [RFC3611]. To accommodate a range
range of jitter buffer algorithms and packet discard logic that may of dejitter buffer algorithms and packet discard logic that may be
be used by implementors, the method used to distinguish between used by implementors, the method used to distinguish between bursts
bursts and gaps shall use an equivalent method to that defined in and gaps shall use an equivalent method to that defined in
Section 4.7.2 of [RFC3611]. Note that reporting the specific jitter Section 4.7.2 of [RFC3611]. Note that reporting the specific
buffer algorithms and/or packet discard logic is out of the scope of dejitter buffer algorithm and/or the packet discard logic is out of
this document. the scope of this document.
1.2. RTCP and RTCP Extended Reports 1.2. RTCP and RTCP Extended Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611]. 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 RTP
Monitoring Framework [RFC6792] provides guidelines for reporting Monitoring Framework [RFC6792] provides guidelines 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 is in accordance with the guidelines in [RFC6390] and document is 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 that These metrics are applicable to a range of RTP applications that
contain de-jitter buffers [RFC5481] at the receiving end to smooth contain dejitter buffers [RFC5481] at the receiving end to smooth
variation in packet-arrival time and don't use stream repair means, variation in packet-arrival time and don't use stream repair means,
e.g., Forward Error Correction (FEC) e.g., Forward Error Correction (FEC)
[I-D.ietf-payload-flexible-fec-scheme] and/or retransmission [I-D.ietf-payload-flexible-fec-scheme] and/or retransmission
[RFC4588]. [RFC4588].
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 RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 5, line 5 skipping to change at page 5, line 5
different types of discard counts [RFC7002]. different types of discard counts [RFC7002].
Bursts and Gaps Bursts and Gaps
The terms "burst" and "gap" are used in a manner consistent with The terms "burst" and "gap" are used in a manner consistent with
that of RTCP XR [RFC3611]. RTCP XR views an RTP stream as being that of RTCP XR [RFC3611]. RTCP XR views an RTP stream as being
divided into bursts, which are periods during which the discard divided into bursts, which are periods during which the discard
rate is high enough to cause noticeable quality degradation rate is high enough to cause noticeable quality degradation
(generally over 5 percent discard rate), and gaps, which are (generally over 5 percent discard rate), and gaps, which are
periods during which discarded packets are infrequent and hence periods during which discarded packets are infrequent and hence
quality is generally acceptable. quality is generally acceptable. [RFC3611] RECOMMENDS a Gmin
value of 16.
3. Burst/Gap Discard Metrics Block 3. Burst/Gap Discard Metrics Block
Metrics in this block report on burst/gap discard in the stream Metrics in this block report on burst/gap discard in the stream
arriving at the RTP system. Measurements of these metrics are made arriving at the RTP system. Measurements of these metrics are made
at the receiving end of the RTP stream. Instances of this metrics at the receiving end of the RTP stream. Instances of this metrics
block use the synchronization source (SSRC) to refer to the separate block use the synchronization source (SSRC) to refer to the separate
auxiliary Measurement Information Block [RFC6776], which describes auxiliary Measurement Information Block [RFC6776], which describes
measurement periods in use (see [RFC6776], Section 4.2). measurement periods in use (see [RFC6776], Section 4.2).
skipping to change at page 5, line 27 skipping to change at page 5, line 28
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
The structure of the Burst/Gap Discard Metrics Block is as follows. The structure of the Burst/Gap Discard 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=IBGD | I | resv | block length | | BT=IBGD | I | resv | Block Length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Sum of Burst Durations (ms) | | Threshold | Sum of Burst Durations (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Discarded in Bursts | Number of | | Packets Discarded in Bursts | Number of |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bursts | Total Packets Expected in Bursts | | Bursts | Total Packets Expected in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Count | | Discard Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Burst/Gap Discard Metrics Block 3.2. Definition of Fields in Burst/Gap Discard Metrics Block
Block Type (BT): 8 bits Block Type (BT): 8 bits
A Burst/Gap Discard Metrics Block is identified by the constant A Burst/Gap Discard Metrics Block is identified by the constant
IBGD. IBGD.
[Note to RFC Editor: Please replace IBGD with the IANA provided [Note to RFC Editor: Please replace IBGD with the IANA provided
RTCP XR block type for this block.] 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 discard This field is used to indicate whether the burst/gap discard
metrics are Sampled, Interval, or Cumulative metrics [RFC6792]: metrics are Sampled, Interval, or Cumulative metrics [RFC6792]:
skipping to change at page 7, line 32 skipping to change at page 7, line 35
The number of discard bursts in the period of the report (Interval The number of discard bursts in the period of the report (Interval
or Cumulative). or Cumulative).
The measured value is an 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.
Total Packets Expected in Bursts: 24 bits Total Packets Expected in Bursts: 24 bits
The total number of packets expected during discarded bursts (that The total number of packets expected during the discard bursts
is, the sum of received packets and lost packets). The metric is (that is, the sum of received packets and lost packets). The
defined in [RFC7003]. metric is defined in [RFC7003].
Discard Count: 32 bits Discard Count: 32 bits
Number of packets discarded over the period (Interval or Number of packets discarded over the period (Interval or
Cumulative) covered by this report, as defined in Section 3.2 of Cumulative) covered by this report, as defined in Section 3.2 of
[RFC7002]. [RFC7002].
3.3. Derived Metrics Based on the Reported Metrics 3.3. Derived Metrics Based on the Reported Metrics
The metrics described here are intended to be used in conjunction The metrics described here are intended to be used in conjunction
with information from the Measurement Information Block [RFC6776]. with information from the Measurement Information Block [RFC6776].
These metrics provide the following information relevant to These metrics provide the following information relevant to
statistical parameters (depending on cumulative of interval statistical parameters (depending on cumulative of interval
measures), for example: measures), for example:
o The average discarded burst size, which can be calculated by o The average discarded burst size, which can be calculated by
dividing the metric "Packets Discarded in Bursts" with the "Number dividing the metric "Packets Discarded in Bursts" by the "Number
of Bursts". of Bursts".
o The average burst duration, which can be calculated by dividing o The average burst duration, which can be calculated by dividing
the metric "Sum of Burst Durations (ms)" with the "Number of the metric "Sum of Burst Durations (ms)" by the "Number of
bursts". bursts".
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-over-IP (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
skipping to change at page 9, line 37 skipping to change at page 9, line 41
6.2. New RTCP XR SDP Parameter 6.2. New RTCP XR SDP Parameter
This document also registers a new parameter "ind-burst-gap-discard" This document also registers a new parameter "ind-burst-gap-discard"
in the "RTP Control Protocol Extended Reports (RTCP XR) Session in the "RTP Control Protocol Extended Reports (RTCP XR) Session
Description Protocol (SDP) Parameters Registry". Description 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:
RAI Area Directors <rai-ads@tools.ietf.org> ART Area Directors <art-ads@tools.ietf.org>
7. Security Considerations 7. Security Considerations
It is believed that this RTCP XR block introduces no new security It is believed that this RTCP XR block introduces no new security
considerations beyond those described in [RFC3611]. This block does considerations beyond those described in [RFC3611]. This block does
not provide per-packet statistics, so the risk to confidentiality not provide per-packet statistics, so the risk to confidentiality
documented in Section 7, paragraph 3 of [RFC3611] does not apply. documented in Section 7, paragraph 3 of [RFC3611] does not apply.
8. Contributors 8. Contributors
Qin Wu, Rachel Huang, and Alan Clark wrote RFC7003, which this Qin Wu, Rachel Huang, and Alan Clark wrote RFC7003, which this
document extends. document extends.
9. Acknowledgments 9. Acknowledgments
The authors acknowledge the reviews and feedback provided by various The authors would like to thank Paul Kyzivat, Jan Novak, Dan
people. Romascanu for providing valuable feedback on earlier versions of this
draft.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
Protocol Extended Reports (RTCP XR)", RFC 3611, November "RTP Control Protocol Extended Reports (RTCP XR)", RFC
2003. 3611, DOI 10.17487/RFC3611, November 2003,
<http://www.rfc-editor.org/info/rfc3611>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/ Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/
RFC5234, January 2008, RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <http://www.rfc-editor.org/info/rfc5234>.
[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 2010. Reports (XRs)", RFC 5725, DOI 10.17487/RFC5725, February
2010, <http://www.rfc-editor.org/info/rfc5725>.
[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, DOI 10.17487/
RFC6776, October 2012,
<http://www.rfc-editor.org/info/rfc6776>.
[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003,
September 2013, <http://www.rfc-editor.org/info/rfc7003>.
10.2. Informative References 10.2. Informative References
[I-D.ietf-payload-flexible-fec-scheme] [I-D.ietf-payload-flexible-fec-scheme]
Singh, V., Begen, A., Zanaty, M., and G. Mandyam, "RTP Singh, V., Begen, A., Zanaty, M., and G. Mandyam, "RTP
Payload Format for Flexible Forward Error Correction Payload Format for Flexible Forward Error Correction
(FEC)", draft-ietf-payload-flexible-fec-scheme-01 (work in (FEC)", draft-ietf-payload-flexible-fec-scheme-01 (work in
progress), October 2015. progress), October 2015.
[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hakenberg, "RTP Retransmission Payload Format", RFC 4588, Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
July 2006. DOI 10.17487/RFC4588, July 2006,
<http://www.rfc-editor.org/info/rfc4588>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, Applicability Statement", RFC 5481, DOI 10.17487/RFC5481,
March 2009, <http://www.rfc-editor.org/info/rfc5481>. March 2009, <http://www.rfc-editor.org/info/rfc5481>.
[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, DOI
October 2011. 10.17487/RFC6390, October 2011,
<http://www.rfc-editor.org/info/rfc6390>.
[RFC6709] Carpenter, B., Aboba, B., Ed., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., Ed., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, DOI Considerations for Protocol Extensions", RFC 6709, DOI
10.17487/RFC6709, September 2012, 10.17487/RFC6709, September 2012,
<http://www.rfc-editor.org/info/rfc6709>. <http://www.rfc-editor.org/info/rfc6709>.
[RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use [RFC6792] Wu, Q., Ed., Hunt, G., and P. Arden, "Guidelines for Use
of the RTP Monitoring Framework", RFC 6792, DOI 10.17487/ of the RTP Monitoring Framework", RFC 6792, DOI 10.17487/
RFC6792, November 2012, RFC6792, November 2012,
<http://www.rfc-editor.org/info/rfc6792>. <http://www.rfc-editor.org/info/rfc6792>.
[RFC6958] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control [RFC6958] Clark, A., Zhang, S., Zhao, J., and Q. Wu, Ed., "RTP
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Control Protocol (RTCP) Extended Report (XR) Block for
Loss Metric Reporting", RFC 6958, May 2013. Burst/Gap Loss Metric Reporting", RFC 6958, DOI 10.17487/
RFC6958, May 2013,
<http://www.rfc-editor.org/info/rfc6958>.
[RFC7002] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol [RFC7002] Clark, A., Zorn, G., and Q. 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", RFC 7002, DOI 10.17487/RFC7002, September
2013, <http://www.rfc-editor.org/info/rfc7002>.
[RFC7003] Clark, A., Huang, R., and Q. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Burst/Gap Discard
Metric Reporting", RFC 7003, September 2013.
Appendix A. Metrics Represented Using the Template from RFC 6390 Appendix A. Metrics Represented Using the Template from RFC 6390
a. Threshold Metric a. Threshold Metric
* Defined in Appenix A.a of [RFC7003]. * Defined in Appendix A.a of [RFC7003].
b. Sum of burst durations (ms) b. Sum of burst durations (ms)
* Metric Name: Sum of Burst Durations with Discarded RTP * Metric Name: Sum of Burst Durations with Discarded RTP
Packets. Packets.
* Metric Description: The total duration of bursts of discarded * Metric Description: The total duration of bursts of discarded
RTP packets in the period of the report. RTP packets in the period of the report.
* Method of Measurement or Calculation: See Section 3.1, Sum of * Method of Measurement or Calculation: See Section 3.1, Sum of
skipping to change at page 12, line 37 skipping to change at page 13, line 37
* Measurement Timing: See Section 3, 2nd paragraph for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and Section 3.1 for Interval Metric flag. measurement timing and Section 3.1 for Interval Metric flag.
* Use and Applications: See Section 1.4. * Use and Applications: See Section 1.4.
* Reporting Model: See RFC 3611. * Reporting Model: See RFC 3611.
c. Packets Discarded in Bursts Metric c. Packets Discarded in Bursts Metric
* Defined in Appenix A.b of [RFC7003]. * Defined in Appendix A.b of [RFC7003].
d. Number of bursts d. Number of bursts
* Metric Name: Number of discard bursts in RTP. * Metric Name: Number of discard bursts in RTP.
* Metric Description: The total number of bursts with discarded * Metric Description: The total number of bursts with discarded
RTP packets in the period of the report. RTP packets in the period of the report.
* Method of Measurement or Calculation: See Section 3.1, Number * Method of Measurement or Calculation: See Section 3.1, Number
of discard bursts definition. of discard bursts definition.
skipping to change at page 13, line 17 skipping to change at page 14, line 17
* Measurement Timing: See Section 3, 2nd paragraph for * Measurement Timing: See Section 3, 2nd paragraph for
measurement timing and Section 3.1 for Interval Metric flag. measurement timing and Section 3.1 for Interval Metric flag.
* Use and Applications: See Section 1.4. * Use and Applications: See Section 1.4.
* Reporting Model: See RFC 3611. * Reporting Model: See RFC 3611.
e. Total Packets Expected in Bursts Metric e. Total Packets Expected in Bursts Metric
* Defined in Appenix A.c of [RFC7003]. * Defined in Appendix A.c of [RFC7003].
f. Discard Count f. Discard Count
* Defined in Appenix A.a of [RFC7002]. * Defined in Appendix A.a of [RFC7002].
Authors' Addresses Authors' Addresses
Varun Singh Varun Singh
Nemu Dialogue Systems Oy Nemu Dialogue Systems Oy
Runeberginkatu 4c A 4 Runeberginkatu 4c A 4
Helsinki 00100 Helsinki 00100
Finland Finland
EMail: varun@callstats.io EMail: varun.singh@iki.fi
URI: http://www.callstats.io/ URI: http://www.callstats.io/
Colin Perkins Colin Perkins
University of Glasgow University of Glasgow
School of Computing Science School of Computing Science
Glasgow G12 8QQ Glasgow G12 8QQ
United Kingdom United Kingdom
EMail: csp@csperkins.org EMail: csp@csperkins.org
 End of changes. 37 change blocks. 
73 lines changed or deleted 87 lines changed or added

This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/