draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09.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, Ed.
Expires: July 21, 2013 J. Zhao Expires: September 22, 2013 J. Zhao
STTRI STTRI
Q. Wu Q. Wu
Huawei Huawei
January 17, 2013 March 21, 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-08.txt draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09.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 July 21, 2013. This Internet-Draft will expire on September 22, 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 36 skipping to change at page 2, line 36
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. Change Log . . . . . . . . . . . . . . . . . . . . . 18
A.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 18 A.1. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09 . . . . . . . 18
A.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 18 A.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08 . . . . . . . 18
A.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 18 A.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 . . . . . . . 18
A.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 18 A.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 . . . . . . . 18
A.5. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
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 draft 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
skipping to change at page 3, line 33 skipping to change at page 3, line 33
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
equivalent method to that defined in [RFC3611]. The method used equivalent method to that defined in [RFC3611]. The method used
SHOULD produce the same result as that defined in [RFC3611] for should produce the same result as that defined in [RFC3611] for
conditions of burst packet loss, but MAY produce different results conditions of burst packet loss, but may produce different results
for conditions of time varying jitter. 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 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
skipping to change at page 7, line 28 skipping to change at page 7, line 28
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 used. In addition,
the value I=00 is reserved and also MUST NOT be used. The block the value I=00 is reserved and also MUST NOT be used. The block
MUST be discarded if the value I=01 or I=00 is received. MUST be discarded if the value I=01 or I=00 is 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 combining loss/discard The 'C' flag is used to indicate whether the loss/discard report
report is needed. This field MUST be set to '1' if the burst gap is combined with the burst gap loss report in the same compound
loss report is present in conjunction with the burst gap discard RTCP packet. The value MUST be set to '1' if the loss/discard
report in the same compound RTCP packet and MUST be set to '0' report and the burst gap loss report are combined. Otherwise, the
otherwise. If the burst gap discard is not sent with the burst value MUST be set to '0'. If the burst gap discard is not sent
gap loss, then the receiver MUST discard the burst gap loss with with the burst gap loss, then the receiver MUST discard the burst
'C' flag set to 1. If the 'C' flag is set to 0, then receiver gap loss with 'C' flag set to 1. If the 'C' flag is set to 0,
MUST NOT discard the burst gap loss Metrics Block when the burst then receiver MUST NOT discard the burst gap loss Metrics Block
gap discard is not received. 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). The block MUST be ignored by receivers (See RFC6709 section 4.2).
discarded if the block length is set to a different value.
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
block MUST be discarded if the block length is set to a different block MUST be discarded if the block length is set to a different
value. 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. of a gap. Note that the threshold is calculated in accordance
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 If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFF MUST be reported. measurement is unavailable, the value 0xFFFFFF MUST be reported.
skipping to change at page 16, line 12 skipping to change at page 16, line 12
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 and Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Adam Roach,
Dan Romascanu.. Dan Romascanu,Chris Lonvick and Alfred C.,Morton Jr.
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 18, line 10 skipping to change at page 18, line 10
[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-05,
December 2012. December 2012.
Appendix A. Change Log Appendix A. 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-08 A.1. 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.
A.2. 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.2. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07 A.3. 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.3. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 A.4. 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.4. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 A.5. 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
 End of changes. 14 change blocks. 
28 lines changed or deleted 36 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/