Network Working Group J. Xia
Internet-Draft Huawei
Intended status: Standards Track G. Zorn
Expires: March 18, 2012 Network Zen
Q. Wu
Huawei
R. Schott
Deutsche Telekom
September 15, 2011

RTCP XR Blocks for layered Stream statistics metric reporting
draft-xia-xrblock-rtcp-xr-layered-statistics-01

Abstract

This document defines an RTCP XR Report Block and associated SDP parameters that allow the reporting of layered stream statistics metrics for use in a range of RTP applications.

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 March 18, 2012.

Copyright Notice

Copyright (c) 2011 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 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.

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.


Table of Contents

1. Introduction

This draft defines a new block type to augment those defined in [RFC3611], for use in a range of RTP applications.

The new block type provides layered streams statistics beyond the information carried in the Statistics Summary Report Block RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. Information is recorded about lost layered component packets, duplicated layered component packets.

The metrics belong to the class of transport level metrics defined in [MONARCH] (work in progress).

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].

In addition, the following terms are defined:

Layered Component Packet


a RTP packet using layered codecs containing the specified layered component, e.g., encoded stream at the base layer or at the enhancement layer.

3. Applicability

Layered Streams Statistics Metrics Block can be applied to any real time applications that use layered or multi-description video coding.

4. Layered Streams Statistics Metrics Block

Metrics in this block report on lost packets, duplicated packets in the layered stream arriving at the RTP system.

4.1. Metric Block Structure

The report block contents are dependent upon a series of flag bits carried in the first part of the header. Not all parameters need to be reported in each block. Flags indicate which are and which are not reported. The fields corresponding to unreported parameters MUST be present, but are set to zero. The receiver MUST ignore any Perceptual Quality Metrics Block with a non-zero value in any field flagged as unreported.

   
    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    |I|T|D|   rsd.  |        block length           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        SSRC of source                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          begin_seq            |             end_seq           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                 Lost_Layered Component Packets                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Dup Layered Component_Packets                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Layered Stream Statistics metrics Block has the following format:

4.2. Definition of Fields in layered stream statistics Metrics Block

Block type (BT): 8 bits

The Layered stream Statistics Metrics Block is identified by the constant <LSSM>.

Interval Metric flag (I): 1 bit


This field is used to indicate whether the Basic Loss/Discard metrics are Interval or Cumulative metrics, that is, whether the reported values applies to the most recent measurement interval duration between successive metrics reports (I=1) (the Interval Duration) or to the accumulation period characteristic of cumulative measurements (I=0) (the Cumulative Duration).

Layer Type flag (T): 1 bit

This field is used to indicate the Layer Type of layered video to be reported. LT is set to 0 if the loss_component_packet field and dup_component packet contain the base layer packet in layered codecs,e.g, SVC in [RFC6190], 1 if the loss_component packet field and dup_component packet contain enhancement layer packet in layered codec.

Layer Dependency (D): 1 bit


This field is used to indicate the layer dependency between different enhancement layers if there is more than one enhancement layers. D is set to 0 if there is no layer dependency between different enhancement layers, 1 if there is layer dependency between different enhancement layers.

Rsd.: 5 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 MUST be ignored by the receiver.

Block length: 16 bits

The constant 3, in accordance with the definition of this field in Section 3 of RFC 3611 [RFC3611].

begin_seq: 16 bits

As defined in Section 4.1 of RFC 3611 [RFC3611].

end_seq: 16 bits

As defined in Section 4.1 of RFC 3611 [RFC3611].

Lost_Layered Component Packets: 32 bits

Number of lost_component packets in the above sequence number interval.

Dup_Layered Component Packets: 32 bits

Number of dup_component packets in the above sequence number interval.

5. SDP Signaling

  rtcp-xr-attrib =  "a=rtcp-xr:"
                    [xr-format *(SP xr-format)] CRLF
        xr-format = layered-stream-stat-metrics
           layered-stream-stat-metrics = "layered-stream-stat-metrics"
                                ["=" stat-flag *("," stat-flag)]
                 stat-flag = "base layer packet"
                             / "enhancment layer packet"

One new parameter is defined for the report block defined in this document to be used with Session Description Protocol (SDP) [RFC4566] using the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the following syntax within the "rtcp-xr" attribute [RFC3611]: RFC 3611 [RFC3611] for a detailed description and the full syntax of the "rtcp-xr" attribute.

6. IANA Considerations

Qin Wu
sunseawq@huawei.com
101 Software Avenue, Yuhua District 
Nanjing, JiangSu 210012 China

New report block type for RTCP XR is subject to IANA registration. For general guidelines on IANA allocations for RTCP XR, refer to Section 6.2 of [RFC3611].

This document assigns one new block type value in the RTCP XR Block Type Registry: [RFC4566] parameter for the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry:

The contact information for the registrations is:

This document also registers one new SDP

7. Security Considerations

The new RTCP XR report blocks proposed in this document introduces no new security considerations beyond those described in [RFC3611].

8. Acknowledgements

The authors would like to thank Bill Ver Steeg, David R Oran, Ali Begen,Colin Perkins, Roni Even,Youqing Yang, Wenxiao Yu and Yinliang Hu for their valuable comments and suggestions on this document.

9. References

9.1. Normative References

[RFC6190] Wenger, S, Wang, Y, Schierl, T and A Eleftheriadis, "RTP Payload Format for Scalable Video Coding", RFC 6190, May 2011.
[RFC3611] Friedman, T., Caceres, R. and A. Clark, "RTP Control Protocol Extended Reports (RTCP XR)", RFC 3611, November 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4566] Handley, M., Jacobson, V. and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003.

9.2. Informative References

[MONARCH] Wu, Q., "Monitoring Architectures for RTP", ID draft-ietf-avtcore-monarch-00, April 2011.

Appendix A. Change Log

Appendix A.1. draft-xia-xrblock-rtcp-xr-layered-statistics-01

The following are the major changes compared to previous version 00:

Authors' Addresses

Jinwei Xia Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China EMail: xiajinwei@huawei.com
Glen Zorn Network Zen 77/440 Soi Phoomjit, Rama IV Road Phra Khanong, Khlong Toie Bangkok, 10110 Thailand Phone: +66 (0) 87 502 4274 EMail: gwz@net-zen.net
Qin Wu Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China EMail: sunseawq@huawei.com
Roland Schott Deutsche Telekom Deutsche-Telekom-Allee 7 Darmstadt, 64295 Germany EMail: Roland.Schott@telekom.de