One document matched: draft-huang-xrblock-rtcp-xr-decodability-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-huang-xrblock-rtcp-xr-decodability-00"
ipr="pre5378Trust200902">
<front>
<title abbrev=" RTCP XR Decodability Report Blocks">RTCP XR Report Block
for TS Decodability Statistics Metric reporting</title>
<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>
<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="Hitoshi Asaeda" initials="H." surname="Asaeda">
<organization>Keio University</organization>
<address>
<postal>
<street>Graduate School of Media and Governance 5322 Endo</street>
<city>Fujisawa</city>
<region>Kanagawa</region>
<code>252-0882</code>
<country>Japan</country>
</postal>
<email>asaeda@wide.ad.jp</email>
</address>
</author>
<date year="2011" />
<abstract>
<t>This document defines an RTCP XR Report Block that allows the
reporting of Decodability Statistics Metric used for Transport
Stream.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This draft defines a new block type to augment those defined in <xref
target="RFC3611"></xref> for use in Transport Stream. The new block type
supports the reporting of consistency of Transport Stream <xref
target="ETSI"></xref>by checking TS header information. This new block
type can be useful for identifying the existence, and characterizing the
severity, of a packet transport problem which may affect users'
perception of a service delivered over RTP, also useful for Verifying
the continued correct operation of an existing system management and
providing accurate measures of Transport Stream quality for
operators.</t>
<t>The metric is applicable to any other types of RTP application that
use TS standard format for transmission and storage of audio, video, and
data.</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>
</section>
<section title="Acronyms">
<t><list style="hanging">
<t hangText="SSRC"><vspace blankLines="0" /> <xref
target="RFC3550">Synchronization Source</xref> <vspace
blankLines="1" /></t>
<t hangText="TS"><vspace blankLines="0" /> <xref
target="ISO-IEC.13818-1.2007">Transport Stream</xref></t>
</list></t>
</section>
</section>
<section anchor="TDM"
title="TR 101 290 Decodability Statistics Metric Report Block">
<t>This block reports decodability statistics metric beyond the
information carried in the standard RTCP packet format. Information is
recorded about basic monitoring parameters necessary to ensure that the
TS can be decoded including the number of Transport Stream
Synchronization Losses, Sync byte errors, Continuity count errors, and
continuous monitoring parameters including Transport errors, Program
Clock Reference (PCR) errors, PCR repetition errors, PCR discontinuity
indicator errors, and Presentation Time Stamp (PTS) errors <xref
target="ETSI"></xref>. Such information can be useful for network
management and real time application quality monitoring. <vspace
blankLines="1" />Note that this metric report block is not only
applicable to MPEG-2 transport streams<xref target="RFC2250"></xref>,but
also applicable to any other Transport Streams that adopt other audio
and video codec.<vspace blankLines="1" /> The Decodability Metrics 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 | rvd | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of packets | Number of TSs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transport Stream Synchronization Losses |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sync byte errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Continuity count errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transport errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR repetition errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR discontinuity indicator errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PTS errors |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure> <list style="hanging">
<t hangText="block type (BT): 8 bits"><vspace blankLines="0" /> A TR
101 290 decodability metrics report block is identified by the
constant <TDM>. <vspace blankLines="1" /></t>
<t hangText="rvd: 8 bits"><vspace blankLines="0" /> 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="0" /> The
constant 10, 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="0" /> As
defined in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
blankLines="1" /></t>
<t hangText="begin_seq: 16 bits"><vspace blankLines="0" /> As
defined in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
blankLines="1" /></t>
<t hangText="end_seq: 16 bits"><vspace blankLines="0" /> As defined
in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
blankLines="1" /></t>
<t hangText="Number of Packets: 16 bits"><vspace blankLines="0" />
Number of RTP packets in the above sequence number interval. <vspace
blankLines="1" /></t>
<t hangText="Number of TSs: 16 bits"><vspace blankLines="0" />
Number of Transport Streams in the above sequence number interval.
<vspace blankLines="1" /></t>
<t
hangText="Transport Stream Synchronization Losses: 32 bits"><vspace
blankLines="0" /> Number of Transport Stream Synchronization Losses
in the above sequence number interval. <vspace blankLines="1" /></t>
<t hangText="Sync byte errors: 32 bits"><vspace blankLines="0" />
Number of Transport sync byte errors in the above sequence number
interval.</t>
<t hangText="Continuity count error: 32 bits"><vspace
blankLines="0" /> Number of Transport Continuity count errors in the
above sequence number interval. <vspace blankLines="1" /></t>
<t hangText="Transport errors: 32 bits"><vspace blankLines="0" />
Number of Transport errors in the above sequence number interval.
<vspace blankLines="1" /></t>
<t hangText="PCR errors: 32 bits "><vspace blankLines="0" /> Number
of PCR errors in the above sequence number interval. <vspace
blankLines="1" /></t>
<t hangText="PCR repetition errors: 32 bits"><vspace
blankLines="0" /> Number of Transport PCR repetition errors in the
above sequence number interval. <vspace blankLines="1" /></t>
<t hangText="PCR discontinuity indicator errors: 32 bits"><vspace
blankLines="0" /> Number of PCR discontinuity indicator errors in
the above sequence number interval. <vspace blankLines="1" /></t>
<t hangText="PTS errors: 32 bits"><vspace blankLines="0" /> Number
of PTS errors in the above sequence number interval. <vspace
blankLines="1" /></t>
</list></t>
</section>
<section title="SDP Signaling">
<t>One new parameter is defined for the one 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 = decodability-metrics
decodability-metrics = "decodability-metrics"
</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 one new block type values in the RTCP XR Block Type
Registry: <list>
<t><list hangIndent="12" style="hanging">
<t hangText="Name:">TDM</t>
<t hangText="Long Name:">TR 101 290 Decodability Metrics</t>
<t hangText="Value"><TDM></t>
<t hangText="Reference:">section 3<vspace blankLines="1" /></t>
</list></t>
</list> This document also registers one SDP <xref
target="RFC4566"></xref> parameters for the "rtcp-xr" attribute in the
RTCP XR SDP Parameters Registry: <list>
<t><list style="symbols">
<t>“decodability-metrics”</t>
</list></t>
</list> <vspace blankLines="1" /> The contact information for the
registrations is: <figure align="center">
<artwork>
Rachel Huang
Rachel@huawei.com
101 Software Avenue, Yuhua District
Nanjing, JiangSu 210012 China
</artwork>
</figure></t>
</section>
<section title="Security Considerations">
<t>This proposed RTCP XR report block introduces no new security
considerations beyond those described in <xref
target="RFC3611"></xref>.</t>
</section>
</middle>
<back>
<references title="Normative References">
&rfc2250;
&rfc3611;
&rfc2119;
&rfc4566;
&rfc5234;
&rfc3550;
<reference anchor="ETSI">
<front>
<title>Digital Video Broadcasting (DVB); Measurement guidelines for
DVB systems</title>
<author>
<organization>ETSI</organization>
</author>
<date year="2001" />
</front>
<seriesInfo name="Technical Report" value="TR 101 290" />
</reference>
<reference anchor="ISO-IEC.13818-1.2007">
<front>
<title>Information technology - Generic coding of moving pictures
and associated audio information: Systems</title>
<author>
<organization>International Organization for
Standardization</organization>
</author>
<date month="October" year="2007" />
</front>
<seriesInfo name="ISO" value="International Standard 13818-1" />
</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="G.1082">
<front>
<title>Measurement-based methods for improving the robustness of
IPTV performance</title>
<author>
<organization>ITU-T</organization>
</author>
<date month="April" year="2009" />
</front>
<seriesInfo name="ITU-T Recommendation" value="G.1082" />
</reference>
<reference anchor="P.NAMS">
<front>
<title>Non-intrusive parametric model for the Assessment of
performance of Multimedia Streaming</title>
<author>
<organization>ITU-T</organization>
</author>
<date month="November" year="2009" />
</front>
<seriesInfo name="ITU-T Recommendation" value="P.NAMS" />
</reference>
<reference anchor="IEEE">
<front>
<title>Human Perception of Jitter and Media Synchronization</title>
<author>
<organization>IEEE</organization>
</author>
<date month="January" year="1996" />
</front>
<seriesInfo name="IEEE Journal on Selected Areas in Communications"
value="Vol. 14, No. 1" />
</reference>
<reference anchor="I-D.ietf-pmol-metrics-framework-02">
<front>
<title>Framework for Performance Metric Development</title>
<author fullname="Alan Clark " initials="A." surname="Clark">
<organization>Telchemy Incorporated</organization>
</author>
<date />
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 03:20:36 |