draft-ietf-xrblock-rtcp-xr-decodability-12.txt   rfc6990.txt 
Network Working Group R. Huang Internet Engineering Task Force (IETF) R. Huang
Internet-Draft Q. Wu Request for Comments: 6990 Q. Wu
Intended status: Standards Track Huawei Category: Standards Track Huawei
Expires: December 2, 2013 H. Asaeda ISSN: 2070-1721 H. Asaeda
NICT NICT
G. Zorn G. Zorn
Network Zen Network Zen
May 31, 2013 August 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2
Transport Stream (TS) Program Specific Information (PSI) Independent Transport Stream (TS) Program Specific Information (PSI) Independent
Decodability Statistics Metrics reporting Decodability Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-decodability-12
Abstract Abstract
An MPEG2 Transport Stream (TS) is a standard container format used in An MPEG-2 Transport Stream (TS) is a standard container format used
the transmission and storage of multimedia data. Unicast/Multicast in the transmission and storage of multimedia data. Unicast/
MPEG2 TS over RTP is widely deployed in IPTV systems. This document multicast MPEG-2 TS over RTP is widely deployed in IPTV systems.
defines an RTP Control Protocol (RTCP) Extended Report (XR) Block This document defines an RTP Control Protocol (RTCP) Extended Report
that allows the reporting of MPEG2 TS decodability statistics metrics (XR) block that allows the reporting of MPEG-2 TS decodability
related to transmissions of MPEG2 TS over RTP. The metrics specified statistics metrics related to transmissions of MPEG-2 TS over RTP.
in the RTCP XR Block are not dependent on Program specific The metrics specified in the RTCP XR block are not dependent on
information carried in MPEG TS. Program Specific Information (PSI) carried in MPEG-2 TS.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
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 December 2, 2013. 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/rfc6990.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. MPEG2 Transport Stream Decodability Metrics . . . . . . . 3 1.1. MPEG-2 Transport Stream Decodability Metrics . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP Extended Reports . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Standards Language . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 3. MPEG-2 TS PSI-Independent Decodability Statistics Metrics
3. MPEG2 TS PSI Independent Decodability Statistics Metrics Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. SDP rtcp-xr Attribute Extension . . . . . . . . . . . . . 8
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 8
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . 8 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8 5.3. Contact Information for Registrations . . . . . . . . . . 9
5.3. Contact information for registrations . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
1.1. MPEG2 Transport Stream Decodability Metrics 1.1. MPEG-2 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 MPEG-2 Transport Streams [ISO-IEC.13818-1.2013]. 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 is based on information consistency tests and resulting
indicators defined by ETSI [ETSI] and defines a new block type to indicators defined by ETSI [ETSI] and defines a new block type to
augment those defined in [RFC3611] for use with MPEG2 Transport augment those defined in [RFC3611] for use with MPEG-2 Transport
Stream (TS) [ISO-IEC.13818-1.2007]. The new block type supports Stream (TS) [ISO-IEC.13818-1.2013]. The new block type supports
reporting of the number of occurrences of each Program Specific reporting of the number of occurrences of each PSI-independent
Information (PSI) Independent indicator in the first and second indicator in the first and second priorities; third priority
priorities; third priority indicators are not supported. indicators are not supported.
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP Extended 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 defined 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 "Guidelines for Considering New Performance Metric Development"
definition and specification of performance metrics. The RTP [RFC6390] provides guidance on the definition and specification of
Monitoring Architectures [RFC6792] provides guideline for reporting performance metrics. "Guidelines for Use of the RTP Monitoring
block format using RTCP XR. The new report block described in this Framework" [RFC6792] provides guidance on the reporting block format
memo is in compliance with the monitoring architecture specified in using RTCP XR. The new report block described in this memo is in
[RFC6792] and the Performance Metrics Framework [RFC6390]. compliance with the monitoring architecture specified in [RFC6792]
and the performance metrics framework [RFC6390].
1.4. Applicability 1.4. Applicability
This block type allows a counts of MPEG Transport Stream quality This block type allows a count of MPEG-2 Transport Stream quality
metrics that are measured in accordance with ETSI TR 101290 [ETSI] to metrics that are measured in accordance with ETSI TR 101290 [ETSI] to
be reported by an endpoint. These metrics are useful for identifying be reported by an endpoint. These metrics are useful for identifying
bitstream packetization and transport stream encoding problems that bitstream packetization and transport stream encoding problems that
may affect the user's perception of a video service delivered over may affect the user's perception of a video service delivered over
RTP. RTP.
2. Terminology 2. 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 Independent Decodability Statistics Metrics Block 3. MPEG-2 TS PSI-Independent Decodability Statistics Metrics Block
ETSI TR 101290 [ETSI] generally defines metrics related to error ETSI TR 101290 [ETSI] generally defines metrics related to error
events while this document contains counts of those metrics defined events while this document contains counts of those metrics defined
in [ETSI]. The block defined in this document reports MPEG2 TS PSI in [ETSI]. The block defined in this document reports MPEG-2 TS PSI-
Independent decodability statistics metrics beyond the information independent decodability statistics metrics beyond the information
carried in the standard RTCP packet format, which are measured at the carried in the standard RTCP packet format, which are measured at the
receiving end of the RTP stream. It contains counts of eight metrics receiving end of the RTP stream. It contains counts of eight metrics
defined in ETSI TR 101290 [ETSI]. Information is reported about defined in ETSI TR 101290 [ETSI]. Information is reported about
basic monitoring parameters necessary to ensure that the TS can be basic monitoring parameters necessary to ensure that the TS can be
decoded including: decoded, including:
o Transport Stream Synchronization Losses o Transport Stream Synchronization Losses
o Sync byte errors o Sync byte errors
o Continuity count errors o Continuity count errors
and continuous monitoring parameters necessary to ensure the and continuous monitoring parameters necessary to ensure the
continuous decoding including: continuous decoding, including:
o Transport errors o Transport errors
o Program Clock Reference (PCR) errors o Program Clock Reference (PCR) errors
o PCR repetition errors o PCR repetition errors
o PCR discontinuity indicator errors o PCR discontinuity indicator errors
o PCR accuracy errors o PCR accuracy errors
o Presentation Time Stamp (PTS) errors
The other parameters are ignored since they do not apply to all MPEG2 o Presentation Time Stamp (PTS) errors
implementations. For further information on these parameters, see The other parameters are ignored since they do not apply to all
[ETSI]. Note that when the report of this block spans across more MPEG-2 implementations. For further information on these parameters,
than one measurement intervals [RFC6776], the count of the metrics see [ETSI]. Note that when the report of this block spans across
(e.g., Sync byte errors, PCR errors )defined in [ETSI] may reflect a more than one measurement interval [RFC6776], the count of the
problem in the current or previous measurement interval. metrics (e.g., Sync byte errors and PCR errors) defined in [ETSI] may
reflect a problem in the current or previous measurement interval.
The MPEG2 TS PSI Independent Decodability Metrics Block has the The MPEG-2 TS PSI-Independent Decodability Statistics Metrics Block
following format: 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=MTPID | Reserved | block length | | BT=22 | Reserved | Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TS_sync_loss_count | | TS_sync_loss_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sync_byte_error_count | | Sync_byte_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Continuity_count_error_count | | Continuity_count_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transport_error_count | | Transport_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_error_count | | PCR_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_repetition_error_count | | PCR_repetition_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_discontinuity_indicator_error_count | | PCR_discontinuity_indicator_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PCR_accuracy_error_count | | PCR_accuracy_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PTS_error_count | | PTS_error_count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
block type (BT): 8 bits Block Type (BT): 8 bits
The MPEG2 TS PSI Independent Decodability Metrics Block is The MPEG-2 TS PSI-Independent Decodability Statistics Metrics
identified by the constant <MTPID>. Block is identified by the constant 22.
Reserved: 8 bits Reserved: 8 bits
These bits are reserved. They MUST be set to zero by senders and These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (See [RFC6709] section 4.2). ignored by receivers (see [RFC6709] Section 4.2).
block length: 16 bits Block Length: 16 bits
The constant 11, in accordance with the definition of this field The constant 11, in accordance with the definition of this field
in Section 3 of RFC 3611. The block MUST be discarded if the in Section 3 of RFC 3611. The block MUST be discarded if the
block length is set to a different value. block 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 RFC 3611.
begin_seq: 16 bits begin_seq: 16 bits
The RTP sequence number corresponding to the start of the The RTP sequence number corresponding to the start of the
measurement period, as defined in Section 4.1 of RFC 3611. measurement period, as defined in Section 4.1 of RFC 3611.
end_seq: 16 bits end_seq: 16 bits
The RTP sequence number corresponding to the end of the The RTP sequence number corresponding to the end of the
measurement period, as defined in Section 4.1 of RFC 3611. measurement period, as defined in Section 4.1 of RFC 3611.
TS_sync_loss_count: 32 bits TS_sync_loss_count: 32 bits
A count of the number of TS_sync_loss errors that occurred in the A count of the number of TS_sync_loss errors that occurred in the
above sequence number interval. A TS_sync_loss error occurs when above sequence number interval. A TS_sync_loss error occurs when
there are two or more consecutive incorrect sync bytes within the there are two or more consecutive incorrect sync bytes within the
MPEG TS stream, as defined in section 5.2.1 of [ETSI]. MPEG-2 TS, as defined in Section 5.2.1 of [ETSI].
Sync_byte_error_count: 32 bits Sync_byte_error_count: 32 bits
A count of the number of Sync_byte_errors that occurred in the A count of the number of Sync_byte_errors that occurred in the
above sequence number interval. A sync byte error occurs when the above sequence number interval. A sync byte error occurs when the
sync byte is not equal to 0x47 in any TS packet contained in the sync byte is not equal to 0x47 in any TS packet contained in the
MPEG TS stream, as defined in section 5.2.1 of [ETSI]. MPEG-2 TS, as defined in Section 5.2.1 of [ETSI].
Continuity_count_error_count: 32 bits Continuity_count_error_count: 32 bits
A count of the number of Continuity_count_errors that occurred in A count of the number of Continuity_count_errors that occurred in
the above sequence number interval. A Continuity_count_error the above sequence number interval. A Continuity_count_error
occurs when any of the following faults happen within the MPEG TS occurs when any of the following faults happen within the MPEG-2
stream - incorrect packet order, a packet occurs more than twice TS -- incorrect packet order, a packet occurs more than twice, or
or a packet is lost,as defined in the section 5.2.1 of [ETSI]. a packet is lost, as defined in Section 5.2.1 of [ETSI].
Transport_error_count: 32 bits Transport_error_count: 32 bits
A count of the number of Transport_errors that occurred in the A count of the number of Transport_errors that occurred in the
above sequence number interval. A Transport_error occurs when above sequence number interval. A Transport_error occurs when an
erroneous TS packet can not be corrected within the MPEG TS erroneous TS packet cannot be corrected within the MPEG-2 TS, as
stream. as defined in the section 5.2.2 of [ETSI]. defined in Section 5.2.2 of [ETSI].
PCR_error_count: 32 bits PCR_error_count: 32 bits
A count of the number of PCR_errors that occurred in the above A count of the number of PCR_errors that occurred in the above
sequence number interval. A PCR_error occurs if the primary clock sequence number interval. A PCR_error occurs if the primary clock
reference (PCR) is not seen for more than 100ms within the MPEG TS reference (PCR) is not seen for more than 100 ms within the MPEG-2
stream, as defined in the section 5.2.2 of [ETSI]. The time TS, as defined in Section 5.2.2 of [ETSI]. The time interval
interval between two consecutive PCR values should be no more than between two consecutive PCR values should be no more than 40 ms.
40ms.
PCR_repetition_error_count: 32 bits PCR_repetition_error_count: 32 bits
A count of the number of PCR_repetition_errors that occurred in A count of the number of PCR_repetition_errors that occurred in
the above sequence number interval. A PCR_repeition_error occurs the above sequence number interval. A PCR_repetition_error occurs
when the time interval between two consecutive PCR values is more when the time interval between two consecutive PCR values is more
than 40ms within the MPEG TS stream,as defined in the section than 40 ms within the MPEG-2 TS, as defined in Section 5.2.2 of
5.2.2 of [ETSI]. [ETSI].
PCR_discontinuity_indicator_error_count: 32 bits PCR_discontinuity_indicator_error_count: 32 bits
A count of the number of PCR_discontinuity_indicator_errors that A count of the number of PCR_discontinuity_indicator_errors that
occurred in the above sequence number interval. A occurred in the above sequence number interval. A
PCR_discontinuity_indicator_error occurs if the time interval PCR_discontinuity_indicator_error occurs if the time interval
between two consecutive PCR values is more than 100ms within the between two consecutive PCR values is more than 100 ms within the
MPEG TS stream, as defined in the section 5.2.2 of [ETSI]. MPEG-2 TS, as defined in Section 5.2.2 of [ETSI].
PCR_accuracy_error_count: 32 bits PCR_accuracy_error_count: 32 bits
A count of the Number of PCR_accuracy_errors that occurred in the A count of the number of PCR_accuracy_errors that occurred in the
above sequence number interval. A PCR_accuracy_error occurs when above sequence number interval. A PCR_accuracy_error occurs when
the PCR accuracy of the selected program is outside the range of the PCR accuracy of the selected program is outside the range of
+/-500ns within the MPEG TS stream,as defined in the section 5.2.2 +/-500 ns within the MPEG-2 TS, as defined in Section 5.2.2 of
of [ETSI]. [ETSI].
PTS_error_count: 32 bits PTS_error_count: 32 bits
A count of the number of PTS_errors that occurred in the above A count of the number of PTS_errors that occurred in the above
sequence number interval. A PTS_error occurs when the PTS sequence number interval. A PTS_error occurs when the PTS
repetition is more than 700ms within the MPEG TS stream, as repetition is more than 700 ms within the MPEG-2 TS, as defined in
defined in the section 5.2.2 of[ETSI]. Note that the PTS is Section 5.2.2 of [ETSI]. Note that the PTS is contained in the
contained in the MPEG-2 TS stream and is used to aid the decoder MPEG-2 TS and is used to aid the decoder in presenting the program
in presenting the program on time, at the correct speed and on time, at the correct speed, and synchronized.
synchronized.
4. SDP Signaling 4. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) RFC 3611 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 RFC
3611).
4.1. SDP rtcp-xr-attrib Attribute Extension 4.1. SDP rtcp-xr Attribute Extension
This session augments the SDP attribute "rtcp-xr" defined in Section This session augments the SDP attribute "rtcp-xr" defined in
5.1 of RFC 3611 by providing an additional value of "xr-format" to Section 5.1 of RFC 3611 by providing an additional value of
signal the use of the report block defined in this document. "xr-format" to signal the use of the report block defined in this
document. The ABNF [RFC5234] syntax is as follows.
xr-format =/ xr-tpid-block xr-format =/ xr-tpid-block
xr-tpid-block = "ts-psi-indep-decodability" xr-tpid-block = "ts-psi-indep-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].
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 RFC 3611.
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type Value
This document assigns the block type value MTPID in the IANA " RTP This document assigns the block type value 22 in the IANA "RTP
Control Protocol Extended Reports (RTCP XR) Block Type Registry " to Control Protocol Extended Reports (RTCP XR) Block Type Registry" to
the "MPEG2 Transport Stream PSI Independent Decodability Statistics the "MPEG-2 Transport Stream PSI-Independent Decodability Statistics
Metrics Block". Metrics Block".
[Note to RFC Editor: please replace MPITD with the IANA provided RTCP
XR block type for this block.]
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "ts-psi-indep- This document also registers the new parameter "ts-psi-
decodability" in the "RTP Control Protocol Extended Reports (RTCP XR) indep-decodability" in the "RTP Control Protocol Extended Reports
Session Description Protocol (SDP) Parameters Registry". (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 registrations is:
Qin Wu Qin Wu (sunseawq@huawei.com)
sunseawq@huawei.com 101 Software Avenue, Yuhua District
101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012
Nanjing, JiangSu 210012 China China
6. Security Considerations 6. Security Considerations
There might be some relationship between reported error counters and There might be some relationship between reported error counters and
contractual Service Level Agreements (SLA)s and hence an attack contractual Service Level Agreements (SLAs); hence, an attack (e.g.,
(e.g., RTP endpoints report fake information, or an attacker in the RTP endpoints reporting false data, or an attacker in the path
path modifies the data being reported ) may deliberately corrupt modifying the data being reported) might deliberately corrupt these
these error counters fields and will result in financial implications error counters, resulting in financial implications for the network
for the network operator (either as a result of un-needed Performance operator (either as a result of unneeded performance metrics, or
metrics, or penalty charges for SLA failure). penalty charges for SLA failure).
A solution to prevent such attack is to apply an authentication and A solution to prevent such an attack is to apply an authentication
integrity protection framework for the RTCP XR report block. This and integrity protection framework for the RTCP XR block. This can
can be accomplished using the RTP profile that combines Secure RTP be accomplished using the RTP profile that combines Secure RTP
[RFC3711] and AVPF into SAVPF [RFC5124]. [RFC3711] and the Audio-Visual Profile with Feedback (AVPF) into
Secure AVPF (SAVPF) [RFC5124].
Besides this, the proposed RTCP XR report block in this document Besides this, the RTCP XR block in this document introduces no new
introduces no other new security considerations beyond those security considerations beyond those described in [RFC3611].
described in [RFC3611].
7. Acknowledgements 7. Acknowledgements
Thanks to Ray van Brandenburg, Claire Bi, Colin Perkin, Roni Even, Thanks to Ray van Brandenburg, Claire Bi, Colin Perkins, Roni Even,
Dan Romascanu, Ali Begen and Alan Clark for useful review and Dan Romascanu, Ali Begen, Alexey Melnikov, Bert Wijnen, Gonzalo
Camarillo, Benoit Claise, and Alan Clark for useful reviews and
suggestions. suggestions.
8. References 8. References
8.1. Normative References 8.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
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., Casner, S., Frederick, R., and V.
Applications", RFC 3550, July 2003. Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, 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, Protocol Extended Reports (RTCP XR)", RFC 3611, November
November 2003. 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004. RFC 3711, March 2004.
[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.
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008. (RTP/SAVPF)", RFC 5124, February 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
8.2. Informative References 8.2. Informative References
[ISO-IEC.13818-1.2007] [ISO-IEC.13818-1.2013]
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", pictures and associated audio information: Systems", ISO
ISO International Standard 13818-1, October 2007. International Standard 13818-1, May 2013.
[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.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
using SDES item and XR Block", RFC 6776, August 2012. Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 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
RTP Monitoring Framework", RFC 6792, November 2012. RTP Monitoring Framework", RFC 6792, November 2012.
Authors' Addresses Authors' Addresses
Rachel Huang Rachel Huang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing 210012 Nanjing 210012
China China
Email: rachel.huang@huawei.com EMail: rachel.huang@huawei.com
Qin Wu Qin Wu
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
Hitoshi Asaeda Hitoshi Asaeda
National Institute of Information and Communications Technology National Institute of Information and Communications Technology
4-2-1 Nukui-Kitamachi 4-2-1 Nukui-Kitamachi
Koganei, Tokyo 184-8795 Koganei, Tokyo 184-8795
Japan Japan
Email: asaeda@nict.go.jp EMail: asaeda@nict.go.jp
Glen Zorn Glen Zorn
Network Zen Network Zen
227/358 Thanon Sanphawut 227/358 Thanon Sanphawut
Bang Na, Bangkok 10260 Bang Na, Bangkok 10260
Thailand Thailand
Phone: +66 (0) 909-201060 Phone: +66 (0) 8-1000-4155
Email: glenzorn@gmail.com EMail: glenzorn@gmail.com
 End of changes. 75 change blocks. 
193 lines changed or deleted 198 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/