draft-ietf-xrblock-rtcp-xr-concsec-02.txt   draft-ietf-xrblock-rtcp-xr-concsec-03.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group G. Zorn
Internet-Draft Telchemy Internet-Draft Network Zen
Intended status: Standards Track G. Zorn Intended status: Standards Track Q. Wu
Expires: April 22, 2013 Network Zen Expires: April 25, 2013 Huawei
A. Clark
Telchemy
C. Bi C. Bi
STTRI STTRI
Q. Wu October 22, 2012
Huawei
October 19, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for Concealed RTP Control Protocol (RTCP) Extended Report (XR) Block for Concealed
Seconds metric Reporting Seconds Metric Reporting
draft-ietf-xrblock-rtcp-xr-concsec-02.txt draft-ietf-xrblock-rtcp-xr-concsec-03.txt
Abstract Abstract
This document defines an RTP Control Protocol(RTCP) Extended Report This document defines an RTP Control Protocol(RTCP) Extended Report
(XR) Block that allows the reporting of Concealed Seconds metrics (XR) Block that allows the reporting of Concealed Seconds metrics,
primarily for audio applications of RTP. primarily 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.
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 22, 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 16 skipping to change at page 2, line 16
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. Concealed Seconds Block . . . . . . . . . . . . . . . . . 3 1.1. Concealed Seconds Block . . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Concealment Seconds Block . . . . . . . . . . . . . . . . . . 6 3. Concealment Seconds Block . . . . . . . . . . . . . . . . . . 4
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Concealed Seconds Metrics Block . 7 3.2. Definition of Fields in Concealed Seconds Metrics Block . 5
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 13 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 13 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
5.3. Contact information for registrations . . . . . . . . . . 13 5.3. Contact information for registrations . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
A.1. draft-ietf-xrblock-rtcp-xr-concsec-02 . . . . . . . . . . 18
A.2. draft-ietf-xrblock-rtcp-xr-concsec-01 . . . . . . . . . . 18
A.3. draft-ietf-xrblock-rtcp-xr-concsec-00 . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
1.1. Concealed Seconds Block 1.1. Concealed Seconds Block
This draft defines a new block type to augment those defined in This draft defines a new block type to augment those defined in
[RFC3611], for use primarily in audio applications of RTP. [RFC3611], for use primarily in audio applications of RTP.
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 'Concealed' refers to playout of locally-generated signals used to
mask the impact of network impairments such as lost packets or to mask the impact of network impairments such as lost packets or to
reduce the audibility of jitter buffer adaptations. reduce the audibility of jitter buffer adaptations.
Editor's Note: For video applications, the output at a receiver
Editor's Note: For video application, the output at a receiver
should also be classified as either normal or concealed. Should should also be classified as either normal or concealed. Should
this paragraph be clear about this? this paragraph be clear about this?
The new block type provides metrics for concealment. Specifically, The new block type provides metrics for concealment. 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 metric
(Severely Concealed Seconds (SCS)) reports the number of whole (Severely Concealed Seconds (SCS)) reports the number of whole
seconds during which the receiver played out locally-generated data seconds during which the receiver played out locally-generated data
for more than SCS Threshold (ms). for longer than SCS Threshold milliseconds.
The metric belongs to the class of transport-related end system The metric belongs to the class of transport-related end system
metrics defined in [MONARCH]. metrics defined in Wu, Hunt & Arden [I-D.ietf-avtcore-monarch].
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 Schulzrinne et al.
defined an extensible structure for reporting using an RTCP Extended [RFC3550]. Freidman, et al. [RFC3611] defines an extensible
Report (XR). This draft defines a new Extended Report block that structure for reporting using an RTCP Extended Report (XR). This
MUST be used as defined in [RFC3550] and [RFC3611]. draft defines a new Extended Report block that MUST be used as
specified in RFC 3550 and RFC 3611.
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [MONARCH] provides guideline for reporting Monitoring Architecture [I-D.ietf-avtcore-monarch] provides
block format using RTCP XR. The Metrics Block described in this guidelines for formatting RTCP XR blocks. The Metrics Block
document are in accordance with the guidelines in [RFC6390] and described in this document are in accordance with the guidelines in
[MONARCH]. [RFC6390] and [I-D.ietf-avtcore-monarch].
1.4. Applicability 1.4. Applicability
This metric is primarily applicable to audio applications of RTP. This metric is primarily applicable to audio applications of RTP.
EDITOR'S NOTE: are there metrics for concealment of transport errors EDITOR'S NOTE: are there metrics for concealment of transport errors
for video? for video?
Editor's Note: note that with video it is possible to use RTP based Editor's Note: note that with video it is possible to use RTP based
retransmission and also FEC (e.g. COP3) - typically these would only retransmission and also FEC (e.g. COP3) - typically these would only
skipping to change at page 6, line 7 skipping to change at page 4, line 35
In addition, the following terms are defined: In addition, the following terms are defined:
Editor's Note: For Video loss concealment, at least the following Editor's Note: For Video loss concealment, at least the following
four methods are used,i.e., Frame freeze,inter-frame four methods are used,i.e., Frame freeze,inter-frame
extrapolation, interpolation, Noise insertation, should this extrapolation, interpolation, Noise insertation, should this
section consider giving definition of these four methods for video section consider giving definition of these four methods for video
loss concealment? loss concealment?
3. Concealment Seconds Block 3. Concealment Seconds Block
This sub-block provides a description of potentially audible This block provides a description of potentially audible impairments
impairments due to lost and discarded packets at the endpoint, due to lost and discarded packets at the endpoint, expressed on a
expressed on a time basis analogous to a traditional PSTN T1/E1 time basis analogous to a traditional PSTN T1/E1 errored seconds
errored seconds metric. metric.
Editor's Note: Should impairment also cover video application? Editor's Note: Should impairment also cover video application?
The following metrics are based on successive one second intervals as The following metrics are based on successive one second intervals as
declared by a local clock. This local clock does NOT need to be declared by a local clock. This local clock does NOT need to be
synchronized to any external time reference. The starting time of synchronized to any external time reference. The starting time of
this clock is unspecified. Note that this implies that the same loss this clock is unspecified. Note that this implies that the same loss
pattern could result in slightly different count values, depending on pattern could result in slightly different count values, depending on
where the losses occur relative to the particular one-second where the losses occur relative to the particular one-second
demarcation points. For example, two loss events occurring 50ms demarcation points. For example, two loss events occurring 50ms
apart could result in either one concealed second or two, depending apart could result in either one concealed second or two, depending
on the particular 1000 ms boundaries used. on the particular 1000 ms boundaries used.
The seconds in this sub-block are not necessarily calendar seconds. 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 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 incorporated into these counts if they exceed 500ms and
shall be disregarded if they are less than 500ms. shall be disregarded if they are less than 500ms.
3.1. Report Block Structure 3.1. Report Block Structure
Concealed Seconds metrics block Concealed Seconds Metrics Block
0 1 2 3 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 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 | | BT=NCS | I |plc|Rserved| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unimpaired Seconds | | Unimpaired Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Concealed Seconds | | Concealed Seconds |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Severely Concealed Seconds | RESERVED | SCS Threshold | | Severely Concealed Seconds | RESERVED | SCS Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Concealed Seconds Metrics Block 3.2. Definition of Fields in Concealed Seconds Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Concealed Seconds Metrics Report Block is identified by the A Concealed Seconds Metrics Report Block is identified by the
constant NCS. constant <NCS>.
[Note to RFC Editor: please replace NCS with the IANA provided [Note to RFC Editor: please replace <NCS> with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Concealed Seconds This field is used to indicate whether the Concealed Seconds
metrics are Sampled, Interval or Cumulative metrics, that is, metrics are Sampled, Interval or Cumulative metrics, that is,
whether the reported values applies to the most recent measurement whether the reported values applies to the most recent measurement
interval duration between successive metrics reports (I=10) (the interval duration between successive metrics reports (I=10) (the
Interval Duration) or to the accumulation period characteristic of Interval Duration) or to the accumulation period characteristic of
cumulative measurements (I=11) (the Cumulative Duration) or is a cumulative measurements (I=11) (the Cumulative Duration) or is a
skipping to change at page 8, line 44 skipping to change at page 7, line 12
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
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 Delay block, the block length is equal to 4. the Delay block, the block length is equal to 4.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of RFC 3611.
Unimpaired Seconds: 32 bits Unimpaired Seconds: 32 bits
A count of the number of unimpaired Seconds that have occurred. A count of the number of unimpaired Seconds that have occurred.
An unimpaired Second is defined as a continuous period of 1000ms An unimpaired Second is defined as a continuous period of 1000ms
during which no frame loss or discard due to late arrival has during which no frame loss or discard due to late arrival has
occurred. Every second in a session must be classified as either occurred. Every second in a session must be classified as either
OK or Concealed. OK or Concealed.
Normal playout of comfort noise or other silence concealment If voice activity detection [VAD] is used, normal playout of
signal during periods of talker silence, if VAD [VAD] is used, comfort noise or other silence concealment signals during periods
shall be counted as unimpaired seconds. of talker silence SHALL be counted as unimpaired seconds.
Editor's Note: It should be clear that voice activity detection
Editor's Note: It should be clear that VAD does not apply to does not apply to video.
video.
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 SHOULD be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFF SHOULD be
reported. reported.
Concealed Seconds: 32 bits Concealed Seconds: 32 bits
A count of the number of Concealed Seconds that have occurred. A count of the number of Concealed Seconds that have occurred.
A Concealed Second is defined as a continuous period of 1000ms A Concealed Second is defined as a continuous period of 1000ms
during which any frame loss or discard due to late arrival has during which any frame loss or discard due to late arrival has
occurred. occurred.
Equivalently, a concealed second is one in which some Loss-type Equivalently, a concealed second is one in which some Loss-type
concealment has occurred. Buffer adjustment-type concealment concealment has occurred. Buffer adjustment-type concealment
SHALL not cause Concealed Seconds to be incremented, with the SHALL NOT cause Concealed Seconds to be incremented, with the
following exception. An implementation MAY cause Concealed following exception. An implementation MAY cause Concealed
Seconds to be incremented for 'emergency' buffer adjustments made Seconds to be incremented for 'emergency' buffer adjustments made
during talkspurts. during talkspurts.
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
skipping to change at page 12, line 7 skipping to change at page 9, line 30
or discarded frames that must occur within a one second period in or discarded frames that must occur within a one second period in
order for the second to be classified as a Severely Concealed order for the second to be classified as a Severely Concealed
Second. This is expressed in milliseconds and hence can represent Second. This is expressed in milliseconds and hence can represent
a range of 0.1 to 25.5 percent loss or discard. a range of 0.1 to 25.5 percent loss or discard.
A default threshold of 50ms (5% effective frame loss per second) A default threshold of 50ms (5% effective frame loss per second)
is suggested. is suggested.
4. SDP Signaling 4. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) RFC 3611 defines the use of Session Description Protocol (SDP,
[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.
4.1. SDP rtcp-xr-attrib Attribute Extension 4.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP attribute "rtcp-xr" defined in Section
in [RFC3611] by providing an additional value of "xr-format" to 5.1 of RFC 3611 by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
The SDP attribute for the block has an additional optional paremeter, The SDP attribute for the block has an additional optional paremeter,
"thresh", used to supply a value for the SCS Threshold parameter. If "thresh", used to supply a value for the SCS Threshold parameter. If
this parameter is present, the RTP system receiving the SDP SHOULD this parameter is present, the RTP system receiving the SDP SHOULD
use this value for the current session. If the parameter is not use this value for the current session. If the parameter is not
present, the RTP system SHOULD use a locally configured value. present, the RTP system SHOULD use a locally configured value.
xr-format =/ xr-conc-sec-block xr-format =/ xr-conc-sec-block
xr-conc-sec-block = "conc-sec" ["=" thresh] xr-conc-sec-block = "conc-sec" ["=" thresh]
thresh = 1*DIGIT ; threshold for SCS (ms) thresh = 1*DIGIT ; threshold for SCS (ms)
DIGIT = <as defined in Section 3.4 of [RFC5234]> DIGIT = <as defined in Section 3.4 of [RFC5234]>
4.2. Offer/Answer Usage 4.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] applies. defined in Section 5.2 of RFC 3611 applies.
5. IANA Considerations 5. 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 general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611]. Section 6 of RFC 3611.
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type value
This document assigns the block type value NJB in the IANA "RTCP XR This document assigns the block type value <NCS> in the IANA "RTCP XR
Block Type Registry" to the "Concealed Seconds Metrics Block". Block Type Registry" to the "Concealed Seconds Metrics Block".
[Note to RFC Editor: please replace NCS with the IANA provided RTCP [Note to RFC Editor: please replace <NCS> with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
5.2. New RTCP XR SDP Parameter 5.2. New RTCP XR SDP Parameter
This document also registers a new parameter "conc-sec" in the "RTCP This document also registers a new parameter "conc-sec" in the "RTCP
XR SDP Parameters Registry". XR SDP Parameters Registry".
5.3. Contact information for registrations 5.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Alan Clark (alan.d.clark@telchemy.com) Alan Clark (alan.d.clark@telchemy.com)
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
6. Security Considerations 6. 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 [RFC3611]. new security considerations beyond those described in RFC 3611. This
This block does not provide per-packet statistics so the risk to block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply.
7. Contributors 7. Contributors
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
8. Acknowledgements 8. Acknowledgements
The authors gratefully acknowledge reviews and feedback provided by The authors gratefully acknowledge reviews and feedback provided by
skipping to change at page 17, line 10 skipping to change at page 11, line 31
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.
9. References 9. References
9.1. Normative References 9.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", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Applications", RFC 3550, July 2003. Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, 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)", November 2003. Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", RFC 4566, July 2006.
9.2. Informative References 9.2. Informative References
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [I-D.ietf-avtcore-monarch]
ID draft-ietf-avtcore-monarch-22, September 2012. Wu, W., Hunt, G., and P. Arden, "Guidelines for Use of the
RTP Monitoring Framework", draft-ietf-avtcore-monarch-22
(work in progress), September 2012.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Development", RFC 6390, October 2011. Performance Metric Development", BCP 170, RFC 6390,
October 2011.
[VAD] "http://en.wikipedia.org/wiki/Voice_activity_detection". [VAD] "http://en.wikipedia.org/wiki/Voice_activity_detection".
Appendix A. Change Log Authors' Addresses
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-concsec-02
The following are the major changes to previous version :
o One typo fixed.
o Add one note to highlight these metrics are primarily applicable
to audio.
A.2. draft-ietf-xrblock-rtcp-xr-concsec-01
The following are the major changes to previous version :
o Outdated references update.
o Add Editor's notes to point out where to require more texts for
video loss concealment support
o Other Editorial changes.
A.3. draft-ietf-xrblock-rtcp-xr-concsec-00
The following are the major changes to previous version :
o Updated references. Glen Zorn
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
o Allocate two bits for interval metric flag and 32 bit for SSRC Phone: +66 (0) 909-0201060
Email: glenzorn@gmail.com
o Other editorial changes to get in line with MONARCH and MeasID Qin Wu
draft. Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Authors' Addresses Email: sunseawq@huawei.com
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
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
Claire Bi Claire Bi
Shanghai Research Institure of China Telecom Corporation Limited Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road No.1835,South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: bijy@sttri.com.cn Email: bijy@sttri.com.cn
Qin Wu
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Email: sunseawq@huawei.com
 End of changes. 40 change blocks. 
138 lines changed or deleted 107 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/