Network Working Group R. Huang Internet-Draft Q. Wu Intended status: Standards Track Huawei Expires: April 21, 2013 H. Asaeda NICT G. Zorn, Ed. Network Zen October 18, 2012 RTP Control Protocol (RTCP) Extended Report (XR) Block for TS Decodability Statistics Metric reporting draft-ietf-xrblock-rtcp-xr-decodability-01 Abstract Transport Stream (TS) is a standard container format used in the transmission and storage of multimedia data. Unicast/Multicast/ Broadcast MPEG-TS over RTP is widely deployed in IPTV systems. This document defines an RTP Control Protocol (RTCP) Extended Report (XR) Block that allows the reporting of decodability statistics metrics related to transmissions of MPEG-TS over RTP. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on April 21, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Huang, et al. Expires April 21, 2013 [Page 1] Internet-Draft RTCP XR Decodability Report Blocks October 2012 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 3. TR 101 290 Decodability Statistics Metric Report Block . . . . 3 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. SDP rtcp-xr-attrib Atrribute Extension . . . . . . . . . . 6 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Huang, et al. Expires April 21, 2013 [Page 2] Internet-Draft RTCP XR Decodability Report Blocks October 2012 1. Introduction The European Telecommunications Standards Institute (ETSI) has defined a set of syntax and information consistency tests and corresponding indicators [ETSI] that are recommended for the monitoring of MPEG-2 Transport Streams [ISO-IEC.13818-1.2007]. The tests and corresponding indicators are grouped according to priority: o First priority - Necessary for de-codability (basic monitoring) o Second priority - Recommended for continuous or periodic monitoring o Third priority - Recommended for application-dependant monitoring This draft is based on information consistency tests and resulting indicators defined by ETSI [ETSI] and defines a new block type to augment those defined in Freidman, et al. [RFC3611] for use with Transport Stream (TS) [ISO-IEC.13818-1.2007]. The new block type supports reporting of the number of occurances of each indicator in the first and second priorities; third priority indicators are not supported. This new block type can be useful for measuring content stream or TS quality by checking TS header information [ETSI] and identifying the existence, and characterizing the severity, of bitstream packetization problems which may affect users' perception of a service delivered over RTP; it may also be useful for verifying the continued correct operation of an existing management system. The new report block is in compliance with the monitoring architecture specified in Wu, et al. [MONARCH] and the Performance Metrics Framework [RFC6390]. The metric is applicable to any type of RTP application that uses the TS standard format for multimedia data; for example, MPEG4 TS content over RTP. 2. Terminology 2.1. Standards Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. TR 101 290 Decodability Statistics Metric Report Block This block reports decodability statistics metrics beyond the information carried in the standard RTCP packet format. It defines eight metrics based on ETSI TR 101 290. Information is reported about basic monitoring parameters necessary to ensure that the TS can Huang, et al. Expires April 21, 2013 [Page 3] Internet-Draft RTCP XR Decodability Report Blocks October 2012 be decoded including: o Transport Stream Synchronization Losses o Sync byte errors o Continuity count errors and continuous monitoring parameters including: o Transport errors o Program Clock Reference (PCR) errors o PCR repetition errors o PCR discontinuity indicator errors o Presentation Time Stamp (PTS) errors The other parameters are ignored since they do not apply to all MPEG implementations. For further information on these parameters, see [ETSI]. The Decodability Metrics Block has the following format: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=TBD | Reserved | block length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | begin_seq | end_seq | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of TSs | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TS_sync_loss_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sync_byte_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Continuity_count_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Transport_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PCR_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PCR_repetition_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PCR_discontinuity_indicator_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PTS_error_count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Huang, et al. Expires April 21, 2013 [Page 4] Internet-Draft RTCP XR Decodability Report Blocks October 2012 block type (BT): 8 bits A TR 101 290 decodability metrics report block is identified by the constant . Reserved: 8 bits This field is reserved for future definition. In the absence of such a definition, the bits in this field MUST be set to zero and SHOULD be ignored by the receiver. block length: 16 bits The constant 11, in accordance with the definition of this field in Section 3 of RFC 3611. SSRC of source: 32 bits As defined in Section 4.1 of RFC 3611. begin_seq: 16 bits As defined in Section 4.1 of RFC 3611. end_seq: 16 bits 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 Number of TS_sync_loss errors in the above sequence number interval. Sync_byte_error_count: 32 bits Number of sync_byte_errors in the above sequence number interval. Continuity_count_error_count: 32 bits Number of Continuity_count_errors in the above sequence number interval. Huang, et al. Expires April 21, 2013 [Page 5] Internet-Draft RTCP XR Decodability Report Blocks October 2012 Transport_error_count: 32 bits Number of Transport_errors in the above sequence number interval. PCR_error_count: 32 bits Number of PCR_errors in the above sequence number interval. PCR_repetition_error_count: 32 bits Number of PCR_repetition_errors in the above sequence number interval. PCR_discontinuity_indicator_error_count: 32 bits Number of PCR_discontinuity_indicator_errors in the above sequence number interval. PTS_error_count: 32 bits Number of PTS_errors in the above sequence number interval. 4. SDP Signaling RFC 3611 defines the use of SDP (Session Description Protocol) [RFC4566] for signaling the use of RTCP XR blocks. XR blocks MAY be used without prior signaling. 4.1. SDP rtcp-xr-attrib Atrribute Extension 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 signal the use of the report block defined in this document. xr-format =/ decodability-metrics decodability-metrics = "decodability-metrics" 4.2. Offer/Answer Usage When SDP is used in offer-answer context, the SDP Offer/Answer usage defined in RFC 3611 applies. Huang, et al. Expires April 21, 2013 [Page 6] Internet-Draft RTCP XR Decodability Report Blocks October 2012 5. IANA Considerations New report block types for RTCP XR are subject to IANA registration. For general guidelines on IANA allocations for RTCP XR, refer to Section 6.2 ofRFC 3611. This document assigns one new block type value in the RTCP XR Block Type Registry: Name: TDM Long Name: TR 101 290 Decodability Metrics Value Reference: Section 3 This document also registers one SDP [RFC4566] parameters for the "rtcp-xr" attribute in the RTCP XR SDP Parameter Registry: * "decodability-metrics" The contact information for the registrations is: Rachel Huang rachel.huang@huawei.com 101 Software Avenue, Yuhua District Nanjing, JiangSu 210012 China 6. Security Considerations This proposed RTCP XR report block introduces no new security considerations beyond those described in RFC 3611. 7. Acknowledgements Thanks to Ray van Brandenburg for useful review and suggestions. 8. References 8.1. Normative References [ETSI] ETSI, "Digital Video Broadcasting (DVB); Measurement guidelines for DVB systems", Technical Report TR 101 290, 2001. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Huang, et al. Expires April 21, 2013 [Page 7] Internet-Draft RTCP XR Decodability Report Blocks October 2012 [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol Extended Reports (RTCP XR)", RFC 3611, November 2003. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006. 8.2. Informative References [ISO-IEC.13818-1.2007] International Organization for Standardization, "Information technology - Generic coding of moving pictures and associated audio information: Systems", ISO International Standard 13818-1, October 2007. [MONARCH] Wu, Q., Hunt, G., and P. , "Monitoring Architectures for RTP", ID draft-ietf-avtcore-monarch-22, September 2012. [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New Performance Metric Development", BCP 170, RFC 6390, October 2011. Authors' Addresses Rachel Huang Huawei 101 Software Avenue, Yuhua District Nanjing 210012 China Email: rachel.huang@huawei.com Qin Wu Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China Email: bill.wu@huawei.com Huang, et al. Expires April 21, 2013 [Page 8] Internet-Draft RTCP XR Decodability Report Blocks October 2012 Hitoshi Asaeda National Institute of Information and Communications Technology 4-2-1 Nukui-Kitamachi Koganei, Tokyo 184-8795 Japan Email: asaeda@nict.go.jp Glen Zorn (editor) Network Zen 227/358 Thanon Sanphawut Bang Na, Bangkok 10260 Thailand Phone: +66 (0) 909-201060 Email: glenzorn@gmail.com Huang, et al. Expires April 21, 2013 [Page 9]