draft-ietf-xrblock-rtcp-xr-decodability-07.txt   draft-ietf-xrblock-rtcp-xr-decodability-08.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: July 20, 2013 H. Asaeda Expires: August 29, 2013 H. Asaeda
NICT NICT
G. Zorn, Ed. G. Zorn, Ed.
Network Zen Network Zen
January 16, 2013 February 25, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 Program
Transport Stream (TS) Program Specific Information (PSI) Independent Specific Information (PSI) Independent Transport Stream (TS)
Decodability Statistics Metric reporting Decodability Statistics Metric reporting
draft-ietf-xrblock-rtcp-xr-decodability-07 draft-ietf-xrblock-rtcp-xr-decodability-08
Abstract Abstract
An MPEG 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
Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This MPEG2 TS over RTP is widely deployed in IPTV systems. This document
document defines an RTP Control Protocol (RTCP) Extended Report (XR) defines an RTP Control Protocol (RTCP) Extended Report (XR) Block
Block that allows the reporting of MPEG TS Program Specific that allows the reporting of MPEG2 Program Specific Information (PSI)
Information (PSI) Independent decodability statistics metrics related Independent TS decodability statistics metrics related to
to transmissions of MPEG-TS over RTP. transmissions of MPEG2 TS over RTP.
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 July 20, 2013. This Internet-Draft will expire on August 29, 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 2, line 22 skipping to change at page 2, line 22
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. MPEG Transport Stream Decodability Metrics . . . . . . . . 3 1.1. MPEG 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. MPEG TS PSI Independent Decodability Statistics Metric 3. MPEG PSI Independent TS Decodability Statistics Metrics
Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . 8 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 8
5.3. Contact information for registrations . . . . . . . . . . 8 5.3. Contact information for registrations . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
1.1. MPEG Transport Stream Decodability Metrics 1.1. MPEG 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 MPEG-2 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 de-codability (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-dependant 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 Freidman, et al. [RFC3611] for use with MPEG augment those defined in Freidman, et al. [RFC3611] for use with
Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type MPEG2 Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block
supports reporting of the number of occurrences of each Program type supports reporting of the number of occurrences of each Program
Specific Information (PSI) Independent indicator in the first and Specific Information (PSI) Independent indicator in the first and
second priorities; third priority indicators are not supported. second priorities; third priority indicators are not supported.
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 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].
skipping to change at page 3, line 47 skipping to change at page 3, line 47
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 guideline for reporting
block format using RTCP XR. The new report block described in this block format using RTCP XR. The new report block described in this
memo is in compliance with the monitoring architecture specified in memo 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 MPEG-TS standard format for multimedia data; for example, MPEG4 the MPEG2 TS standard format for multimedia data; for example, MPEG4
TS content over RTP. This new block type can be useful for measuring over MPEG2 TS over RTP. This new block type can be useful for
content stream or TS quality by checking TS header information [ETSI] measuring content stream or TS quality by checking TS header
and identifying the existence, and characterizing the severity, of information [ETSI] and identifying the existence, and characterizing
bitstream packetization problems which may affect users' perception the severity, of bitstream packetization problems which may affect
of a service delivered over RTP; it may also be useful for verifying users' perception of a service delivered over RTP; it may also be
the continued correct operation of an existing system management useful for verifying the continued correct operation of an existing
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. MPEG TS PSI Independent Decodability Statistics Metric Block 3. MPEG PSI Independent TS Decodability Statistics Metrics Block
This block reports MPEG TS PSI Independent decodability statistics This block reports MPEG PSI Independent TS 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 TR 101 290. Information
is reported about basic monitoring parameters necessary to ensure is reported about basic monitoring parameters necessary to ensure
that the TS can be decoded including: that 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
skipping to change at page 4, line 42 skipping to change at page 4, line 42
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 o Presentation Time Stamp (PTS) errors
The other parameters are ignored since they do not apply to all MPEG The other parameters are ignored since they do not apply to all MPEG
implementations. For further information on these parameters, see implementations. For further information on these parameters, see
[ETSI]. [ETSI].
The MPEG-TS PSI Independent Decodability Metrics Block has the The MPEG2 PSI Independent TS Decodability Metrics Block has the
following format: 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=TSDM | Reserved | block length | | BT=MPITD | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of TSs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 37 skipping to change at page 5, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 MPEG-TS PSI Independent Decodability Metrics Block is The MPEG PSI Independent TS Decodability Metrics Block is
identified by the constant <MPID>. identified by the constant <MPITD>.
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).
block length: 16 bits block length: 16 bits
The constant 12, 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 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
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.
Number of TSs: 32 bits
Number of TS in the above sequence number interval.
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 ETSI TR
101 290 (See section 5.5.1 of ETSI TR 101 290). 101 290 (See section 5.5.1 of ETSI TR 101 290).
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 TR 101 290.
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. Simiarly, 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 TR 101 290.
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.
Simiarly, 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 ETSI
TR 101 290. TR 101 290.
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.
Simiarly, 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 TR 101
290. 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. Simiarly, 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 TR 101 290.
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. Simiarly, it is calculated based on the number interval. Similarly, it is calculated based on the
occurrence of errors for occurrence of errors for "PCR_discontinuity_indicator_error"
"PCR_discontinuity_indicator_error"parameter defined in the parameter defined in the section 5.2.2 of ETSI TR 101 290.
section 5.2.2 of ETSI TR 101 290.
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. Simiarly, 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 TR 101 290.
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.
Simiarly, 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 TR 101
290. 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
5.1 of RFC 3611 by providing an additional value of "xr-format" to 5.1 of RFC 3611 by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
xr-format =/ xr-nptd-block xr-format =/ xr-pitd-block
xr-nptd-block = "non-psi-ts-decodability" xr-pitd-block = "psi-indep-ts-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]. parameter, 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 ofRFC 3611. Section 6.2 ofRFC 3611.
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type value
This document assigns the block type value MPID in the IANA " RTP This document assigns the block type value MPITD 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 " MPEG Transport Stream PSI Independent Decodability Statistics the " MPEG PSI Independent Transport Stream Decodability Statistics
Metric Block". Metrics Block".
[Note to RFC Editor: please replace MPID with the IANA provided RTCP [Note to RFC Editor: please replace MPITD with the IANA provided RTCP
XR block type for this block.] 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 " non-psi-ts- This document also registers a new parameter "psi-indep-ts-
decodability " in the "RTP Control Protocol Extended Reports (RTCP decodability" in the "RTP Control Protocol Extended Reports (RTCP XR)
XR) Session Description Protocol (SDP) Parameters Registry". 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 the 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 China Nanjing, JiangSu 210012 China
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 RFC 3611.
7. Acknowledgements 7. Acknowledgements
Thanks to Ray van Brandenburg, Claire Bi,Colin Perkin,Roni Even and Thanks to Ray van Brandenburg, Claire Bi, Colin Perkin, Roni Even,
Dan Romascanufor useful review and suggestions. Dan Romascanu and Ali Begen for useful review and 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
 End of changes. 35 change blocks. 
68 lines changed or deleted 61 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/