draft-ietf-xrblock-rtcp-xr-discard-11.txt   draft-ietf-xrblock-rtcp-xr-discard-12.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 G. Zorn Intended status: Standards Track G. Zorn
Expires: June 22, 2013 Network Zen Expires: October 13, 2013 Network Zen
Q. Wu Q. Wu
Huawei Huawei
December 19, 2012 April 11, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count
metric Reporting metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-11.txt draft-ietf-xrblock-rtcp-xr-discard-12.txt
Abstract Abstract
This document defines an RTP Control Protocol(RTCP) Extended Report This document defines an RTP Control Protocol(RTCP) Extended Report
(XR) Block that allows the reporting of a simple discard count metric (XR) Block that allows the reporting of a simple discard count metric
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 36 skipping to change at page 1, line 36
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 22, 2013. This Internet-Draft will expire on October 13, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 33 skipping to change at page 2, line 33
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
5.3. Contact information for registrations . . . . . . . . . . 10 5.3. Contact information for registrations . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Metrics represented using RFC6390 Template . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-discard-11 . . . . . . . . . . 15 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 16
A.2. draft-ietf-xrblock-rtcp-xr-discard-10 . . . . . . . . . . 15 B.1. draft-ietf-xrblock-rtcp-xr-discard-12 . . . . . . . . . . 16
A.3. draft-ietf-xrblock-rtcp-xr-discard-09 . . . . . . . . . . 15 B.2. draft-ietf-xrblock-rtcp-xr-discard-11 . . . . . . . . . . 16
A.4. draft-ietf-xrblock-rtcp-xr-discard-08 . . . . . . . . . . 15 B.3. draft-ietf-xrblock-rtcp-xr-discard-10 . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 B.4. draft-ietf-xrblock-rtcp-xr-discard-09 . . . . . . . . . . 16
B.5. draft-ietf-xrblock-rtcp-xr-discard-08 . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
1.1. Discard Count Report Block 1.1. Discard Count 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 number of packets which are received supports the reporting of the number of packets which are received
correctly but are never played out, typically because they arrive too correctly but are never played out, typically because they arrive too
late to be played out (buffer underflow) or too early (buffer late to be played out (buffer underflow) or too early (buffer
skipping to change at page 6, line 14 skipping to change at page 6, line 14
3. Discard Count Metric Report Block 3. Discard Count Metric Report Block
Metrics in this block report on the number of packets discarded in Metrics in this block report on the number of packets discarded in
the stream arriving at the RTP end system. The measurement of these the stream arriving at the RTP end system. The measurement of these
metrics is made at the receiving end of the RTP stream. Instances of metrics is made at the receiving end of the RTP stream. Instances of
this Metrics Block refer by SSRC to the separate auxiliary this Metrics Block refer by SSRC to the separate auxiliary
Measurement Information block [RFC6776] which describes measurement Measurement Information block [RFC6776] which describes measurement
Intervals in use. This Metrics Block relies on the measurement Intervals in use. This Metrics Block relies on the measurement
interval in the Measurement Information block indicating the span of interval in the Measurement Information block indicating the span of
the report and should be sent in the same compound RTCP packet as the the report and MUST be sent in the same compound RTCP packet as the
measurement information block. If the measurement interval is not measurement information block. If the measurement interval is not
received in the same compound RTCP packet as this Metrics Block, this received in the same compound RTCP packet as this Metrics Block, this
Metrics Block should be discarded. Metrics Block MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
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=PDC | I |DT | resv.| block length = 2 | | BT=PDC | I |DT | resv.| block length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 49 skipping to change at page 6, line 49
[Note to RFC Editor: please replace PDC with the IANA provided [Note to RFC Editor: please replace PDC 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 indicates whether the reported metric is an interval, This field indicates whether the reported metric is an interval,
cumulative, or sampled metric [RFC6792]. The Discard Count Metric cumulative, or sampled metric [RFC6792]. The Discard Count Metric
can only be measured over definite intervals, and cannot be can only be measured over definite intervals, and cannot be
sampled. Accordingly, the value I=01, indicating a sampled value, sampled. Accordingly, the value I=01, indicating a sampled value,
MUST NOT be used. The value I=00 is reserved for future MUST NOT be sent, and MUST be discarded when received. In
definition, and MUST NOT be used. addition, the value I=00 is reserved and also MUST NOT be sent,
and MUST be discarded when received.
Discard Type (DT): 2bits Discard Type (DT): 2bits
This field is used to identify the discard type used in this This field is used to identify the discard type used in this
report block. The discard type is defined as follows: report block. The discard type is defined as follows:
00: Report packet discarded or being thrown away before playout 00: Report packet discarded or being thrown away before playout
due to packets duplication. due to packets duplication.
01: Report packet discarded due to too early to be played out. 01: Report packet discarded due to too early to be played out.
10: Report packet discarded due to too late to be played out. 10: Report packet discarded due to too late to be played out.
The value DT=11 is reserved for future definition and MUST NOT be The value DT=11 is reserved for future definition and MUST NOT be
used. Sent,and MUST be discarded when received.
An endpoint MAY report any combination of discard types in each An endpoint MAY report any combination of discard types in each
reporting interval by including several Discard Count Metric reporting interval by including several Discard Count Metric
Report Blocks in a single RTCP XR packet. Report Blocks in a single RTCP XR packet.
Some systems send duplicate RTP packets for robustness or error Some systems send duplicate RTP packets for robustness or error
resilience. This is NOT RECOMMENDED since it breaks RTCP packet resilience. This is NOT RECOMMENDED since it breaks RTCP packet
statistics. If duplication is desired for error resilience, the statistics. If duplication is desired for error resilience, the
mechanism described in [RTPDUP] can be used, since this will not mechanism described in [RTPDUP] can be used, since this will not
cause breakage of RTP streams or RTCP statistics. cause breakage of RTP streams or RTCP statistics.
skipping to change at page 8, line 10 skipping to change at page 8, line 10
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].
number of packets discarded: 32 bits number of packets discarded: 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. Cumulative) covered by this report.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE The measured value is unsigned value. If the measured value
MUST be reported to indicate an over-range measurement. If the exceeds 0xFFFFFFFD, the value 0xFFFFFFFE MUST be reported to
measurement is unavailable, the value 0xFFFFFFFF MUST be reported. indicate an over-range measurement. If the measurement is
unavailable, the value 0xFFFFFFFF MUST be reported.
Note that the number of packets expected in the period associated Note that the number of packets expected in the period associated
with this metric (whether interval or cumulative) is available with this metric (whether interval or cumulative) is available
from the difference between a pair of extended sequence numbers in from the difference between a pair of extended sequence numbers in
the Measurement Information block [RFC6776], so need not be the Measurement Information block [RFC6776], so need not be
repeated in this block. repeated in this block.
4. SDP Signaling 4. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
skipping to change at page 9, line 19 skipping to change at page 9, line 19
be used without prior signaling (see section 5 of RFC3611). be used without prior signaling (see section 5 of RFC3611).
4.1. SDP rtcp-xr-attrib Attribute Extension 4.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-pdc-block xr-format =/ xr-pdc-block
xr-pdc-block = "pkt-dscrd-count" xr-pdc-block = "pkt-discard-count"
4.2. Offer/Answer Usage 4.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 of Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameter, refer to section 5.2 of [RFC3611].
5. IANA Considerations 5. IANA Considerations
skipping to change at page 10, line 22 skipping to change at page 10, line 22
This document assigns the block type value PDC in the IANA " RTP This document assigns the block type value PDC 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 "Discard Count Metrics Block". the "Discard Count Metrics Block".
[Note to RFC Editor: please replace PDC with the IANA provided RTCP [Note to RFC Editor: please replace PDC with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "pkt-dscrd-count" in the This document also registers a new parameter "pkt-discard-count" in
" RTP Control Protocol Extended Reports (RTCP XR) Session Description the " RTP Control Protocol Extended Reports (RTCP XR) Session
Protocol (SDP) Parameters Registry ". Description Protocol (SDP) Parameters Registry ".
5.3. Contact information for registrations 5.3. Contact information for registrations
The following contact information is provided for all The following contact information is provided for all
registrations in this document: registrations in this document:
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
skipping to change at page 13, line 12 skipping to change at page 13, line 12
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
8. Acknowledgments 8. 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, and Hideaki Yamada,Kevin Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada, Kevin
Gross, Varun Singh, Claire Bi, Roni Even, Dan Romascanu and Jonathan Gross, Varun Singh, Claire Bi, Roni Even, Dan Romascanu and Jonathan
Lennox. Lennox.
9. References 9. References
9.1. Normative References 9.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.
skipping to change at page 14, line 33 skipping to change at page 14, line 33
September 2012. September 2012.
[RFC6776] Hunt, G., "Measurement Identity and information Reporting [RFC6776] Hunt, G., "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.
9.2. Informative References 9.2. Informative References
[BGDISCARD] [BGDISCARD]
Hunt, G., "RTCP XR Report Block for Burst Gap Discard Hunt, G., "RTCP XR Report Block for Burst Gap Discard
metric Reporting", metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06, ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-11,
October 2012. April 2013.
[RFC4588] Rey, J., "RTP Retransmission Payload Format", RFC 4588, [RFC4588] Rey, J., "RTP Retransmission Payload Format", RFC 4588,
July 2006. July 2006.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, July 2006. Correction", RFC 5109, July 2006.
[RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss [RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss
metric Reporting", RFC 5725, February 2010. metric Reporting", RFC 5725, February 2010.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 2011.
[RFC6792] Wu, Q., "Monitoring Architectures for RTP", RFC 6792, [RFC6792] Wu, Q., "Monitoring Architectures for RTP", RFC 6792,
November 2012. November 2012.
[RTPDUP] Begen, A. and C. Perkins, "Duplicating RTP Streams", [RTPDUP] Begen, A. and C. Perkins, "Duplicating RTP Streams",
ID draft-ietf-avtext-rtp-duplication-00, July 2012. ID draft-ietf-avtext-rtp-duplication-02, 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. Number of packets discarded Metric
* Metric Name: Number of RTP packets discarded Metric
* Metric Description: Number of RTP packets discarded over the
period covered by this report.
* Method of Measurement or Calculation: See section 3.2, number
of packets discarded definition [RFCXXXX].
* Units of Measurement: See section 3.2, number of packets
discarded 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-discard-11 B.1. draft-ietf-xrblock-rtcp-xr-discard-12
The following are the major changes compared to previous version:
o Incorporate some changes to burst gap draft that applies to this
document.
o Use RFC6390 template to the metrics in the appendix.
B.2. draft-ietf-xrblock-rtcp-xr-discard-11
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Editorial change t based on SDP Directorate and Colin's Review. o Editorial change t based on SDP Directorate and Colin's Review.
A.2. draft-ietf-xrblock-rtcp-xr-discard-10 B.3. draft-ietf-xrblock-rtcp-xr-discard-10
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o Editorial change to get in line with recently discussed drafts. o Editorial change to get in line with recently discussed drafts.
o Remove DT=3 based on the discussion to summary statistics draft. o Remove DT=3 based on the discussion to summary statistics draft.
A.3. draft-ietf-xrblock-rtcp-xr-discard-09 B.4. draft-ietf-xrblock-rtcp-xr-discard-09
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
o SDP Duplicated Parameter Deleting. o SDP Duplicated Parameter Deleting.
A.4. draft-ietf-xrblock-rtcp-xr-discard-08 B.5. draft-ietf-xrblock-rtcp-xr-discard-08
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. 21 change blocks. 
32 lines changed or deleted 74 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/