draft-ietf-xrblock-rtcp-xr-discard-02.txt   draft-ietf-xrblock-rtcp-xr-discard-03.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: October 20, 2012 Telchemy Expires: December 2, 2012 Telchemy
G. Zorn G. Zorn
Network Zen Network Zen
Q. Wu Q. Wu
Huawei Huawei
April 18, 2012 May 31, 2012
RTCP XR Report Block for Discard metric Reporting RTCP XR Report Block for Discard metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-02.txt draft-ietf-xrblock-rtcp-xr-discard-03.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of a simple discard count metric for use in a range of RTP reporting of a simple discard count metric for use in a range of RTP
applications. 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 October 20, 2012. This Internet-Draft will expire on December 2, 2012.
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 26 skipping to change at page 2, line 26
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Discard Metric Report Block . . . . . . . . . . . . . . . . . 5 3. Discard Metric Report Block . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Discard Metric Report Block . . . 5 3.2. Definition of Fields in Discard Metric Report Block . . . 5
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8
5.3. Contact information for registrations . . . . . . . . . . 8 5.3. Contact information for registrations . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
8. Changes from previous version . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
1.1. Discard Report Block 1.1. Discard 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 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 3, line 35 skipping to change at page 3, line 35
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 draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611]. MUST be used as defined in [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. Metrics definition and specification of performance metrics. The RTP
described in this draft either reference external definitions or Monitoring Architectures [MONARCH] provides guideline for reporting
define metrics generally in accordance with the guidelines in block format using RTCP XR. The Metrics Block described in this
[RFC6390]. document are in accordance with the guidelines in [RFC6390] and
[MONARCH].
1.4. Applicability 1.4. Applicability
This metric is believed to be applicable to a large class of RTP This metric is believed to be applicable to a large class of RTP
applications which use a jitter buffer. applications which use a jitter buffer.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
skipping to change at page 5, line 33 skipping to change at page 5, line 33
Block type (BT): 8 bits Block type (BT): 8 bits
A Discard Metric Report Block is identified by the constant ND. A Discard Metric Report Block is identified by the constant ND.
[Note to RFC Editor: please replace ND with the IANA provided RTCP [Note to RFC Editor: please replace ND with the IANA provided RTCP
XR block type for this block.] 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 Discard metric is an This field is used to indicate whether the Discard metric is an
sampled,Interval or Cumulative metric, that is, whether the Interval or Cumulative metric, that is, whether the reported
reported values applies to the most recent measurement interval values applies to the most recent measurement interval duration
duration between successive metrics reports (I=10) (the Interval between successive metrics reports (I=10) (the Interval Duration)
Duration) or to the accumulation period characteristic of or to the accumulation period characteristic of cumulative
cumulative measurements (I=11) (the Cumulative Duration) or to the measurements (I=11) (the Cumulative Duration).
value of a continuously measured or calculated that has been
sampled at end of the interval (I=01) (Sampled Value).
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: packets are discarded due to other reasons than late
arrival, early arrival, or both (e.g., duplicate, redundant
packets).
01: packets are discarded due to too early arrival. 01: packets are discarded due to too early arrival.
10: packets are discarded due to too late arrival. 10: packets are discarded due to too late arrival.
11: packets are discarded due to both early arrival and late 11: packets are discarded due to both early arrival and late
arrival. arrival.
Reserved (resv): 5 bits Reserved (resv): 5 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
skipping to change at page 6, line 31 skipping to change at page 6, line 33
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 If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the SHOULD be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
reported.
Note that the number of packets expected in the period covered by Note that the number of packets expected in the period covered by
the metric (whether interval or cumulative) is available from the the metric (whether interval or cumulative) is available from the
difference between a pair of extended sequence numbers in the difference between a pair of extended sequence numbers in the
Measurement Identity block, so need not be repeated in this block. Measurement Identity block, so need not be 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)
[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 10, line 5 skipping to change at page 10, line 5
Kingdom Kingdom
6. Security Considerations 6. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
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. Acknowledgments
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Kevin
Gross, Varun Singh.
8. Changes from previous version
Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009), now aligned with RFC 5234 section
3.3 "Incremental Alternatives".
Updated references.
Allocate 1 bit to distinguish early discard from later discard.
Expand Interval Metric flag to 2 bit to allow using sampled metric.
9. References 8. References
9.1. Normative References 8.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.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
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 8.2. Informative References
[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-12, April 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.
 End of changes. 14 change blocks. 
40 lines changed or deleted 30 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/