One document matched: draft-huang-xrblock-rtcp-xr-decodability-04.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-04"
     ipr="trust200902">
  <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.huang@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>bill.wu@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>

    <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, Bangkok</city>

          <code>10260</code>

          <country>Thailand</country>
        </postal>

        <phone>+66 (0) 87-040-4617</phone>

        <email>glenzorn@gmail.com</email>
      </address>
    </author>

    <date year="2012" />

    <abstract>
      <t>Transport Stream is a standard container format used in the
      transmission and storage of multimedia data. Unicast/Multicast/Broadcast
      MPEG-TS over RTP is widely adopted in the IPTV deployment. This document
      defines an RTCP XR Report Block that allows the reporting of
      decodability statistics metrics related to transmissions of MPEG-TS over
      RTP.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>This draft defines a new block type to augment those defined in
      [RFC3611] for use with Transport Stream (TS) <xref
      target="ISO-IEC.13818-1.2007"></xref>. The new block type supports
      reporting on the consistency of important elements in the transport
      stream. This new block type can be useful for measuring content stream
      or TS quality by checking TS header information <xref
      target="ETSI"></xref> and identifying the existence, and characterizing
      the severity, of bitstream packetization problem which may affect users'
      perception of a service delivered over RTP; it may also be useful for
      verifying the continued correct operation of an existing system
      management.</t>

      <t>The new report block is in compliance with the monitoring
      architecture specified in <xref target="MONARCH"></xref> and the
      Performance Metrics Framework <xref target="RFC6390"></xref>. The metric
      is applicable to any type of RTP application that uses TS standard
      format for container of multimedia data, for example MPEG4 TS content
      over RTP.</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>
      </section>
    </section>

    <section anchor="TDM"
             title="TR 101 290 Decodability Statistics Metric Report Block">
      <t>This block reports decodability statistics metrics beyond the
      information carried in the standard RTCP packet format. It defines eight
      metrics based on ETSI TR 101 290. ETSI TR 101 290 focuses on what kind
      of de-codability errors occur and specifies over 30 measurements split
      into three different priorities, depending on how drastically they
      affect content stream<xref target="ETSI"></xref> . The parameters from
      priority 1 or 2 are either considered necessary to ensure decodability
      or recommended for continuous monitoring. The parameters from priority 3
      are not applied to every MPEG-TS implememtation and regarded as
      application dependent monitoring specific. However ETSI TR_101_290 does
      not specify how many de-codability errrors happen when the client
      receives a sequence of consecutive RTP packets. The metrics defined in
      this block are used to deal with this issue. It accommodates three basic
      monitoring parameters in priority 1 to ensure that the TS can be decoded
      and report the number of TS_sync_losses, Sync_byte_errors,
      Continuity_count_errors; It also accommodates 5 continuous monitoring
      parameters in priority 2 and report the number of Transport_errors,
      PCR_errors, PCR_repetition_errors, PCR_discontinuity_indicator_errors,
      and PTS_errors <xref target="ETSI"></xref>. The other parameters are
      ignored since they are not applied to all the MPEG implantations.
      <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 TSs                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      TS_sync_loss_count                       |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      Sync_byte_error_count                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                  Continuity_count_error_count                 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      Transport_error_count                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                        PCR_error_count                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   PCR_repetition_error_count                  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|            PCR_discontinuity_indicator_error_count            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                       PTS_error_count                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </figure> <list style="hanging">
          <t hangText="block type (BT): 8 bits"><vspace blankLines="1" /> 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="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 11, 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"></xref>. <vspace
          blankLines="1" /></t>

          <t hangText="begin_seq: 16 bits"><vspace blankLines="1" /> As
          defined in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
          blankLines="1" /></t>

          <t hangText="end_seq: 16 bits"><vspace blankLines="1" /> As defined
          in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
          blankLines="1" /></t>

          <t hangText="Number of TSs: 32 bits"><vspace blankLines="1" />
          Number of TS in the above sequence number interval. <vspace
          blankLines="1" /></t>

          <t hangText="TS_sync_loss_count: 32 bits"><vspace blankLines="1" />
          Number of TS_sync_loss errors in the above sequence number interval.
          <vspace blankLines="1" /></t>

          <t hangText="Sync_byte_error_count: 32 bits"><vspace
          blankLines="1" /> Number of sync_byte_errors in the above sequence
          number interval.<vspace blankLines="1" /></t>

          <t hangText="Continuity_count_error_count: 32 bits"><vspace
          blankLines="1" /> Number of Continuity_count_errors in the above
          sequence number interval. <vspace blankLines="1" /></t>

          <t hangText="Transport_error_count: 32 bits"><vspace
          blankLines="1" /> Number of Transport_errors in the above sequence
          number interval. <vspace blankLines="1" /></t>

          <t hangText="PCR_error_count: 32 bits "><vspace blankLines="1" />
          Number of PCR_errors in the above sequence number interval. <vspace
          blankLines="1" /></t>

          <t hangText="PCR_repetition_error_count: 32 bits"><vspace
          blankLines="1" /> Number of PCR_repetition_errors in the above
          sequence number interval. <vspace blankLines="1" /></t>

          <t
          hangText="PCR_discontinuity_indicator_error_count: 32 bits"><vspace
          blankLines="1" /> Number of PCR_discontinuity_indicator_errors in
          the above sequence number interval. <vspace blankLines="1" /></t>

          <t hangText="PTS_error_count: 32 bits"><vspace blankLines="1" />
          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 report block 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>. It has 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 value 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 Parameter 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.huang@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="MONARCH">
        <front>
          <title>Monitoring Architectures for RTP</title>

          <author fullname="Qin Wu" initials="Q." surname="Wu">
            <organization></organization>
          </author>

          <author fullname="Geoff Hunt" initials="G." surname="Hunt">
            <organization></organization>
          </author>

          <author fullname="Philip Arden" initials="P.">
            <organization></organization>
          </author>

          <date month="June" year="2012" />
        </front>

        <seriesInfo name="ID" value="draft-ietf-avtcore-monarch-17" />

        <format type="TXT" />
      </reference>

      <reference anchor="RFC6390">
        <front>
          <title>Guidelines for Considering New Performance Metric
          Development</title>

          <author fullname="Alan Clark " initials="A." surname="Clark">
            <organization>Telchemy Incorporated</organization>
          </author>

          <author fullname="Benoit Claise " initials="B." surname="Claise">
            <organization abbrev="Cisco Systems, Inc."></organization>

            <address>
              <postal>
                <street>De Kleetlaan 6a b1</street>

                <city>Diegem</city>

                <code>1831</code>

                <country>Belgium</country>
              </postal>

              <phone>+32 2 704 5622</phone>

              <email>bclaise@cisco.com</email>
            </address>
          </author>

          <date month="October" year="2011" />
        </front>

        <seriesInfo name="BCP" value="170" />

        <seriesInfo name="RFC" value="6390" />
      </reference>
    </references>
  </back>
</rfc>