draft-ietf-xrblock-rtcp-xr-loss-conceal-10.txt   draft-ietf-xrblock-rtcp-xr-loss-conceal-11.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track G. Zorn Intended status: Standards Track G. Zorn
Expires: September 18, 2014 Network Zen Expires: September 30, 2014 Network Zen
C. Bi C. Bi
STTRI STTRI
Q. Wu, Ed. Q. Wu, Ed.
Huawei Huawei
March 17, 2014 March 29, 2014
RTCP XR Report Block for Concealment metrics Reporting on Audio RTCP XR Report Block for Concealment metrics Reporting on Audio
Applications Applications
draft-ietf-xrblock-rtcp-xr-loss-conceal-10.txt draft-ietf-xrblock-rtcp-xr-loss-conceal-11.txt
Abstract Abstract
This document defines two RTCP XR Report Blocks that allows the This document defines two RTCP XR Report Blocks that allows the
reporting of concealment metrics for audio applications of RTP. reporting of concealment metrics for audio 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 September 18, 2014. This Internet-Draft will expire on September 30, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 40 skipping to change at page 2, line 40
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 17 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 17
6.3. Contact information for registrations . . . . . . . . . . 17 6.3. Contact information for registrations . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 19
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.1. Normative References . . . . . . . . . . . . . . . . . . . 21 10.1. Normative References . . . . . . . . . . . . . . . . . . . 21
10.2. Informative References . . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Metrics represented using RFC6390 Template . . . . . 22 Appendix A. Metrics represented using RFC6390 Template . . . . . 22
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 29 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 29
B.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-09 . . . . . . . . 29 B.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-11 . . . . . . . . 29
B.2. draft-ietf-xrblock-rtcp-xr-loss-conceal-07 . . . . . . . . 29 B.2. draft-ietf-xrblock-rtcp-xr-loss-conceal-09 . . . . . . . . 29
B.3. draft-ietf-xrblock-rtcp-xr-loss-conceal-06 . . . . . . . . 29 B.3. draft-ietf-xrblock-rtcp-xr-loss-conceal-07 . . . . . . . . 29
B.4. draft-ietf-xrblock-rtcp-xr-loss-conceal-05 . . . . . . . . 29 B.4. draft-ietf-xrblock-rtcp-xr-loss-conceal-06 . . . . . . . . 29
B.5. draft-ietf-xrblock-rtcp-xr-loss-conceal-04 . . . . . . . . 29 B.5. draft-ietf-xrblock-rtcp-xr-loss-conceal-05 . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 B.6. draft-ietf-xrblock-rtcp-xr-loss-conceal-04 . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
1.1. Loss Concealment and Concealment Seconds Metrics Reporting Block 1.1. Loss Concealment and Concealment Seconds Metrics Reporting Block
At any instant, the audio output at a receiver may be classified as At any instant, the audio output at a receiver may be classified as
either 'normal' or 'concealed'. 'Normal' refers to playout of audio either 'normal' or 'concealed'. 'Normal' refers to playout of audio
payload received from the remote end, and also includes locally payload received from the remote end, and also includes locally
generated signals such as announcements, tones and comfort noise. generated signals such as announcements, tones and comfort noise.
Concealment refers to playout of locally-generated signals used to Concealment refers to playout of locally-generated signals used to
skipping to change at page 3, line 48 skipping to change at page 3, line 48
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 so may have very little impact
on user experience, whilst loss concealment may occur at any time. on user experience, whilst loss concealment may occur at any time.
The second block type provides metrics for concealment seconds, which The second block type provides metrics for concealment seconds, which
are measured at the receiving end of the RTP stream. Specifically, are measured at the receiving end of the RTP stream. Specifically,
the first metric (Unimpaired Seconds) reports the number of whole the first metric (Unimpaired Seconds) reports the number of whole
seconds occupied only with normal playout of data which the receiver seconds occupied only with normal playout of data which the receiver
obtained from the sender's stream. The second metric (Concealed obtained from the sender's stream. The second metric (Concealed
Seconds) reports the number of whole seconds during which the Seconds) reports the number of whole seconds during which the
receiver played out any locally-generated media data. A third metric receiver played out any locally-generated media data. A third
(Severely Concealed Seconds) reports the number of whole seconds metric, Severely Concealed Seconds (SCS), reports the number of whole
during which the receiver played out locally-generated data for more seconds during which the receiver played out locally-generated data
than SCS Threshold. for more than SCS Threshold.
These metrics belongs to the class of transport-related terminal These metrics belongs to the class of transport-related terminal
metrics defined in [RFC6792]. metrics defined in [RFC6792].
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 draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611]. MUST be used as defined in [RFC3550] and [RFC3611].
skipping to change at page 7, line 18 skipping to change at page 7, line 18
metrics are Sampled, Interval or Cumulative metrics: metrics are Sampled, Interval or Cumulative metrics:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value ( Not allowed in this block).
I=00: Reserved value- this value is reserved for future use.
In this document, Loss Concealment Metrics can only be measured In this document, Loss Concealment Metrics can only be measured
over definite intervals, and cannot be sampled. Also, the value over definite intervals, and cannot be sampled. Senders MUST NOT
I=00 is reserved for future use. Senders MUST NOT use the values use the values I=00 or I=01. If a block is received with I=00 or
I=00 or I=01. If a block is received with I=00 or I=01, the I=01, the receiver MUST discard the block.
receiver MUST discard the block.
Packet Loss Concealment Method (plc): 2 bits Packet Loss Concealment Method (plc): 2 bits
This field is used to identify the packet loss concealment method This field is used to identify the packet loss concealment method
in use at the receiver, according to the following code: in use at the receiver, according to the following code:
bits 014-015 bits 014-015
0 = silence insertion 0 = silence insertion
skipping to change at page 12, line 31 skipping to change at page 12, line 31
Metrics are Sampled, Interval or Cumulative metrics: Metrics are Sampled, Interval or Cumulative metrics:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value (Not allowed in this block).
I=00: Reserved value- this value is reserved for future use.
In this document, Concealment Seconds Metrics can only be measured In this document, Concealment Seconds Metrics can only be measured
over definite intervals, and cannot be sampled. Also, the value over definite intervals, and cannot be sampled. Senders MUST NOT
I=00 is reserved for future use. Senders MUST NOT use the values use the values I=00 or I=01. If a block is received with I=00 or
I=00 or I=01. If a block is received with I=00 or I=01, the I=01, the receiver MUST discard the block.
receiver MUST discard the block.
Packet Loss Concealment Method (plc): 2 bits Packet Loss Concealment Method (plc): 2 bits
This field is used to identify the packet loss concealment method This field is used to identify the packet loss concealment method
in use at the receiver, according to the following code: in use at the receiver, according to the following code:
bits 014-015 bits 014-015
0 = silence insertion 0 = silence insertion
1 = simple replay, no attenuation 1 = simple replay, no attenuation
skipping to change at page 15, line 44 skipping to change at page 15, line 44
These bits are reserved. They MUST be set to zero by senders and These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (See [RFC6709] section 4.2). ignored by receivers (See [RFC6709] section 4.2).
SCS Threshold: 8 bits SCS Threshold: 8 bits
The SCS Threshold is defined as the percentage of packets The SCS Threshold is defined as the percentage of packets
corresponding to lost or discarded frames that must occur within a corresponding to lost or discarded frames that must occur within a
one second period in order for the second to be classified as a one second period in order for the second to be classified as a
Severely Concealed Second. This is expressed in numeric format Severely Concealed Second. This is expressed in numeric format
0:8 and hence can represent a range of 0.1 to 25.5 percent loss or 0:8 and hence can represent a range of 0 to 99.6 percent loss or
discard. discard.
A default threshold of 5% effective frame loss (50ms effective A default threshold of 5% effective frame loss (50ms effective
frame loss ) per second is suggested. frame loss ) per second is suggested. This corresponds to an SCS
Threshold in hexadecimal of 0x0D.
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling. without prior signaling.
5.1. SDP rtcp-xr-attrib Attribute Extension 5.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP attribute "rtcp-xr" [RFC3611] by This section augments the SDP attribute "rtcp-xr" [RFC3611] by
skipping to change at page 20, line 12 skipping to change at page 20, line 12
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
9. Acknowledgements 9. Acknowledgements
The authors gratefully acknowledge reviews and feedback provided by The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada and Alissa Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada ,Alissa
Cooper. Cooper,Meral Shirazipour and MORTON, ALFRED C (AL).
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", 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.
skipping to change at page 29, line 10 skipping to change at page 29, line 10
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix B. Change Log Appendix B. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-09 B.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-11
The following are the major changes to previous version :
o Address comments recieved in Gen-Art Review and OPS-DIR Review.
B.2. draft-ietf-xrblock-rtcp-xr-loss-conceal-09
The following are the major changes to previous version : The following are the major changes to previous version :
o Only Version Number changes. o Only Version Number changes.
B.2. draft-ietf-xrblock-rtcp-xr-loss-conceal-07 B.3. draft-ietf-xrblock-rtcp-xr-loss-conceal-07
The following are the major changes to previous version : The following are the major changes to previous version :
o Change units for threshold and units used for reporting in loss o Change units for threshold and units used for reporting in loss
concealment block and concealment seconds block. concealment block and concealment seconds block.
o Change 16bit "Mean Playout Interrupt Size" into 32bits. o Change 16bit "Mean Playout Interrupt Size" into 32bits.
B.3. draft-ietf-xrblock-rtcp-xr-loss-conceal-06 B.4. draft-ietf-xrblock-rtcp-xr-loss-conceal-06
The following are the major changes to previous version : The following are the major changes to previous version :
o Comments in the WGLC are addressed in this version. o Comments in the WGLC are addressed in this version.
B.4. draft-ietf-xrblock-rtcp-xr-loss-conceal-05 B.5. draft-ietf-xrblock-rtcp-xr-loss-conceal-05
The following are the major changes to previous version : The following are the major changes to previous version :
o Add text to clarify the definition of enhanced method. o Add text to clarify the definition of enhanced method.
o Add appendix to apply RFC6390 template to the metrics. o Add appendix to apply RFC6390 template to the metrics.
B.5. draft-ietf-xrblock-rtcp-xr-loss-conceal-04 B.6. draft-ietf-xrblock-rtcp-xr-loss-conceal-04
The following are the major changes to previous version : The following are the major changes to previous version :
o Merge Concealment Seconds draft into this draft (i.e.,Loss o Merge Concealment Seconds draft into this draft (i.e.,Loss
Concealment draft). Concealment draft).
o Updated references. o Updated references.
Authors' Addresses Authors' Addresses
 End of changes. 18 change blocks. 
33 lines changed or deleted 43 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/