draft-ietf-xrblock-rtcp-xr-loss-conceal-02.txt   draft-ietf-xrblock-rtcp-xr-loss-conceal-03.txt 
Network Working Group C. Bi Network Working Group C. Bi
Internet-Draft STTRI Internet-Draft STTRI
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: January 3, 2013 Telchemy Expires: April 25, 2013 Telchemy
G. Hunt G. Hunt
Unaffiliated Unaffiliated
Q. Wu Q. Wu
Huawei Huawei
G. Zorn, Ed. G. Zorn, Ed.
Network Zen Network Zen
July 2, 2012 October 22, 2012
RTCP XR Report Block for Loss Concealment Metric Reporting RTCP XR Report Block for Loss Concealment Metric Reporting
draft-ietf-xrblock-rtcp-xr-loss-conceal-02.txt draft-ietf-xrblock-rtcp-xr-loss-conceal-03.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of loss concealment metrics primarily for audio reporting of loss concealment metrics primarily for audio
applications of RTP. applications of 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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 January 3, 2013. This Internet-Draft will expire on April 25, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 15 skipping to change at page 2, line 15
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 1.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3
1.2. Loss Concealment Report Block . . . . . . . . . . . . . . . 3 1.2. Loss Concealment Report Block . . . . . . . . . . . . . . . 3
1.3. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.3. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4
1.4. Performance Metrics Framework . . . . . . . . . . . . . . . 4 1.4. Performance Metrics Framework . . . . . . . . . . . . . . . 4
1.5. Applicability . . . . . . . . . . . . . . . . . . . . . . . 4 1.5. Applicability . . . . . . . . . . . . . . . . . . . . . . . 4
2. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 4 2. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 4
2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4
2.2. Definition of Fields in Loss Concealment Report Block . . . 4 2.2. Definition of Fields in Loss Concealment Report Block . . . 5
3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . . 8 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . . 8
4.3. Contact Information for Registrations . . . . . . . . . . . 8 4.3. Contact Information for Registrations . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
1.1. Standards Language 1.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 3, line 43 skipping to change at page 3, line 43
these periods was not available due to packet loss or discard. A these periods was not available due to packet loss or discard. A
similar metric (Buffer Adjustment Concealment Duration) reports the similar metric (Buffer Adjustment Concealment Duration) reports the
duration of playout of locally-manufactured data replacing data duration of playout of locally-manufactured data replacing data
unavailable due to adaptation of an adaptive de-jitter buffer. unavailable due to adaptation of an adaptive de-jitter buffer.
Further metrics (Playout Interrupt Count and Mean Playout Interrupt Further metrics (Playout Interrupt Count and Mean Playout Interrupt
Size) report the number of times normal playout was interrupted, and Size) report the number of times normal playout was interrupted, and
the mean duration of these interruptions. the mean duration of these interruptions.
Loss Concealment Duration and Buffer Adjustment Concealment Duration Loss Concealment Duration and Buffer Adjustment Concealment Duration
are reported separately because buffer adjustment is typically are reported separately because buffer adjustment is typically
arranged to occur in silence periods so may have very little impact arranged to occur in silence periods and so may have very little
on user experience, whilst loss concealment may occur at any time. impact on user experience, whilst loss concealment may occur at any
time.
The metric belongs to the class of transport-related terminal metrics The metric belongs to the class of transport-related terminal metrics
defined in Wu, et al. [I-D.ietf-avtcore-monarch]. defined in Wu, et al. [I-D.ietf-avtcore-monarch].
1.3. RTCP and RTCP XR Reports 1.3. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in Schulzrinne, et The use of RTCP for reporting is defined in Schulzrinne, et
al. [RFC3550]. Friedman, Cacares & Clark [RFC3611] define an al. [RFC3550]. Friedman, Cacares & Clark [RFC3611] define an
extensible structure for reporting using an RTCP Extended Report extensible structure for reporting using an RTCP Extended Report
(XR). This draft defines a new Extended Report block that MUST be (XR). This draft defines a new Extended Report block that MUST be
skipping to change at page 7, line 46 skipping to change at page 8, line 11
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
3. SDP Signaling 3. SDP Signaling
The use of the Session Description Protocol (SDP) [RFC4566] for The use of the Session Description Protocol (SDP) [RFC4566] for
signaling the use of XR blocks is described in RFC 3611. XR blocks signaling the use of XR blocks is described in RFC 3611. XR blocks
MAY be used without prior signaling. MAY be used without prior signaling.
This section augments the SDP attribute "rtcp-xr" [RFC3611] by This section augments the SDP attribute "rtcp-xr" defined in Section
providing an additional value of "xr-format" to signal the use of the 5.1 of RFC 3611 by providing an additional value of "xr-format" to
report block defined in this document. signal the use of the report block defined in this document.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in RFC 3611) (defined in RFC 3611)
xr-format =/ xr-conceal-block xr-format =/ xr-conceal-block
xr-conceal-block = "loss-conceal" xr-conceal-block = "loss-conceal"
4. IANA Considerations 4. IANA Considerations
skipping to change at page 9, line 39 skipping to change at page 9, line 47
(RTCP XR)", RFC 3611, November 2003. (RTCP XR)", RFC 3611, November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. [RFC4566] Handley, M., Jacobson, V., and C.
Perkins, "SDP: Session Description Perkins, "SDP: Session Description
Protocol", RFC 4566, July 2006. Protocol", RFC 4566, July 2006.
7.2. Informative References 7.2. Informative References
[I-D.ietf-avtcore-monarch] Wu, W., Hunt, G., and P. Arden, [I-D.ietf-avtcore-monarch] Wu, W., Hunt, G., and P. Arden,
"Guidelines for Use of the RTP Monitoring "Guidelines for Use of the RTP Monitoring
Framework", draft-ietf-avtcore-monarch-17 Framework", draft-ietf-avtcore-monarch-22
(work in progress), June 2012. (work in progress), September 2012.
[RFC6390] Clark, A. and B. Claise, "Guidelines for [RFC6390] Clark, A. and B. Claise, "Guidelines for
Considering New Performance Metric Considering New Performance Metric
Development", BCP 170, RFC 6390, Development", BCP 170, RFC 6390,
October 2011. October 2011.
Authors' Addresses Authors' Addresses
Claire Bi Claire Bi
Shanghai Research Institure of China Telecom Corporation Limited Shanghai Research Institure of China Telecom Corporation Limited
 End of changes. 10 change blocks. 
15 lines changed or deleted 16 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/