draft-ietf-xrblock-rtcp-xr-psi-decodability-04.txt   draft-ietf-xrblock-rtcp-xr-psi-decodability-05.txt 
Network Working Group J. Tong Network Working Group J. Tong
Internet-Draft C. Bi, Ed. Internet-Draft C. Bi, Ed.
Intended status: Standards Track China Telecom Intended status: Standards Track China Telecom
Expires: December 7, 2014 R. Even Expires: January 22, 2015 R. Even
Gesher Erove Ltd Gesher Erove Ltd
Q. Wu, Ed. Q. Wu, Ed.
R. Huang R. Huang
Huawei Huawei
June 5, 2014 July 21, 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-04 draft-ietf-xrblock-rtcp-xr-psi-decodability-05
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. carried in MPEG TS.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 7, 2014. This Internet-Draft will expire on January 22, 2015.
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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
skipping to change at page 3, line 10 skipping to change at page 3, line 10
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) o First priority - Necessary for decodability (basic monitoring)
o Second priority - Recommended for continuous or periodic o Second priority - Recommended for continuous or periodic
monitoring monitoring
o Third priority - Recommended for application-dependent monitoring o Third priority - Recommended for application-dependent monitoring
This memo is based on information consistency tests and resulting This memo defines a new block type for use with MPEG2 Transport
indicators defined by ETSI [ETSI] and defines a new block type to Stream (TS) [ISO-IEC.13818-1.2007], to augment those defined in
augment those defined in [RFC3611] for use with MPEG2 Transport [RFC3611]. The new block type supports reporting of the number of
Stream (TS) [ISO-IEC.13818-1.2007]. The new block type supports occurrences of each Program Specific Information (PSI) indicator in
reporting of the number of occurrences of each Program Specific the first and second priorities listed by [ETSI] sections 5.2.1 and
Information (PSI) indicator in the first and second priorities that 5.2.2 respectively. Third priority indicators are not supported.
supplements information from PSI independent Decodability Statistics The metrics defined here supplement information from the PSI-
Metrics Block [RFC6990]; third priority indicators are not supported. independent 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]
defined 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 guideline for reporting Monitoring Architectures [RFC6792] provides guidelines for RTCP XR
block format using RTCP XR. The new report block described in this reporting block formats. The new report block described in this memo
memo is in compliance with the monitoring architecture specified in is in compliance with the monitoring architecture specified in
[RFC6792] and the Performance Metrics Framework [RFC6390]. [RFC6792] 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 which 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 metrics related to error ETSI TR 101290 [ETSI] generally defines indicators related to error
events while this document contains counts of those metrics defined events, while the XR block defined in this document contains counts
in [ETSI]. The block defined in this document reports MPEG2 TS PSI of occurrences of the [ETSI] indicators. The block defined in this
decodability statistics metrics beyond the information carried in the document reports MPEG2 TS PSI decodability statistics metrics beyond
standard RTCP packet format and PSI independent Decodability Metrics the information carried in the standard RTCP packet format and PSI-
Block [RFC6990], which are measured at the receiving end of the RTP independent Decodability Metrics Block [RFC6990], which are measured
stream. It contains counts of six metrics defined in ETSI TR 101290 at the receiving end of the RTP stream. It contains counts of seven
[ETSI]. Information is reported about basic monitoring parameters metrics defined in ETSI TR 101290 [ETSI]. Information is reported
necessary to ensure that the TS can be decoded including: about basic monitoring parameters necessary 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 PAT 2 errors
o Program Map Table(PMT) errors o Program Map Table (PMT) errors
o PMT 2 errors o PMT 2 errors
o Packet Identifier(PID) errors o Packet Identifier (PID) errors
and continuous monitoring parameters necessary to ensure the and continuous monitoring parameters necessary to ensure the
continuous decoding including: 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,scrambling may be considered. The other In these parameters, PAT 2 errors and PMT 2 errors are actually
parameters are ignored since they do not apply to all MPEG2 replacements for and improvements on PAT errors and PMT errors
respectively and are therefore preferred in future implementations.
In addition, measurement results for some of these parameters (e.g.,
PAT errors or PMT errors) may be different based on whether
scrambling is employed. The other parameters defined in [ETSI]
Section 5 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=MTPD | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 26 skipping to change at page 6, line 26
unavailable, the value 0xFFFF MUST be reported. Note that unavailable, the value 0xFFFF MUST be reported. Note that
PAT_error_count and PAT_error_2_count MUST NOT be reported at the 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 same time in the same metric block. If PAT_error_count is
reported, PAT_error_2_count MUST be set to 0xFFFF. reported, PAT_error_2_count MUST be set to 0xFFFF.
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 one every 0.5 seconds,or (2) a packet with PID 0x0000 contains a table
table with table_id other than 0x00, or (3) with table_id other than 0x00, or (3) Scrambling_control_field in
Scrambling_control_field in the TS packet header is not 00 for a the TS packet header is not 00 for a packet with PID 0x0000. See
packet with PID 0x0000. See section 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 unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. Note that unavailable, the value 0xFFFF MUST be reported. Note that
PAT_error_count and PAT_error_2_count MUST NOT be reported at the 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 same time in the same metric block. If PAT_error_2_count is
reported, PAT_error_count MUST be set to 0xFFFF. reported, PAT_error_count MUST be set to 0xFFFF.
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 one 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.5s on the PID that is referred to in the PAT,
or(2) Scrambling_control_field in the TS packet header is not 00 or(2) Scrambling_control_field in the TS packet header is not 00
for all packets with PID containing one table with table_id 0x02 for all packets with PID containing a table with table_id 0x02
(i.e. a PMT). See the section 5.2.1 of [ETSI]. (i.e. a PMT). See the section 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. Note that unavailable, the value 0xFFFF MUST be reported. Note that
PMT_error_count and PMT_error_2_count MUST NOT be reported at the 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 same time in the same metric block. If PMT_error_count is
reported, PMT_error_2_count MUST be set to 0xFFFF. reported, PMT_error_2_count MUST be set to 0xFFFF.
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 every
0.5s on each program_map_PID which is referred to in the PAT, or 0.5s on each program_map_PID which is referred to in the PAT, or
(2) Scrambling_control_field in the TS packet header is not 00 for (2) Scrambling_control_field in the TS packet header is not 00 for
all packets containing one table with table_id 0x02 (i.e. a PMT) all packets containing a table with table_id 0x02 (i.e. a PMT) on
on each program_map_PID which is referred to in the PAT. See each program_map_PID which is referred to in the PAT. See section
section 5.2.1 of [ETSI]. 5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. Note that unavailable, the value 0xFFFF MUST be reported. Note that
PMT_error_count and PMT_error_2_count MUST NOT be reported at the 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 same time in the same metric block. If PMT_error_2_count is
reported, PMT_error_count MUST be set to 0xFFFF. reported, PMT_error_count MUST be set to 0xFFFF.
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 MPEG TS streams sequence number interval. A PID error occurs when no data stream
are remultiplexed and any PID doesn't refer to an actual data is present corresponding to a given PID. This may be caused by
stream, as defined in the section 5.2.1 of [ETSI]. multiplexing or demultiplexing, then remultiplexing. See section
5.2.1 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, 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 the section 5.2.2 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, 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 one table with table_id other than with PID 0x0001 contains a table with table_id other than
0x01(i.e.,not a CAT), or (2) A packet does not contain one table 0x01(i.e.,not a CAT), or (2) A packet does not contain a table
with table_id = 0x01 (i.e. a CAT) when scrambling is employed with table_id = 0x01 (i.e. a CAT) when scrambling is employed
((i.e., scrambling_control field is set as a value other than ((i.e., scrambling_control field is set as a value other than
00)). See the section 5.2.2 of [ETSI]. 00)). See the section 5.2.2 of [ETSI].
The measured value is unsigned value. If the measurement is The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported. unavailable, 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
 End of changes. 22 change blocks. 
48 lines changed or deleted 55 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/