draft-ietf-xrblock-rtcp-xr-decodability-11.txt   draft-ietf-xrblock-rtcp-xr-decodability-12.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: October 9, 2013 H. Asaeda Expires: December 2, 2013 H. Asaeda
NICT NICT
G. Zorn G. Zorn
Network Zen Network Zen
April 7, 2013 May 31, 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-11 draft-ietf-xrblock-rtcp-xr-decodability-12
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 not dependent on Program specific in the RTCP XR Block are not dependent on Program specific
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 October 9, 2013. This Internet-Draft will expire on December 2, 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 37 skipping to change at page 2, line 37
4.1. SDP rtcp-xr-attrib 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 . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 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
skipping to change at page 9, line 7 skipping to change at page 9, line 7
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 There might be some relationship between reported error counters and
considerations beyond those described in RFC 3611. contractual Service Level Agreements (SLA)s and hence an attack
(e.g., RTP endpoints report fake information, or an attacker in the
path modifies the data being reported ) may deliberately corrupt
these error counters fields and will result in financial implications
for the network operator (either as a result of un-needed Performance
metrics, or penalty charges for SLA failure).
A solution to prevent such attack is to apply an authentication and
integrity protection framework for the RTCP XR report block. This
can be accomplished using the RTP profile that combines Secure RTP
[RFC3711] and AVPF into SAVPF [RFC5124].
Besides this, the proposed RTCP XR report block in this document
introduces no other new security considerations beyond those
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 Perkin, Roni Even,
Dan Romascanu, Ali Begen and Alan Clark for useful review and Dan Romascanu, Ali Begen and Alan Clark for useful review and
suggestions. suggestions.
8. References 8. References
8.1. Normative References 8.1. Normative References
skipping to change at page 9, line 34 skipping to change at page 9, line 48
[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, Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003. November 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
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
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008.
8.2. Informative References 8.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", pictures and associated audio information: Systems",
ISO 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,
 End of changes. 8 change blocks. 
7 lines changed or deleted 29 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/