draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13.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 R. Huang Intended status: Standards Track R. Huang
Expires: October 14, 2013 Q. Wu, Ed. Expires: October 17, 2013 Q. Wu, Ed.
Huawei Huawei
April 12, 2013 April 15, 2013
RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap RTP Control Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
Discard metric Reporting Discard metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12.txt draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13.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 Discard metrics (XR) Block that allows the reporting of Burst and Gap Discard 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 35 skipping to change at page 1, line 35
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 October 14, 2013. This Internet-Draft will expire on October 17, 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.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12
6.3. Contact information for registrations . . . . . . . . . . 12 6.3. Contact information for registrations . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . . 16 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16
10.2. Informative References . . . . . . . . . . . . . . . . . . 16 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Metrics represented using RFC6390 Template . . . . . 17 Appendix A. Metrics represented using RFC6390 Template . . . . . 17
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20
B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12 . . . . . 20 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13 . . . . . 20
B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11 . . . . . 20 B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12 . . . . . 20
B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10 . . . . . 20 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11 . . . . . 20
B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-09 . . . . . 20 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10 . . . . . 20
B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 . . . . . 20
B.6. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06 . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
1.1. Burst and Gap Discard Report Block 1.1. Burst and Gap Discard Report 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 discarded by the supports the reporting of the proportion of packets discarded by the
receiver due to jitter. The discards during discard bursts are receiver due to jitter. The discards during discard bursts are
reported, together with the number of bursts. This block is intended reported, together with the number of bursts. This block is intended
to be used in conjunction with [DISCARD] which provides the total to be used in conjunction with [DISCARD] which provides the total
packets discarded, and on which this block therefore depends. packets discarded, and on which this block therefore depends.
However the metric in [DISCARD] may be used independently of the However the metric in [DISCARD] may be used independently of the
metrics in this block. metrics in this block.
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 discard may be used in Interval reports. The burstiness of packet discard
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 consistent with
definitions in [RFC3611]. To accommodate the range of jitter buffer definitions in [RFC3611]. To accommodate the range of jitter buffer
algorithms and packet discard logic that may be used by implementors, algorithms and packet discard logic that may be used by implementors,
the method used to distinguish between bursts and gaps may be an the method used to distinguish between bursts and gaps may be an
skipping to change at page 7, line 47 skipping to change at page 7, line 47
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 not be discarded prior to and of successive packets that must not be discarded prior to and
following a discard packet in order for this discarded packet to following a discard packet in order for this discarded packet to
be regarded as part of a gap. be regarded as part of a gap. Note that the threshold is
calculated in accordance with Gmin Calculation defined in section
4.7.2 of RFC3611.
Packets discarded in bursts: 24 bits Packets discarded in bursts: 24 bits
The total number of packets discarded during discard bursts. The total number of packets discarded during discard bursts.
The measured value is unsigned value. If the measured value The measured value is 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.
skipping to change at page 8, line 34 skipping to change at page 8, line 35
Reserved (resv): 8 bits Reserved (resv): 8 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).
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 in conjunction The metrics described here are intended to be used in conjunction
with information from the Measurement Information block [RFC6776] and with information from the Measurement Information block [RFC6776] and
also with the metric "number of packets discarded" provided in the also with the metric "number of packets discarded" provided in the
RTCP XR Discard Count Block [DISCARD]. The RTCP XR Discard Count RTCP XR Discard Count Block [DISCARD].
Block should be sent if the Burst/Gap Discard block is sent, but the
converse does not apply.
These metrics provide the following information relevant to These metrics provide the following information relevant to
statistical parameters, including: statistical parameters, including:
o The fraction of packets discarded during bursts (burst discard o The fraction of packets discarded during bursts (burst discard
rate in [SUMSTAT]), which can be calculated using the metric " rate in [SUMSTAT]), which can be calculated using the metric "
Packets Discarded in Bursts " and the metric " Total Packets Packets Discarded in Bursts " and the metric " Total Packets
expected in Bursts " provided in the Burst/Gap Discard metrics expected in Bursts " provided in the Burst/Gap Discard metrics
block. block.
skipping to change at page 10, line 18 skipping to change at page 10, line 18
applications. Where the metric is used with a Voice-overIP (VoIP) applications. Where the metric is used with a Voice-overIP (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 discard rate is high enough to cause noticeable call during which the discard rate is high enough to cause noticeable call
quality degradation (generally over 5 percent discard rate), and quality degradation (generally over 5 percent discard rate), and
gaps, which are periods during which discarded packets are infrequent gaps, which are periods during which discarded packets are infrequent
and hence call quality is generally acceptable. and hence 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 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] 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
skipping to change at page 20, line 10 skipping to change at page 20, line 10
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix B. Change Log 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.
B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12 B.1. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
The following are the major changes compared to previous version:
o Additional editorial changes to Burst Gap discard draft to get in
line with Burst Gap Loss draft.
B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-12
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Similar changes to Burst Gap loss draft to get in line with Burst o Similar changes to Burst Gap loss draft to get in line with Burst
Gap Loss draft. Gap Loss draft.
B.2. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11 B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Similar changes to Burst Gap loss draft to address IESG review o Similar changes to Burst Gap loss draft to address IESG review
comments apply to this document. comments apply to this document.
B.3. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10 B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10
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.
B.4. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-09
The following are the major changes compared to previous version:
o Editorial changes based on comments received in WGLC.
B.5. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08
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.6. draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06
The following are the major changes compared to previous version:
o Outdated reference update.
o Editorial changes based on comments that applied to PDV and Delay
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
 End of changes. 14 change blocks. 
43 lines changed or deleted 25 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/