Internet Engineering Task Force (IETF) A. Clark
Request for Comments: 7003 Telchemy
Category: Standards Track R. Huang
ISSN: 2070-1721 Q. Wu, Ed.
Huawei
September 2013
Internet Engineering Task Force (IETF) A. Clark
Request for Comments: 7003 Telchemy
Category: Standards Track R. Huang
ISSN: 2070-1721 Q. Wu, Ed.
Huawei
September 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Discard Metric Reporting
用于突发/间隙丢弃度量报告的RTP控制协议（RTCP）扩展报告（XR）块
Abstract
摘要
This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows the reporting of burst and gap discard metrics for use in a range of RTP applications.
本文档定义了一个RTP控制协议（RTCP）扩展报告（XR）块，该块允许报告在一系列RTP应用程序中使用的突发和间隙丢弃度量。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
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/rfc7003.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7003.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
1. Introduction ....................................................2
1.1. Burst/Gap Discard Metrics Block ............................2
1.2. RTCP and RTCP Extended Reports .............................3
1.3. Performance Metrics Framework ..............................3
1.4. Applicability ..............................................3
2. Terminology .....................................................3
3. Burst/Gap Discard Metrics Block .................................4
3.1. Report Block Structure .....................................5
3.2. Definition of Fields in Burst/Gap Discard Metrics Block ....5
3.3. Derived Metrics Based on Reported Metrics ..................7
4. Considerations for Voice-over-IP Applications ...................7
5. SDP Signaling ...................................................8
5.1. SDP rtcp-xr Attribute Extension ............................8
5.2. Offer/Answer Usage .........................................8
6. IANA Considerations .............................................8
6.1. New RTCP XR Block Type Value ...............................8
6.2. New RTCP XR SDP Parameter ..................................9
6.3. Contact Information for Registrations ......................9
7. Security Considerations .........................................9
8. Contributors ....................................................9
9. Acknowledgments .................................................9
10. References ....................................................10
10.1. Normative References .....................................10
10.2. Informative References ...................................10
Appendix A. Metrics Represented Using the Template from RFC 6390..12
Table of Contents
1. Introduction ....................................................2
1.1. Burst/Gap Discard Metrics Block ............................2
1.2. RTCP and RTCP Extended Reports .............................3
1.3. Performance Metrics Framework ..............................3
1.4. Applicability ..............................................3
2. Terminology .....................................................3
3. Burst/Gap Discard Metrics Block .................................4
3.1. Report Block Structure .....................................5
3.2. Definition of Fields in Burst/Gap Discard Metrics Block ....5
3.3. Derived Metrics Based on Reported Metrics ..................7
4. Considerations for Voice-over-IP Applications ...................7
5. SDP Signaling ...................................................8
5.1. SDP rtcp-xr Attribute Extension ............................8
5.2. Offer/Answer Usage .........................................8
6. IANA Considerations .............................................8
6.1. New RTCP XR Block Type Value ...............................8
6.2. New RTCP XR SDP Parameter ..................................9
6.3. Contact Information for Registrations ......................9
7. Security Considerations .........................................9
8. Contributors ....................................................9
9. Acknowledgments .................................................9
10. References ....................................................10
10.1. Normative References .....................................10
10.2. Informative References ...................................10
Appendix A. Metrics Represented Using the Template from RFC 6390..12
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 supports the reporting of the proportion of packets discarded by the jitter buffer at the receiver, using packet discard logic according to the jitter buffer algorithms. The discards during discard bursts are reported, together with the number of bursts. This block is intended to be used in conjunction with [RFC7002], which provides the total packets discarded and on which this block therefore depends. However, the metric in [RFC7002] may be used independently of the metrics in this block.
本文件定义了一种新的块类型，以扩充[RFC3611]中定义的块类型，以便在一系列RTP应用中使用。新的块类型支持使用根据抖动缓冲算法的分组丢弃逻辑，报告接收机处抖动缓冲丢弃的分组比例。报告丢弃突发期间的丢弃以及突发数。此块拟与[RFC7002]结合使用，后者提供丢弃的总数据包，因此此块依赖于此数据包。然而，[RFC7002]中的度量可以独立于该块中的度量使用。
This block provides information on transient IP problems. Burst/gap metrics are typically used in cumulative reports; however, they also may be used in interval reports (see the Interval Metric flag in Section 3.2). The burstiness of packet discard affects user experience, may influence any sender strategies to mitigate the problem, and may also have diagnostic value.
此块提供有关瞬时IP问题的信息。突发/间隙指标通常用于累积报告中；但是，它们也可用于间隔报告（见第3.2节中的间隔度量标志）。数据包丢弃的突发性会影响用户体验，可能会影响任何发送方缓解问题的策略，还可能具有诊断价值。
The metric belongs to the class of transport-related end-system metrics defined in [RFC6792].
该指标属于[RFC6792]中定义的与传输相关的终端系统指标类别。
The definitions of "burst", "gap", "loss", and "discard" are consistent with the definitions in [RFC3611]. To accommodate the range of jitter buffer algorithms and packet discard logic that may be used by implementors, the method used to distinguish between bursts and gaps shall use an equivalent method to that defined in Section 4.7.2 of [RFC3611]. Note that reporting the specific jitter buffer algorithms and/or packet discard logic is out of the scope of this document.
“突发”、“间隙”、“丢失”和“丢弃”的定义与[RFC3611]中的定义一致。为了适应实施者可能使用的抖动缓冲算法和数据包丢弃逻辑的范围，用于区分突发和间隙的方法应使用[RFC3611]第4.7.2节中定义的等效方法。请注意，报告特定的抖动缓冲算法和/或数据包丢弃逻辑超出了本文档的范围。
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] defined an extensible structure for reporting using an RTCP Extended Report (XR). This document defines a new Extended Report block for use with [RFC3550] and [RFC3611].
[RFC3550]中定义了使用RTCP进行报告。[RFC3611]定义了使用RTCP扩展报告（XR）进行报告的可扩展结构。本文档定义了一个新的扩展报告块，用于[RFC3550]和[RFC3611]。
The Performance Metrics Framework [RFC6390] provides guidance on the definition and specification of performance metrics. The RTP Monitoring Framework [RFC6792] provides guidelines for reporting block format using RTCP XR. The metrics block described in this document is in accordance with the guidelines in [RFC6390] and [RFC6792].
性能指标框架[RFC6390]提供了有关性能指标定义和规范的指导。RTP监控框架[RFC6792]提供了使用RTCP XR报告块格式的指南。本文件中描述的度量块符合[RFC6390]和[RFC6792]中的指南。
These metrics are applicable to a range of RTP applications that contain de-jitter buffers [RFC5481] at the receiving end to smooth variation in packet-arrival time and don't use stream repair means, e.g., Forward Error Correction (FEC) [RFC5109] and/or retransmission [RFC4588].
这些指标适用于在接收端包含去抖动缓冲器[RFC5481]的一系列RTP应用，以平滑数据包到达时间的变化，并且不使用流修复手段，例如前向纠错（FEC）[RFC5109]和/或重传[RFC4588]。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
In addition, the following terms are defined:
此外，定义了以下术语：
Received, Lost, and Discarded
接收、丢失和丢弃
A packet shall be regarded as "lost" if it fails to arrive within an implementation-specific time window. A packet that arrives within this time window but is too early to be played out, too late to be played out, or thrown away before playout due to packet duplication or redundancy shall be regarded as discarded. A packet shall not be regarded as discarded if it arrives within this time window but is dropped during decoding by some higher-layer decoder, e.g., due to a decoding error. A packet shall be classified as one of received (or OK), discarded, or lost. The metric "cumulative number of packets lost" defined in [RFC3550] reports a count of packets lost from the media stream (single synchronization source (SSRC) within a single RTP session). Similarly, the metric "number of packets discarded" defined in [RFC7002] reports a count of packets discarded from the media stream (single SSRC within a single RTP session) arriving at the receiver. Another metric, defined in [RFC5725], is available to report on packets that are not recovered by any repair techniques that may be in use. Note that the term "discard" defined here builds on the "discard" definition in [RFC3611] but extends the concept to take into account packet duplication and reports different types of discard counts [RFC7002].
如果数据包未能在特定于实现的时间窗口内到达，则该数据包应视为“丢失”。在该时间窗口内到达但由于数据包重复或冗余而过早播放、太晚播放或在播放前丢弃的数据包应视为丢弃。如果数据包在此时间窗口内到达，但在某个更高层解码器解码期间（例如，由于解码错误）被丢弃，则该数据包不应被视为丢弃。数据包应分类为接收（或正常）、丢弃或丢失。[RFC3550]中定义的度量“累计丢失的数据包数”报告从媒体流（单个RTP会话中的单个同步源（SSRC））丢失的数据包计数。类似地，[RFC7002]中定义的度量“丢弃的包数”报告从到达接收器的媒体流（单个RTP会话中的单个SSRC）丢弃的包的计数。[RFC5725]中定义的另一个指标可用于报告可能使用的任何修复技术都无法恢复的数据包。注意，此处定义的术语“丢弃”基于[RFC3611]中的“丢弃”定义，但扩展了该概念，以考虑数据包重复并报告不同类型的丢弃计数[RFC7002]。
Bursts and Gaps
爆发和缺口
The terms "burst" and "gap" are used in a manner consistent with that of RTCP XR [RFC3611]. RTCP XR views an RTP stream as being divided into bursts, which are periods during which the discard rate is high enough to cause noticeable quality degradation (generally over 5 percent discard rate), and gaps, which are periods during which discarded packets are infrequent and hence quality is generally acceptable.
术语“突发”和“间隙”的使用方式与RTCP XR[RFC3611]一致。RTCP XR将RTP流视为被划分为突发，突发是丢弃率高到足以导致明显质量下降（通常超过5%丢弃率）的时段，间隙是丢弃的数据包不频繁的时段，因此质量通常是可接受的。
Metrics in this block report on burst/gap discard in the stream arriving at the RTP system. Measurements of these metrics are made at the receiving end of the RTP stream. Instances of this metrics block use the synchronization source (SSRC) to refer to the separate auxiliary Measurement Information Block [RFC6776], which describes measurement periods in use (see [RFC6776], Section 4.2).
此块中的度量报告到达RTP系统的流中的突发/间隙丢弃。在RTP流的接收端对这些度量进行测量。此度量块的实例使用同步源（SSRC）引用单独的辅助度量信息块[RFC6776]，该信息块描述了使用中的度量周期（请参见[RFC6776]，第4.2节）。
This metrics block relies on the measurement period in the Measurement Information Block indicating the span of the report. Senders MUST send this block in the same compound RTCP packet as the
此度量块依赖于度量信息块中指示报告范围的度量周期。发送方必须将此块以与发送方相同的复合RTCP数据包的形式发送
Measurement Information Block. Receivers MUST verify that the measurement period is received in the same compound RTCP packet as this metrics block. If not, this metrics block MUST be discarded.
测量信息块。接收器必须验证测量周期是否在与此度量块相同的复合RTCP数据包中接收。如果不是，则必须放弃此度量块。
The structure of the Burst/Gap Discard Metrics Block is as follows.
突发/间隙丢弃度量块的结构如下所示。
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=20 | I | resv | Block Length = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Packets Discarded in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Total Packets Expected in Bursts | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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=20 | I | resv | Block Length = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Packets Discarded in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Total Packets Expected in Bursts | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure
图1：报告块结构
Block Type (BT): 8 bits
块类型（BT）：8位
A Burst/Gap Discard Metrics Block is identified by the constant 20.
突发/间隙丢弃度量块由常数20标识。
Interval Metric flag (I): 2 bits
间隔度量标志（I）：2位
This field is used to indicate whether the burst/gap discard metrics are Sampled, Interval, or Cumulative metrics [RFC6792]:
此字段用于指示突发/间隔丢弃度量是采样、间隔还是累积度量[RFC6792]：
I=10: Interval Duration - the reported value applies to the most recent measurement interval duration between successive metrics reports.
I=10：间隔持续时间-报告值适用于连续度量报告之间的最新度量间隔持续时间。
I=11: Cumulative Duration - the reported value applies to the accumulation period characteristic of cumulative measurements.
I=11：累积持续时间-报告值适用于累积测量的累积周期特征。
I=01: Sampled Value - the reported value is a sampled instantaneous value.
I=01：采样值-报告值为采样瞬时值。
In this document, burst/gap discard metrics can only be measured over definite intervals and cannot be sampled. Also, the value I=00 is reserved for future use. Senders MUST NOT use the values I=00 or I=01. If a block is received with I=00 or I=01, the receiver MUST discard the block.
在本文档中，突发/间隙丢弃度量只能在确定的时间间隔内进行测量，不能进行采样。此外，值I=00保留供将来使用。发件人不得使用I=00或I=01的值。如果接收到I=00或I=01的块，接收器必须丢弃该块。
Reserved (resv): 6 bits
保留（resv）：6位
These bits are reserved. They MUST be set to zero by senders and ignored by receivers (see [RFC6709], Section 4.2).
这些位是保留的。发送方必须将其设置为零，接收方必须忽略（见[RFC6709]，第4.2节）。
Block Length: 16 bits
块长度：16位
The length of this report block in 32-bit words, minus one. For the Burst/Gap Discard Metrics Block, the block length is equal to 3. The block MUST be discarded if the block length is set to a different value.
此报表块的长度（32位字）减去1。对于突发/间隙丢弃度量块，块长度等于3。如果块长度设置为不同的值，则必须丢弃该块。
SSRC of Source: 32 bits
源的SSRC：32位
As defined in Section 4.1 of [RFC3611].
如[RFC3611]第4.1节所定义。
Threshold: 8 bits
阈值：8位
The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of successive packets that must not be discarded prior to and following a discard packet in order for this discarded packet to be regarded as part of a gap. Note that the Threshold is set in accordance with the Gmin calculation defined in Section 4.7.2 of [RFC3611].
阈值相当于[RFC3611]中的Gmin，即在丢弃数据包之前和之后不得丢弃的连续数据包的数量，以便将该丢弃的数据包视为间隙的一部分。注意，阈值是根据[RFC3611]第4.7.2节中定义的Gmin计算设置的。
Packets Discarded in Bursts: 24 bits
突发丢弃的数据包：24位
The total number of packets discarded during discard bursts.
丢弃突发期间丢弃的数据包总数。
The measured value is unsigned value. If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over-range measurement. If the measurement is unavailable, the value 0xFFFFFF MUST be reported.
测量值为无符号值。如果测量值超过0xFFFFFD，则必须报告值0xFFFFFE以指示超量程测量。如果测量不可用，则必须报告值0xFFFFFF。
Total Packets Expected in Bursts: 24 bits
突发中预期的数据包总数：24位
The total number of packets expected during discard bursts (that is, the sum of received packets and lost packets).
丢弃突发期间预期的数据包总数（即接收到的数据包和丢失的数据包之和）。
The measured value is unsigned value. If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE MUST be reported to indicate an over-range measurement. If the measurement is unavailable, the value 0xFFFFFF MUST be reported.
测量值为无符号值。如果测量值超过0xFFFFFD，则必须报告值0xFFFFFE以指示超量程测量。如果测量不可用，则必须报告值0xFFFFFF。
Reserved: 8 bits
保留：8位
These bits are reserved. They MUST be set to zero by senders and ignored by receivers (See [RFC6709], Section 4.2).
这些位是保留的。发送方必须将其设置为零，接收方必须忽略（见[RFC6709]，第4.2节）。
The metrics described here are intended to be used in conjunction with information from the Measurement Information Block [RFC6776] and also with the metric "number of packets discarded" provided in the RTCP XR Discard Count Metrics Block [RFC7002].
此处描述的指标旨在与测量信息块[RFC6776]中的信息以及RTCP XR丢弃计数指标块[RFC7002]中提供的指标“丢弃的数据包数”结合使用。
These metrics provide the following information relevant to statistical parameters, including:
这些指标提供了与统计参数相关的以下信息，包括：
o The fraction of packets discarded during bursts (Burst Discard Rate in [RFC7004]), which can be calculated using the metric "Packets Discarded in Bursts" and the metric "Total Packets Expected in Bursts" provided in the Burst/Gap Discard Metrics Block.
o 突发期间丢弃的数据包的分数（在[RFC7004]中为突发丢弃率），可使用突发/间隙丢弃度量块中提供的度量“突发中丢弃的数据包”和度量“突发中预期的数据包总数”进行计算。
o The fraction of packets discarded during gaps (Gap Discard Rate in [RFC7004]), which can be calculated using the metric "Packets Discarded in Bursts" and the metric "Total Packets Expected in Bursts" provided in the Burst/Gap Discard Metrics Block.
o 在间隔期间丢弃的数据包的分数（[RFC7004]中的间隔丢弃率），可使用突发/间隔丢弃度量块中提供的度量“突发中丢弃的数据包”和度量“突发中预期的数据包总数”来计算。
The details on calculation these parameters in the metrics are described in [RFC7004].
[RFC7004]中描述了度量中这些参数的计算细节。
This metrics block is applicable to a broad range of RTP applications. Where the metric is used with a Voice-over-IP (VoIP) application and the stream repair means is not available, the following considerations apply.
此度量块适用于广泛的RTP应用程序。如果该度量用于IP语音（VoIP）应用程序，且流修复手段不可用，则以下注意事项适用。
RTCP XR views a call as being divided into bursts, which are periods during which the discard rate is high enough to cause noticeable call quality degradation (generally over 5 percent discard rate) and gaps, which are periods during which discarded packets are infrequent and hence call quality is generally acceptable.
RTCP XR将呼叫视为分为突发，突发是指丢弃率高到足以导致明显呼叫质量下降（通常超过5%丢弃率）的时段和间隔，间隔是指丢弃的数据包不频繁的时段，因此呼叫质量通常是可接受的。
If voice activity detection is used, the burst and gap duration shall be determined as if silence packets had been sent, i.e., a period of silence in excess of Gmin packets will terminate a burst condition.
如果使用语音活动检测，则应确定突发和间隔持续时间，如同发送了静默数据包一样，即，超过Gmin数据包的静默时间将终止突发条件。
The recommended value for the threshold Gmin in [RFC3611] results in a burst being a period of time during which the call quality is degraded to a similar extent to a typical pulse code modulation (PCM) severely errored second.
[RFC3611]中阈值Gmin的建议值会导致突发，这是一段时间，在此期间，呼叫质量下降到与典型脉冲编码调制（PCM）严重错误秒相似的程度。
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used without prior signaling.
[RFC3611]定义了SDP（会话描述协议）[RFC4566]的使用，用于发送使用XR块的信号。XR块可以在没有事先信令的情况下使用。
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined in [RFC3611] by providing an additional value of "xr-format" to signal the use of the report block defined in this document. The ABNF [RFC5234] syntax is as follows.
本节增加了[RFC3611]中定义的SDP[RFC4566]属性“rtcp xr”，提供了“xr format”的附加值，以表示使用了本文档中定义的报告块。ABNF[RFC5234]语法如下所示。
xr-format =/ xr-bgd-block
xr format=/xr bgd块
xr-bgd-block = "burst-gap-discard"
xr-bgd-block = "burst-gap-discard"
When SDP is used in Offer/Answer context, the SDP Offer/Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters applies. For detailed usage in Offer/Answer for unilateral parameters, refer to Section 5.2 of [RFC3611].
在提供/应答上下文中使用SDP时，[RFC3611]中为单边“rtcp xr”属性参数定义的SDP提供/应答用法适用。有关单边参数在报价/应答中的详细用法，请参阅[RFC3611]第5.2节。
New block types for RTCP XR are subject to IANA registration. For general guidelines on IANA considerations for RTCP XR, refer to [RFC3611].
RTCP XR的新块类型需要IANA注册。有关RTCP XR的IANA注意事项的一般指南，请参阅[RFC3611]。
This document assigns the block type value 20 in the IANA "RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry" to the "Burst/Gap Discard Metrics Block".
本文档将IANA“RTP控制协议扩展报告（RTCP XR）块类型注册表”中的块类型值20分配给“突发/间隙丢弃度量块”。
This document also registers a new parameter "burst-gap-discard" in the "RTP Control Protocol Extended Reports (RTCP XR) Session Description Protocol (SDP) Parameters Registry".
本文档还在“RTP控制协议扩展报告（RTCP XR）会话描述协议（SDP）参数注册表”中注册新参数“突发间隔丢弃”。
The contact information for the registrations is:
注册的联系信息为：
Qin Wu (sunseawq@huawei.com) 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
秦武(sunseawq@huawei.com)中国江苏省南京市雨花区软件大道101号210012
It is believed that this RTCP XR block introduces no new security considerations beyond those described in [RFC3611]. This block does not provide per-packet statistics, so the risk to confidentiality documented in Section 7, paragraph 3 of [RFC3611] does not apply.
据信，除了[RFC3611]中所述的安全注意事项外，该RTCP XR块未引入任何新的安全注意事项。该块不提供每包统计数据，因此[RFC3611]第7节第3段中记录的保密风险不适用。
Geoff Hunt wrote the initial draft of this document.
杰夫·亨特撰写了这份文件的初稿。
The authors gratefully acknowledge reviews and feedback provided by Bruce Adams, Philip Arden, Amit Arora, Claire Bi, Bob Biskner, Benoit Claise, Kevin Connor, Claus Dahm, Randy Ethier, Roni Even, Stephen Farrell, Jim Frauenthal, Albert Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Paul Kyzivat, Keith Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Raviraj, Dan Romascanu, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
作者衷心感谢Bruce Adams、Philip Arden、Amit Arora、Claire Bi、Bob Biskner、Benoit Claise、Kevin Connor、Claus Dahm、Randy Ethier、Roni Even、Stephen Farrell、Jim Frauenthal、Albert Higashi、Tom Hock、Shane Holthaus、Paul Jones、Rajesh Kumar、Paul Kyzivat、Keith Lantz、Mohamed Mostafa、，艾米·彭德尔顿、科林·帕金斯、迈克·拉马霍、拉维·拉维拉吉、丹·罗马斯坎努、阿尔布雷希特·施瓦兹、汤姆·泰勒和山田英代克。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003.
[RFC3550]Schulzrinne，H.，Casner，S.，Frederick，R.，和V.Jacobson，“RTP：实时应用的传输协议”，STD 64，RFC 35502003年7月。
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol Extended Reports (RTCP XR)", RFC 3611, November 2003.
[RFC3611]Friedman，T.，Caceres，R.，和A.Clark，“RTP控制协议扩展报告（RTCP XR）”，RFC 36112003年11月。
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006.
[RFC4566]Handley，M.，Jacobson，V.，和C.Perkins，“SDP：会话描述协议”，RFC4566，2006年7月。
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)", RFC 5725, February 2010.
[RFC5725]Begen，A.，Hsu，D.，和M.Lague，“RTP控制协议（RTCP）扩展报告（XRs）的修复后损失RLE报告块类型”，RFC 5725，2010年2月。
[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block", RFC 6776, October 2012.
[RFC6776]Clark，A.和Q.Wu，“使用源描述（SDES）项和RTCP扩展报告（XR）块的测量标识和信息报告”，RFC 6776，2012年10月。
[RFC7002] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol (RTCP) Extended Report (XR) for Discard Count Metric Reporting", RFC 7002, September 2013.
[RFC7002]Clark，A.，Zorn，G.，和Q.Wu，“用于丢弃计数度量报告的RTP控制协议（RTCP）扩展报告（XR）”，RFC 7002，2013年9月。
[RFC7004] Zorn, G., Schott, R., Wu, Q., Ed., and R. Huang, "RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary Statistics Metrics Reporting", RFC 7004, September 2013.
[RFC7004]Zorn，G.，Schott，R.，Wu，Q.，Ed.，和R.Huang，“用于汇总统计指标报告的RTP控制协议（RTCP）扩展报告（XR）块”，RFC 70042013年9月。
[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. Hakenberg, "RTP Retransmission Payload Format", RFC 4588, July 2006.
[RFC4588]Rey，J.，Leon，D.，Miyazaki，A.，Varsa，V.，和R.Hakenberg，“RTP重传有效载荷格式”，RFC 4588，2006年7月。
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error Correction", RFC 5109, December 2007.
[RFC5109]Li，A.“通用前向纠错的RTP有效载荷格式”，RFC 5109，2007年12月。
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation Applicability Statement", RFC 5481, March 2009.
[RFC5481]Morton，A.和B.Claise，“数据包延迟变化适用性声明”，RFC 54812009年3月。
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New Performance Metric Development", BCP 170, RFC 6390, October 2011.
[RFC6390]Clark，A.和B.Claise，“考虑新性能指标开发的指南”，BCP 170，RFC 63902011年10月。
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design Considerations for Protocol Extensions", RFC 6709, September 2012.
[RFC6709]Carpenter，B.，Aboba，B.，和S.Cheshire，“协议扩展的设计考虑”，RFC 6709，2012年9月。
[RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the RTP Monitoring Framework", RFC 6792, November 2012.
[RFC6792]Wu，Q.，Hunt，G.，和P.Arden，“RTP监控框架的使用指南”，RFC 6792，2012年11月。
a. Burst/Gap Discard Threshold in RTP Metric
a. RTP度量中的突发/间隙丢弃阈值
* Metric Name: Burst/gap discard threshold in RTP
* 度量名称：RTP中的突发/间隙丢弃阈值
* Metric Description: The Threshold is equivalent to Gmin in [RFC3611], i.e., the number of successive packets that must not be discarded prior to and following a discard packet in order for this discarded packet to be regarded as part of a gap.
* 度量说明：阈值相当于[RFC3611]中的Gmin，即在丢弃数据包之前和之后不得丢弃的连续数据包数量，以便将该丢弃数据包视为间隙的一部分。
* Method of Measurement or Calculation: See Section 3.2, Threshold definition.
* 测量或计算方法：见第3.2节，阈值定义。
* Units of Measurement: See Section 3.2, Threshold definition.
* 计量单位：见第3.2节，阈值定义。
* Measurement Point(s) with Potential Measurement Domain: See Section 3, 1st paragraph.
* 具有潜在测量域的测量点：见第3节第1段。
* Measurement Timing: See Section 3, 2nd paragraph for measurement timing and Section 3.2 for Interval Metric flag.
* 测量定时：测量定时见第3节第2段，间隔公制标志见第3.2节。
* Use and Applications: See Section 1.4.
* 用途和应用：见第1.4节。
* Reporting Model: See RFC 3611.
* 报告模式：见RFC 3611。
b. Packets Discarded in Bursts Metric
b. 在突发度量中丢弃的数据包
* Metric Name: RTP packets discarded in bursts
* 度量名称：突发丢弃的RTP数据包
* Metric Description: The total number of RTP packets discarded during discard bursts.
* 度量说明：丢弃突发期间丢弃的RTP数据包总数。
* Method of Measurement or Calculation: See Section 3.2, Packets Discarded in Bursts definition.
* 测量或计算方法：见第3.2节，突发定义中丢弃的数据包。
* Units of Measurement: See Section 3.2, Packets Discarded in Bursts definition.
* 测量单位：见第3.2节，突发定义中丢弃的数据包。
* Measurement Point(s) with Potential Measurement Domain: See Section 3, 1st paragraph.
* 具有潜在测量域的测量点：见第3节第1段。
* Measurement Timing: See Section 3, 2nd paragraph for measurement timing and Section 3.2 for Interval Metric flag.
* 测量定时：测量定时见第3节第2段，间隔公制标志见第3.2节。
* Use and Applications: See Section 1.4.
* 用途和应用：见第1.4节。
* Reporting Model: See RFC 3611.
* 报告模式：见RFC 3611。
c. Total Packets Expected in Discard Bursts Metric
c. 丢弃突发度量中预期的数据包总数
* Metric Name: Total RTP packets expected in discard bursts
* 度量名称：丢弃突发中预期的RTP数据包总数
* Metric Description: The total number of packets expected during discard bursts (that is, the sum of received packets and lost packets).
* 度量说明：丢弃突发期间预期的数据包总数（即接收数据包和丢失数据包的总和）。
* Method of Measurement or Calculation: See Section 3.2, Total Packets Expected in Bursts definition.
* 测量或计算方法：见第3.2节，突发定义中预期的总数据包。
* Units of Measurement: See Section 3.2, Total Packets Expected in Bursts definition.
* 测量单位：见第3.2节，突发定义中预期的总数据包。
* Measurement Point(s) with Potential Measurement Domain: See Section 3, 1st paragraph.
* 具有潜在测量域的测量点：见第3节第1段。
* Measurement Timing: See Section 3, 2nd paragraph for measurement timing and Section 3.2 for Interval Metric flag.
* 测量定时：测量定时见第3节第2段，间隔公制标志见第3.2节。
* Use and Applications: See Section 1.4.
* 用途和应用：见第1.4节。
* Reporting Model: See RFC 3611.
* 报告模式：见RFC 3611。
Authors' Addresses
作者地址
Alan Clark Telchemy Incorporated 2905 Premiere Parkway, Suite 280 Duluth, GA 30097 USA
Alan Clark Telchemy Incorporated 2905 Premiere Parkway，美国佐治亚州德卢斯280号套房，邮编30097
EMail: alan.d.clark@telchemy.com
EMail: alan.d.clark@telchemy.com
Rachel Huang Huawei Technologies Co., Ltd. 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
中国江苏省南京市雨花区软件大道101号瑞秋黄华为技术有限公司210012
EMail: Rachel@huawei.com
EMail: Rachel@huawei.com
Qin Wu (editor) Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China
秦武（编辑）中国江苏省南京市雨花区华为软件大道101号210012
EMail: sunseawq@huawei.com
EMail: sunseawq@huawei.com