draft-ietf-xrblock-rtcp-xr-summary-stat-03.txt   draft-ietf-xrblock-rtcp-xr-summary-stat-04.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track R. Schott Intended status: Standards Track R. Schott
Expires: May 30, 2013 Deutsche Telekom Expires: June 17, 2013 Deutsche Telekom
Q. Wu Q. Wu
R. Huang R. Huang
Huawei Huawei
November 26, 2012 December 14, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary
Statistics Metrics Reporting Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-summary-stat-03 draft-ietf-xrblock-rtcp-xr-summary-stat-04
Abstract Abstract
This document defines three RTP Control Protcol (RTCP) Extended This document defines three RTP Control Protcol (RTCP) Extended
Report (XR) Blocks and associated SDP parameters that allow the Report (XR) Blocks that allow the reporting of loss, duplication and
reporting of loss, duplication and discard summary statistics metrics discard summary statistics metrics in a range of RTP applications.
in a range of RTP applications.
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 May 30, 2013. This Internet-Draft will expire on June 17, 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
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
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Summary Statistics Metrics . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Transport Related End System Metrics . . . . . . . . . . . . . 4 3. Transport Related End System Metrics . . . . . . . . . . . . . 4
3.1. Burst/Gap Loss Summary Statistics Block . . . . . . . . . 4 3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 4
3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 4 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 5
3.1.2. Definition of Fields in Loss Summary Statistics 3.1.2. Definition of Fields in Loss Summary Statistics
Block . . . . . . . . . . . . . . . . . . . . . . . . 4 Block . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 6 3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7
3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7
3.2.2. Definition of Fields inBurst/Gap Discard Summary 3.2.2. Definition of Fields inBurst/Gap Discard Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 7 Statistics Block . . . . . . . . . . . . . . . . . . . 8
4. Application Level Metrics . . . . . . . . . . . . . . . . . . 8 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 9
4.1. Frame Impairment Statistics Summary Block . . . . . . . . 8 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 9
4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10
4.1.2. Definition of Fields in Frame Impairment Summary 4.1.2. Definition of Fields in Frame Impairment Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 9 Statistics Block . . . . . . . . . . . . . . . . . . . 10
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 12
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13
6.3. Contact information for registrations . . . . . . . . . . 12 6.3. Contact information for registrations . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-02 . . . . . . . . 14 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-04 . . . . . . . . 15
A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-01 . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
1.1. Summary Statistics Metrics
This draft defines three new block types to augment those defined in This draft defines three new block types to augment those defined in
Freidman, et al. [RFC3611] for use in a range of RTP applications. [RFC3611] for use in a range of RTP applications.
The first two block types support the reporting of burst gap loss/ The first two block types support the reporting of burst gap loss/
discard summary statistics including packet loss/discard proportion, discard summary statistics including packet loss/discard proportion,
mean and variance and belong to the class of transport-related end mean and variance and belong to the class of transport-related end
system metrics defined in Wu, Hunt & Arden [RFC6792]. These two system metrics defined in [RFC6792]. These two blocks are intended
blocks are intended to be used in conjunction with information from to be used in conjunction with information from the Burst Gap Loss
the Burst Gap Loss metric block or Burst Gap Discard metric block, metric block or Burst Gap Discard metric block, and on which these
and on which these two block therefore depend. The metrics in the two block therefore depend. The metrics in the Burst Gap Loss block
Burst Gap Loss block or Burst Gap Discard metric block can be used or Burst Gap Discard metric block can be used independently of the
independently of the metrics defined in the first two blocks, metrics defined in the first two blocks, however.
however. These two blocks reflect transient IP problems that affect
user experience and can be used to influence sender strategies to
mitigate the problem.
To form an accurate assessment of users' quality of experience, it is The third block supports the reporting of detailed statistics for
therefore necessary to know not just overall rates of packet loss/ each frame type, including the number of frames received, lost and
discard, but also which frame types were affected. The third block discarded of each frame type in the Group of Pictures (GOP) and
supports the reporting of detailed statistics for each frame type, additional data allowing the calculation of statistical parameters
including the number of frames received, lost and discarded of each (e.g.,the proportion of each frame type impaired by packet loss and
frame type in the Group of Pictures (GOP) and additional data discard). The metrics defined in this block belong to the class of
allowing the calculation of statistical parameters (e.g.,the application layer metrics defined in [RFC6792].
proportion of each frame type impaired by packet loss and discard).
The metrics defined in this block belong to the class of application 1.2. RTCP and RTCP XR Reports
layer metrics defined in Wu, Hunt & Arden [RFC6792].
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework
The RTP Monitoring Architectures [RFC6792] provides guideline for
reporting block format using RTCP XR. Metrics described in this
draft are in accordance with the guidelines in [RFC6792].
1.4. Applicability
These metrics are applicable to a wide range of RTP applications and
reflect transient IP problems that affect user experience. They can
be used to form an accurate assessment of users' quality of
experience and influence sender strategies to mitigate the problem.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
In addition, the following terms are defined: In addition, the following terms are defined:
skipping to change at page 4, line 7 skipping to change at page 4, line 26
Picture Types used in the different video algorithms are composed Picture Types used in the different video algorithms are composed
of the Key frame and Derived frames. The Key frame is also called of the Key frame and Derived frames. The Key frame is also called
a reference frame and used as a reference for predicting other a reference frame and used as a reference for predicting other
pictures. It is coded without prediction from other pictures. pictures. It is coded without prediction from other pictures.
Derived frames are derived from a Key frame using a prediction Derived frames are derived from a Key frame using a prediction
algorithm. algorithm.
3. Transport Related End System Metrics 3. Transport Related End System Metrics
3.1. Burst/Gap Loss Summary Statistics Block 3.1. Burst/Gap Loss Summary Statistics Metrics Block
The metrics described here are intended to be used as described in The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement this section, in conjunction with information from the Measurement
Information block [RFC6776] (which MUST be present in the same RTCP Information block [RFC6776] (which MUST be present in the same RTCP
packet as the Burst/Gap Loss block) and also with the metric packet as the Burst/Gap Loss block) and also with the metric
"cumulative number of packets lost" provided in standard RTCP "cumulative number of packets lost" provided in standard RTCP
[RFC3550]. [RFC3550]. Instances of this Metrics Block refer by Synchronization
source (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which contains measurement periods (see [RFC6776] section
4.2). This metrics block relies on the measurement period in the
Measurement Information block indicating the span of the report and
SHOULD be sent in the same compound RTCP packet as the measurement
information block. If the measurement period is not received in the
same compound RTCP packet as this metric block, this metrics block
MUST be discarded.
These metrics provide information relevant to statistical parameters, The metrics carried in this metrics block provide information
including burst loss rate, gap loss rate, burst duration mean, burst relevant to statistical parameters, including burst loss rate, gap
duration variance and are calculated using burst gap loss metrics loss rate, burst duration mean, burst duration variance and are
defined in [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss] and other calculated at the receiving end of the RTP stream using burst gap
information which is sent together with this report block. loss metrics defined in [BGLOSS] and other information which is sent
together with this report block.
3.1.1. Report Block Structure 3.1.1. Report Block Structure
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=BGLSS | I | Reserved | block length | | BT=BGLSS | I | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 43 skipping to change at page 5, line 26
| Burst duration Mean | Burst duration Variance | | Burst duration Mean | Burst duration Variance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2. Definition of Fields in Loss Summary Statistics Block 3.1.2. Definition of Fields in Loss Summary Statistics Block
Block Type (BT): 8 bits Block Type (BT): 8 bits
Burst/Gap Loss Summary Statistics Block is identified by the Burst/Gap Loss Summary Statistics Block is identified by the
constant <BGLSS>. constant <BGLSS>.
Interval Metric flag (I): 2 bits Interval Metric Flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Loss Summary This field is used to indicate whether the Burst/Gap Loss Summary
Statistics metrics are Sampled, Interval or Cumulative metrics: Statistics 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.
In this document, the value I=00 is the reserved value and MUST
NOT be used.
Reserved: 6 bits Reserved: 6 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver (See RFC6709 section 4.2). SHOULD be ignored by the receiver (See RFC6709 section 4.2).
Block Length: 16 bits Block Length: 16 bits
The constant 3, in accordance with the definition of this field in The constant 3, in accordance with the definition of this field in
skipping to change at page 6, line 17 skipping to change at page 6, line 49
values of "cumulative number of packets lost" in RTCP, to obtain values of "cumulative number of packets lost" in RTCP, to obtain
the "number of packets lost" for the reporting interval. the "number of packets lost" for the reporting interval.
Burst Duration Mean:16bits Burst Duration Mean:16bits
The mean burst duration is obtained as the quotient: The mean burst duration is obtained as the quotient:
mean = Sum of Burst Durations / Number of Bursts mean = Sum of Burst Durations / Number of Bursts
where "Sum of Burst Durations" and "Number of Bursts" is obtained where "Sum of Burst Durations" and "Number of Bursts" is obtained
from the RTCP XR Burst/Gap Loss Block from the RTCP XR Burst/Gap Loss Block [BGLOSS].
[I-D.ietf-xrblock-rtcp-xr-burst-gap-loss].
Burst Duration Variance:16bits Burst Duration Variance:16bits
The variance of the burst duration is obtained using the standard The variance of the burst duration is obtained using the standard
result: result:
var = ( Sum of Squares of Burst Durations - Number of Bursts * var = ( Sum of Squares of Burst Durations - Number of Bursts *
mean^2 ) / (Number of Bursts - 1) mean^2 ) / (Number of Bursts - 1)
where "Sum of Squares of Burst Durations" and "Number of Bursts"is where "Sum of Squares of Burst Durations" and "Number of Bursts"is
obtained from the RTCP XR Burst/Gap Loss Block obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS].
[I-D.ietf-xrblock-rtcp-xr-burst-gap-loss].
3.2. Burst/Gap Discard Summary Statistics Block 3.2. Burst/Gap Discard Summary Statistics Metrics Block
The metrics described here are intended to be used as described in The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement this section, in conjunction with information from the Measurement
Identity block [RFC6776] (which MUST be present in the same RTCP Identity block [RFC6776] (which MUST be present in the same RTCP
packet as the Burst/Gap Discard Summary Statistics block) and also packet as the Burst/Gap Discard Summary Statistics block) .
with the metric "number of packets discarded" provided in the RTCP XR
Discard Block [I-D.ietf-xrblock-rtcp-xr-discard]. The RTCP XR
Discard Block SHOULD be sent if the Burst/Gap Discard Summary
Statistics block is sent, but the converse does not apply.
These metrics provide information relevant to statistical parameters, These metrics provide information relevant to statistical parameters,
including burst discard rate, gap discard rate and are calculated including burst discard rate, gap discard rate and are calculated at
using burst gap loss metrics defined in the receiving end of the RTP stream using burst gap discard metrics
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] and other information defined in [BGDISCARD] and other information which is sent together
which is sent together with this report block. with this report block.
Instances of this Metrics Block refer by Synchronization source
(SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which contains measurement periods (see [RFC6776] section
4.2). This metrics block relies on the measurement period in the
Measurement Information block indicating the span of the report and
SHOULD be sent in the same compound RTCP packet as the measurement
information block. If the measurement period is not received in the
same compound RTCP packet as this metric block, this metrics block
MUST be discarded.
3.2.1. Report Block Structure 3.2.1. Report Block Structure
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=BGDSS | I | Reserved | block length | | BT=BGDSS | I | Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 25 skipping to change at page 8, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2.2. Definition of Fields inBurst/Gap Discard Summary Statistics 3.2.2. Definition of Fields inBurst/Gap Discard Summary Statistics
Block Block
Block Type (BT): 8 bits Block Type (BT): 8 bits
Burst/Gap Discard Summary Statistics Block is identified by the Burst/Gap Discard Summary Statistics Block is identified by the
constant <BGDSS>. constant <BGDSS>.
Interval Metric Type (I): 2 bits Interval Metric Flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Discard This field is used to indicate whether the Burst/Gap Discard
Summary Statistics metrics are Sampled, Interval or Cumulative Summary Statistics metrics are Sampled, Interval or Cumulative
metrics: 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.
In this document, the value I=00 is the reserved value and MUST
NOT be used.
Reserved: 6 bits Reserved: 6 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver (See RFC6709 section 4.2). SHOULD be ignored by the receiver (See RFC6709 section 4.2).
Block Length: 16 bits Block Length: 16 bits
The constant 2, in accordance with the definition of this field in The constant 2, in accordance with the definition of this field in
Section 3 of RFC 3611 [RFC3611]. Section 3 of RFC 3611 [RFC3611].
skipping to change at page 8, line 32 skipping to change at page 9, line 20
of reception expressed as a fixed point number with the binary of reception expressed as a fixed point number with the binary
point at the left edge of the field. This value is calculated by point at the left edge of the field. This value is calculated by
dividing the difference between number of packets discarded and dividing the difference between number of packets discarded and
Packets Discarded in Bursts by the difference between Packets Packets Discarded in Bursts by the difference between Packets
Expected and Total Packets expected in Bursts as follows: Expected and Total Packets expected in Bursts as follows:
(number of packets discarded - Packets Discarded in Bursts) / (number of packets discarded - Packets Discarded in Bursts) /
(Packets Expected - Total Packets expected in Bursts) (Packets Expected - Total Packets expected in Bursts)
where "number of packets discarded" is obtained from the RTCP XR where "number of packets discarded" is obtained from the RTCP XR
Discard Count Block [I-D.ietf-xrblock-rtcp-xr-discard] and filled Discard Count Block [DISCARD] and filled with the sum of packets
with the total number of packets discarded due to both early and discarded due to early arrival (DT=1) and packets discarded due to
late arrival(DT=3) and Packets Expected is calculated as the late arrival(DT=2) and Packets Expected is calculated as the
difference between "extended last sequence number" and "extended difference between "extended last sequence number" and "extended
first sequence number" (Interval or Cumulative) provided in the first sequence number" (Interval or Cumulative) provided in the
Measurement Information block [RFC6776]. In order for the Burst/ Measurement Information block [RFC6776]. In order for the Burst/
Gap Discard Summary Statistics Block to be meaningful a single Gap Discard Summary Statistics Block to be meaningful, 2 instances
instance of the Discard Count block with DT=3 and a single of the Discard Count block with DT=1 and DT=2 MUST be included in
instance of the Burst Gap Discard Block MUST be included in the the same RTCP compound packet as the Burst/Gap Discard Summary
same RTCP compound packet as the Burst/Gap Discard Summary
Statistics Block. Statistics Block.
4. Application Level Metrics 4. Application Level Metrics
4.1. Frame Impairment Statistics Summary Block 4.1. Frame Impairment Statistics Summary Metrics Block
This block reports statistics on which frame type were affected This block reports statistics on which frame type were affected
beyond the information carried in the Statistics Summary Report Block beyond the information carried in the Statistics Summary Report Block
RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611].
Information is recorded about thenumber of frames received, lost Information is measured at the receiving end of the RTP stream and
frames, duplicated frames and lost partial frames. Such information recorded about thenumber of frames received, lost frames, duplicated
can be useful for network management and video quality monitoring. frames and lost partial frames. Such information can be useful for
network management and video quality monitoring.
4.1.1. Report Block Structure 4.1.1. Report Block Structure
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=FISS |T| Reserved | block length | | BT=FISS |T| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 42 skipping to change at page 10, line 40
Block type (BT): 8 bits Block type (BT): 8 bits
Frame Impairment Statistics Summary Block is identified by the Frame Impairment Statistics Summary Block is identified by the
constant <FISS>. constant <FISS>.
Picture type indicator (T): 1 bit Picture type indicator (T): 1 bit
This field is used to indicate the frame type to be reported. The This field is used to indicate the frame type to be reported. The
bit is set to 0 if the lost_full_frames, lost_partial_frames and bit is set to 0 if the lost_full_frames, lost_partial_frames and
dup_frames fields contain Key frame (reference frame) counts or 1 dup_frames fields contain Key frame (reference frame) counts or 1
if they contain Derivation frame counts. Note that if both the if they contain Derived frame counts. Note that if both the Key
Key frame and Derivation frame report are sent, they should be frame and Derivation frame report are sent, they should be sent in
sent in the same RTCP compound packet using two Frame Impairment the same RTCP compound packet using two Frame Impairment Summary
Summary Statistics Blocks. Statistics Blocks.
Reserved: 7 bits Reserved: 7 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
SHOULD be ignored by the receiver. SHOULD be ignored by the receiver.
Block Length: 16 bits Block Length: 16 bits
The constant 7, in accordance with the definition of this field in The constant 7, in accordance with the definition of this field in
skipping to change at page 11, line 28 skipping to change at page 12, line 28
xr-format = / burst-gap-loss-stat xr-format = / burst-gap-loss-stat
/ burst-gap-discard-stat / burst-gap-discard-stat
/ frame-impairment-stat / frame-impairment-stat
Burst-gap-loss-stat ="burst gap loss summary statistics" Burst-gap-loss-stat ="burst gap loss summary statistics"
Burst-gap-discard-stat="burst gap discard summary statistics" Burst-gap-discard-stat="burst gap discard summary statistics"
Frame-impairment-stat="frame impairment summary statistics" Frame-impairment-stat="frame impairment summary statistics"
5.2. Offer/Answer Usage 5.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 Section 5.2 of RFC 3611 applies. defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611].
6. IANA Considerations 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 RFC
3611. 3611.
6.1. New RTCP XR Block Type values 6.1. New RTCP XR Block Type values
This document assigns three new block type value in the RTCP XR Block This document assigns three new block type value in the RTCP XR Block
Type Registry: Type Registry:
Name: BGLSS Name: BGLSS
Long Name: Burst/Gap Loss Summsary Statistics Block Long Name: Burst/Gap Loss Summary Statistics Block
Value <BGLSS> Value <BGLSS>
Reference: Section 3.1 Reference: Section 3.1
Name: BGDSS Name: BGDSS
Long Name: Burst/Gap Discard Summary Statistics Block Long Name: Burst/Gap Discard Summary Statistics Block
Value <BGDSS> Value <BGDSS>
Reference: Section 3.2 Reference: Section 3.2
Name: FISS Name: FISS
Long Name: Frame Impairment Statistics Summary Long Name: Frame Impairment Statistics Summary
skipping to change at page 12, line 33 skipping to change at page 13, line 33
the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: the "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry:
* " burst-gap-loss-stat " * " burst-gap-loss-stat "
* " burst-gap-discard-stat " * " burst-gap-discard-stat "
* " frame-impairment-stat " * " frame-impairment-stat "
6.3. Contact information for registrations 6.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Glen Zorn Qin Wu (sunseawq@huawei.com)
Network Zen 101 Software Avenue, Yuhua District
227/358 Thanon Sanphawut Nanjing, Jiangsu 210012
Bang Na, Bangkok 10260 China
Thailand
7. Security Considerations 7. Security Considerations
The new RTCP XR report blocks proposed in this document introduces no The new RTCP XR report blocks proposed in this document introduces no
new security considerations beyond those described in RFC 3611. new security considerations beyond those described in RFC 3611.
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Bill Ver Steeg, David R Oran, Ali The authors would like to thank Bill Ver Steeg, David R Oran, Ali
Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang
Hu, Jing Zhao and Ray van Brandenburg for their valuable comments and Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu for
suggestions on this document. their valuable comments and suggestions on this document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[BGDISCARD]
Clark, A., Huang, R., and W. Wu, "RTP Control
Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
Discard metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in
progress), December 2012.
[BGLOSS] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Loss metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06 (work in
progress), December 2012.
[DISCARD] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Discard Count metric
Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in
progress), October 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. 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)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003. November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
9.2. Informative References
[I-D.ietf-xrblock-rtcp-xr-burst-gap-discard]
Clark, A., Huang, R., and W. Wu, "RTP Control
Protocol(RTCP) Extended Report (XR) Block for Discard
Count metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-06 (work in
progress), October 2012.
[I-D.ietf-xrblock-rtcp-xr-burst-gap-loss]
Clark, A., Zhang, S., Zhao, J., and W. Wu, "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Loss metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 (work in
progress), October 2012.
[I-D.ietf-xrblock-rtcp-xr-discard]
Clark, A., Zorn, G., and W. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Discard Count metric
Reporting", draft-ietf-xrblock-rtcp-xr-discard-09 (work in
progress), October 2012.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012. using SDES item and XR Block", RFC 6776, August 2012.
9.2. Informative References
[RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures
for RTP", RFC 6792, November 2012. for RTP", RFC 6792, November 2012.
Appendix A. Change Log Appendix A. 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.
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-02 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-04
The following are the major changes compared to 01:
o Modify texts to clarify the selection of discard count based on
discard count metric block.
A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-01
The following are the major changes compared to 00: The following are the major changes compared to 03:
o Outdated Reference update o Editorial changes to get in line with Delay and Burst Gap related
o Add text to clarify the selection of discard count based on drafts.
discard count metric block.
o Revise Interval metric flag defintion for consistency.
o SDP text restructure
o Other editorial changes based on comments on the list.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) Glen Zorn (editor)
Network Zen Network Zen
227/358 Thanon Sanphawut 227/358 Thanon Sanphawut
Bang Na, Bangkok 10260 Bang Na, Bangkok 10260
Thailand Thailand
Phone: +66 (0) 909-201060 Phone: +66 (0) 909-201060
 End of changes. 44 change blocks. 
137 lines changed or deleted 163 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/