One document matched: draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<rfc category="std" docName="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt"
ipr="trust200902">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<front>
<title abbrev="RTCP XR Burst/Gap Loss">RTP Control Protocol (RTCP)
Extended Report (XR) Block for Burst/Gap Loss metric Reporting</title>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization abbrev="Telchemy">Telchemy Incorporated</organization>
<address>
<postal>
<street>2905 Premiere Parkway, Suite 280</street>
<city>Duluth</city>
<region>GA</region>
<code>30097</code>
<country>USA</country>
</postal>
<email>alan.d.clark@telchemy.com</email>
</address>
</author>
<author fullname="Sunshine Zhang" initials="S." surname="Zhang">
<organization abbrev="STTRI">Shanghai Research Institute of China
Telecom Corporation Limited</organization>
<address>
<postal>
<street>No.1835,South Pudong Road</street>
<city>Shanghai</city>
<code>200122</code>
<country>China</country>
</postal>
<email>zhangyx@sttri.com.cn</email>
</address>
</author>
<author fullname="Jing Zhao" initials="J." surname="Zhao">
<organization abbrev="STTRI">Shanghai Research Institute of China
Telecom Corporation Limited</organization>
<address>
<postal>
<street>No.1835,South Pudong Road</street>
<city>Shanghai</city>
<code>200122</code>
<country>China</country>
</postal>
<email>zhaojing@sttri.com.cn</email>
</address>
</author>
<author fullname="Qin Wu" initials="Q." role="editor" surname="Wu">
<organization>Huawei</organization>
<address>
<postal>
<street>101 Software Avenue, Yuhua District</street>
<city>Nanjing</city>
<region>Jiangsu</region>
<code>210012</code>
<country>China</country>
</postal>
<email>sunseawq@huawei.com</email>
</address>
</author>
<date year="2013" />
<area>Real-time Applications and Infrastructure Area</area>
<workgroup>Audio/Video Transport Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>Real Time Control Protocol</keyword>
<abstract>
<t>This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) Block that allows the reporting of Burst and Gap Loss metrics for
use in a range of RTP applications.</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<section title="Burst and Gap Loss Report Block">
<t>This document defines a new block type to augment those defined in
<xref target="RFC3611"></xref> for use in a range of RTP applications.
The new block type supports the reporting of the proportion of packets
lost by the network. The losses during loss bursts are reported,
together with the number of bursts and additional data allowing the
calculation of statistical parameters (mean and variance) of the
distribution of burst lengths. Some uses of these metrics depend on
the availability of the metric "cumulative number of packets lost"
from RTCP <xref target="RFC3550"></xref>.</t>
<t>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. The burstiness of packet loss affects
user experience, may influence any sender strategies to mitigate the
problem, and may also have diagnostic value.</t>
<t>The metric belongs to the class of transport-related end system
metrics defined in <xref target="RFC6792"></xref>.</t>
<t>The definitions of Burst, Gap, Loss and Discard are consistent with
definitions in <xref target="RFC3611"></xref>. 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 may be an equivalent method to that defined in <xref
target="RFC3611"></xref>. The method used should produce the same
result as that defined in [RFC3611] for conditions of burst packet
loss, but may produce different results for conditions of time varying
jitter.</t>
</section>
<section title="RTCP and RTCP XR Reports">
<t>The use of RTCP for reporting is defined in <xref
target="RFC3550"></xref>. <xref target="RFC3611"></xref> defined an
extensible structure for reporting using an RTCP Extended Report (XR).
This document defines a new Extended Report block for use with <xref
target="RFC3550"></xref> and <xref target="RFC3611"></xref>.</t>
</section>
<section title="Performance Metrics Framework">
<t>The Performance Metrics Framework <xref target="RFC6390"></xref>
provides guidance on the definition and specification of performance
metrics. The RTP Monitoring Architectures <xref
target="RFC6792"></xref> provides guideline for reporting block format
using RTCP XR. The Metrics Block described in this document are in
accordance with the guidelines in <xref target="RFC6390"></xref> and
<xref target="RFC6792"></xref>.</t>
</section>
<section title="Applicability">
<t>These metrics are applicable to a range of RTP applications which
contain jitter buffers and don't use stream repair means, e.g.,
Forward Error Correction (FEC) <xref target="RFC5109"></xref> and/or
retransmission <xref target="RFC4588"></xref>.</t>
</section>
</section>
<section title="Terminology">
<section title="Standards Language">
<t>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 <xref
target="RFC2119">RFC 2119</xref>.</t>
<t>In addition, the following terms are defined:</t>
<t><list style="hanging">
<t hangText="Received, Lost and Discarded"><vspace
blankLines="1" />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 or late to
be played out or thrown away before playout due to packet
duplication or redundancy shall be regarded as discarded. A packet
shall be classified as one of received (or OK), discarded or lost.
The metric "cumulative number of packets lost" defined in <xref
target="RFC3550"></xref> reports a count of packets lost from the
media stream (single SSRC within single RTP session). Similarly
the metric "number of packets discarded" defined in <xref
target="DISCARD"></xref> reports a count of packets discarded from
the media stream (single SSRC within single RTP session) arriving
at the receiver. Another metric defined in <xref
target="RFC5725"></xref> is available to report on packets which
are not recovered by any repair techniques which may be in use.
<vspace blankLines="1" /></t>
<t hangText="Bursts and Gaps"><vspace blankLines="1" />The terms
Burst and Gap are used in a manner consistent with that of RTCP XR
[RFC3611]. RTCP XR views a RTP stream as being divided into
bursts, which are periods during which the loss rate is high
enough to cause noticeable quality degradation (generally over 5
percent loss rate), and gaps, which are periods during which lost
packets are infrequent and hence quality is generally acceptable.
<vspace blankLines="1" /></t>
</list></t>
</section>
</section>
<section title="Burst/Gap Loss Block">
<t>Metrics in this block report on Burst/Gap Loss in the stream arriving
at the RTP system. The measurement of these metrics are made at the
receiving end of the RTP stream. Instances of this Metrics Block refer
by Synchronization source (SSRC) to the separate auxiliary Measurement
Information block <xref target="RFC6776"></xref> which describes
measurement periods in use(see RFC6776 section 4.2).</t>
<t>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 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.</t>
<section title="Report Block Structure">
<t>Burst/Gap Loss metrics block<figure
title="Figure 1: Report Block Structure">
<artwork>
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=NBGL | I |C| resv. | block length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Sum of Burst Durations (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Lost in Bursts | Total... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Packets expected in bursts | Number of bursts | Sum of|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Squares of Burst Durations (ms-squared) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure></t>
</section>
<section title="Definition of Fields in Burst/Gap Loss Report Block">
<t><list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace blankLines="1" />A
Burst/Gap Loss Report Block is identified by the constant
NBGL.<vspace blankLines="1" />[Note to RFC Editor: please replace
NBGL with the IANA provided RTCP XR block type for this
block.]<vspace blankLines="1" /></t>
<t hangText="Interval Metric flag (I): 2 bits"><vspace
blankLines="1" />This field is used to indicate whether the
Burst/Gap Loss metrics are Sampled, Interval or Cumulative
metrics: <list>
<t>I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive
metrics reports.</t>
<t>I=11: Cumulative Duration - the reported value applies to
the accumulation period characteristic of cumulative
measurements.</t>
<t>I=01: Sampled Value - the reported value is a sampled
instantaneous value.</t>
</list>In this document, Burst/Gap Loss 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. <vspace blankLines="1" /></t>
<t
hangText=" Loss and Discard Combination flag (C): 1 bit"><vspace
blankLines="1" />The 'C' flag is used to indicate whether the
loss/discard report is combined with the burst gap loss report in
the same compound RTCP packet. The value is set to '1' if the
loss/discard report and the burst gap loss report are combined.
Otherwise, the value is set to '0'. If the 'C' flag is set to 1
but the burst gap discard was not sent, the receiver MUST discard
the burst gap loss. <vspace blankLines="1" /></t>
<t hangText="Reserved (resv): 5 bits"><vspace
blankLines="1" />These bits are reserved. They MUST be set to zero
by senders and ignored by receivers (See RFC6709 section 4.2).
<vspace blankLines="1" /></t>
<t hangText="block length: 16 bits"><vspace blankLines="1" /> The
length of this report block in 32-bit words, minus one. For the
Burst/Gap Loss block, the block length is equal to 5. The block
MUST be discarded if the block length is set to a different
value.<vspace blankLines="1" /></t>
<t hangText="SSRC of source: 32 bits"><vspace blankLines="1" />As
defined in Section 4.1 of <xref target="RFC3611"></xref>.<vspace
blankLines="1" /></t>
<t hangText="Threshold: 8 bits"><vspace blankLines="1" />The
Threshold is equivalent to Gmin in <xref target="RFC3611"></xref>,
i.e. the number of successive packets that must be received prior
to and following a lost packet in order for this lost packet to be
regarded as part of a gap. Note that the threshold is calculated
in accordance with Gmin Calculation defined in section 4.7.2 of
RFC3611.<vspace blankLines="1" /></t>
<t hangText="Sum of Burst Durations (ms): 24 bits"><vspace
blankLines="1" />The total duration of bursts of lost packets in
the period of the report (Interval or Cumulative). <vspace
blankLines="1" />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. <vspace
blankLines="1" /></t>
<t hangText="Packets lost in bursts: 24 bits"><vspace
blankLines="1" />The total number of packets lost during loss
bursts.<vspace blankLines="1" />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.
<vspace blankLines="1" /></t>
<t hangText="Total packets expected in bursts: 24 bits"><vspace
blankLines="1" />The total number of packets expected during loss
bursts (that is, the sum of received packets and lost packets).
<vspace blankLines="1" />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. <vspace
blankLines="1" /></t>
<t hangText="Number of bursts: 16 bits"><vspace
blankLines="1" />The number of bursts in the period of the report
(Interval or Cumulative). <vspace blankLines="1" />The measured
value is unsigned value. If the measured value exceeds 0xFFFD, the
value 0xFFFE MUST be reported to indicate an over-range
measurement. If the measurement is unavailable, the value 0xFFFF
MUST be reported. <vspace blankLines="1" /></t>
<t
hangText="Sum of Squares of Burst Durations (ms-squared): 36 bits"><vspace
blankLines="1" />The sum of the squares of burst durations (where
individual burst durations are expressed in ms) over in the period
of the report (Interval or Cumulative). The units for this
quantity are milliseconds-squared. <vspace blankLines="1" />The
measured value is unsigned value. If the measured value exceeds
0xFFFFFFFFD, the value 0xFFFFFFFFE MUST be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFFFFFFF MUST be reported. <vspace blankLines="1" /></t>
</list></t>
</section>
<section title="Derived metrics based on reported metrics">
<t>The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement
Information block <xref target="RFC6776"></xref> and also with the
metric "cumulative number of packets lost" provided in standard RTCP
<xref target="RFC3550"></xref>.</t>
<t>These metrics provide information relevant to statistical
parameters, including:<list style="symbols">
<t>The fraction of packets lost during bursts (i.e., Burst Loss
Rate in <xref target="SUMSTAT"></xref>), which can be calculated
using the metric " Packets Loss in Bursts " and the metric " Total
Packets expected in Bursts " provided in the Burst/Gap Loss
metrics block.</t>
<t>The fraction of packets lost during gaps (i.e., Gap Loss Rate
in <xref target="SUMSTAT"></xref>), which can be calculated using
the metric " Packets Loss in Bursts " and the metric " Total
Packets expected in Bursts " provided in the Burst/Gap Loss
metrics block.</t>
<t>burst duration mean <xref target="SUMSTAT"></xref>, which can
be calculated using the metric " Packets Loss in Bursts " and the
metric " Total Packets expected in Bursts " provided in the
Burst/Gap Loss metrics block.</t>
<t>burst duration variance <xref target="SUMSTAT"></xref>, which
can be calculated using the metric " Packets Loss in Bursts " and
the metric " Total Packets expected in Bursts " provided in the
Burst/Gap Loss metrics block.</t>
</list></t>
<t>The details on calculation these parameters in the metrics are
described in <xref target="SUMSTAT"></xref>.</t>
</section>
</section>
<section title="Considerations for Voice-over-IP applications">
<t>This Metrics Block is applicable to a broad range of RTP
applications. Where the metric is used with a Voice-overIP (VoIP)
application and the stream repair means is not available, the following
considerations apply.</t>
<t>RTCP XR views a call as being divided into bursts, which are periods
during which the loss rate is high enough to cause noticeable call
quality degradation (generally over 5 percent loss rate), and gaps,
which are periods during which lost packets are infrequent and hence
call quality is generally acceptable.</t>
<t>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.</t>
<t>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.</t>
</section>
<section title="SDP Signaling">
<t>[RFC3611] defines the use of SDP (Session Description Protocol) <xref
target="RFC4566"></xref> for signaling the use of XR blocks. XR blocks
MAY be used without prior signaling.</t>
<section title="SDP rtcp-xr-attrib Attribute Extension">
<t>This section augments the SDP <xref target="RFC4566"></xref>
attribute "rtcp-xr" defined in <xref target="RFC3611"></xref> by
providing an additional value of "xr-format" to signal the use of the
report block defined in this document.<figure>
<artwork>
xr-format =/ xr-bgl-block
xr-bgl-block = "burst-gap-loss"
</artwork>
</figure></t>
</section>
<section title="Offer/Answer Usage">
<t>When SDP is used in offer-answer context, the SDP Offer/Answer
usage defined in <xref target="RFC3611"></xref> for unilateral
"rtcp-xr" attribute parameters applies. For detailed usage in
Offer/Answer for unilateral parameter, refer to section 5.2 of <xref
target="RFC3611"></xref>.</t>
</section>
</section>
<section title="IANA Considerations">
<t>New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to <xref
target="RFC3611"></xref>.</t>
<section title="New RTCP XR Block Type value">
<t>This document assigns the block type value NBGL in the IANA " RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry " to
the "Burst/Gap Loss Metrics Block".</t>
<t>[Note to RFC Editor: please replace NBGL with the IANA provided
RTCP XR block type for this block.]</t>
</section>
<section title="New RTCP XR SDP Parameter">
<t>This document also registers a new parameter "burst-gap-loss" in
the " RTP Control Protocol Extended Reports (RTCP XR) Session
Description Protocol (SDP) Parameters Registry".</t>
</section>
<section title="Contact information for registrations">
<t><figure>
<artwork>
The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
</artwork>
</figure><vspace blankLines="1" /></t>
</section>
</section>
<section title="Security Considerations">
<t>This block does not provide per-packet statistics, so the risk to
confidentiality documented in Section 7, paragraph 3 of <xref
target="RFC3611"></xref> does not apply. However the gaps indicated
within this block could be used to detect the timing of other events on
the path between the sender and receiver. For example, a competing
multimedia stream might cause a loss burst for the duration of the
stream, allowing the receiver of this block to know when the competing
stream was active. This risk is not a significant threat since the only
information leaked is the timing of the loss, not the cause. Besides
this, it is believed that this proposed RTCP XR report block introduces
no other new security considerations beyond those described in <xref
target="RFC3611"></xref>.</t>
</section>
<section title="Contributors">
<t>Geoff Hunt wrote the initial draft of this document.</t>
</section>
<section title="Acknowledgments">
<t>The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, Claus
Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, Tom Hock,
Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, Mohamed Mostafa,
Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Raviraj, Albrecht
Schwarz, Tom Taylor, Hideaki Yamada, Adam Roach, Dan Romascanu,Chris
Lonvick, Alfred C.,Morton Jr., Pete Resnick, Ted Lemon, Stephen Farrell,
Richard Barnes, Benoit Claise.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC2119">
<front>
<title abbrev="RFC Key Words">Key words for use in RFCs to Indicate
Requirement Levels</title>
<author fullname="Scott Bradner" initials="S." surname="Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass. Ave.</street>
<street>Cambridge</street>
<street>MA 02138</street>
</postal>
<phone>- +1 617 495 3864</phone>
<email>sob@harvard.edu</email>
</address>
</author>
<date month="March" year="1997" />
<area>General</area>
<keyword>keyword</keyword>
<abstract>
<t>In many standards track documents several words are used to
signify the requirements in the specification. These words are
often capitalized. This document defines these words as they
should be interpreted in IETF documents. Authors who follow these
guidelines should incorporate this phrase near the beginning of
their document: <list>
<t>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.</t>
</list></t>
<t>Note that the force of these words is modified by the
requirement level of the document in which they are used.</t>
</abstract>
</front>
</reference>
<reference anchor="RFC3611">
<front>
<title>RTP Control Protocol Extended Reports (RTCP XR)</title>
<author fullname="T. Friedman" initials="T." surname="Friedman">
<organization></organization>
</author>
<author fullname="R. Caceres" initials="R." surname="Caceres">
<organization></organization>
</author>
<author fullname="A. Clark" initials="A." surname="Clark">
<organization></organization>
</author>
<date month="November" year="2003" />
<abstract>
<t>This document defines the Extended Report (XR) packet type for
the RTP Control Protocol (RTCP), and defines how the use of XR
packets can be signaled by an application if it employs the
Session Description Protocol (SDP). XR packets are composed of
report blocks, and seven block types are defined here. The purpose
of the extended reporting format is to convey information that
supplements the six statistics that are contained in the report
blocks used by RTCP's Sender Report (SR) and Receiver Report (RR)
packets. Some applications, such as multicast inference of network
characteristics (MINC) or voice over IP (VoIP) monitoring, require
other and more detailed statistics. In addition to the block types
defined here, additional block types may be defined in the future
by adhering to the framework that this document provides.</t>
</abstract>
</front>
</reference>
<reference anchor="RFC4566">
<front>
<title>SDP: Session Description Protocol</title>
<author fullname="M. Handley" initials="M." surname="Handley">
<organization></organization>
</author>
<author fullname="V. Jacobson" initials="V." surname="Jacobson">
<organization></organization>
</author>
<author fullname="C. Perkins" initials="C." surname="Perkins">
<organization></organization>
</author>
<date month="July" year="2006" />
<abstract>
<t>This memo defines the Session Description Protocol (SDP). SDP
is intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation. [STANDARDS-TRACK]</t>
</abstract>
</front>
</reference>
<reference anchor="RFC3550">
<front>
<title>RTP: A Transport Protocol for Real-Time Applications</title>
<author fullname="Henning Schulzrinne" initials="H."
surname="Schulzrinne">
<organization>Columbia University</organization>
</author>
<date month="July" year="2003" />
</front>
<seriesInfo name="RFC" value="3550" />
<format type="TXT" />
</reference>
<reference anchor="RFC5725">
<front>
<title>Post-Repair Loss RLE Report Block Type for RTP Control
Protocol (RTCP) Extended Reports (XRs)</title>
<author fullname="Ali Begen" initials="A." surname="Begen">
<organization></organization>
</author>
<author fullname="Dong Hsu" initials="D." surname="Hsu">
<organization></organization>
</author>
<author fullname="Michael Lague" initials="M." surname="Lague">
<organization></organization>
</author>
<date month="February" year="2020" />
</front>
<seriesInfo name="RFC" value="5725" />
<format type="TXT" />
</reference>
</references>
<references title="Informative References">
<reference anchor="RFC6709">
<front>
<title>Design Considerations for Protocol Extensions</title>
<author fullname="B.Carpenter" initials="B." surname="Carpenter">
<organization></organization>
</author>
<author fullname="B.Aboba" initials="B." surname="Aboba">
<organization></organization>
</author>
<author fullname="S.Cheshire" initials="S." surname="Cheshire">
<organization></organization>
</author>
<date month="September" year="2012" />
</front>
<seriesInfo name="RFC" value="6709" />
<format type="TXT" />
</reference>
<reference anchor="DISCARD">
<front>
<title>RTCP XR Report Block for Discard metric Reporting</title>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<date month="December" year="2012" />
</front>
<seriesInfo name="ID" value="draft-ietf-xrblock-rtcp-xr-discard-11" />
<format type="TXT" />
</reference>
<reference anchor="SUMSTAT">
<front>
<title>RTCP XR for Summary Statistics Metrics Reporting</title>
<author fullname="Glen Zorn" initials="G." surname="Zorn">
<organization></organization>
</author>
<date month="March" year="2013" />
</front>
<seriesInfo name="ID"
value="draft-ietf-xrblock-rtcp-xr-summary-stat-11" />
<format type="TXT" />
</reference>
<reference anchor="RFC6776">
<front>
<title>Measurement Identity and information Reporting using SDES
item and XR Block</title>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<date month="October" year="2012" />
</front>
<seriesInfo name="RFC" value="6776" />
<format type="TXT" />
</reference>
<reference anchor="RFC6792">
<front>
<title>Monitoring Architectures for RTP</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<date month="November" year="2012" />
</front>
<seriesInfo name="RFC" value="6792" />
<format type="TXT" />
</reference>
<reference anchor="RFC6390">
<front>
<title>Framework for Performance Metric Development</title>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization></organization>
</author>
<author fullname="Benoit Claise " initials="B." surname="Claise">
<organization></organization>
</author>
<date month="July" year="2011" />
</front>
<seriesInfo name="RFC" value="6390" />
</reference>
<reference anchor="RFC5109">
<front>
<title>RTP Payload Format for Generic Forward Error
Correction</title>
<author fullname="A.,Li" initials="A." surname="Li">
<organization></organization>
</author>
<date month="December" year="2007" />
</front>
<seriesInfo name="RFC" value="5109" />
</reference>
<reference anchor="RFC4588">
<front>
<title>RTP Retransmission Payload Format</title>
<author fullname="J.,Rey" initials="J." surname="Rey">
<organization></organization>
</author>
<author fullname="D.,Leon" initials="D." surname="Leon">
<organization></organization>
</author>
<author fullname="A.,Miyazaki" initials="A.">
<organization></organization>
</author>
<author fullname="V.,Varsa" initials="V." surname="Varsa">
<organization></organization>
</author>
<author fullname="R.,Hakenberg" initials="R." surname="Hakenberg">
<organization></organization>
</author>
<date month="July" year="2006" />
</front>
<seriesInfo name="RFC" value="4588" />
</reference>
</references>
<section title="Metrics represented using RFC6390 Template">
<t>RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC
number, when assigned.</t>
<t><list style="letters">
<t>Threshold Metric<vspace blankLines="1" /><list style="symbols">
<t>Metric Name: Threshold in RTP<vspace blankLines="1" /></t>
<t>Metric Description: The Threshold is equivalent to Gmin in
[RFC3611], i.e. the number of successive RTP packets that must
be received prior to and following a lost RTP packet in order
for this lost RTP packet to be regarded as part of a gap.<vspace
blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2,
Threshold definition [RFCXXXX].<vspace blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Threshold definition
[RFCXXXX]. <vspace blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
<t>Sum of Burst Durations Metric<vspace blankLines="1" /><list
style="symbols">
<t>Metric Name: Sum of Burst Durations in RTP<vspace
blankLines="1" /></t>
<t>Metric Description: The total duration of bursts of lost RTP
packets in the period of the report.<vspace
blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2, Sum of
Burst Durations definition [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Sum of Burst Durations
definition [RFCXXXX]. <vspace blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
<t>Packets lost in bursts Metric<vspace blankLines="1" /><list
style="symbols">
<t>Metric Name: RTP Packets lost in bursts<vspace
blankLines="1" /></t>
<t>Metric Description: The total number of RTP packets lost
during loss bursts.<vspace blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2,
Packets lost in bursts definition [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Packets lost in bursts
definition [RFCXXXX]. <vspace blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
<t>Total packets expected in bursts Metric<vspace
blankLines="1" /><list style="symbols">
<t>Metric Name: Total RTP packets expected in bursts<vspace
blankLines="1" /></t>
<t>Metric Description: The total number of RTP packets expected
during loss bursts (that is, the sum of received RTP packets and
lost RTP packets).<vspace blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2, Total
packets expected in bursts definition [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Total packets expected
in bursts definition [RFCXXXX].<vspace blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
<t>Number of bursts Metric<vspace blankLines="1" /><list
style="symbols">
<t>Metric Name: Number of bursts in RTP<vspace
blankLines="1" /></t>
<t>Metric Description: The total duration of bursts of lost RTP
packets in the period of the report.<vspace
blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2, Number
of bursts definition [RFCXXXX].<vspace blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Number of bursts
definition [RFCXXXX]. <vspace blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
<t>Sum of Squares of Burst Durations Metric<vspace
blankLines="1" /><list style="symbols">
<t>Metric Name: Sum of Squares of Burst Durations in RTP<vspace
blankLines="1" /></t>
<t>Metric Description: The sum of the squares of burst durations
(where individual burst durations are expressed in ms) over in
the period of the report.<vspace blankLines="1" /></t>
<t>Method of Measurement or Calculation: See section 3.2, Sum of
Squares of Burst Durations definition [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Units of Measurement: See section 3.2, Sum of Squares of
Burst Durations definition [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Measurement Point(s) with Potential Measurement Domain: See
section 3, 1st paragraph [RFCXXXX]. <vspace
blankLines="1" /></t>
<t>Measurement Timing: See section 3, 2nd paragraph [RFCXXXX]
for measurement timing and section 3.2 [RFCXXXX] for Interval
Metric flag. <vspace blankLines="1" /></t>
<t>Use and applications: See section 1.4 [RFCXXXX].<vspace
blankLines="1" /></t>
<t>Reporting model: See RFC3611.<vspace blankLines="1" /></t>
</list></t>
</list></t>
</section>
<section title="Change Log">
<t>Note to the RFC-Editor: please remove this section prior to
publication as an RFC.</t>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-11">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>Incorporated Ted's proposed change during IESG review.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-10">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>IESG Review comments are addressed in this version.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-09">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>IETF LC comments are addressed together with AD's comment on
Normative language in this version.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>Move RFC6709 as one informative reference.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-07">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>Editorial changes based on comments in the WGLC.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>SDP update based on SDP Directorate Review.</t>
<t>Add some texts to get consistent with RFC6798 and Delay
draft.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04">
<t>The following are the major changes compared to previous
version:<list style="symbols">
<t>Outdated reference update.</t>
<t>Editorial changes based on comments that applied to PDV and
Delay drafts.</t>
</list></t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 03:24:20 |