One document matched: draft-zorn-xrblock-rtcp-xr-al-stat-03.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 rfc2250 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2250.xml">
<!ENTITY rfc3611 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3611.xml">
<!ENTITY rfc3357 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3357.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 rfc5216 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5216.xml">
<!ENTITY rfc5234 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml">
<!ENTITY rfc5296 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5296.xml">
<!ENTITY rfc5247 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5247.xml">
<!ENTITY I-D.ietf-avt-rapid-rtp-sync PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-avt-rapid-rtp-sync.xml">
<!ENTITY I-D.ietf-pmol-metrics-framework PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-pmol-metrics-framework.xml">
<!ENTITY I-D.hunt-avt-monarch PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.hunt-avt-monarch.xml">
<!ENTITY I-D.ietf-avt-rtp-svc PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-avt-rtp-svc.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-zorn-xrblock-rtcp-xr-al-stat-03"
ipr="pre5378Trust200902">
<front>
<title abbrev="Statistics Summary Blocks">RTCP XR for Summary Statistics
Metrics Reporting</title>
<author fullname="Glen Zorn" initials="G." surname="Zorn">
<organization>Network Zen</organization>
<address>
<postal>
<street>77/440 Soi Phoomjit, Rama IV Road</street>
<street>Phra Khanong, Khlong Toie</street>
<city>Bangkok</city>
<code>10110</code>
<country>Thailand</country>
</postal>
<phone>+66 (0) 87 502 4274</phone>
<email>gwz@net-zen.net</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="2011" />
<abstract>
<t>This document defines three RTCP XR Report Blocks and associated SDP
parameters that allows the reporting of loss, duplication and discard
summary statistics metrics for use in a range of RTP applications.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>RFC 3611 <xref target="RFC3611"></xref> defines seven report block
formats for network management and quality monitoring. However, some of
these metrics are mostly for multicast inference of network
characteristics (MINC) or voice over IP (VoIP) monitoring and not widely
applicable to other applications, e.g., video quality monitoring. This
document focuses on specifying new additional report block types used to
convey loss, duplication and discard summary statistics that are
generically designed for use in audio and video services. <vspace
blankLines="1" />The metrics belong to both the class of application
layer metrics and transport layer metrics defined in <xref
target="MONARCH"></xref> (work in progress).</t>
<section title="Applicability">
<t>The Report Blocks defined in this document can be applied to any
real-time applications that convey loss, duplication and discard
summary statistics. </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 compose of the key-frame
and the Derivation frame. 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. The Derivation frame
is derived from Key-frame using prediction from the reference
frame. <vspace blankLines="1" /></t>
</list></t>
</section>
</section>
<section title="Transport Layer Metrics">
<section anchor="BGLSS" title="Burst/Gap Loss Summsary Statistics 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 (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>. </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=TBD |I| rsv. | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Loss Rate | Gap Loss Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</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 Summsary Statistics Block is
identified by the constant <BGLSS>. <vspace
blankLines="1" /></t>
<t hangText="Interval Metric flag (I): 1 bit"><vspace
blankLines="1" />This field is used to indicate whether the
metrics block is an Interval or a Cumulative report,<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
MUST be ignored by the receiver. <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 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 Discarded 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 standard RTCP [RFC3550] 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 [MEASIDENT]. <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>
</list></t>
</section>
</section>
<section anchor="BGDSS"
title="Burst/Gap Discard Summary Statistics 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 (which MUST be present in the same RTCP packet as the
Burst/Gap Discard block) and also with the metric "number of packets
discarded" provided in the RTCP XR Discard Block [DISCARD]. The RTCP
XR Discard Block SHOULD be sent if the Burst/Gap Discard block is
sent, but the converse does not apply. </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=TBD |I| Rsv. | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Discard Rate | Gap Discard Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst duration Mean | Burst duration Varianc |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in 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="reserved: 8 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
MUST be ignored by the receiver. <vspace blankLines="1" /></t>
<t hangText="Interval Metric flag (I): 1 bit"><vspace
blankLines="1" />This field is used to indicate whether the
metrics block is an Interval or a Cumulative report,<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
MUST be ignored by the receiver. <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 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 Block [DISCARD] 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
[MEASIDENT]. </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 Discard Block. <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 Discard Block.<vspace
blankLines="1" /></t>
</list></t>
</section>
</section>
</section>
<section title="Application Layer Metrics">
<section anchor="ALDSS"
title="Application Layer Loss/Duplication Statistics Summary Block">
<t>This block reports statistics 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
recorded about lost frames ,duplicated frames, 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=TBD | |T|P| rsv. | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of frames expected |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| lost_full_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| lost_partial_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in Loss/Duplication Summary Statistics Block">
<t><list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace
blankLines="1" />Application Layer Loss/Duplication Statistics
Summary Bloc is identified by the constant <ALDSS>.
<vspace blankLines="1" /></t>
<t hangText="Picture type indicator (T): 1 bit"><vspace
blankLines="1" /> Picture types used in the different video
algorithms compose of key-frame and derivation frame. This field
is used to indicate the frame type to be reported. Bits set to 0
if the lost_frames field or dup_frames field contain a key_frame
report or reference frame report, 1 if the lost_frames field and
dup_frames field contain other derivation frame report. <vspace
blankLines="1" /></t>
<t hangText="P: 1 bit"><vspace blankLines="1" /> Bit set to 1 if
the partial_lost_frames field or the partial_dup_ frames field
contains a report, 0 otherwise. <vspace blankLines="1" /></t>
<t hangText="Rsv.: 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 MUST
be ignored by the receiver.<vspace blankLines="1" /></t>
<t hangText="Block length: 16 bits"><vspace blankLines="1" />
The constant 6, 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 expected:32bits"><vspace
blankLines="1" />A count of the number of frames expected,
estimated if necessary. If no frames have been received then
this count shall be set to Zero. <vspace blankLines="1" /></t>
<t hangText="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 lost_full_frames in the above
sequence number interval.<vspace blankLines="1" /></t>
<t hangText="dup_frames: 32 bits"><vspace blankLines="1" />
Number of dup_frames in the above sequence number interval.
<vspace blankLines="1" /></t>
<t hangText="lost_partial_frames: 32 bits"><vspace
blankLines="1" />If one frame is partially lost, this frame is
regarded as one lost fractional frame. The lost_partial_frames
is equivalent to the number of lost_partial_frames in the above
sequence number interval.<vspace blankLines="1" /></t>
</list></t>
</section>
</section>
</section>
<section title="SDP Signaling">
<t><xref target="RFC3611"></xref> 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>
<t>This section augments the SDP <xref target="RFC4566"></xref>
attribute "rtcp-xr" defined in <xref target="RFC3611"></xref> by
providing three additional value of "xr-format" to signal the use of the
report block defined in this document. </t>
<figure align="left">
<artwork>
rtcp-xr-attrib = "a=rtcp-xr:"
[xr-format *(SP xr-format)] CRLF
xr-format =
/ burst-gap-loss-stat
/ burst-gap-discard-stat
/ application-loss-dup-stat
</artwork>
</figure>
<t>Refer to Section 5.1 of RFC 3611 <xref target="RFC3611"></xref> for a
detailed description and the full syntax of the "rtcp-xr" attribute.
</t>
</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 values">
<t>This document assigns three new block type value in the RTCP XR
Block Type Registry: <figure>
<artwork>
Name: BGLSS
Long Name: Burst/Gap Loss Summsary Statistics Block
Value <BGLSS>
Reference: Section 5.1
Name: BGDSS
Long Name: Burst/Gap Discard Summary Statistics Block
Value <BGDSS>
Reference: Section 5.2
Name: ALDSS
Long Name: Application Layer Loss/Duplication Statistics Summary
Value <ALDSS>
Reference: Section 6.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
RTCP XR SDP Parameters Registry: <figure>
<artwork>
* " burst-gap-loss-stat "
* " burst-gap-discard-stat "
* "application-loss-dup-stat "
</artwork>
</figure></t>
</section>
<section title="Contact information for registrations">
<t>The contact information for the registrations is:</t>
<figure>
<artwork>
Glen Zorn
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10110
Thailand
</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 <xref
target="RFC3611"></xref>.</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 and Yinliang Hu
for their valuable comments and suggestions on this document.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="I-D.ietf-avt-rtp-svc">
<front>
<title>RTP Payload Format for Scalable Video Coding</title>
<author fullname="Stephan Wenger" initials="S" surname="Wenger">
<organization></organization>
</author>
<author fullname="Ye-Kui Wang" initials="Y" surname="Wang">
<organization></organization>
</author>
<author fullname="Thomas Schierl" initials="T" surname="Schierl">
<organization></organization>
</author>
<author fullname="Alex Eleftheriadis" initials="A"
surname="Eleftheriadis">
<organization></organization>
</author>
<date day="1" month="February" year="2011" />
<abstract>
<t>This memo describes an RTP payload format for Scalable Video
Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264,
which is technically identical to Amendment 3 of ISO/IEC
International Standard 14496-10. The RTP payload format allows for
packetization of one or more Network Abstraction Layer (NAL) units
in each RTP packet payload, as well as fragmentation of a NAL unit
in multiple RTP packets. Furthermore, it supports transmission of
an SVC stream over a single as well as multiple RTP sessions. The
payload format defines a new media subtype name "H264-SVC", but is
still backwards compatible to [I-D.ietf-avt-rtp-rfc3984bis] since
the base layer, when encapsulated in its own RTP stream, must use
the H.264 media subtype name ("H264") and the packetization method
specified in [I- D.ietf-avt-rtp-rfc3984bis]. The payload format
has wide applicability in videoconferencing, Internet video
streaming, and high bit-rate entertainment-quality video, among
others.Table of Contents</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-avt-rtp-svc-27" />
<format target="http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-svc-27.txt"
type="TXT" />
</reference>
&rfc2250;
&rfc3611;
&rfc2119;
&rfc4566;
&rfc5234;
&rfc3550;
<reference anchor="RFC3357">
<front>
<title>One-way Loss Pattern Sample Metrics</title>
<author fullname="R. Koodli" initials="R." surname="Koodli">
<organization></organization>
</author>
<author fullname="R. Ravikanth" initials="R." surname="Ravikanth">
<organization></organization>
</author>
<date month="August" year="2002" />
</front>
<seriesInfo name="RFC" value="3357" />
<format octets="30570"
target="http://www.rfc-editor.org/rfc/rfc3357.txt" type="TXT" />
</reference>
<reference anchor="MEASIDENT">
<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="2011" />
</front>
<seriesInfo name="ID"
value="draft-ietf-xrblock-rtcp-xr-meas-identity-01" />
<format type="TXT" />
</reference>
<reference anchor="DISCARD">
<front>
<title>RTCP XR Report Block for Discard metric Reporting </title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<date month="May" year="2009" />
</front>
<seriesInfo name="ID" value="draft-ietf-rtcp-xr-discard-02" />
<format type="TXT" />
</reference>
</references>
<references title="Informative References">
<reference anchor="DSLF">
<front>
<title>Triple-play Services Quality of Experience (QoE)
Requirements</title>
<author fullname="Tim Rahrer" initials="T.R." role="editor"
surname="Rahrer">
<organization>Nortel</organization>
<address>
<postal>
<street>3500 Carling Ave.</street>
<city>Ottawa</city>
<region>Ontario</region>
<country>Canada</country>
</postal>
<phone>+1.613.763.4479</phone>
<email>tim.rahrer@nortel.com</email>
</address>
</author>
<author fullname="Riccardo Fiandra" role="editor" surname="Fiandra">
<organization>FastWeb, SpA</organization>
<address>
<email>riccardo.fiandra@fastweb.it</email>
</address>
</author>
<author fullname="Steven Wright" role="editor" surname="Wright">
<organization>BellSouth Telecommunications</organization>
<address>
<email>steven.wright@bellsouth.com</email>
</address>
</author>
<date day="13" month="December" year="2006" />
</front>
<seriesInfo name="DSL Forum Technical Report" value="TR-126" />
</reference>
<reference anchor="MONARCH">
<front>
<title>Monitoring Architectures for RTP</title>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization>Huawei</organization>
</author>
<date month="April" year="2011" />
</front>
<seriesInfo name="ID" value="draft-ietf-avtcore-monarch-00" />
<format type="TXT" />
</reference>
<reference anchor="PMOL">
<front>
<title>Framework for Performance Metric Development</title>
<author fullname="Alan Clark " initials="A." surname="Clark">
<organization>Telchemy Incorporated</organization>
</author>
<date month="January" year="2011" />
</front>
<seriesInfo name="ID" value="draft-ietf-pmol-metrics-framework-08" />
<format type="TXT" />
</reference>
</references>
<section title="Change Log">
<t>This document is separated from
draft-wu-xrblock-rtcp-xr-quality-monitoring-01 with a few editorial
changes and focuses on loss,duplication, discard, and summary statistics
metrics. </t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 08:05:24 |