draft-ietf-xrblock-rtcp-xr-psi-decodability-07.txt   rfc7380.txt 
Network Working Group J. Tong Internet Engineering Task Force (IETF) J. Tong
Internet-Draft C. Bi, Ed. Request for Comments: 7380 C. Bi, Ed.
Intended status: Standards Track China Telecom Category: Standards Track China Telecom
Expires: February 11, 2015 R. Even ISSN: 2070-1721 R. Even
Gesher Erove Ltd
Q. Wu, Ed. Q. Wu, Ed.
R. Huang R. Huang
Huawei Huawei
August 10, 2014 November 2014
RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2
Transport Stream (TS) Program Specific Information (PSI) Decodability Transport Stream (TS) Program Specific Information (PSI) Decodability
Statistics Metrics reporting Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-psi-decodability-07
Abstract Abstract
An MPEG2 Transport Stream (TS) is a standard container format used in An MPEG2 Transport Stream (TS) is a standard container format used in
the transmission and storage of multimedia data. Unicast/Multicast the transmission and storage of multimedia data. Unicast/multicast
MPEG2 TS over RTP is widely deployed in IPTV systems. This document MPEG2 TS over RTP is widely deployed in IPTV systems. This document
defines an RTP Control Protocol (RTCP) Extended Report (XR) Block defines an RTP Control Protocol (RTCP) Extended Report (XR) block
that allows the reporting of MPEG2 TS decodability statistics metrics that allows the reporting of MPEG2 TS decodability statistics metrics
related to transmissions of MPEG2 TS over RTP. The metrics specified related to transmissions of MPEG2 TS over RTP. The metrics specified
in the RTCP XR Block are related to Program Specific Information in the RTCP XR block are related to Program Specific Information
carried in MPEG TS. (PSI) carried in MPEG TS.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on February 11, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7380.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................3
1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 2 1.1. MPEG2 Transport Stream Decodability Metrics ................3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports ...................................3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework ..............................3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability ..............................................3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology .....................................................4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language .........................................4
3. MPEG2 TS PSI Decodability Statistics Metrics Block . . . . . 4 3. MPEG2 TS PSI Decodability Statistics Metrics Block ..............4
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 4. SDP Signaling ...................................................8
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 8 4.1. SDP rtcp-xr-attrib Attribute Extension .....................8
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 8 4.2. Offer/Answer Usage .........................................8
4.3. Usage Outside of Offer/Answer . . . . . . . . . . . . . . 8 4.3. Usage Outside of Offer/Answer ..............................8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations .............................................9
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . 8 5.1. New RTCP XR Block Type Value ...............................9
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 5.2. New RTCP XR SDP Parameter ..................................9
5.3. Contact information for registrations . . . . . . . . . . 9 5.3. Contact Information for Registrations ......................9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations .........................................9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References ......................................................9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.1. Normative References .......................................9
7.2. Informative References . . . . . . . . . . . . . . . . . 10 7.2. Informative References ....................................10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses .................................................11
1. Introduction 1. Introduction
1.1. MPEG2 Transport Stream Decodability Metrics 1.1. MPEG2 Transport Stream Decodability Metrics
The European Telecommunications Standards Institute (ETSI) has The European Telecommunications Standards Institute (ETSI) has
defined a set of syntax and information consistency tests and defined a set of syntax and information consistency tests and
corresponding indicators [ETSI] that are recommended for the corresponding indicators [ETSI] that are recommended for the
monitoring of MPEG2 Transport Streams [ISO-IEC.13818-1.2007]. The monitoring of MPEG2 Transport Streams [ISO-IEC.13818-1.2007]. The
tests and corresponding indicators are grouped according to priority: tests and corresponding indicators are grouped according to priority:
o First priority - Necessary for decodability (basic monitoring) First priority: Necessary for decodability (basic monitoring)
o Second priority - Recommended for continuous or periodic
monitoring Second priority: Recommended for continuous or periodic monitoring
o Third priority - Recommended for application-dependent monitoring
Third priority: Recommended for application-dependent monitoring
This memo defines a new block type for use with MPEG2 Transport This memo defines a new block type for use with MPEG2 Transport
Stream (TS) [ISO-IEC.13818-1.2007], to augment those defined in Streams [ISO-IEC.13818-1.2007] to augment those defined in [RFC3611].
[RFC3611]. The new block type supports reporting of the number of The new block type supports reporting of the number of occurrences of
occurrences of each Program Specific Information (PSI) indicator in each Program Specific Information (PSI) indicator in the first and
the first and second priorities listed by [ETSI] sections 5.2.1 and second priorities listed in Sections 5.2.1 and 5.2.2, respectively,
5.2.2 respectively. Third priority indicators are not supported. of [ETSI]. The third priority indicators are not supported. The
The metrics defined here supplement information from the PSI- metrics defined here supplement information from the PSI-Independent
independent Decodability Statistics Metrics Block [RFC6990]. Decodability Statistics Metrics Block [RFC6990].
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defines an extensible structure for reporting using an RTCP Extended defines an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611]. use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guidelines for RTCP XR Monitoring Architectures [RFC6792] provides guidelines for RTCP XR
reporting block formats. The new report block described in this memo block formats. The new report block described in this memo is in
is in compliance with the monitoring architecture specified in compliance with the monitoring architecture specified in [RFC6792]
[RFC6792] and the Performance Metrics Framework [RFC6390]. and the Performance Metrics Framework [RFC6390].
1.4. Applicability 1.4. Applicability
These metrics are applicable to any type of RTP application that uses These metrics are applicable to any type of RTP application that uses
the MPEG2 TS standard format for multimedia data, for example, MPEG4 the MPEG2 TS standard format for multimedia data, for example, MPEG4
over MPEG2 TS over RTP. This new block type can be useful for over MPEG2 TS over RTP. This new block type can be useful for
measuring content stream or TS quality by checking TS header measuring content stream or TS quality by checking TS header
information [ETSI] and identifying the existence, and characterizing information [ETSI] and identifying the existence (and characterizing
the severity, of bitstream packetization problems which may affect the severity) of bitstream packetization problems that may affect
users' perception of a service delivered over RTP. It may also be users' perception of a service delivered over RTP. It may also be
useful for verifying the continued correct operation of an existing useful for verifying the continued correct operation of an existing
system management tool. system management tool.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. MPEG2 TS PSI Decodability Statistics Metrics Block 3. MPEG2 TS PSI Decodability Statistics Metrics Block
ETSI TR 101290 [ETSI] generally defines indicators related to error ETSI TR 101 290 [ETSI] generally defines indicators related to error
events, while the XR block defined in this document contains counts events whereas the XR block defined in this document contains counts
of occurrences of the [ETSI] indicators. The block defined in this of occurrences of the [ETSI] indicators. The block defined in this
document reports MPEG2 TS PSI decodability statistics metrics beyond document reports MPEG2 TS PSI decodability statistics metrics beyond
the information carried in the standard RTCP packet format and PSI- the information carried in the standard RTCP packet format and PSI-
independent Decodability Metrics Block [RFC6990], which are measured Independent Decodability Statistics Metrics Block [RFC6990], which
at the receiving end of the RTP stream. It contains counts of seven are measured at the receiving end of the RTP stream. It contains
metrics defined in ETSI TR 101290 [ETSI]. Information is reported counts of seven metrics defined in ETSI TR 101 290 [ETSI].
about basic monitoring parameters necessary to ensure that the TS can Information is reported about basic monitoring parameters necessary
be decoded including: to ensure that the TS can be decoded, including:
o Program Association Table (PAT) errors o Program Association Table (PAT) errors
o PAT 2 errors
o PAT2 errors
o Program Map Table (PMT) errors o Program Map Table (PMT) errors
o PMT 2 errors
o PMT2 errors
o Packet Identifier (PID) errors o Packet Identifier (PID) errors
and continuous monitoring parameters necessary to ensure the Information is also reported about continuous monitoring parameters
continuous decoding including: necessary to ensure continuous decoding, including:
o Cyclic Redundancy Check (CRC) errors o Cyclic Redundancy Check (CRC) errors
o Conditional Access Table (CAT) errors o Conditional Access Table (CAT) errors
In these parameters, PAT 2 errors and PMT 2 errors are actually In these parameters, PAT2 errors and PMT2 errors are actually
replacements for and improvements on PAT errors and PMT errors replacements for and improvements on PAT errors and PMT errors,
respectively and are therefore preferred in future implementations. respectively, and are therefore preferred in future implementations.
In addition, measurement results for some of these parameters (e.g., In addition, measurement results for some of these parameters (e.g.,
PAT errors or PMT errors) may be different based on whether PAT errors or PMT errors) may be different based on whether
scrambling is employed. The other parameters defined in [ETSI] scrambling is employed. The other parameters defined in Section 5 of
Section 5 are ignored since they do not apply to all MPEG2 [ETSI] are ignored since they do not apply to all MPEG2
implementations. For further detailed information on these implementations. For further detailed information on these
parameters, see [ETSI]. parameters, see [ETSI].
The MPEG2 TS PSI Decodability Metrics Block has the following format: The MPEG2 TS PSI Decodability Metrics Block has the following format:
0 1 2 3 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 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 | | BT=32 | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PAT_error_count | PAT_error_2_count | | PAT_error_count | PAT_error_2_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PMT_error_count | PMT_error_2_count | | PMT_error_count | PMT_error_2_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PID_error_count | CRC_error_count | | PID_error_count | CRC_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CAT_error_count | Reserved | | CAT_error_count | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
block type (BT): 8 bits block type (BT): 8 bits
The MPEG2 TS PSI Decodability Metrics Block is identified by the The MPEG2 TS PSI Decodability Metrics Block is identified by the
constant <MTPD>;. constant 32;.
Reserved: 8 bits Reserved: 8 bits
These bits are reserved. They MUST be set to zero by senders These bits are reserved. They MUST be set to zero by senders
ignored by receivers (See [RFC6709] section 4.2). ignored by receivers (see Section 4.2 of [RFC6709]).
block length: 16 bits block length: 16 bits
The constant 6, in accordance with the definition of this field in The constant 6, in accordance with the definition of this field in
Section 3 of RFC 3611. The block MUST be discarded if the block Section 3 of [RFC3611]. The block MUST be discarded if the block
length is set to a different value. length is set to a different value.
SSRC of source: 32 bits Synchronization Source (SSRC) of source: 32 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of [RFC3611].
begin_seq: 16 bits begin_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of [RFC3611].
end_seq: 16 bits end_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of [RFC3611].
PAT_error_count: 16 bits PAT_error_count: 16 bits
A count of the number of PAT errors that occurred in the above A count of the number of PAT errors that occurred in the above
sequence number interval. The program association table (PAT) is sequence number interval. The Program Association Table (PAT) is
the only packet with packet ID (PID) 0x 0000. A PAT error occurs the only packet with Packet Identifier (PID) 0x0000. A PAT error
when: (1) a packet with PID 0x0000 does not occur at least every occurs when (1) a packet with PID 0x0000 does not occur at least
0.5 seconds, or (2) a packet with PID 0x0000 does not contain a every 0.5 seconds, (2) a packet with PID 0x0000 does not contain
table_id 0x00 (i.e., a PAT), or (3)Scrambling_control_field in the table_id 0x00 (i.e., a PAT), or (3) the Scrambling_control_field
TS packet header is not 00 for a packet with PID 0x0000. See in the TS packet header is not 00 for a packet with PID 0x0000.
section 5.2.1 of [ETSI]. Every program within the MPEG TS stream See Section 5.2.1 of [ETSI]. Every program within the MPEG TS
is listed in the PAT; if it is missing, then no programs can be stream is listed in the PAT; if it is missing, then no programs
decoded. can be decoded.
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. As indicated in unavailable, then the value 0xFFFF MUST be reported. NOTE 1 of
the NOTE 1 of the table in the section 5.2.1 of TR101.290, TR the table in Section 5.2.1 of [ETSI] recommends using
101.290 recommends using PAT_error_2_count. Upon reception, If PAT_error_2_count. Upon reception, if PAT_error_2_count is
PAT_error_2_count is available (that is, other than 0xFFFF), then available (that is, other than 0xFFFF), then receivers MUST ignore
receivers MUST ignore PAT_error_count. PAT_error_count.
PAT_error_2_count: 16 bits PAT_error_2_count: 16 bits
A count of the number of PAT2 errors that occurred in the above A count of the number of PAT2 errors that occurred in the above
sequence number interval. A PAT2 error occurs when: (1) a packet sequence number interval. A PAT2 error occurs when (1) a packet
with PID 0x0000 containing table_id 0x00 does not occur at least with PID 0x0000 containing table_id 0x00 does not occur at least
every 0.5 seconds,or (2) a packet with PID 0x0000 contains a table every 0.5 seconds, (2) a packet with PID 0x0000 contains a table
with table_id other than 0x00, or (3) Scrambling_control_field in with a table_id other than 0x00, or (3) the
the TS packet header is not 00 for a packet with PID 0x0000. See Scrambling_control_field in the TS packet header is not 00 for a
section 5.2.1 of [ETSI]. packet with PID 0x0000. See Section 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, then the value 0xFFFF MUST be reported.
PMT_error_count: 16 bits PMT_error_count: 16 bits
A count of the number of PMT_errors that occurred in the above A count of the number of PMT errors that occurred in the above
sequence number interval. A PMT_error occurs when: (1) a packet sequence number interval. A PMT_error occurs when (1) a packet
containing a table with table_id 0x02(i.e.,a PMT) does not occur containing a table with table_id 0x02 (i.e., a PMT) does not occur
at least every 0.5s on the PID that is referred to in the PAT, at least every 0.5 seconds on the PID that is referred to in the
or(2) Scrambling_control_field in the TS packet header is not 00 PAT or (2) the Scrambling_control_field in the TS packet header is
for all packets with PID containing a table with table_id 0x02 not 00 for all packets with PID containing a table with table_id
(i.e. a PMT). See the section 5.2.1 of [ETSI]. 0x02 (i.e., a PMT). See Section 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. As indicated in unavailable, the value 0xFFFF MUST be reported. NOTE 2 of the
the NOTE 2 of table in the section 5.2.1 of TR101.290, TR 101.290 table in Section 5.2.1 of [ETSI] recommends using
recommends using PMT_error_2_count. Upon reception, If PMT_error_2_count. Upon reception, if PMT_error_2_count is
PMT_error_2_count is available (that is, other than 0xFFFF), then available (that is, other than 0xFFFF), then receivers MUST ignore
receivers MUST ignore PMT_error_count. PMT_error_count.
PMT_error_2_count: 16 bits PMT_error_2_count: 16 bits
A count of the number of PMT2 errors that occurred in the above A count of the number of PMT2 errors that occurred in the above
sequence number interval. A PMT2_error occurs when: (1) a packet sequence number interval. A PMT2_error occurs when (1) a packet
containing table_id 0x02(i.e.,a PMT) does not occur at least every containing table_id 0x02 (i.e., a PMT) does not occur at least
0.5s on each program_map_PID which is referred to in the PAT, or every 0.5 seconds on each program_map_PID that is referred to in
(2) Scrambling_control_field in the TS packet header is not 00 for the PAT or (2) the Scrambling_control_field in the TS packet
all packets containing a table with table_id 0x02 (i.e. a PMT) on header is not 00 for all packets containing a table with table_id
each program_map_PID which is referred to in the PAT. See section 0x02 (i.e., a PMT) on each program_map_PID that is referred to in
5.2.1 of [ETSI]. the PAT. See Section 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, then the value 0xFFFF MUST be reported.
PID_error_count: 16 bits PID_error_count: 16 bits
A count of the number of PID_errors that occurred in the above A count of the number of PID errors that occurred in the above
sequence number interval. A PID error occurs when no data stream sequence number interval. A PID error occurs when no data stream
is present corresponding to a given PID. This may be caused by is present corresponding to a given PID. This may be caused by
multiplexing or demultiplexing, then remultiplexing. See section multiplexing or demultiplexing, then remultiplexing. See
5.2.1 of [ETSI]. Section 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, then the value 0xFFFF MUST be reported.
CRC_error_count: 16 bits CRC_error_count: 16 bits
A count of the number of CRC_errors that occurred in the above A count of the number of CRC errors that occurred in the above
sequence number interval. A CRC_error occurs if data corruption sequence number interval. A CRC_error occurs if data corruption
occurred in any of the following tables -- CAT, PAT, PMT, Network occurred in any of the following tables -- CAT, PAT, PMT, Network
Information Table (NIT), Event Information Table (EIT), Bouquet Information Table (NIT), Event Information Table (EIT), Bouquet
Association Table (BAT), Service Description Table (SDT) or Time Association Table (BAT), Service Description Table (SDT), or Time
Offset Table (TOT), as defined in the section 5.2.2 of [ETSI]. Offset Table (TOT), as defined in Section 5.2.2 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, then the value 0xFFFF MUST be reported.
CAT_error_count: 16 bits CAT_error_count: 16 bits
A count of the number of CAT_errors that occurred in the above A count of the number of CAT errors that occurred in the above
sequence number interval. A CAT_error occurs when: (1) a packet sequence number interval. A CAT_error occurs when (1) a packet
with PID 0x0001 contains a table with table_id other than with PID 0x0001 contains a table with a table_id other than 0x01
0x01(i.e.,not a CAT), or (2) A packet does not contain a table (i.e., not a CAT) or (2) a packet does not contain a table with
with table_id = 0x01 (i.e. a CAT) when scrambling is employed table_id = 0x01 (i.e., a CAT) when scrambling is employed (i.e.,
((i.e., scrambling_control field is set as a value other than the Scrambling_control_field is set as a value other than 00).
00)). See the section 5.2.2 of [ETSI]. See Section 5.2.2 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is an unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, then the value 0xFFFF MUST be reported.
Reserved: 16 bits Reserved: 16 bits
These bits are reserved. They MUST be set to zero by senders These bits are reserved. They MUST be set to zero by senders
ignored by receivers (See [RFC6709] section 4.2). ignored by receivers (see Section 4.2 of [RFC6709]).
4. SDP Signaling 4. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of the Session Description Protocol (SDP)
[RFC4566] for signaling the use of RTCP XR blocks. However XR blocks [RFC4566] for signaling the use of RTCP XR blocks. However, XR
MAY be used without prior signaling (See section 5 of RFC3611). blocks MAY be used without prior signaling (see Section 5 of
[RFC3611]).
4.1. SDP rtcp-xr-attrib Attribute Extension 4.1. SDP rtcp-xr-attrib Attribute Extension
This session augments the SDP attribute "rtcp-xr" defined in This session augments the SDP attribute "rtcp-xr" defined in
Section 5.1 of RFC 3611 by providing an additional value of "xr- Section 5.1 of [RFC3611] by providing an additional value of
format" to signal the use of the report block defined in this "xr-format" to signal the use of the report block defined in this
document. document. The ABNF [RFC5234] syntax is as follows:
xr-format =/ xr-tpd-block xr-format =/ xr-tpd-block
xr-tpd-block = "ts-psi-decodability" xr-tpd-block = "ts-psi-decodability"
4.2. Offer/Answer Usage 4.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in Offer/Answer context, the SDP Offer/Answer usage
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage of Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameters, refer to Section 5.2 of [RFC3611].
4.3. Usage Outside of Offer/Answer 4.3. Usage Outside of Offer/Answer
For usage outside of Offer/Answer,refer to section 5.3 of [RFC3611]. For usage outside of Offer/Answer, refer to Section 5.3 of [RFC3611].
5. IANA Considerations 5. IANA Considerations
New report block types for RTCP XR are subject to IANA registration. New report block types for RTCP XR are subject to IANA registration.
For general guidelines on IANA allocations for RTCP XR, refer to For general guidelines on IANA allocations for RTCP XR, refer to
Section 6.2 of RFC 3611. Section 6.2 of [RFC3611].
5.1. New RTCP XR Block Type value
This document assigns the block type value MTPD in the IANA " RTP 5.1. New RTCP XR Block Type Value
Control Protocol Extended Reports (RTCP XR) Block Type Registry " to
the "MPEG2 Transport Stream PSI Decodability Statistics Metrics
Block".
[Note to RFC Editor: please replace MTPD with the IANA provided RTCP This document assigns the block type value 32 "MPEG2 Transport Stream
XR block type for this block.] PSI Decodability Statistics Metrics Block" in the "RTCP XR Block
Type" subregistry of the IANA "RTP Control Protocol Extended Reports
(RTCP XR) Block Type Registry".
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "ts-psi-decodability" in This document also registers a new parameter "ts-psi-decodability" in
the "RTP Control Protocol Extended Reports (RTCP XR) Session the "RTCP XR SDP Parameters" subregistry of the "RTP Control Protocol
Description Protocol (SDP) Parameters Registry". Extended Reports (RTCP XR) Session Description Protocol (SDP)
Parameters Registry".
5.3. Contact information for registrations 5.3. Contact Information for Registrations
The contact information for the registrations is: The contact information for the registrations is:
RAI Area Directors <rai-ads@tools.ietf.org> RAI Area Directors <rai-ads@tools.ietf.org>
6. Security Considerations 6. Security Considerations
This proposed RTCP XR report block introduces no new security This proposed RTCP XR block introduces no new security considerations
considerations beyond those described in [RFC3611] [RFC6990]. beyond those described in [RFC3611] and [RFC6990].
7. References 7. References
7.1. Normative References 7.1. Normative References
[ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement
guidelines for DVB systems", Technical Report TR 101 290, guidelines for DVB systems", ETSI TR 101 290, June 2014.
2001.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003,
<http://www.rfc-editor.org/info/rfc3550>.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, November Protocol Extended Reports (RTCP XR)", RFC 3611, November
2003. 2003, <http://www.rfc-editor.org/info/rfc3611>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006,
<http://www.rfc-editor.org/info/rfc4566>.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
7.2. Informative References 7.2. Informative References
[ISO-IEC.13818-1.2007] [ISO-IEC.13818-1.2007]
International Organization for Standardization, ISO/IEC, "Information technology - Generic coding of
"Information technology - Generic coding of moving moving pictures and associated audio information - Part 1:
pictures and associated audio information: Systems", ISO Systems", ISO International Standard 13818-1, 2013.
International Standard 13818-1, October 2007.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390, Performance Metric Development", BCP 170, RFC 6390,
October 2011. October 2011, <http://www.rfc-editor.org/info/rfc6390>.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012, <http://www.rfc-editor.org/info/rfc6709>.
[RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
RTP Monitoring Framework", RFC 6792, November 2012. RTP Monitoring Framework", RFC 6792, November 2012,
<http://www.rfc-editor.org/info/rfc6792>.
[RFC6990] Wu, Q., "RTP Control Protocol (RTCP) Extended Report (XR) [RFC6990] Wu, Q., "RTP Control Protocol (RTCP) Extended Report (XR)
Block for MPEG2 Transport Stream (TS) Program Specific Block for MPEG2 Transport Stream (TS) Program Specific
Information (PSI) Independent Decodability Statistics Information (PSI) Independent Decodability Statistics
Metrics reporting", RFC 6990, May 2013. Metrics reporting", RFC 6990, May 2013,
<http://www.rfc-editor.org/info/rfc6990>.
Authors' Addresses Authors' Addresses
Jiangang Tong Jiangang Tong
Shanghai Research Institure of China Telecom Corporation Limited Shanghai Research Institute of China Telecom Corporation Limited
No.1835,South Pudong Road No. 1835, South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: tongjg@sttri.com.cn EMail: tongjg@sttri.com.cn
Claire Bi (editor) Claire Bi (editor)
Shanghai Research Institure of China Telecom Corporation Limited Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road No. 1835, South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: bijy@sttri.com.cn EMail: bijy@sttri.com.cn
Roni Even Roni Even
Gesher Erove Ltd Huawei
14 David Hamelech 14 David Hamelech
Tel Aviv 64953 Tel Aviv 64953
Israel Israel
Email: ron.even.tlv@gmail.com EMail: roni.even@mail01.huawei.com
Qin Wu (editor) Qin Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: bill.wu@huawei.com EMail: bill.wu@huawei.com
Rachel Huang Rachel Huang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: rachel.huang@huawei.com EMail: rachel.huang@huawei.com
 End of changes. 79 change blocks. 
194 lines changed or deleted 204 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/