draft-ietf-xrblock-rtcp-xr-decodability-09.txt   draft-ietf-xrblock-rtcp-xr-decodability-10.txt 
Network Working Group R. Huang Network Working Group R. Huang
Internet-Draft Q. Wu Internet-Draft Q. Wu
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: August 29, 2013 H. Asaeda Expires: September 22, 2013 H. Asaeda
NICT NICT
G. Zorn G. Zorn
Network Zen Network Zen
February 25, 2013 March 21, 2013
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) Independent Transport Stream (TS) Program Specific Information (PSI) Independent
Decodability Statistics Metrics reporting Decodability Statistics Metrics reporting
draft-ietf-xrblock-rtcp-xr-decodability-09 draft-ietf-xrblock-rtcp-xr-decodability-10
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 Program Specific Information that allows the reporting of MPEG2 TS decodability statistics metrics
(PSI) Independent decodability statistics metrics related to related to transmissions of MPEG2 TS over RTP. The metrics specified
transmissions of MPEG2 TS over RTP. in the RTCP XR Block are not dependent on Program specific
information 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 August 29, 2013. This Internet-Draft will expire on September 22, 2013.
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
skipping to change at page 4, line 20 skipping to change at page 4, line 20
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. MPEG2 TS PSI Independent Decodability Statistics Metrics Block
This block reports MPEG2 TS PSI Independent decodability statistics This block reports MPEG2 TS PSI Independent decodability statistics
metrics beyond the information carried in the standard RTCP packet metrics beyond the information carried in the standard RTCP packet
format, which are measured at the receiving end of the RTP stream. format, which are measured at the receiving end of the RTP stream.
It describes eight metrics specified in ETSI TR 101 290. Information It describes eight metrics specified in [ETSI]. Information is
is reported about basic monitoring parameters necessary to ensure reported about basic monitoring parameters necessary to ensure that
that the TS can be decoded including: the TS can be 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
skipping to change at page 6, line 21 skipping to change at page 6, line 21
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.
TS_sync_loss_count: 32 bits TS_sync_loss_count: 32 bits
Number of TS_sync_loss errors in the above sequence number Number of TS_sync_loss errors in the above sequence number
interval. It is calculated based on the occurrence of errors for interval. It is calculated based on the occurrence of errors for
"TS_sync_loss"parameter defined in the section 5.2.1 of ETSI TR "TS_sync_loss"parameter defined in the section 5.2.1 of
101 290 (See section 5.5.1 of ETSI TR 101 290). [ETSI](Also see section 5.5.1 of [ETSI]).
Sync_byte_error_count: 32 bits Sync_byte_error_count: 32 bits
Number of sync_byte_errors in the above sequence number interval. Number of sync_byte_errors in the above sequence number interval.
It is calculated in the same way as TS_sync_loss_count, i.e.,based It is calculated in the same way as TS_sync_loss_count, i.e.,based
on the occurrence of errors for "Sync_byte_error"parameter defined on the occurrence of errors for "Sync_byte_error"parameter defined
in the section 5.2.1 of ETSI TR 101 290. in the section 5.2.1 of [ETSI].
Continuity_count_error_count: 32 bits Continuity_count_error_count: 32 bits
Number of Continuity_count_errors in the above sequence number Number of Continuity_count_errors in the above sequence number
interval. Similarly, it is calculated based on the occurrence of interval. Similarly, it is calculated based on the occurrence of
errors for "Continuity_count_error" parameter defined in the errors for "Continuity_count_error" parameter defined in the
section 5.2.1 of ETSI TR 101 290. section 5.2.1 of [ETSI].
Transport_error_count: 32 bits Transport_error_count: 32 bits
Number of Transport_errors in the above sequence number interval. Number of Transport_errors in the above sequence number interval.
Similarly, it is calculated based on the occurrence of errors for Similarly, it is calculated based on the occurrence of errors for
"Transport_error" parameter defined in the section 5.2.2 of ETSI "Transport_error" parameter defined in the section 5.2.2 of
TR 101 290. [ETSI].
PCR_error_count: 32 bits PCR_error_count: 32 bits
Number of PCR_errors in the above sequence number interval. Number of PCR_errors in the above sequence number interval.
Similarly, it is calculated based on the occurrence of errors for Similarly, it is calculated based on the occurrence of errors for
"PCR_error" parameter defined in the section 5.2.2 of ETSI TR 101 "PCR_error" parameter defined in the section 5.2.2 of [ETSI].
290.
PCR_repetition_error_count: 32 bits PCR_repetition_error_count: 32 bits
Number of PCR_repetition_errors in the above sequence number Number of PCR_repetition_errors in the above sequence number
interval. Similarly, it is calculated based on the occurrence of interval. Similarly, it is calculated based on the occurrence of
errors for "PCR_repetition_error" parameter defined in the section errors for "PCR_repetition_error" parameter defined in the section
5.2.2 of ETSI TR 101 290. 5.2.2 of [ETSI].
PCR_discontinuity_indicator_error_count: 32 bits PCR_discontinuity_indicator_error_count: 32 bits
Number of PCR_discontinuity_indicator_errors in the above sequence Number of PCR_discontinuity_indicator_errors in the above sequence
number interval. Similarly, it is calculated based on the number interval. Similarly, it is calculated based on the
occurrence of errors for "PCR_discontinuity_indicator_error" occurrence of errors for "PCR_discontinuity_indicator_error"
parameter defined in the section 5.2.2 of ETSI TR 101 290. parameter defined in the section 5.2.2 of [ETSI].
PCR_error_count: 32 bits PCR_error_count: 32 bits
Number of PCR_accuracy_errors in the above sequence number Number of PCR_accuracy_errors in the above sequence number
interval. Similarly, it is calculated based on the occurrence of interval. Similarly, it is calculated based on the occurrence of
errors for "PCR_accuracy_error" parameter defined in the section errors for "PCR_accuracy_error" parameter defined in the section
5.2.2 of ETSI TR 101 290. 5.2.2 of [ETSI].
PTS_error_count: 32 bits PTS_error_count: 32 bits
Number of PTS_errors in the above sequence number interval. Number of PTS_errors in the above sequence number interval.
Similarly, it is calculated based on the occurrence of errors for Similarly, it is calculated based on the occurrence of errors for
"PTS_error" parameter defined in the section 5.2.2 of ETSI TR 101 "PTS_error" parameter defined in the section 5.2.2 of [ETSI].
290.
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 Section This session augments the SDP attribute "rtcp-xr" defined in Section
 End of changes. 15 change blocks. 
23 lines changed or deleted 22 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/