draft-ietf-xrblock-rtcp-xr-loss-conceal-03.txt   draft-ietf-xrblock-rtcp-xr-loss-conceal-04.txt 
Network Working Group C. Bi Audio/Video Transport Working Group A. Clark
Internet-Draft STTRI Internet-Draft Telchemy
Intended status: Standards Track A. Clark Intended status: Standards Track G. Zorn, Ed.
Expires: April 25, 2013 Telchemy Expires: July 28, 2013 Network Zen
G. Hunt C. Bi
Unaffiliated STTRI
Q. Wu Q. Wu, Ed.
Huawei Huawei
G. Zorn, Ed. January 24, 2013
Network Zen
October 22, 2012
RTCP XR Report Block for Loss Concealment Metric Reporting RTCP XR Report Block for Concealment metrics Reporting on Audio
draft-ietf-xrblock-rtcp-xr-loss-conceal-03.txt Applications
draft-ietf-xrblock-rtcp-xr-loss-conceal-04.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines two RTCP XR Report Blocks that allows the
reporting of loss concealment metrics primarily for audio reporting of loss concealment metrics 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 April 25, 2013. This Internet-Draft will expire on July 28, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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. Loss Concealment and Concealment Seconds Metrics
1.2. Loss Concealment Report Block . . . . . . . . . . . . . . . 3 Reporting Block . . . . . . . . . . . . . . . . . . . . . 3
1.3. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4
1.4. Performance Metrics Framework . . . . . . . . . . . . . . . 4 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4
1.5. Applicability . . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
2.2. Definition of Fields in Loss Concealment Report Block . . . 5 3. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 6
3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 3.2. Definition of Fields in Loss Concealment Report Block . . 6
4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8 4. Concealment Seconds Block . . . . . . . . . . . . . . . . . . 10
4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . . 8 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 10
4.3. Contact Information for Registrations . . . . . . . . . . . 8 4.2. Definition of Fields in Concealed Seconds Metrics Block . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 9 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 15
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . . 9 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 16
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 16
6.3. Contact information for registrations . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 18
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21
A.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-04 . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
1.1. Standards Language 1.1. Loss Concealment and Concealment Seconds Metrics Reporting Block
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].
1.2. Loss Concealment Report Block
This draft defines a new block type to augment those defined in
Friedman, et al. [RFC3611] for use in a range of RTP applications.
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
mask the impact of network impairments or to reduce the audibility of mask the impact of network impairments or to reduce the audibility of
jitter buffer adaptations. jitter buffer adaptations.
The new block type provides metrics for actions taken by the receiver This draft defines two new concealment related block types to augment
to mitigate the effect of packet loss and packet discard. those defined in [RFC3611] for use in a range of RTP applications.
The first block type provides metrics for actions taken by the
receiver to mitigate the effect of packet loss and packet discard.
Specifically, the first metric (On-Time Playout Duration) reports the Specifically, the first metric (On-Time Playout Duration) reports the
duration of normal playout of data which the receiver obtained from duration of normal playout of data which the receiver obtained from
the sender's stream. A second metric (Loss Concealment Duration) the sender's stream. A second metric (Loss Concealment Duration)
reports the total time during which the receiver played out media reports the total time during which the receiver played out media
data which was manufactured locally, because the sender's data for data which was manufactured locally, because the sender's data for
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 which
unavailable due to adaptation of an adaptive de-jitter buffer. is 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 and so may have very little arranged to occur in silence periods so may have very little impact
impact on user experience, whilst loss concealment may occur at any on user experience, whilst loss concealment may occur at any time.
time.
The metric belongs to the class of transport-related terminal metrics The second block type provides metrics for concealment.
defined in Wu, et al. [I-D.ietf-avtcore-monarch]. Specifically, the first metric (Unimpaired Seconds) reports the
number of whole seconds occupied only with normal playout of data
which the receiver obtained from the sender's stream. The second
metric (Concealed Seconds) reports the number of whole seconds during
which the receiver played out any locally-generated media data. A
third metric (Severely Concealed Seconds) reports the number of whole
seconds during which the receiver played out locally-generated data
for more than SCS Threshold (ms).
1.3. RTCP and RTCP XR Reports These metrics belongs to the class of transport-related terminal
metrics defined in [RFC6792].
The use of RTCP for reporting is defined in Schulzrinne, et 1.2. RTCP and RTCP XR Reports
al. [RFC3550]. Friedman, Cacares & Clark [RFC3611] define an
extensible structure for reporting using an RTCP Extended Report
(XR). This draft defines a new Extended Report block that MUST be
used as specified in RFC 3550 and RFC 3611.
1.4. Performance Metrics Framework The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended
Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611].
Clark & Claise [RFC6390] provides guidance on the definition and 1.3. Performance Metrics Framework
specification of performance metrics. Wu, et
al. [I-D.ietf-avtcore-monarch] provides guidelines for RTCP XR report
block formats. The report block defined in this document is in
accordance with those guidelines.
1.5. Applicability The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guideline for reporting
block format using RTCP XR. The Metrics Block described in this
document are in accordance with those guidelines.
This metric is primarily applicable to audio applications of RTP. 1.4. Applicability
EDITOR'S NOTE: are there metrics for concealment of transport errors
for video?
2. Loss Concealment Block These metrics are only applicable to audio applications of RTP.
2.1. Report Block Structure 2. Terminology
0 1 2 3 2.1. Standards Language
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=<NLC> | I |plc| resv | block length=5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| On-time Playout Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffer Adjustment Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Playout Interrupt Count | Mean Playout Interrupt Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Structure of the Loss Concealment Metrics Block 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 RFC2119 [RFC2119].
2.2. Definition of Fields in Loss Concealment Report Block 3. Loss Concealment Block
3.1. Report Block Structure
Loss Concealment metrics block
0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NLC | I |plc| rsv. | block length=5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| On-time Playout Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffer Adjustment Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Playout Interrupt Count | Mean Playout Interrupt Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure
3.2. Definition of Fields in Loss Concealment Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Loss Concealment Metrics Report Block is identified by the A Loss Concealment Metrics Report Block is identified by the
constant <NLC>. constant NLC.
[Note to RFC Editor: please replace <NLC> with the RTCP XR block [Note to RFC Editor: please replace NLC with the IANA provided
type allocated by IANA for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bits Interval Metric flag (I): 2 bit
This field is used to indicate whether the delay metrics are This field is used to indicate whether the Loss Concealment
sampled, interval or cumulative metrics, that is, whether the metrics are Sampled, Interval or Cumulative metrics:
reported values applies to the most recent measurement interval
duration between successive metrics reports (I=10) (the interval I=10: Interval Duration - the reported value applies to the
duration) or to the accumulation period characteristic of most recent measurement interval duration between successive
cumulative measurements (I=11) (the cumulative duration) or is a metrics reports.
sampled instantaneous value (I=01) (sampled value).
I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled
instantaneous value.
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 scheme: in use at the receiver, according to the following code:
00 = silence insertion bits 014-015
01 = simple replay, no attenuation 0 = silence insertion
10 = simple replay, with attenuation 1 = simple replay, no attenuation
11 = enhanced 2 = simple replay, with attenuation
3 = enhanced
Other values reserved
Reserved (resv): 4 bits Reserved (resv): 4 bits
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
SHOULD be ignored by receivers. ignored by receivers (See [RFC6709] section 4.2).
block length: 16 bits block length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the Loss Concealment block, the block length is equal to 5. the Loss Concealment block, the block length is equal to 5.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of RFC 3611. As defined in Section 4.1 of [RFC3611].
On-time Playout Duration (ms): 32 bits On-time Playout Duration (ms): 32 bits
'On-time' playout is the uninterrupted, in-sequence playout of 'On-time' playout is the uninterrupted, in-sequence playout of
valid decoded audio information originating from the remote valid decoded audio information originating from the remote
endpoint. This includes comfort noise during periods of remote endpoint. This includes comfort noise during periods of remote
talker silence if voice activity detection (VAD) is in use, and talker silence, if VAD is used, and locally generated or
locally generated or regenerated tones and announcements. regenerated tones and announcements.
An equivalent definition is that on-time playout is playout of any An equivalent definition is that on-time playout is playout of any
signal other than those used for concealment. signal other than those used for concealment.
On-time playout duration MUST include both speech and silence On-time playout duration MUST include both speech and silence
intervals, whether VAD is used or not. This duration is reported intervals, whether VAD is used or not. This duration is reported
in millisecond units. in millisecond units.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
reported.
Loss Concealment Duration (ms): 32 bits Loss Concealment Duration (ms): 32 bits
The duration, in milliseconds, of audio playout corresponding to The duration, in milliseconds, of audio playout corresponding to
loss-type concealment. Loss-type concealment.
Loss-type concealment is reactive insertion or deletion of samples Loss-type concealment is reactive insertion or deletion of samples
in the audio playout stream due to effective frame loss at the in the audio playout stream due to effective frame loss at the
audio decoder. "Effective frame loss" is the event in which a audio decoder. "Effective frame loss" is the event in which a
frame of coded audio is simply not present at the audio decoder frame of coded audio is simply not present at the audio decoder
when required. In this case, substitute audio samples are when required. In this case, substitute audio samples are
generally formed, at the decoder or elsewhere, to reduce audible generally formed, at the decoder or elsewhere, to reduce audible
impairment. impairment.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
reported.
Buffer Adjustment Concealment Duration (ms): 32 bits Buffer Adjustment Concealment Duration (ms): 32 bits
The duration, in milliseconds, of audio playout corresponding to The duration, in milliseconds, of audio playout corresponding to
buffer adjustment concealment, if known. Buffer Adjustment-type concealment, if known.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
reported.
Buffer adjustment concealment is proactive or controlled insertion Buffer Adjustment-type concealment is proactive or controlled
or deletion of samples in the audio playout stream due to jitter insertion or deletion of samples in the audio playout stream due
buffer adaptation, re-sizing or re-centering decisions within the to jitter buffer adaptation, re-sizing or re-centering decisions
endpoint. within the endpoint.
Because this insertion is controlled, rather than occurring Because this insertion is controlled, rather than occurring
randomly in response to losses, it is typically less audible than randomly in response to losses, it is typically less audible than
loss-type concealment. For example, jitter buffer adaptation loss-type concealment. For example, jitter buffer adaptation
events may be constrained to occur during periods of talker events may be constrained to occur during periods of talker
silence, in which case only silence duration is affected, or silence, in which case only silence duration is affected, or
sophisticated time-stretching methods for insertion/deletion sophisticated time-stretching methods for insertion/deletion
during favorable periods in active speech may be employed. during favorable periods in active speech may be employed.
Concealment events which cannot be classified as buffer adjustment Concealment events which cannot be classified as Buffer
MUST be classified as loss concealment. Adjustment- type MUST be classified as Loss-type.
Playout Interrupt Count: 16 bits Playout Interrupt Count: 16 bits
The number of interruptions to normal playout which occurred The number of interruptions to normal playout which occurred
during the reporting period. during the reporting period.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST 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 MUST be reported.
Mean Playout Interrupt Size (ms): 16 bits Mean Playout Interrupt Size (ms): 16 bits
The mean duration, in ms, of interruptions to normal playout which The mean duration, in ms, of interruptions to normal playout which
occurred during the reporting period. occurred during the reporting period.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST 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 MUST be reported.
3. SDP Signaling 4. Concealment Seconds Block
The use of the Session Description Protocol (SDP) [RFC4566] for This sub-block provides a description of potentially audible
signaling the use of XR blocks is described in RFC 3611. XR blocks impairments due to lost and discarded packets at the endpoint,
MAY be used without prior signaling. expressed on a time basis analogous to a traditional PSTN T1/E1
errored seconds metric.
This section augments the SDP attribute "rtcp-xr" defined in Section The following metrics are based on successive one second intervals as
5.1 of RFC 3611 by providing an additional value of "xr-format" to declared by a local clock. This local clock does NOT need to be
signal the use of the report block defined in this document. synchronized to any external time reference. The starting time of
this clock is unspecified. Note that this implies that the same loss
pattern could result in slightly different count values, depending on
where the losses occur relative to the particular one-second
demarcation points. For example, two loss events occurring 50ms
apart could result in either one concealed second or two, depending
on the particular 1000 ms boundaries used.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF The seconds in this sub-block are not necessarily calendar seconds.
At the tail end of a session, periods of time of less than 1000ms
shall be incorporated into these counts if they exceed 500ms and
shall be disregarded if they are less than 500ms.
(defined in RFC 3611) 4.1. Report Block Structure
Concealed Seconds metrics block
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=NCS | I |plc|Rserved| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unimpaired Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Concealed Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Severely Concealed Seconds | RESERVED | SCS Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure
4.2. Definition of Fields in Concealed Seconds Metrics Block
Block type (BT): 8 bits
A Concealed Seconds Metrics Report Block is identified by the
constant NCS.
[Note to RFC Editor: please replace NCS with the IANA provided
RTCP XR block type for this block.]
Interval Metric flag (I): 2 bit
This field is used to indicate whether the Concealment Seconds
metrics are Sampled, Interval or Cumulative metrics:
I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive
metrics reports.
I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled
instantaneous value.
Packet Loss Concealment Method (plc): 2 bits
This field is used to identify the packet loss concealment method
in use at the receiver, according to the following code:
bits 014-015
0 = silence insertion
1 = simple replay, no attenuation
2 = simple replay, with attenuation
3 = enhanced
Other values reserved
Reserved (resv): 4 bits
These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (See [RFC6709] section 4.2).
Block Length: 16 bits
The length of this report block in 32-bit words, minus one. For
the Concealment Seconds block, the block length is equal to 4.
SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611].
Unimpaired Seconds: 32 bits
A count of the number of unimpaired Seconds that have occurred.
An unimpaired Second is defined as a continuous period of 1000ms
during which no frame loss or discard due to late arrival has
occurred. Every second in a session must be classified as either
OK or Concealed.
Normal playout of comfort noise or other silence concealment
signal during periods of talker silence, if VAD [VAD] is used,
shall be counted as unimpaired seconds.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
Concealed Seconds: 32 bits
A count of the number of Concealed Seconds that have occurred.
A Concealed Second is defined as a continuous period of 1000ms
during which any frame loss or discard due to late arrival has
occurred.
Equivalently, a concealed second is one in which some Loss-type
concealment has occurred. Buffer adjustment-type concealment
SHALL not cause Concealed Seconds to be incremented, with the
following exception. An implementation MAY cause Concealed
Seconds to be incremented for 'emergency' buffer adjustments made
during talkspurts.
Loss-type concealment is reactive insertion or deletion of samples
in the audio playout stream due to effective frame loss at the
audio decoder. "Effective frame loss" is the event in which a
frame of coded audio is simply not present at the audio decoder
when required. In this case, substitute audio samples are
generally formed, at the decoder or elsewhere, to reduce audible
impairment.
Buffer Adjustment-type concealment is proactive or controlled
insertion or deletion of samples in the audio playout stream due
to jitter buffer adaptation, re-sizing or re-centering decisions
within the endpoint.
Because this insertion is controlled, rather than occurring
randomly in response to losses, it is typically less audible than
loss-type concealment. For example, jitter buffer adaptation
events may be constrained to occur during periods of talker
silence, in which case only silence duration is affected, or
sophisticated time-stretching methods for insertion/deletion
during favorable periods in active speech may be employed. For
these reasons, buffer adjustment-type concealment MAY be exempted
from inclusion in calculations of Concealed Seconds and Severely
Concealed Seconds.
However, an implementation SHOULD include buffer-type concealment
in counts of Concealed Seconds and Severely Concealed Seconds if
the event occurs at an 'inopportune' moment, with an emergency or
large, immediate adaptation during active speech, or for
unsophisticated adaptation during speech without regard for the
underlying signal, in which cases the assumption of low-audibility
cannot hold. In other words, jitter buffer adaptation events
which may be presumed to be audible SHOULD be included in
Concealed Seconds and Severely Concealed Seconds counts.
Concealment events which cannot be classified as Buffer
Adjustment- type MUST be classified as Loss-type.
For clarification, the count of Concealed Seconds MUST include the
count of Severely Concealed Seconds.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
MUST be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF MUST be reported.
Severely Concealed Seconds: 16 bits
A count of the number of Severely Concealed Seconds.
A Severely Concealed Second is defined as a non-overlapping period
of 1000 ms during which the cumulative amount of time that has
been subject to frame loss or discard due to late arrival, exceeds
the SCS Threshold.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be
reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF MUST be reported.
Reserved: 8 bits
These bits are reserved. They MUST be set to zero by senders and
ignored by receivers (See [RFC6709] section 4.2).
SCS Threshold: 8 bits
The SCS Threshold defines the amount of time corresponding to lost
or discarded frames that must occur within a one second period in
order for the second to be classified as a Severely Concealed
Second. This is expressed in milliseconds and hence can represent
a range of 0.1 to 25.5 percent loss or discard.
A default threshold of 50ms (5% effective frame loss per second)
is suggested.
5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling.
5.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP attribute "rtcp-xr" [RFC3611] by
providing two additional values of "xr-format" to signal the use of
the report block defined in this document.
xr-format =/ xr-conceal-block xr-format =/ xr-conceal-block
xr-format =/ xr-conc-sec-block
xr-conceal-block = "loss-conceal" xr-conceal-block = "loss-conceal"
xr-conc-sec-block = "conc-sec" ["=" thresh]
4. IANA Considerations thresh = 1*DIGIT ; threshold for SCS (ms)
DIGIT = %x30-39
5.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] applies.
6. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to RFC general guidelines on IANA considerations for RTCP XR, refer to
3611. [RFC3611].
4.1. New RTCP XR Block Type value 6.1. New RTCP XR Block Type values
This document assigns the block type value <NLC> in the IANA "RTCP XR This document assigns two block type values in the IANA "RTCP XR
Block Type Registry" to the "Loss Concealment Metrics Block". Block Type Registry":
[Note to RFC Editor: please replace <NLC> with the RTCP XR block type Name: NLC
assigned by IANA for this block.] Long Name: Loss Concealment Block
Value <NLC>
Reference: Section 3.1
4.2. New RTCP XR SDP Parameter Name: NCS
Long Name: Concealment Seconds Block
Value <NCS>
Reference: Section 4.1
This document also registers a new parameter "loss-conceal" in the [Note to RFC Editor: please replace <NLC> and <NCS> with the RTCP XR
"RTCP XR SDP Parameters Registry". block type assigned by IANA for this block.]
4.3. Contact Information for Registrations 6.2. New RTCP XR SDP Parameters
The contact information for the registrations is: This document also registers two new parameters in the "RTCP XR SDP
Parameters Registry":
Alan Clark (alan.d.clark@telchemy.com) o "loss-conceal"
2905 Premiere Parkway, Suite 280 o "conc-sec"
Duluth, GA 30097
USA
5. Security Considerations 6.3. Contact information for registrations
The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
7. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in RFC 3611. This new security considerations beyond those described in [RFC3611].
block does not provide per-packet statistics so the risk to This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of RFC 3611 does confidentiality documented in Section 7, paragraph 3 of [RFC3611]
not apply. does not apply.
6. Acknowledgements 8. Contributors
The authors gratefully acknowledge the comments and suggestions made Geoff Hunt wrote the initial draft of this document.
by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
9. Acknowledgements
The authors gratefully acknowledge reviews and feedback provided by
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, and Hideaki Yamada. Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
7. References 10. References
7.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
to Indicate Requirement Levels", BCP 14, Requirement Levels", March 1997.
RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
R., and V. Jacobson, "RTP: A Transport Applications", RFC 3550, July 2003.
Protocol for Real-Time Applications",
STD 64, RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
"RTP Control Protocol Extended Reports Protocol Extended Reports (RTCP XR)", 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
Perkins, "SDP: Session Description Description Protocol", July 2006.
Protocol", RFC 4566, July 2006.
7.2. Informative References 10.2. Informative References
[I-D.ietf-avtcore-monarch] Wu, W., Hunt, G., and P. Arden, [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
"Guidelines for Use of the RTP Monitoring Development", RFC 6390, October 2011.
Framework", draft-ietf-avtcore-monarch-22
(work in progress), September 2012.
[RFC6390] Clark, A. and B. Claise, "Guidelines for [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considering New Performance Metric Considerations for Protocol Extensions", RFC 6709,
Development", BCP 170, RFC 6390, September 2012.
October 2011.
Authors' Addresses [RFC6792] Hunt, G., "Monitoring Architectures for RTP", RFC 6792,
November 2012.
Claire Bi [VAD] "http://en.wikipedia.org/wiki/Voice_activity_detection".
Shanghai Research Institure of China Telecom Corporation Limited
No.1835, South Pudong Road
Shanghai 200122
China
EMail: bijy@sttri.com.cn Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-04
The following are the major changes to previous version :
o Merge Concealment Seconds draft into this draft (i.e.,Loss
Concealment draft).
o Updated references.
Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
EMail: alan.d.clark@telchemy.com Email: alan.d.clark@telchemy.com
Geoff Hunt Glen Zorn (editor)
Unaffiliated Network Zen
77/440 Soi Phoomjit, Rama IV Road
Phra Khanong, Khlong Toie
Bangkok 10110
Thailand
EMail: r.geoff.hunt@gmail.com Phone: +66 (0) 87 502 4274
Email: gwz@net-zen.net
Qin Wu Claire Bi
Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road
Shanghai 200122
China
Email: bijy@sttri.com.cn
Qin Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
EMail: sunseawq@huawei.com Email: sunseawq@huawei.com
Glen Zorn (editor)
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 90 920 1060
EMail: glenzorn@gmail.com
 End of changes. 86 change blocks. 
202 lines changed or deleted 470 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/