One document matched: draft-zorn-xrblock-rtcp-xr-al-stat-00.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-00"
ipr="pre5378Trust200902">
<front>
<title abbrev="Application Layer Statistics Blocks">RTCP XR for
Application Layer 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 an RTCP XR Report Block and associated SDP
parameters that allows the reporting of application layer summary, loss
discard and burst 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 video related parameters at application layer that are genericly
designed for use in voice, audio and video services. <vspace
blankLines="1" />The metrics belong to the class of transport level
metrics defined in <xref target="MONARCH"></xref> (work in
progress).</t>
</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="Applicability">
<t>The Metric Block defined in this document can be applied to any real
time applications that convey video related parameters at application
layer.</t>
</section>
<section title="Application Layer Metrics">
<section anchor="ALSS"
title="Application Layer Statistics Summary Report 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 <xref target="RFC3611">RFC 3611</xref>. Information is recorded
about lost frame packets, duplicated frame packets, lost layered
component packets, duplicated layered component packets. Such
information can be useful for network management and video quality
monitoring. <vspace blankLines="1" /> The report block contents are
dependent upon a series of flag bits carried in the first part of the
header. Not all parameters need to be reported in each block. Flags
indicate which parameters are reported and which are not. The fields
corresponding to unreported parameters MUST be present, but are set to
zero. The receiver MUST ignore any Video Statistics Summary Report
Block with a non-zero value in any field flagged as unreported.
<vspace blankLines="1" /> The Application Layer Statistics Summary
Report Block has the following format: <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| tag |T|P|rsd| block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dup frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| partial_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| partial_dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| key frames impairement proportion |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure> <list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace blankLines="1" />
The Application Layer Statistics Summary Report Block is
identified by the constant <ALSS>. <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="Measurement Identifier association (tag): 3 bits"><vspace
blankLines="1" />This field is used to identify the Measurement
Identifier block <xref target="MEASIDENT"></xref> which describes
this measurement. <vspace blankLines="1" /></t>
<t hangText="Picture type indicator (T): 1 bits"><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="Rsd.: 2 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 5, in accordance with the definition of this field in
Section 3 of <xref target="RFC3611">RFC 3611</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="lost_frames: 32 bits"><vspace blankLines="1" />
Number of lost_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="partial lost_frames: 32 bits"><vspace
blankLines="1" />Number of partial lost_frames in the above
sequence number interval. <vspace blankLines="1" /></t>
<t hangText="partial dup_frames: 32 bits"><vspace
blankLines="1" />Number of partial_dup_frames in the above
sequence number interval. <vspace blankLines="1" /></t>
<t hangText="key frames impairment proportion:32bits"><vspace
blankLines="1" />The proportion of key frame impaired by packet
loss,discard and duplication.<vspace blankLines="1" /></t>
</list></t>
</section>
<section anchor="ALLDM"
title="Application Layer Loss and Discard Metrics Block">
<t>This block reports Loss and Discard metrics statistics beyond the
information carried in the standard RTCP packet format. The block
reports separately on packets lost on the IP channel, and those that
have been received but then discarded by the receiving jitter buffer.
<vspace blankLines="1" />It is very useful to distinguish between
packets lost by the network and those discarded due to jitter. Both
have equal effect on the quality of the video stream, however, having
separate counts helps identify the source of quality degradation.
These fields MUST be populated, and MUST be set to zero if no packets
have been received. <vspace blankLines="1" /> Implementations MUST
provide values for all the fields defined here. For certain metrics,
if the value is undefined or unknown, then the specified default or
unknown field value MUST be provided.<vspace blankLines="1" />The
block is encoded as six 32-bit words: <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| tag |T| rsv.| block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss rate | Discard rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure><list style="hanging">
<t hangText="block type (BT): 8 bits"><vspace blankLines="1" /> A
Application Layer Metrics Report Block is identified by the
constant <ALLDM>. <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="Measurement Identifier association (tag): 3 bits"><vspace
blankLines="1" />This field is used to identify the Measurement
Identifier block <xref target="MEASIDENT"></xref> which describes
this measurement. <vspace blankLines="1" /></t>
<t hangText="Picture type indicator (T): 1 bits"><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 picture type to be reported. Bits set to 0
if the Loss rate field and discard rate field contain a Key_frame
report or reference frame report, 1 if the Loss rate field and
discard rate field contain other derivation frame reports. <vspace
blankLines="1" /></t>
<t hangText="reserved: 3 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 1, in accordance with the definition of this field in
Section 3 of <xref target="RFC3611">RFC 3611</xref>. <vspace
blankLines="1" /></t>
<t hangText="Loss rate: 8 bits"><vspace blankLines="1" /> The
fraction of RTP data packets from the source lost 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 total number of lost packets containing
specified frame (e.g., Key frame) (after the effects of applying
any error protection such as FEC) by the total number of packets
expected, multiplying the result of the division by 256, limiting
the maximum value to 255 (to avoid overflow), and taking the
integer part. The numbers of duplicated packets and discarded
packets do not enter into this calculation. Since receivers cannot
be required to maintain unlimited buffers, a receiver MAY
categorize late-arriving packets as lost. The degree of lateness
that triggers a loss SHOULD be significantly greater than that
which triggers a discard.<vspace blankLines="1" /></t>
<t hangText="Discard rate: 8 bits"><vspace blankLines="1" /> The
fraction of RTP data packets from the source that have been
discarded since the beginning of reception, due to late or early
arrival, under-run or overflow at the receiving jitter buffer.
This value is expressed as a fixed point number with the binary
point at the left edge of the field. It is calculated by dividing
the total number of discarded packets containing specified frame
(e.g., Key Frame) (excluding duplicate packet discards) by the
total number of packets expected, multiplying the result of the
division by 256, limiting the maximum value to 255 (to avoid
overflow), and taking the integer part.<vspace
blankLines="1" /></t>
</list></t>
</section>
<section anchor="ALBM" title="Application Layer Burst Metrics Block">
<t>This block reports Burst metrics statistics beyond the information
carried in the standard RTCP packet format. It reports on the combined
effect of losses and discards, as both have equal effect on video
quality. <vspace blankLines="1" /> In order to properly assess the
quality of a video stream, it is desirable to consider the degree of
burstiness of packet loss <xref target="RFC3357">RFC 3357</xref>.
Following the one-way loss pattern sample metrics discussed in <xref
target="RFC3357"></xref>, a measure of the spacing between consecutive
network packet loss or error events, is a "loss distance". The loss
distance metric captures the spacing between the loss periods. The
duration of a loss or error event (e.g. and how many packets are lost
in that duration) is a "loss period", the loss period metric captures
the frequency and length (burstiness) of loss once it starts. Delay
reports include the transit delay between RTP end points and the end
system processing delays, both of which contribute to the user
perceived delay. <vspace blankLines="1" />Implementations MUST provide
values for all the fields defined here. For certain metrics, if the
value is undefined or unknown, then the specified default or unknown
field value MUST be provided. <vspace blankLines="1" />The block is
encoded as three 32-bit words: <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| tag | Rsv. | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Distance | Loss Period |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Loss Duration | Reserved. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure><list style="hanging">
<t hangText="block type (BT): 8 bits"><vspace blankLines="1" />
Appliation Layer Metrics Report Block is identified by the
constant <ALBM>. <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="Measurement Identifier association (tag): 3 bits"><vspace
blankLines="1" />This field is used to identify the Measurement
Identifier block <xref target="MEASIDENT"></xref> which describes
this measurement. <vspace blankLines="1" /></t>
<t hangText="reserved: 4 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="Loss Distance: 16 bits"><vspace blankLines="1" /> The
mean duration, expressed in milliseconds, of the loss intervals
that have occurred since the beginning of reception <xref
target="DSLF"></xref>. The duration of each loss distance is
calculated based upon the frames that mark the beginning and end
of that period. It is equal to the timestamp of the end frame,
plus the duration of the end frame, minus the timestamp of the
beginning frame. If the actual values are not available, estimated
values MUST be used. If there have been no burst periods, the
burst duration value MUST be zero. <vspace blankLines="1" /></t>
<t hangText="Loss Period: 16 bits"><vspace blankLines="1" /> The
mean duration, expressed in milliseconds, of the burst loss
periods that have occurred since the beginning of reception <xref
target="DSLF"></xref>. The duration of each period is calculated
based upon the frame that marks the end of the prior burst loss
and the frame that marks the beginning of the subsequent burst
loss. It is equal to the timestamp of the subsequent burst frame,
minus the timestamp of the prior burst packet, plus the duration
of the prior burst packet. If the actual values are not available,
estimated values MUST be used. In the case of a gap that occurs at
the beginning of reception, the sum of the timestamp of the prior
burst packet and the duration of the prior burst packet are
replaced by the reception start time. In the case of a gap that
occurs at the end of reception, the timestamp of the subsequent
burst packet is replaced by the reception end time. If there have
been no gap periods, the gap duration value MUST be zero. <vspace
blankLines="1" /></t>
<t hangText="Max Loss Duration of a single error: 16 bits"><vspace
blankLines="1" /> The maximum loss duration, expressed in
milliseconds, of the loss periods that have occurred since the
beginning of reception. The recommended max loss duration is
specified as less than 16 ms in <xref target="DSLF"></xref>, which
provides a balance between interleaver depth protection from xDSL
errors induced by impulse noise, delay added to other applications
and video service QoE requirements to reduce visible
impairments.<vspace blankLines="1" /></t>
<t hangText="Reserved: 16 bits"><vspace blankLines="1" />All bits
SHALL be set to 0 by the sender and SHALL be ignored on
reception.<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>
</list></t>
</section>
</section>
<section title="SDP Signaling">
<t>Three new parameter is defined for the six report blocks defined in
this document to be used with Session Description Protocol (SDP) <xref
target="RFC4566"></xref> using the Augmented Backus-Naur Form (ABNF)
<xref target="RFC5234"></xref>. They have the following syntax within
the "rtcp-xr" attribute <xref target="RFC3611"></xref>: <figure
align="left">
<artwork>
rtcp-xr-attrib = "a=rtcp-xr:"
[xr-format *(SP xr-format)] CRLF
xr-format =
/ application-loss-metrics
/ application-burst-metrics
/ application-stat-summary
application-burst-metrics = " application-burst-metrics"
["=" max-size]
max-size = 1*DIGIT ; maximum block size in octets
application--loss-metrics = " application-loss-metrics"
["=" stat-flag *("," stat-flag)]
stat-flag = "key Frame loss and duplication"
/ "derivation Frame loss and duplication"
application-stat-summary = "application-stat-summary"
["=" stat-flag *("," stat-flag)]
stat-flag = "key Frame loss and duplication"
/ "derivation Frame loss and duplication"
</artwork>
</figure> Refer to Section 5.1 of <xref target="RFC3611">RFC
3611</xref> for a detailed description and the full syntax of the
"rtcp-xr" attribute.</t>
</section>
<section title="IANA Considerations">
<t>New report block types for RTCP XR are subject to IANA registration.
For general guidelines on IANA allocations for RTCP XR, refer to <xref
target="RFC3611">Section 6.2 of</xref>. <vspace blankLines="1" /> This
document assigns three new block type value in the RTCP XR Block Type
Registry: <list>
<t><list>
<t><list hangIndent="12" style="hanging">
<t hangText="Name:">ALSS</t>
<t hangText="Long Name:">Application Layer Statistics
Summary</t>
<t hangText="Value"><ALSS></t>
<t hangText="Reference:"><xref target="ALSS"></xref> <vspace
blankLines="1" /></t>
<t hangText="Name:">ALLDM</t>
<t hangText="Long Name:">Application Layer Loss and Discard
Metrics</t>
<t hangText="Value"><ALLDM></t>
<t hangText="Reference:"><xref target="ALLDM"></xref>
<vspace blankLines="1" /></t>
<t hangText="Name:">ALBM</t>
<t hangText="Long Name:">Application Layer Burst Metrics</t>
<t hangText="Value"><ALBM></t>
<t hangText="Reference:"><xref target="ALBM"></xref></t>
</list></t>
</list></t>
</list> This document also registers three new SDP <xref
target="RFC4566"></xref> parameters for the "rtcp-xr" attribute in the
RTCP XR SDP Parameters Registry: <list>
<t><list style="symbols">
<t>"application-layer-loss-metrics"</t>
<t>"application-layer -burst-metrics"</t>
<t>"application-layer -stat-summary"</t>
</list></t>
</list> <vspace blankLines="1" /> The contact information for the
registrations is: <figure align="center">
<artwork>
Qin Wu
sunseawq@huawei.com
101 Software Avenue, Yuhua District
Nanjing, JiangSu 210012 China
</artwork>
</figure></t>
</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="RFC6051">
<front>
<title>Rapid Synchronisation of RTP Flows</title>
<author fullname="Colin Perkins" initials="C." surname="Perkins">
<organization></organization>
</author>
<author fullname="Thomas Schierl" initials="T" surname="Schierl">
<organization></organization>
</author>
<date day="10" month="November" year="2010" />
<abstract>
<t>This memo outlines how RTP sessions are synchronised, and
discusses how rapidly such synchronisation can occur. We show that
most RTP sessions can be synchronised immediately, but that the
use of video switching multipoint conference units (MCUs) or large
source specific multicast (SSM) groups can greatly increase the
synchronisation delay. This increase in delay can be unacceptable
to some applications that use layered and/or multi-description
codecs. This memo introduces three mechanisms to reduce the
synchronisation delay for such sessions. First, it updates the RTP
Control Protocol (RTCP) timing rules to reduce the initial
synchronisation delay for SSM sessions. Second, a new feedback
packet is defined for use with the Extended RTP Profile for
RTCP-based Feedback (RTP/AVPF), allowing video switching MCUs to
rapidly request resynchronisation. Finally, new RTP header
extensions are defined to allow rapid synchronisation of late
joiners, and guarantee correct timestamp based decoding order
recovery for layered codecs in the presence of clock skew.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6051" />
<format target="http://tools.ietf.org/html/rfc6051" type="TXT" />
</reference>
<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>
</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>
<reference anchor="MEASIDENT">
<front>
<title>RTCP XR Measurement Identifier Block</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization>Telchemy</organization>
</author>
<date month="May" year="2009" />
</front>
<seriesInfo name="ID" value="draft-ietf-avt-rtcp-xr-meas-identity-02" />
<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 application layer summary, loss, discard, and
burst metrics.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 08:07:45 |