draft-ietf-xrblock-rtcp-xr-discard-07.txt   draft-ietf-xrblock-rtcp-xr-discard-08.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: March 15, 2013 Network Zen Expires: April 14, 2013 Network Zen
Q. Wu Q. Wu
Huawei Huawei
September 11, 2012 October 11, 2012
RTCP XR Report Block for Discard Count metric Reporting RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count
draft-ietf-xrblock-rtcp-xr-discard-07.txt metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-08.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTP Control Protocol(RTCP) Extended Report
reporting of a simple discard count metric for use in a range of RTP (XR) Block that allows the reporting of a simple discard count metric
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 March 15, 2013. This Internet-Draft will expire on April 14, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 20 skipping to change at page 2, line 21
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
3. Discard Count Metric Report Block . . . . . . . . . . . . . . 6 3. Discard Count Metric Report Block . . . . . . . . . . . . . . 6
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6
3.2. Definition of Fields in Discard Count Metric Report 3.2. Definition of Fields in Discard Count Metric Report
Block . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Block . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9
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
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-discard-08 . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
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
overflow). The metric is applicable both to systems which use packet overflow). The metric is applicable both to systems which use packet
loss repair techniques (such as forward error correction [RFC5109] or loss repair techniques (such as forward error correction [RFC5109] or
retransmission [RFC4588]) and to those which do not. retransmission [RFC4588]) and to those which do not.
This metric is useful for identifying the existence, and This metric is useful for identifying the existence, and
characterising the severity, of a packet transport problem which may characterizing the severity, of a packet transport problem which may
affect users' perception of a service delivered over RTP. affect users' perception of a service delivered over RTP.
This block may be used in conjunction with [BGDISCARD] which provides This block may be used in conjunction with [BGDISCARD] which provides
additional information on the pattern of discarded packets. However additional information on the pattern of discarded packets. However
the metric in [BGDISCARD] may be used independently of the metrics in the metric in [BGDISCARD] may be used independently of the metrics in
this block. this block.
In case of Discard count metric block sent together with Burst gap In case of Discard count metric block sent together with Burst gap
discard metric block defined in [BGDISCARD] to the media sender or discard metric block defined in [BGDISCARD] to the media sender or
RTP based network management system, information carried in the RTP based network management system, information carried in the
discard count metric block and Burst gap discard metric block allows discard count metric block and Burst gap discard metric block allows
them calculate the some bust gap summary statistics, e.g., gap them calculate the some bust gap summary statistics, e.g., gap
discard rate. discard rate.
The metric belongs to the class of transport-related terminal metrics The metric belongs to the class of transport-related end system
defined in [MONARCH]. metrics defined in [MONARCH].
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. The Report (XR). This document defines a new Extended Report block for
use of Extended Report blocks is defined by [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 Architectures [MONARCH] provides guideline for reporting Monitoring Architectures [MONARCH] 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
[MONARCH]. [MONARCH].
skipping to change at page 6, line 9 skipping to change at page 6, line 9
reports a count of packets discarded from the media stream (single reports a count of packets discarded from the media stream (single
SSRC within single RTP session) arriving at the receiver. Another SSRC within single RTP session) arriving at the receiver. Another
metric defined in [RFC5725] is available to report on packets metric defined in [RFC5725] is available to report on packets
which are not recovered by any repair techniques which may be in which are not recovered by any repair techniques which may be in
use. use.
3. Discard Count Metric Report Block 3. Discard Count Metric Report Block
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 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| number of packets discarded | | number of packets discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
skipping to change at page 9, line 11 skipping to change at page 9, line 11
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 [MEASI], so need not be repeated the Measurement Information block [MEASI], so need not be repeated
in this block. 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)
[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.
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.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611]) (defined in [RFC3611])
xr-format =/ xr-pdc-block xr-format =/ xr-pdc-block
xr-pdc-block = "pkt-dscrd-count" xr-pdc-block = "pkt-dscrd-count"
4.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] applies.
5. IANA Considerations 5. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611]. [RFC3611].
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type value
This document assigns the block type value PDC in the IANA "RTCP XR This document assigns the block type value PDC in the IANA "RTCP XR
Block Type Registry" to the "Discard Count Metrics Block". Block Type Registry" to 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" in the "RTCP This document also registers a new parameter "pkt-dscrd-count" in the
XR SDP Parameters Registry". "RTCP XR 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 7 skipping to change at page 13, line 7
This block does not provide per-packet statistics so the risk to 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.
7. Contributors 7. Contributors
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 the comments and contributions The authors gratefully acknowledge reviews and feedback provided by
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
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. Gross, Varun Singh, Claire Bi, Roni Even, Dan Romascanu.
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.
[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 14, line 26 skipping to change at page 14, line 26
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
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-05, ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06,
July 2012. October 2012.
[MEASI] Hunt, G., "Measurement Identity and information Reporting [MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block", using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-06, ID draft-ietf-xrblock-rtcp-xr-meas-identity-10,
April 2012. August 2012.
[MONARCH] Wu, Q., "Monitoring Architectures for RTP", [MONARCH] Wu, Q., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-12, April 2012. ID draft-ietf-avtcore-monarch-22, September 2012.
[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.
[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-00, July 2012.
Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-discard-08
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. 19 change blocks. 
30 lines changed or deleted 56 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/