draft-ietf-xrblock-rtcp-xr-psi-decodability-00.txt   draft-ietf-xrblock-rtcp-xr-psi-decodability-01.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: June 8, 2014 R. Even Expires: August 17, 2014 R. Even
Gesher Erove Ltd Gesher Erove Ltd
Q. Wu, Ed. Q. Wu, Ed.
R. Huang R. Huang
Huawei Huawei
December 5, 2013 February 13, 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-00 draft-ietf-xrblock-rtcp-xr-psi-decodability-01
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 June 8, 2014. This Internet-Draft will expire on August 17, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . 3 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. MPEG2 TS PSI Decodability Statistics Metrics Block . . . . . 3 3. MPEG2 TS PSI Decodability Statistics Metrics Block . . . . . . 4
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 7 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 7 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . 8 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
5.3. Contact information for registrations . . . . . . . . . . 8 5.3. Contact information for registrations . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 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
tests and corresponding indicators are grouped according to priority: tests and corresponding indicators are grouped according to priority:
skipping to change at page 4, line 32 skipping to change at page 5, line 5
o Cyclic Redundancy Check (CRC) errors o Cyclic Redundancy Check (CRC) errors
o Conditional Access Table (CAT) errors o Conditional Access Table (CAT) errors
The other parameters are ignored since they do not apply to all MPEG2 The other parameters are ignored since they do not apply to all MPEG2
implementations. For further information on these parameters, see implementations. For further information on these parameters, see
[ETSI]. [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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PAT_error_count | | PAT_error_count | PAT_error_2_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PAT_error_2_count | | PMT_error_count | PMT_error_2_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PMT_error_count | | PID_error_count | CRC_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PMT_error_2_count | | CAT_error_count | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PID_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CRC_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CAT_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 <MTPD>.
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 [RFC6709] section 4.2).
skipping to change at page 5, line 40 skipping to change at page 6, line 5
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
begin_seq: 16 bits begin_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
end_seq: 16 bits end_seq: 16 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of RFC 3611.
PAT_error_count: 32 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 ID (PID) 0x 0000. A PAT error occurs
when it does not occur at least every 0.5s or the table has an ID 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 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 program within the MPEG TS stream is listed in the PAT; if it is
missing, then no programs can be decoded. missing, then no programs can be 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. 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: 32 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 it does not 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 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 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]. the PAT PID, as defined in 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: 32 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 the program map 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 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 is referred to in the PAT, as defined in the section 5.2.1 of
[ETSI]. [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: 32 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 the program 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 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 that is referred to in the PAT, as defined in the section 5.2.1 of
[ETSI]. [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: 32 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 MPEG TS streams
are remultiplexed and any PID doesn't refer to an actual data are remultiplexed and any PID doesn't refer to an actual data
stream, as defined in the section 5.2.2 of [ETSI]. stream, as defined in the section 5.2.2 of [ETSI].
CRC_error_count: 32 bits The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported.
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 -\u002D CAT, PAT, PMT, occurred in any of the following tables -- CAT, PAT, PMT, Network
Network Information Table(NIT), Event Information Table(EIT), Information Table (NIT), Event Information Table (EIT), Bouquet
Bouquet Association Table(BAT), Service Description Table(SDT) or Association Table (BAT), Service Description Table (SDT) or Time
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].
CAT_error_count: 32 bits The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported.
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 the table has 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]. an ID other than 0x 01,as defined in the section 5.2.2 of [ETSI].
The measured value is unsigned value. If the measurement is
unavailable, the value 0xFFFF MUST be reported.
Reserved: 16 bits
These bits are reserved. They MUST be set to zero by senders
ignored by receivers (See [RFC6709] section 4.2).
4. SDP Signaling 4. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) RFC 3611 defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of RTCP XR blocks. However XR blocks [RFC4566] for signaling the use of RTCP XR blocks. However XR blocks
MAY be used without prior signaling (See section 5 of RFC3611). 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
Section 5.1 of RFC 3611 by providing an additional value of "xr- 5.1 of RFC 3611 by providing an additional value of "xr-format" to
format" to signal the use of the report block defined in this signal the use of the report block defined in this document.
document.
xr-format =/ xr-tpd-block xr-format =/ xr-tpd-block
xr-tpdd-block = "ts-psi-decodability" xr-tpdd-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
skipping to change at page 9, line 6 skipping to change at page 9, line 40
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[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,
2003. November 2003.
[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.
7.2. Informative References 7.2. Informative References
[ISO-IEC.13818-1.2007] [ISO-IEC.13818-1.2007]
International Organization for Standardization, International Organization for Standardization,
"Information technology - Generic coding of moving "Information technology - Generic coding of moving
pictures and associated audio information: Systems", ISO pictures and associated audio information: Systems",
International Standard 13818-1, October 2007. ISO 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.
[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.
[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
 End of changes. 20 change blocks. 
68 lines changed or deleted 76 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/