One document matched: draft-ietf-xrblock-rtcp-xr-summary-stat-05.xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='http://xml.resource.org/authoring/rfc2629.xslt' ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc3611 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3611.xml">
<!ENTITY rfc3550 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3550.xml">
<!ENTITY rfc4566 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4566.xml">
<!ENTITY I-D.ietf-avtcore-monarch PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-avtcore-monarch.xml">
<!ENTITY I-D.ietf-xrblock-rtcp-xr-meas-identity PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-xrblock-rtcp-xr-meas-identity.xml">
<!ENTITY I-D.ietf-xrblock-rtcp-xr-discard PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-xrblock-rtcp-xr-discard.xml">
<!ENTITY I-D.ietf-xrblock-rtcp-xr-burst-gap-loss PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-xrblock-rtcp-xr-burst-gap-loss.xml">
<!ENTITY I-D.ietf-xrblock-rtcp-xr-burst-gap-discard PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-xrblock-rtcp-xr-burst-gap-discard.xml">
]>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
<rfc category="std" docName="draft-ietf-xrblock-rtcp-xr-summary-stat-05"
ipr="trust200902">
<front>
<title abbrev="Summary Stats XR Blocks">RTP Control Protocol (RTCP)
Extended Report (XR) Blocks for Summary Statistics Metrics
Reporting</title>
<author fullname="Glen Zorn" initials="G." role="editor" surname="Zorn">
<organization>Network Zen</organization>
<address>
<postal>
<street>227/358 Thanon Sanphawut</street>
<city>Bang Na</city>
<region>Bangkok</region>
<code>10260</code>
<country>Thailand</country>
</postal>
<phone>+66 (0) 909-201060</phone>
<email>glenzorn@gmail.com</email>
</address>
</author>
<author fullname="Roland Schott" initials="R." surname="Schott">
<organization>Deutsche Telekom</organization>
<address>
<postal>
<street>Deutsche-Telekom-Allee 7</street>
<street></street>
<city>Darmstadt</city>
<code>64295</code>
<country>Germany</country>
</postal>
<email>Roland.Schott@telekom.de</email>
</address>
</author>
<author fullname="Qin Wu" initials="Q." 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>
<author fullname="Rachel Huang" initials="R." surname="Huang">
<organization>Huawei</organization>
<address>
<postal>
<street>101 Software Avenue, Yuhua District</street>
<city>Nanjing</city>
<code>210012</code>
<country>China</country>
</postal>
<email>Rachel@huawei.com</email>
</address>
</author>
<date year="2012" />
<abstract>
<t>This document defines three RTP Control Protocol (RTCP) Extended
Report (XR) Blocks that allow the reporting of loss, duplication and
discard summary statistics metrics in a range of RTP applications.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<section title="Summary Statistics Metrics">
<t>This draft defines three new block types to augment those defined
in <xref target="RFC3611"></xref> for use in a range of RTP
applications.</t>
<t> The first two block types support the reporting of burst gap loss/
discard summary statistics including packet loss/discard proportion,
mean and variance and belong to the class of transport-related end
system metrics defined in <xref target="RFC6792"></xref>. These two
blocks are intended to be used in conjunction with information from
the Burst Gap Loss Metrics Block or Burst Gap Discard Metrics Block,
and on which these two block therefore depend. The metrics in the
Burst Gap Loss block or Burst Gap Discard Metrics Block can be used
independently of the metrics defined in the first two blocks. </t>
<t>The third block supports the reporting of detailed statistics for
each frame type, including the number of frames received, lost and
discarded of each frame type in the Group of Pictures (GOP) and
additional data allowing the calculation of statistical parameters
(e.g.,the proportion of each frame type impaired by packet loss and
discard). The metrics defined in this block belong to the class of
application layer metrics defined in <xref
target="RFC6792"></xref>.</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 RTP Monitoring Architectures <xref target="RFC6792"></xref>
provides guideline for reporting block format using RTCP XR. Metrics
described in this draft are in accordance with the guidelines in <xref
target="RFC6792"></xref>.</t>
</section>
<section title="Applicability">
<t>These metrics are applicable to a wide range of RTP applications
and reflect transient IP problems that affect user experience. They
can be used to form an accurate assessment of users' quality of
experience and influence sender strategies to mitigate the
problem.</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="Picture Type"><vspace blankLines="1" /> Picture Types
used in the different video algorithms are composed of the Key
frame and Derived frames. The Key frame is also called a reference
frame and used as a reference for predicting other pictures. It is
coded without prediction from other pictures. Derived frames are
derived from a Key frame using a prediction algorithm. <vspace
blankLines="1" /></t>
</list></t>
</section>
</section>
<section title="Transport Related End System Metrics">
<section anchor="BGLSS"
title="Burst/Gap Loss Summary Statistics Metrics Block">
<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> (which MUST be
present in the same RTCP packet as the Burst/Gap Loss block) and also
with the metric "cumulative number of packets lost" provided in
standard RTCP <xref target="RFC3550"></xref>. 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 <xref
target="RFC6776"></xref> section 4.2). This Metrics Block relies on
the measurement period in the Measurement Information block indicating
the span of the report and SHOULD be sent in the same compound RTCP
packet as the measurement information block. If the measurement period
is not received in the same compound RTCP packet as this Metrics
Block, this metrics block MUST be discarded.</t>
<t>The metrics carried in this Metrics Block provide information
relevant to statistical parameters, including burst loss rate, gap
loss rate, burst duration mean, burst duration variance and are
calculated at the receiving end of the RTP stream using burst gap loss
metrics defined in <xref target="BGLOSS"></xref> and other information
which is sent together with this report block.</t>
<section title="Report Block Structure">
<figure>
<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=BGLSS | I | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Loss Rate | Gap Loss Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst duration Mean | Burst duration Variance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in Loss Summary Statistics Block">
<t><list style="hanging">
<t hangText="Block Type (BT): 8 bits"><vspace
blankLines="1" />Burst/Gap Loss Summary Statistics Block is
identified by the constant <BGLSS>. <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 Summary Statistics metrics are Sampled, Interval
or Cumulative metrics: <vspace blankLines="1" /><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, the value I=00 is the reserved value
and MUST NOT be used.<vspace blankLines="1" /></t>
<t hangText="Reserved: 6 bits"><vspace blankLines="1" /> This
field is reserved for future definition. In the absence of such
a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver (See RFC6709 section 4.2).
<vspace blankLines="1" /></t>
<t hangText="Block Length: 16 bits"><vspace blankLines="1" />
The constant 3, in accordance with the definition of this field
in Section 3 of <xref target="RFC3611">RFC 3611</xref>. <vspace
blankLines="1" /></t>
<t hangText="SSRC of Source: 32 bits"><vspace blankLines="1" />
As defined in Section 4.1 of <xref
target="RFC3611">RFC3611</xref>. <vspace blankLines="1" /></t>
<t hangText="Burst Loss Rate: 16 bits"><vspace blankLines="1" />
The fraction of packets lost during bursts since the beginning
of reception, expressed as a fixed point number with the binary
point at the left edge of the field. This value is calculated by
dividing Packets Loss in Bursts by Total Packets expected in
Bursts as follows: <vspace blankLines="1" /> Packets Loss in
Bursts / Total Packets expected in Bursts <vspace
blankLines="1" /></t>
<t hangText="Gap Loss Rate: 16 bits"><vspace blankLines="1" />
The fraction of packets lost during gaps since the beginning of
reception expressed as a fixed point number with the binary
point at the left edge of the field. This value is calculated by
dividing the difference between number of packets lost and
Packets lost in Bursts by the difference between Packets
Expected and Total Packets expected in Bursts as follows:
<vspace blankLines="1" /> (number of packets lost - Packets Lost
in Bursts) / (Packets Expected - Total Packets expected in
Bursts) <vspace blankLines="1" /> where "number of packets lost"
is obtained from <xref target="RFC3550">standard RTCP</xref> and
Packets Expected is calculated as the difference between
"extended last sequence number" and "extended first sequence
number" (Interval or Cumulative) provided in the Measurement
Identity and Information block <xref target="RFC6776"></xref>.
<vspace blankLines="1" /> Note that if the metric is to be
calculated on an Interval basis, a difference must be taken
between the current and preceding values of "cumulative number
of packets lost" in RTCP, to obtain the "number of packets lost"
for the reporting interval. <vspace blankLines="1" /></t>
<t hangText="Burst Duration Mean:16bits"><vspace
blankLines="1" /> The mean burst duration is obtained as the
quotient: <vspace blankLines="1" /> mean = Sum of Burst
Durations / Number of Bursts <vspace blankLines="1" /> where
"Sum of Burst Durations" and “Number of Bursts” is obtained from
the RTCP XR Burst/Gap Loss Block <xref target="BGLOSS"></xref>.
<vspace blankLines="1" /></t>
<t hangText="Burst Duration Variance:16bits"><vspace
blankLines="1" /> The variance of the burst duration is obtained
using the standard result: <vspace blankLines="1" /> var = ( Sum
of Squares of Burst Durations - Number of Bursts * mean^2 ) /
(Number of Bursts - 1) <vspace blankLines="1" /> where "Sum of
Squares of Burst Durations" and “Number of Bursts”is obtained
from the RTCP XR Burst/Gap Loss Block <xref
target="BGLOSS"></xref>. <vspace blankLines="1" /></t>
</list></t>
</section>
</section>
<section anchor="BGDSS"
title="Burst/Gap Discard Summary Statistics Metrics Block">
<t>The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement
Identity block <xref target="RFC6776"></xref> (which MUST be present
in the same RTCP packet as the Burst/Gap Discard Summary Statistics
block) .</t>
<t>These metrics provide information relevant to statistical
parameters, including burst discard rate, gap discard rate and are
calculated at the receiving end of the RTP stream using burst gap
discard metrics defined in <xref target="BGDISCARD"></xref> and other
information which is sent together with this report block.</t>
<t>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 <xref target="RFC6776"></xref> section 4.2). This metrics block
relies on the measurement period in the Measurement Information block
indicating the span of the report and SHOULD be sent in the same
compound RTCP packet as the measurement information block. If the
measurement period is not received in the same compound RTCP packet as
this Metrics Block, this Metrics Block MUST be discarded.</t>
<section title="Report Block Structure">
<figure>
<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=BGDSS | I | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Discard Rate | Gap Discard Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in Burst/Gap Discard Summary Statistics Block">
<t><list style="hanging">
<t hangText="Block Type (BT): 8 bits"><vspace blankLines="1" />
Burst/Gap Discard Summary Statistics Block is identified by the
constant <BGDSS>. <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 Discard Summary Statistics metrics are Sampled,
Interval or Cumulative metrics: <vspace blankLines="1" /><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><vspace blankLines="1" /><vspace blankLines="1" />In
this document, the value I=00 is the reserved value and MUST NOT
be used.<vspace blankLines="1" /></t>
<t hangText="Reserved: 6 bits"><vspace blankLines="1" /> This
field is reserved for future definition. In the absence of such
a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver (See RFC6709 section 4.2).
<vspace blankLines="1" /></t>
<t hangText="Block Length: 16 bits"><vspace blankLines="1" />
The constant 2, in accordance with the definition of this field
in Section 3 of <xref target="RFC3611">RFC 3611</xref>. <vspace
blankLines="1" /></t>
<t hangText="SSRC of Source: 32 bits"><vspace blankLines="1" />
As defined in Section 4.1 of <xref
target="RFC3611">RFC3611</xref>. <vspace blankLines="1" /></t>
<t hangText="Burst Discard Rate: 16 bits"><vspace
blankLines="1" /> The fraction of packets discarded during
bursts since the beginning of reception, expressed as a fixed
point number with the binary point at the left edge of the
field. This value is calculated by dividing Packets Discarded in
Bursts by Total Packets expected in Bursts as follows: <vspace
blankLines="1" /> Packets Discarded in Bursts / Total Packets
expected in Bursts <vspace blankLines="1" /></t>
<t hangText="Gap Discard Rate: 16 bits"><vspace
blankLines="1" /> The fraction of packets discarded during gaps
since the beginning of reception expressed as a fixed point
number with the binary point at the left edge of the field. This
value is calculated by dividing the difference between number of
packets discarded and Packets Discarded in Bursts by the
difference between Packets Expected and Total Packets expected
in Bursts as follows: <vspace blankLines="1" /> (number of
packets discarded - Packets Discarded in Bursts) / (Packets
Expected - Total Packets expected in Bursts) <vspace
blankLines="1" />where "number of packets discarded" is obtained
from the RTCP XR Discard Count Block <xref
target="DISCARD"></xref> and filled with the sum of packets
discarded due to early arrival (DT=1) and packets discarded due
to late arrival(DT=2) and Packets Expected is calculated as the
difference between "extended last sequence number" and "extended
first sequence number" (Interval or Cumulative) provided in the
Measurement Information block <xref target="RFC6776"></xref>. In
order for the Burst/ Gap Discard Summary Statistics Block to be
meaningful, 2 instances of the Discard Count block with DT=1 and
DT=2 MUST be included in the same RTCP XR packet as the
Burst/Gap Discard Summary Statistics Block.</t>
</list></t>
</section>
</section>
</section>
<section title="Application Level Metrics">
<section anchor="FISS"
title="Frame Impairment Statistics Summary Metrics Block">
<t>This block reports statistics on which frame type were affected
beyond the information carried in the Statistics Summary Report Block
RTCP packet specified in the section 4.6 of RFC 3611 <xref
target="RFC3611"></xref>. Information is measured at the receiving end
of the RTP stream and recorded about the number of frames received,
lost frames, duplicated frames and lost partial frames. Such
information can be useful for network management and video quality
monitoring.</t>
<section title="Report Block Structure">
<figure>
<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=FISS |T| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Begin_seq | End_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of frames received |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discarded_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lost_full_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lost_partial_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in Frame Impairment Summary Statistics Block">
<t><list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace
blankLines="1" />Frame Impairment Statistics Summary Block is
identified by the constant <FISS>. <vspace
blankLines="1" /></t>
<t hangText="Picture type indicator (T): 1 bit"><vspace
blankLines="1" /> This field is used to indicate the frame type
to be reported. The bit is set to 0 if the lost_full_frames,
lost_partial_frames and dup_frames fields contain Key frame
(reference frame) counts or 1 if they contain Derived frame
counts. Note that if both the Key frame and Derivation frame
report are sent, they should be sent in the same RTCP compound
packet using two Frame Impairment Summary Statistics Blocks.
<vspace blankLines="1" /></t>
<t hangText="Reserved: 7 bits"><vspace blankLines="1" /> This
field is reserved for future definition. In the absence of such
a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver. <vspace blankLines="1" /></t>
<t hangText="Block Length: 16 bits"><vspace blankLines="1" />
The constant 7, in accordance with the definition of this field
in Section 3 of <xref target="RFC3611">RFC 3611</xref>. <vspace
blankLines="1" /></t>
<t hangText="SSRC of Source: 32 bits"><vspace
blankLines="1" />As defined in Section 4.1 of <xref
target="RFC3611">RFC3611</xref>.<vspace blankLines="1" /></t>
<t hangText="Begin_seq: 16 bits "><vspace blankLines="1" /> As
defined in Section 4.1 of <xref target="RFC3611">RFC
3611</xref>. <vspace blankLines="1" /></t>
<t hangText="end_seq: 16 bits "><vspace blankLines="1" /> As
defined in Section 4.1 of <xref target="RFC3611">RFC
3611</xref>. <vspace blankLines="1" /></t>
<t hangText="Number of frames received:32 bits"><vspace
blankLines="1" />A count of the number of frames received in the
above sequence number interval, estimated if necessary. If no
frames have been received then this count SHALL be set to zero.
<vspace blankLines="1" /></t>
<t
hangText="Number of discarded frames (discarded_frames): 32 bits"><vspace
blankLines="1" />Number of frames discarded in the above
sequence number interval.<vspace blankLines="1" /></t>
<t
hangText="Number of duplicate frames (dup_frames): 32 bits"><vspace
blankLines="1" /> Number of duplicate frames received in the
above sequence number interval. <vspace blankLines="1" /></t>
<t
hangText="Number of full frames lost (lost_full_frames): 32 bits"><vspace
blankLines="1" />If one frame is completely lost, this frame is
regarded as one lost full frame. The lost_full_frames is
equivalent to the number of full frames lost in the above
sequence number interval. <vspace blankLines="1" /></t>
<t
hangText="Number of partial frames lost (lost_partial_frames): 32 bits"><vspace
blankLines="1" />If one frame is partially lost, this frame is
regarded as one lost fractional frame. The value of the
lost_partial_frames field is equivalent to the number of partial
frames lost in the above sequence number interval. <vspace
blankLines="1" /></t>
</list></t>
</section>
</section>
</section>
<section title="SDP Signaling">
<t>RFC 3611 defines the use of SDP (Session Description Protocol) <xref
target="RFC4566"></xref> for signaling the use of XR blocks. However XR
blocks MAY be used without prior signaling (see section 5 of
RFC3611).</t>
<section title="SDP rtcp-xr-attrib Attribute Extension">
<t>This section augments the SDP <xref target="RFC4566"></xref>
attribute "rtcp-xr" defined in Section 5.1 of RFC 3611 by providing
three additional values of "xr-format" to signal the use of the report
block defined in this document.</t>
<figure align="left">
<artwork>
xr-format = / burst-gap-loss-stat
/ burst-gap-discard-stat
/ frame-impairment-stat
Burst-gap-loss-stat ="burst gap loss summary statistics"
Burst-gap-discard-stat="burst gap discard summary statistics"
Frame-impairment-stat="frame impairment summary statistics"
</artwork>
</figure>
</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 of
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 RFC
3611.</t>
<section title="New RTCP XR Block Type values">
<t>This document assigns three new block type value in the "RTP
Control Protocol (RTCP) Extended Report (XR) Block Type Registry" :
<figure>
<artwork>
Name: BGLSS
Long Name: Burst/Gap Loss Summary Statistics Block
Value <BGLSS>
Reference: Section 3.1
Name: BGDSS
Long Name: Burst/Gap Discard Summary Statistics Block
Value <BGDSS>
Reference: Section 3.2
Name: FISS
Long Name: Frame Impairment Statistics Summary
Value <FISS>
Reference: Section 4.1
</artwork>
</figure></t>
</section>
<section title="New RTCP XR SDP Parameters">
<t>This document also registers three new SDP <xref
target="RFC4566"></xref> parameters for the "rtcp-xr" attribute in the
" RTP Control Protocol (RTCP) Extended Report (XR) SDP Parameters
Registry ": <figure>
<artwork>
* " burst-gap-loss-stat "
* " burst-gap-discard-stat "
* " frame-impairment-stat "
</artwork>
</figure></t>
</section>
<section title="Contact information for registrations">
<t>The contact information for the registrations is:</t>
<figure>
<artwork>
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
</artwork>
</figure>
</section>
</section>
<section title="Security Considerations">
<t>The new RTCP XR report blocks proposed in this document introduces no
new security considerations beyond those described in RFC 3611.</t>
</section>
<section title="Acknowledgements">
<t>The authors would like to thank Bill Ver Steeg, David R Oran, Ali
Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang Hu,
Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu for their
valuable comments and suggestions on this document.</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc3611;
&rfc2119;
&rfc4566;
&rfc3550;
<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="August" year="2012" />
</front>
<seriesInfo name="RFC" value="6776" />
<format type="TXT" />
</reference>
<reference anchor="DISCARD">
<front>
<title>RTP Control Protocol (RTCP) Extended Report (XR) Block for
Discard Count metric Reporting</title>
<author fullname="Alan Clark" initials="A" surname="Clark">
<organization></organization>
</author>
<author fullname="Glen Zorn" initials="G" surname="Zorn">
<organization></organization>
</author>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<date month="October" year="2012" />
<abstract>
<t>This document defines an RTP Control Protocol(RTCP) Extended
Report (XR) Block that allows the reporting of a simple discard
count metric for use in a range of RTP applications.</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft"
value="draft-ietf-xrblock-rtcp-xr-discard-09" />
<format target="http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-discard-09.txt"
type="TXT" />
</reference>
<reference anchor="BGLOSS">
<front>
<title>RTP Control Protocol (RTCP) Extended Report (XR) Block for
Burst/Gap Loss metric Reporting</title>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization></organization>
</author>
<author fullname="Sunshine Zhang" initials="S" surname="Zhang">
<organization></organization>
</author>
<author fullname="Jing Zhao" initials="J." surname="Zhao">
<organization></organization>
</author>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<date month="December" year="2012" />
<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>
<seriesInfo name="Internet-Draft"
value="draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06" />
<format target="http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06.txt"
type="TXT" />
</reference>
<reference anchor="BGDISCARD">
<front>
<title>RTP Control Protocol(RTCP) Extended Report (XR) Block for
Burst/Gap Discard metric Reporting</title>
<author fullname="Alan Clark" initials="A" surname="Clark">
<organization></organization>
</author>
<author fullname="Rachel Huang" initials="R" surname="Huang">
<organization></organization>
</author>
<author fullname="Wenson Wu" initials="W" surname="Wu">
<organization></organization>
</author>
<date day="4" month="December" year="2012" />
<abstract>
<t>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.</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft"
value="draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08" />
<format target="http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08.txt"
type="TXT" />
</reference>
<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>
</references>
<references title="Informative References">
<reference anchor="RFC6792">
<front>
<title>Monitoring Architectures for RTP</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<author fullname="Philip Arden" initials="P." surname="Arden">
<organization></organization>
</author>
<date month="November" year="2012" />
</front>
<seriesInfo name="RFC" value="6792" />
<format type="TXT" />
</reference>
</references>
<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-summary-stat-05">
<t>The following are the major changes compared to 04: <list
style="symbols">
<t>Editorial changes to get in line with Delay and Burst Gap
related drafts.</t>
</list></t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 03:16:14 |