draft-ietf-xrblock-rtcp-xr-psi-decodability-05.txt   draft-ietf-xrblock-rtcp-xr-psi-decodability-06.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: January 22, 2015 R. Even Expires: February 8, 2015 R. Even
Gesher Erove Ltd Gesher Erove Ltd
Q. Wu, Ed. Q. Wu, Ed.
R. Huang R. Huang
Huawei Huawei
July 21, 2014 August 7, 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-05 draft-ietf-xrblock-rtcp-xr-psi-decodability-06
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
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 January 22, 2015. This Internet-Draft will expire on February 8, 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 . . . . . . . . . . . . . . 9 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
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
skipping to change at page 6, line 16 skipping to change at page 6, line 16
the only packet with packet ID (PID) 0x 0000. A PAT error occurs the only packet with packet ID (PID) 0x 0000. A PAT error occurs
when: (1) a packet with PID 0x0000 does not occur at least every when: (1) a packet with PID 0x0000 does not occur at least every
0.5 seconds, or (2) a packet with PID 0x0000 does not contain a 0.5 seconds, or (2) a packet with PID 0x0000 does not contain a
table_id 0x00 (i.e., a PAT), or (3)Scrambling_control_field in the table_id 0x00 (i.e., a PAT), or (3)Scrambling_control_field in the
TS packet header is not 00 for a packet with PID 0x0000. See TS packet header is not 00 for a packet with PID 0x0000. See
section 5.2.1 of [ETSI]. Every program within the MPEG TS stream 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 is listed in the PAT; if it is missing, then no programs can be
decoded. decoded.
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. Upon reception,
PAT_error_count and PAT_error_2_count MUST NOT be reported at the If PAT_error_2_count is available (that is, other than 0xFFFF),
same time in the same metric block. If PAT_error_count is then receivers MUST ignore PAT_error_count.
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 a table every 0.5 seconds,or (2) a packet with PID 0x0000 contains a table
with table_id other than 0x00, or (3) Scrambling_control_field in with table_id other than 0x00, or (3) Scrambling_control_field in
the TS packet header is not 00 for a packet with PID 0x0000. See the TS packet header is not 00 for a 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.
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.
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.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 a 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. Upon reception,
PMT_error_count and PMT_error_2_count MUST NOT be reported at the If PMT_error_2_count is available (that is, other than 0xFFFF),
same time in the same metric block. If PMT_error_count is then receivers MUST ignore PMT_error_count.
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 a table with table_id 0x02 (i.e. a PMT) on all packets containing a table with table_id 0x02 (i.e. a PMT) on
each program_map_PID which is referred to in the PAT. See section each program_map_PID which is referred to in the PAT. See 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.
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.
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 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
skipping to change at page 9, line 30 skipping to change at page 9, line 20
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 report block introduces no new security
considerations beyond those described in RFC 3611. considerations beyond those described in [RFC3611] [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", Technical Report TR 101 290,
2001. 2001.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 11 change blocks. 
23 lines changed or deleted 15 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/