<?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 rfc3357 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3357.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 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-bi-xrblock-rtcp-xr-psi-dep-decodability-03"
     ipr="trust200902">
  <front>
    <title abbrev=" RTCP XR TS Decodability">RTP Control Protocol (RTCP)
    Extended Report (XR) Block for MPEG2 Transport Stream (TS) Program
    Specific Information (PSI) Decodability Statistics Metrics
    reporting</title>

    <author fullname="Jiangang Tong" initials="J." surname="Tong">
      <organization abbrev="China Telecom">Shanghai Research Institure of
      China Telecom Corporation Limited</organization>

      <address>
        <postal>
          <street>No.1835,South Pudong Road</street>

          <city>Shanghai</city>

          <code>200122</code>

          <country>China</country>
        </postal>

        <email>tongjg@sttri.com.cn</email>
      </address>
    </author>

    <author fullname="Claire Bi" initials="C." surname="Bi">
      <organization abbrev="China Telecom">Shanghai Research Institure of
      China Telecom Corporation Limited</organization>

      <address>
        <postal>
          <street>No.1835,South Pudong Road</street>

          <city>Shanghai</city>

          <code>200122</code>

          <country>China</country>
        </postal>

        <email>bijy@sttri.com.cn</email>
      </address>
    </author>

    <author fullname="Roni Even" initials="R." surname="Even">
      <organization>Gesher Erove Ltd</organization>

      <address>
        <postal>
          <street>14 David Hamelech</street>

          <city>Tel Aviv</city>

          <code>64953</code>

          <country>Israel</country>
        </postal>

        <email>ron.even.tlv@gmail.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="Rachel Huang" initials="R." surname="Huang">
      <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>rachel.huang@huawei.com</email>
      </address>
    </author>

    <date year="2013" />

    <abstract>
      <t>An MPEG2 Transport Stream (TS) is a standard container format used in
      the transmission and storage of multimedia data. Unicast/Multicast MPEG2
      TS over RTP is widely deployed in IPTV systems. This document defines an
      RTP Control Protocol (RTCP) Extended Report (XR) Block that allows the
      reporting of MPEG2 TS decodability statistics metrics related to
      transmissions of MPEG2 TS over RTP. The metrics specified in the RTCP XR
      Block are related to Program specific information carried in MPEG
      TS.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <section title="MPEG2 Transport Stream Decodability Metrics">
        <t>The European Telecommunications Standards Institute (ETSI) has
        defined a set of syntax and information consistency tests and
        corresponding indicators <xref target="ETSI"></xref> that are
        recommended for the monitoring of MPEG2 Transport Streams <xref
        target="ISO-IEC.13818-1.2007"></xref>. The tests and corresponding
        indicators are grouped according to priority: <vspace
        blankLines="1" /><list style="symbols">
            <t>First priority - Necessary for decodability (basic
            monitoring)</t>

            <t>Second priority - Recommended for continuous or periodic
            monitoring</t>

            <t>Third priority - Recommended for application-dependent
            monitoring</t>
          </list></t>

        <t>This memo is based on information consistency tests and resulting
        indicators defined by ETSI <xref target="ETSI"></xref> and defines a
        new block type to augment those defined in Freidman, et al. <xref
        target="RFC3611"></xref> for use with MPEG2 Transport Stream (TS)
        <xref target="ISO-IEC.13818-1.2007"></xref>. The new block type
        supports reporting of the number of occurrences of each Program
        Specific Information (PSI) indicator in the first and second
        priorities that supplements information from PSI independent
        Decodability Statistics Metrics Block [PIDCB]; third priority
        indicators are not supported.</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 Performance Metrics Framework [RFC6390] provides guidance on
        the definition and specification of performance metrics. The RTP
        Monitoring Architectures <xref target="RFC6792"></xref> provides
        guideline for reporting block format using RTCP XR. The new report
        block described in this memo is in compliance with the monitoring
        architecture specified in <xref target="RFC6792"></xref> and the
        Performance Metrics Framework <xref target="RFC6390"></xref>.</t>
      </section>

      <section title="Applicability">
        <t>These metrics are applicable to any type of RTP application that
        uses the MPEG2 TS standard format for multimedia data; for example,
        MPEG4 over MPEG2 TS over RTP. 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 problems
        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 tool.</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>
      </section>
    </section>

    <section anchor="TDM"
             title="MPEG2 TS PSI Decodability Statistics Metrics Block">
      <t>ETSI TR 101290 <xref target="ETSI"></xref> generally defines metrics
      related to error events while this document contains counts of those
      metrics defined in [ETSI]. The block defined in this document reports
      MPEG2 TS PSI decodability statistics metrics beyond the information
      carried in the standard RTCP packet format and PSI independent
      Decodability Metrics Block[PIDCB], which are measured at the receiving
      end of the RTP stream. It contains counts of six metrics defined in ETSI
      TR 101290 <xref target="ETSI"></xref>. Information is reported about
      basic monitoring parameters necessary to ensure that the TS can be
      decoded including: <vspace blankLines="1" /> <list style="symbols">
          <t>Program Association Table(PAT) errors</t>

          <t>PAT 2 errors</t>

          <t>Program Map Table(PMT) errors</t>

          <t>PMT 2 errors</t>

          <t>Packet Identifier(PID) errors<vspace blankLines="1" /></t>
        </list> and continuous monitoring parameters necessary to ensure the
      continuous decoding including: <vspace blankLines="1" /> <list
          style="symbols">
          <t>Cyclic Redundancy Check (CRC) errors</t>

          <t>Conditional Access Table (CAT) errors<vspace
          blankLines="1" /></t>
        </list>The other parameters are ignored since they do not apply to all
      MPEG2 implementations. For further information on these parameters, see
      <xref target="ETSI"></xref>. <vspace blankLines="1" />The MPEG2 TS PSI
      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=MTPD    |    Reserved   |         block length          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     SSRC of source                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          begin_seq            |             end_seq           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       PAT_error_count                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       PAT_error_2_count                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        PMT_error_count                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        PMT_error_2_count                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         PID_error_count                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         CRC_error_count                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         CAT_error_count                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </figure> <list style="hanging">
          <t hangText="block type (BT): 8 bits"><vspace blankLines="1" />The
          MPEG2 TS PSI Decodability Metrics Block is identified by the
          constant &lt;MTPD&gt;. <vspace blankLines="1" /></t>

          <t hangText="Reserved: 8 bits"><vspace blankLines="1" />These bits
          are reserved. They MUST be set to zero by senders ignored by
          receivers (See <xref target="RFC6709"></xref> section 4.2). <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 RFC 3611. The block MUST be discarded if the block
          length is set to a different value.<vspace blankLines="1" /></t>

          <t hangText="SSRC of source: 32 bits"><vspace blankLines="1" />As
          defined in Section 4.1 of RFC 3611. <vspace blankLines="1" /></t>

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

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

          <t hangText="PAT_error_count: 32 bits"><vspace blankLines="1" />A
          count of the number of PAT errors that occurred in the above
          sequence number interval. The program association table (PAT) is the
          only packet with packet ID (PID) 0x 0000. A PAT error occurs when it
          does not occur at least every 0.5s or the table has an ID other than
          0x 00, as defined in section 5.2.1 of [ETSI]. Every program within
          the MPEG TS stream is listed in the PAT; if it is missing, then no
          programs can be decoded. <vspace blankLines="1" />The measured value
          is unsigned value. If the measurement is unavailable, the value
          0xFFFF MUST be reported. Note that PAT_error_count and
          PAT_error_2_count MUST NOT be reported at the same time in the same
          metric block. If PAT_error_count is reported, PAT_error_2_count MUST
          be set to 0xFFFF. <vspace blankLines="1" /></t>

          <t hangText="PAT_error_2_count: 32 bits"><vspace blankLines="1" />A
          count of the number of PAT2 errors that occurred in the above
          sequence number interval. A PAT2 error occurs when it does not occur
          at least every 0.5s or the table has an ID other than 0x 00 or there
          is more than one table ID 0x 00 inside the packet with the PAT PID,
          as defined in section 5.2.1 of [ETSI]. <vspace blankLines="1" />The
          measured value is unsigned value. If the measurement is unavailable,
          the value 0xFFFF MUST be reported. Note that PAT_error_count and
          PAT_error_2_count MUST NOT be reported at the same time in the same
          metric block. If PAT_error_2_count is reported, PAT_error_count MUST
          be set to 0xFFFF. <vspace blankLines="1" /></t>

          <t hangText="PMT_error_count: 32 bits"><vspace blankLines="1" />A
          count of the number of PMT_errors that occurred in the above
          sequence number interval. A PMT_error occurs when the program map
          table (PMT) does not come up at least every 0.5s on the PID that is
          referred to in the PAT, as defined in the section 5.2.1 of [ETSI].
          <vspace blankLines="1" />The measured value is unsigned value. If
          the measurement is unavailable, the value 0xFFFF MUST be reported.
          Note that PMT_error_count and PMT_error_2_count MUST NOT be reported
          at the same time in the same metric block. If PMT_error_count is
          reported, PMT_error_2_count MUST be set to 0xFFFF. <vspace
          blankLines="1" /></t>

          <t hangText="PMT_error_2_count: 32 bits"><vspace blankLines="1" />A
          count of the number of PMT2 errors that occurred in the above
          sequence number interval. A PMT2_error occurs when the program map
          table (PMT) does not come up at least every 0.5s on the PID that is
          referred to in the PAT, as defined in the section 5.2.1 of [ETSI].
          <vspace blankLines="1" />The measured value is unsigned value. If
          the measurement is unavailable, the value 0xFFFF MUST be reported.
          Note that PMT_error_count and PMT_error_2_count MUST NOT be reported
          at the same time in the same metric block. If PMT_error_2_count is
          reported, PMT_error_count MUST be set to 0xFFFF. <vspace
          blankLines="1" /></t>

          <t hangText="PID_error_count: 32 bits"><vspace blankLines="1" />A
          count of the number of PID_errors that occurred in the above
          sequence number interval. A PID_error occurs when MPEG TS streams
          are remultiplexed and any PID doesn’t refer to an actual data
          stream, as defined in the section 5.2.2 of [ETSI]. <vspace
          blankLines="1" /></t>

          <t hangText="CRC_error_count: 32 bits"><vspace blankLines="1" />A
          count of the number of CRC_errors that occurred in the above
          sequence number interval. A CRC_error occurs if data corruption
          occurred in any of the following tables — CAT, PAT, PMT, Network
          Information Table(NIT), Event Information Table(EIT), Bouquet
          Association Table(BAT), Service Description Table(SDT) or Time
          Offset Table(TOT), as defined in the section 5.2.2 of [ETSI].
          <vspace blankLines="1" /></t>

          <t hangText="CAT_error_count: 32 bits"><vspace blankLines="1" />A
          count of the number of CAT_errors that occurred in the above
          sequence number interval. A CAT_error occurs when the table has an
          ID other than 0x 01,as defined in the section 5.2.2 of [ETSI].
          <vspace blankLines="1" /></t>
        </list></t>
    </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 RTCP 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 session augments the SDP attribute "rtcp-xr" defined in
        Section 5.1 of RFC 3611 by providing an additional value of
        "xr-format" to signal the use of the report block defined in this
        document.<figure>
            <artwork>
