draft-ietf-xrblock-rtcp-xr-discard-15.txt   rfc7002.txt 
Audio/Video Transport Working Group A. Clark Internet Engineering Task Force (IETF) A. Clark
Internet-Draft Telchemy Request for Comments: 7002 Telchemy
Intended status: Standards Track G. Zorn Category: Standards Track G. Zorn
Expires: December 30, 2013 Network Zen ISSN: 2070-1721 Network Zen
Q. Wu Q. Wu
Huawei Huawei
June 28, 2013 September 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Discard Count RTP Control Protocol (RTCP) Extended Report (XR) Block
metric Reporting for Discard Count Metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-15.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
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on December 30, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7002.
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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Discard Count Report Block . . . . . . . . . . . . . . . . 3 1.1. Discard Count Report Block . . . . . . . . . . . . . . . 2
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP Extended Reports . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 3. Discard Count Metrics Block . . . . . . . . . . . . . . . . . 4
3. Discard Count Metric Report Block . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.2. Definition of Fields in the Discard Count Metrics Block . 5
3.2. Definition of Fields in Discard Count Metric Report 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
Block . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . 7
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 7
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9 5.1. New RTCP XR Block Type Value . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10 5.3. Contact Information for Registrations . . . . . . . . . . 8
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5.3. Contact information for registrations . . . . . . . . . . 10 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 Appendix A. Metrics Represented Using the Template from RFC 6390 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Metrics represented using RFC6390 Template . . . . . 15
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 16
B.1. draft-ietf-xrblock-rtcp-xr-discard-14 . . . . . . . . . . 16
B.2. draft-ietf-xrblock-rtcp-xr-discard-13 . . . . . . . . . . 16
B.3. draft-ietf-xrblock-rtcp-xr-discard-12 . . . . . . . . . . 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 that 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 (buffer underflow) or too early (buffer overflow) to be played
overflow). The metric is applicable both to systems which use packet out. The metric is applicable both to systems that use packet loss
loss repair techniques (such as forward error correction [RFC5109] or repair techniques (such as forward error correction [RFC5109] or
retransmission [RFC4588]) and to those which do not. retransmission [RFC4588]) and to those that do not.
This metric is useful for identifying the existence, and This metric is useful for identifying the existence, and
characterizing the severity, of a packet transport problem which may characterizing the severity, of packet transport problems that may
affect users' perception of a service delivered over RTP. affect users' perceptions 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 [RFC7003], 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 [RFC7003] may be used independently of the metrics in
this block. this block.
When a Discard Count Metrics Block is sent together with a Burst Gap When a Discard Count Metrics Block is sent together with a Burst/Gap
Discard Metrics Block (defined in [BGDISCARD] ) to the media sender Discard Metrics Block (defined in [RFC7003]) to the media sender or
or RTP based network management system, the information carried in RTP-based network management system, the information carried in the
the Discard Count Metrics Block and the Burst Gap Discard Metrics Discard Count Metrics Block and the Burst/Gap Discard Metrics Block
Block allows systems receiving the blocks to calculate burst gap allows systems receiving the blocks to calculate burst/gap summary
summary statistics (e.g., the gap discard rate). statistics (e.g., the gap discard rate).
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].
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP Extended 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
The Performance Metrics Framework [RFC6390] provides guidance on the "Guidelines for Considering New Performance Metric Development"
definition and specification of performance metrics. The RTP [RFC6390] provides guidance on the definition and specification of
Monitoring Architectures [RFC6792] provides guideline for reporting performance metrics. "Guidelines for Use of the RTP Monitoring
block format using RTCP XR. The metrics block described in this Framework" [RFC6792] provides guidance for reporting block format
document are in accordance with the guidelines in [RFC6390] and using RTCP XR. The metrics block described in this document is in
[RFC6792]. accordance with the guidelines in [RFC6390] and [RFC6792].
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 de-jitter buffer [RFC5481]. applications that use a de-jitter buffer [RFC5481].
Discards due to late or early arriving packets affects user Discards due to late or early arriving packets affect user
experience. The reporting of discards alerts senders and other experience. The reporting of discards alerts senders and other
receivers to the need to adjust their transmission or reception receivers to the need to adjust their transmission or reception
strategies. The reports allow network managers to diagnose these strategies. The reports allow network managers to diagnose these
user experience problems. user experience problems.
The ability to detect duplicate packets can be used by managers to The ability to detect duplicate packets can be used by managers to
detect network layer or sender behavior which may indicate network or detect network layer or sender behavior, which may indicate network
device issues. Based on the reports, these issues may be addressed or device issues. Based on the reports, these issues may be
prior to any impact on user experience. addressed prior to any impact on user experience.
2. Terminology 2. Terminology
2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
In addition, the following terms are defined: In addition, the following terms are defined:
Received, Lost and Discarded Received, Lost, and Discarded
A packet shall be regarded as lost if it fails to arrive within an A packet shall be regarded as lost if it fails to arrive within an
implementation-specific time window. A packet that arrives within implementation-specific time window. A packet that arrives within
this time window but is either too early to be played out or too this time window but is either too early or too late to be played
late to be played out or thrown away before playout due to packet out or is thrown away before playout due to packet duplication or
duplication or redundancy shall be regarded as discarded. A redundancy shall be regarded as discarded. A packet shall not be
packet shall not be regarded as discarded if it arrives within regarded as discarded if it arrives within this time window but is
this time window but is dropped during decoding by some higher dropped during decoding by some higher layer decoder, e.g., due to
layer decoder, e.g., due to a decoding error. A packet shall be a decoding error. A packet shall be classified as one of the
classified as one of received (or OK), discarded or lost. The following: received (or OK), discarded, or lost. The discard
Discard Count Metric counts only discarded packets. The metric count metric counts only discarded packets. The metric
"cumulative number of packets lost" defined in [RFC3550] reports a "cumulative number of packets lost" defined in [RFC3550] reports a
count of packets lost from the media stream (single count of packets lost from the media stream (single
Synchronization source (SSRC) within single RTP session). synchronization source (SSRC) within a single RTP session).
Similarly the metric "number of packets discarded" reports a count Similarly, the metric "number of packets discarded" reports a
of packets discarded from the media stream (single SSRC within count of packets discarded from the media stream (single SSRC
single RTP session) arriving at the receiver. Another metric within a single RTP session) arriving at the receiver. Another
defined in [RFC5725] is available to report on packets which are metric defined in [RFC5725] is available to report on packets that
not recovered by any repair techniques which may be in use. are not recovered by any repair techniques that may be in use.
3. Discard Count Metric Report Block 3. Discard Count Metrics 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 use the SSRC to refer 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 periods in use (see [RFC6776], Section 4.2). This metrics block
interval in the Measurement Information Block indicating the span of relies on the measurement interval in the Measurement Information
the report and MUST be sent in the same compound RTCP packet as the Block indicating the span of the report and MUST be sent in the same
measurement information block. If the measurement interval is not compound RTCP packet as the Measurement Information Block. If the
received in the same compound RTCP packet as this metrics block, this measurement interval is not received in the same compound RTCP packet
metrics block MUST be discarded. as this metrics block, this metrics block MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
0 1 2 3 The structure of the Discard Count Metrics Block is as follows.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| discard count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=24 | I |DT | resv | Block Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2. Definition of Fields in Discard Count Metric Report Block Figure 1: Report Block Structure
Block type (BT): 8 bits 3.2. Definition of Fields in the Discard Count Metrics Block
A Discard Count Metric Report Block is identified by the constant Block Type (BT): 8 bits
PDC.
[Note to RFC Editor: please replace PDC with the IANA provided A Discard Count Metrics Block is identified by the constant 24.
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]: Cumulative, or Sampled metric [RFC6792]:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value.
In this document, the Discard Count Metric can only be measured In this document, the discard count metric can only be measured
over definite intervals, and cannot be sampled. Accordingly, the over definite intervals and cannot be sampled. Accordingly, the
value I=01, indicating a sampled value, MUST NOT be sent, and MUST value I=01, indicating a sampled value, MUST NOT be sent, and MUST
be discarded when received. In addition, the value I=00 is be discarded when received. In addition, the value I=00 is
reserved and also MUST NOT be sent, and MUST be discarded when reserved and also MUST NOT be sent, and MUST be discarded when
received. received.
Discard Type (DT): 2bits Discard Type (DT): 2 bits
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 packet 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
Sent,and MUST be discarded when received. 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 Metrics
Report Blocks in a single RTCP XR packet. 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.
Reserved (resv): 4 bits Reserved (resv): 4 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).
block length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words, minus one, in The length of this report block in 32-bit words, minus one, in
accordance with the definition in [RFC3611]. This field MUST be accordance with the definition in [RFC3611]. This field MUST be
set to 2 to match the fixed length of the report block. The block set to 2 to match the fixed length of the report block. The block
MUST be discarded if the block length is set to a different value. MUST be discarded if the block length is set to a different 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].
discard count Discard Count
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.
The measured value is unsigned value. If the measured value The measured value is an unsigned value. If the measured value
exceeds 0xFFFFFFFD, the value 0xFFFFFFFE MUST be reported to exceeds 0xFFFFFFFD, the value 0xFFFFFFFE MUST be reported to
indicate an over-range measurement. If the measurement is indicate an over-range measurement. If the measurement is
unavailable, the value 0xFFFFFFFF MUST be reported. 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 it 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 the Session Description Protocol (SDP)
[RFC4566] for signaling the use of XR blocks. However XR blocks MAY [RFC4566] for signaling the use of XR blocks. However, XR blocks MAY
be used without prior signaling (see section 5 of RFC3611). be used without prior signaling (see Section 5 of RFC 3611).
4.1. SDP rtcp-xr-attrib Attribute Extension 4.1. SDP rtcp-xr 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. The
ABNF [RFC5234] syntax is as follows.
xr-format =/ xr-pdc-block xr-format =/ xr-pdc-block
xr-pdc-block = "pkt-discard-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]. parameters, refer to Section 5.2 of [RFC3611].
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 " RTP This document assigns the block type value 24 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
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-discard-count" in This document also registers a new parameter "pkt-discard-count" in
the " RTP Control Protocol Extended Reports (RTCP XR) Session the "RTP Control Protocol Extended Reports (RTCP XR) Session
Description 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 registrations The following contact information is provided for all registrations
in this document: 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
China China
6. Security Considerations 6. Security Considerations
In some situations, returning very detailed error information In some situations, returning very detailed error information (e.g.,
(e.g.,over-range measurement or measurement unavailable) using this over-range measurement or measurement unavailable) using this report
report block can provide an attacker with insight into the security block can provide an attacker with insight into the security
processing. Where this is a concern, the implementation should apply processing. Where this is a concern, the implementation should apply
authentication to this report block. This can be achieved by using encryption and authentication to this report block. For example,
the AVPF profile together with the Secure RTP profile as defined in this can be achieved by using the Audio-Visual Profile with Feedback
[RFC3711]; as a prerequisite, an appropriate combination of those two (AVPF) profile together with the Secure RTP profile, as defined in
profiles (an "SAVPF") is being specified [RFC5124]. [RFC3711]; an appropriate combination of those two profiles ("SAVPF")
is specified in [RFC5124].
Besides this, it is believed that this proposed RTCP XR report block Besides this, it is believed that this RTCP XR block introduces no
introduces no new security considerations beyond those described in new security considerations beyond those described in [RFC3611].
[RFC3611]. This block does not provide per-packet statistics so the This block does not provide per-packet statistics, so the risk to
risk to confidentiality documented in Section 7, paragraph 3 of confidentiality documented in Section 7, paragraph 3 of [RFC3611]
[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 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, Claire Bi, Bob Biskner,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, Gonzalo Camarillo, Benoit Claise, Kevin Connor, Claus Dahm, Spencer
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, Dawkins, Randy Ethier, Roni Even, Stephen Farrel, Jim Frauenthal,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Kevin Gross, Albert Higashi, Tom Hock, Shane Holthaus, Paul Jones,
Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada, Kevin Rajesh Kumar, Keith Lantz, Jonathan Lennox, Mohamed Mostafa, Amy
Gross, Varun Singh, Claire Bi, Roni Even, Dan Romascanu and Jonathan Pendleton, Colin Perkins, Mike Ramalho, Ravi Raviraj, Dan Romascanu,
Lennox. Albrecht Schwarz, Varun Singh, Tom Taylor, Dan Wing, and Hideaki
Yamada.
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", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Applications", RFC 3550, July 2003. Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, 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)", RFC 3611, November
2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004.
[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", RFC 4566, July 2006.
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012.
[RFC6776] Hunt, G., "Measurement Identity and information Reporting [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
using SDES item and XR Block", RFC 6776, October 2012. Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 2012.
9.2. Informative References 9.2. Informative References
[BGDISCARD] [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hunt, G., "RTCP XR Report Block for Burst Gap Discard Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-14,
April 2013.
[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, December 2007.
[RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
metric Reporting", RFC 5725, February 2010. Applicability Statement", RFC 5481, March 2009.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE
Development", RFC 6390, October 2011. Report Block Type for RTP Control Protocol (RTCP) Extended
Reports (XRs)", RFC 5725, February 2010.
[RFC6792] Wu, Q., "Monitoring Architectures for RTP", RFC 6792, [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
November 2012. Performance Metric Development", BCP 170, RFC 6390,
October 2011.
[RTPDUP] Begen, A. and C. Perkins, "Duplicating RTP Streams", [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
ID draft-ietf-avtext-rtp-duplication-02, March 2013. RTP Monitoring Framework", RFC 6792, November 2012.
Appendix A. Metrics represented using RFC6390 Template [RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
Discard Metric Reporting", RFC 7003, September 2013.
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC [RTPDUP] Begen, A. and C. Perkins, "Duplicating RTP Streams", Work
number, when assigned. in Progress, March 2013.
a. Number of packets discarded Metric Appendix A. Metrics Represented Using the Template from RFC 6390
* Metric Name: Number of RTP packets discarded Metric a. Number of Packets Discarded Metric
* Metric Name: Number of RTP packets discarded.
* Metric Description: Number of RTP packets discarded over the * Metric Description: Number of RTP packets discarded over the
period covered by this report. period covered by this report.
* Method of Measurement or Calculation: See section 3.2, number * Method of Measurement or Calculation: See Section 3.2, Discard
of packets discarded definition [RFCXXXX]. Count definition.
* Units of Measurement: See section 3.2, number of packets * Units of Measurement: See Section 3.2, Discard Count
discarded definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. Section 3, 1st paragraph.
* 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
publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-discard-14
The following are the major changes compared to previous version:
o Editorial changes to paragraph 4 of section 1.1.
B.2. draft-ietf-xrblock-rtcp-xr-discard-13
The following are the major changes compared to previous version:
o Some editorial changes to get in line with burst gap drafts.
B.3. draft-ietf-xrblock-rtcp-xr-discard-12
The following are the major changes compared to previous version: * Measurement Timing: See Section 3, 1st paragraph for
measurement timing and Section 3.2 for Interval Metric flag.
o Incorporate some changes to burst gap draft that applies to this * Use and Applications: See Section 1.4.
document.
o Use RFC6390 template to the metrics in the appendix. * Reporting Model: See RFC 3611.
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
Glen Zorn Glen Zorn
Network Zen Network Zen
77/440 Soi Phoomjit, Rama IV Road 227/358 Thanon Sanphawut
Phra Khanong, Khlong Toie Bang Na, Bangkok 10260
Bangkok 10110
Thailand Thailand
Phone: +66 (0) 87 502 4274 Phone: +66 (0) 8-1000-4155
Email: gwz@net-zen.net EMail: glenzorn@gmail.com
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com EMail: sunseawq@huawei.com
 End of changes. 86 change blocks. 
247 lines changed or deleted 218 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/