xr-format =/  xr-tpd-block

xr-tpdd-block = "ts-psi-decodability"
</artwork>
          </figure></t>
      </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 report block types for RTCP XR are subject to IANA registration.
      For general guidelines on IANA allocations for RTCP XR, refer to Section
      6.2 of RFC 3611.</t>

      <section title="New RTCP XR Block Type value">
        <t>This document assigns the block type value MTPD in the IANA " RTP
        Control Protocol Extended Reports (RTCP XR) Block Type Registry " to
        the "MPEG2 Transport Stream PSI Decodability Statistics Metrics
        Block".</t>

        <t>[Note to RFC Editor: please replace MTPD with the IANA provided
        RTCP XR block type for this block.]</t>
      </section>

      <section title="New RTCP XR SDP Parameter">
        <t>This document also registers a new parameter "ts-psi-decodability"
        in the "RTP Control Protocol Extended Reports (RTCP XR) Session
        Description Protocol (SDP) Parameters Registry".</t>
      </section>

      <section title="Contact information for registrations">
        <t>The contact information for the registrations is:</t>

        <figure align="center">
          <artwork>
Qin Wu
sunseawq@huawei.com
101 Software Avenue, Yuhua District 
Nanjing, JiangSu 210012 China
</artwork>
        </figure>
      </section>
    </section>

    <section title="Security Considerations">
      <t>This proposed RTCP XR report block introduces no new security
      considerations beyond those described in RFC 3611.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <reference anchor="RFC3550">
        <front>
          <title>RTP: A Transport Protocol for Real-Time Applications</title>

          <author fullname="Henning Schulzrinne" initials="H."
                  surname="Schulzrinne">
            <organization>Columbia University</organization>
          </author>

          <date month="July" year="2003" />
        </front>

        <seriesInfo name="RFC" value="3550" />

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

      &rfc3611;

      &rfc2119;

      &rfc4566;

      <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>
    </references>

    <references title="Informative References">
      <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>

      <reference anchor="RFC6792">
        <front>
          <title>Guidelines for Use of the RTP Monitoring Framework</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." surname="Arden">
            <organization></organization>
          </author>

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

        <seriesInfo name="RFC" value="6792" />

        <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>

      <reference anchor="PIDCB">
        <front>
          <title>RTP Control Protocol (RTCP) Extended Report (XR) Block for
          MPEG2 Transport Stream (TS) Program Specific Information (PSI)
          Independent Decodability Statistics Metrics reporting</title>

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

          <date month="May" year="2013" />
        </front>

        <seriesInfo name="ID" value="ietf-xrblock-rtcp-xr-decodability-12" />
      </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>
  </back>
</rfc>
