draft-ietf-xrblock-rtcp-xr-summary-stat-11.txt   rfc7004.txt 
Network Working Group G. Zorn Internet Engineering Task Force (IETF) G. Zorn
Internet-Draft Network Zen Request for Comments: 7004 Network Zen
Intended status: Standards Track R. Schott Category: Standards Track R. Schott
Expires: September 26, 2013 Deutsche Telekom ISSN: 2070-1721 Deutsche Telekom
Q. Wu, Ed. Q. Wu, Ed.
R. Huang R. Huang
Huawei Huawei
March 25, 2013 September 2013
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary RTP Control Protocol (RTCP) Extended Report (XR) Blocks
Statistics Metrics Reporting for Summary Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-summary-stat-11
Abstract Abstract
This document defines three RTP Control Protocol (RTCP) Extended This document defines three RTP Control Protocol (RTCP) Extended
Report (XR) Blocks that allow the reporting of loss, duplication and Report (XR) blocks that allow the reporting of loss, duplication, and
discard summary statistics metrics in a range of RTP applications. discard summary statistics metrics in a range of RTP applications.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on September 26, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7004.
Copyright Notice Copyright Notice
Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction ....................................................2
1.1. Summary Statistics Metrics . . . . . . . . . . . . . . . . 4 1.1. Summary Statistics Metrics .................................2
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 4 1.2. RTCP and RTCP Extended Reports .............................3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4 1.3. Performance Metrics Framework ..............................3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability ..............................................3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology .....................................................3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 3. Transport-Related End-System Metrics ............................4
3. Transport Related End System Metrics . . . . . . . . . . . . . 5 3.1. Burst/Gap Loss Summary Statistics Block ....................4
3.1. Burst/Gap Loss Summary Statistics Metrics Block . . . . . 5 3.1.1. Report Block Structure ..............................5
3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 6 3.1.2. Definition of Fields in Loss Summary
3.1.2. Definition of Fields in Loss Summary Statistics Statistics Block ....................................5
Block . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Burst/Gap Discard Summary Statistics Block .................7
3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 8 3.2.1. Report Block Structure ..............................8
3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 9 3.2.2. Definition of Fields in Burst/Gap Discard
3.2.2. Definition of Fields in Burst/Gap Discard Summary Summary Statistics Block ............................8
Statistics Block . . . . . . . . . . . . . . . . . . . 9 4. Application-Level Metrics ......................................10
4. Application Level Metrics . . . . . . . . . . . . . . . . . . 11 4.1. Frame Impairment Statistics Summary Block .................10
4.1. Frame Impairment Statistics Summary Metrics Block . . . . 11 4.1.1. Report Block Structure .............................11
4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 11 4.1.2. Definition of Fields in Frame Impairment
4.1.2. Definition of Fields in Frame Impairment Summary Statistics Summary Block ...........................11
Statistics Block . . . . . . . . . . . . . . . . . . . 12 5. SDP Signaling ..................................................13
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 13 5.1. SDP rtcp-xr Attribute Extension ...........................13
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 13 5.2. Offer/Answer Usage ........................................13
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations ............................................13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6.1. New RTCP XR Block Type Values .............................13
6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 14 6.2. New RTCP XR SDP Parameters ................................14
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 14 6.3. Contact Information for Registrations .....................14
6.3. Contact information for registrations . . . . . . . . . . 15 7. Security Considerations ........................................14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements ...............................................14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 9. References .....................................................14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References ......................................14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 9.2. Informative References ....................................15
9.2. Informative References . . . . . . . . . . . . . . . . . . 16 Appendix A. Metrics Represented Using the Template from RFC 6390 .16
Appendix A. Metrics represented using RFC6390 Template . . . . . 16
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 22
B.1. draft-ietf-xrblock-rtcp-xr-summary-stat-11 . . . . . . . . 22
B.2. draft-ietf-xrblock-rtcp-xr-summary-stat-10 . . . . . . . . 22
B.3. draft-ietf-xrblock-rtcp-xr-summary-stat-09 . . . . . . . . 22
B.4. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 22
B.5. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 22
B.6. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 22
B.7. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
1.1. Summary Statistics Metrics 1.1. Summary Statistics Metrics
This draft defines three new block types to augment those defined in This document defines three new block types to augment those defined
[RFC3611] for use in a range of RTP applications. in [RFC3611] for use in a range of RTP applications:
o Burst/Gap Loss Summary Statistics Metrics Block o Burst/Gap Loss Summary Statistics Block
o Burst/Gap Discard Summary Statistics Metrics Block
o Frame Impairment Statistics Summary Metrics Block
The first two block types support the reporting of burst gap loss/ o Burst/Gap Discard Summary Statistics Block
discard summary statistics including packet loss/discard proportion,
mean and variance and belong to the class of transport-related end o Frame Impairment Statistics Summary Block
system metrics defined in [RFC6792]. These two blocks are intended
to be used in conjunction with information from the Burst Gap Loss The first two block types support the reporting of burst/gap loss and
Metrics Block [BGLOSS] or Burst Gap Discard Metrics Block burst/gap discard summary statistics including packet loss/discard
[BGDISCARD], and on which these two blocks therefore depend. The proportion, mean, and variance and belong to the class of transport-
metrics in the Burst Gap Loss Metrics block or Burst Gap Discard related end-system metrics defined in [RFC6792]. These two blocks
Metrics Block are consistent with the definitions of Burst, Gap, Loss are intended to be used in conjunction with information from the
and Discard in RTCP XR [RFC3611]. Burst/Gap Loss Metrics Block [RFC6958] or Burst/Gap Discard Metrics
Block [RFC7003], on which these two blocks therefore depend. The
metrics in the Burst/Gap Loss Metrics Block and Burst/Gap Discard
Metrics Block are consistent with the definitions of "burst", "gap",
"loss", and "discard" in RTCP XR [RFC3611].
The third block supports the reporting of detailed video statistics The third block supports the reporting of detailed video statistics
for each frame type, including the number of frames received, lost for each frame type, including the number of frames received, lost,
and discarded of each frame type in the Group of Pictures (GOP) and and discarded of each frame type in the Group of Pictures (GOP) and
additional data allowing the calculation of statistical parameters additional data allowing the calculation of statistical parameters
(e.g.,the proportion of each frame type impaired by packet loss and (e.g., the proportion of each frame type impaired by packet loss and
discard). The metrics defined in this block belong to the class of discard). The metrics defined in this block belong to the class of
application layer metrics defined in [RFC6792]. application-level metrics defined in [RFC6792].
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP Extended Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defined an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611]. use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The RTP Monitoring Architectures [RFC6792] provides guideline for The RTP Monitoring Framework [RFC6792] provides guidelines for
reporting block format using RTCP XR. Metrics described in this reporting block format using RTCP XR. Metrics described in this
draft are in accordance with the guidelines in [RFC6792]. document are in accordance with the guidelines in [RFC6792].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a wide range of RTP applications and These metrics are applicable to a wide range of RTP applications and
reflect transient IP problems that affect user experience. They can reflect transient IP problems that affect user experience. They can
be used to form an accurate assessment of users' quality of be used to form an accurate assessment of users' quality of
experience and influence sender strategies to mitigate the problem. experience and influence sender strategies to mitigate the problem.
2. Terminology 2. Terminology
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 term is defined:
Frame Type Frame Type
In many cases, a video frame is compressed using different In many cases, a video frame is compressed using different
algorithms. Frame type is used to identify different algorithms algorithms. Frame type is used to identify different algorithms
for video frames. Two frame Types used in the different video for video frames. Two frame types used in the different video
algorithms are the Key frame and Derived frames. The Key frame is algorithms are the Key frame and Derived frames. The Key frame is
independently coded without prediction from other pictures and independently coded without prediction from other pictures and
used as a reference frame for predicting other pictures. Derived used as a reference frame for predicting other pictures. Derived
frames are predicatively coded and derived from a Key frame using frames are predicatively coded and derived from a Key frame using
a prediction algorithm If there is no video image compression, all a prediction algorithm. If there is no video image compression,
frames are Key Frames. all frames are Key frames.
3. Transport Related End System Metrics 3. Transport-Related End-System Metrics
3.1. Burst/Gap Loss Summary Statistics Metrics Block 3.1. Burst/Gap Loss Summary Statistics Block
This Block extends packet loss and discard metrics defined in section This block extends packet loss and discard metrics defined in
4.7.1 of RFC3611. The metrics described here are intended to be used Section 4.7.1 of [RFC3611]. The metrics described here are intended
as described in this section, in conjunction with information from to be used as described in this section, in conjunction with
the Measurement Information block [RFC6776] (which MUST be present in information from the Measurement Information Block [RFC6776] (which
the same RTCP packet as the Burst/Gap Loss block) and also with the MUST be present in the same RTCP packet as the Burst/Gap Loss Metrics
metric "cumulative number of packets lost" provided in standard RTCP Block [RFC6958]) and also with the metric "cumulative number of
[RFC3550]. Instances of this Metrics Block refer by Synchronization packets lost" provided in standard RTCP [RFC3550]. Instances of this
source (SSRC) to the separate auxiliary Measurement Information block metrics block use the synchronization source (SSRC) to refer to the
[RFC6776] which describes measurement periods in use (see [RFC6776] separate auxiliary Measurement Information Block [RFC6776], which
section 4.2). This Metrics Block relies on the measurement period in describes measurement periods in use (see [RFC6776], Section 4.2).
the Measurement Information block indicating the span of the report This metrics block relies on the measurement period in the
and SHOULD be sent in the same compound RTCP packet as the Measurement Information Block indicating the span of the report and
measurement information block. If the measurement period is not SHOULD be sent in the same compound RTCP packet as the Measurement
received in the same compound RTCP packet as this Metrics Block, this Information Block. If the measurement period is not received in the
metrics block MUST be discarded. same compound RTCP packet as this metrics block, this metrics block
MUST be discarded.
The metrics carried in this Metrics Block provide information The metrics carried in this metrics block provide information
relevant to statistical parameters, including burst loss rate, gap relevant to statistical parameters, including Burst Loss Rate, Gap
loss rate, burst duration mean, burst duration variance and are Loss Rate, Burst Duration Mean, and Burst Duration Variance, and are
measured at the receiving end of the RTP stream using burst gap loss measured at the receiving end of the RTP stream using burst/gap loss
metrics defined in [BGLOSS] and other information which is sent metrics defined in [RFC6958] and other information that is sent
together with this report block. together with this report block.
3.1.1. Report Block Structure 3.1.1. Report Block Structure
0 1 2 3 The structure of the Burst/Gap Loss Summary Statistics Block is as
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 follows.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=BGLSS | I | Reserved | block length | 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
| SSRC of Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=17 | I | Reserved | Block Length |
| Burst Loss Rate | Gap Loss Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of Source |
| Burst duration Mean | Burst duration Variance | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Burst Loss Rate | Gap Loss Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 A Burst/Gap Loss Summary Statistics Block is identified by the
constant <BGLSS>. constant 17.
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 In this document, the value I=00 is the reserved value and MUST
NOT be used. 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
skipping to change at page 6, line 51 skipping to change at page 6, line 9
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 In this document, the value I=00 is the reserved value and MUST
NOT be used. 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
ignored by the receiver (See RFC6709 section 4.2). 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
Section 3 of RFC 3611 [RFC3611]. Section 3 of RFC 3611 [RFC3611].
SSRC of Source: 32 bits SSRC of Source: 32 bits
As defined in Section 4.1 of RFC3611 [RFC3611]. As defined in Section 4.1 of RFC 3611 [RFC3611].
Burst Loss Rate: 16 bits Burst Loss Rate: 16 bits
The fraction of packets lost during bursts since the beginning of The fraction of packets lost during bursts since the beginning of
reception, expressed as a fixed point number with the binary point reception, expressed as a fixed point number with the binary point
immediately after the left-most bit. This value is calculated by immediately after the left-most bit. This value is calculated by
dividing Packets Lost in Bursts by Total Packets Expected in dividing Packets Lost in Bursts by Total Packets Expected in
Bursts, multiplying the result of the division by 32768 Bursts, multiplying the result of the division by 32768 (0x8000),
(0x8000),and keeping only the integer part. The maximum value is and keeping only the integer part. The maximum value is thus
thus 0x8000. Representing this as a formula: 0x8000. Representing this as a formula:
integer-part( (Packets Lost in Bursts / Total Packets Expected in integer-part( (Packets Lost in Bursts / Total Packets Expected in
Bursts) * 0x8000 ) Bursts) * 0x8000 )
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
Gap Loss Rate: 16 bits Gap Loss Rate: 16 bits
The fraction of packets lost during gaps since the beginning of The fraction of packets lost during gaps since the beginning of
reception expressed as a fixed point number with the binary point reception expressed as a fixed point number with the binary point
immediately after the left-most bit. This value is calculated by immediately after the left-most bit. This value is calculated by
dividing the difference between number of packets lost and Packets dividing the difference between number of packets lost and Packets
lost in Bursts by the difference between Packets Expected and Lost in Bursts by the difference between Packets Expected and
Total Packets expected in Bursts, multiplying the result of the Total Packets Expected in Bursts, multiplying the result of the
division by 32768 (0x8000),and keeping only the integer part. The division by 32768 (0x8000), and keeping only the integer part.
maximum value is thus 0x8000. Representing this as a formula: The maximum value is thus 0x8000. Representing this as a formula:
integer-part ( (number of packets lost - Packets Lost in Bursts)/ integer-part ( (number of packets lost - Packets Lost in Bursts)/
(Packets Expected - Total Packets expected in Bursts) * 0x8000 ) (Packets Expected - Total Packets Expected in Bursts) * 0x8000 )
where "number of packets lost" is obtained from standard RTCP where "number of packets lost" is obtained from standard RTCP
[RFC3550] and Packets Expected is calculated as the difference [RFC3550] and Packets Expected is calculated as the difference
between "extended last sequence number" and "extended first between "extended last sequence number" and "extended first
sequence number" (Interval or Cumulative) provided in the sequence number" (Interval or Cumulative) provided in the
Measurement Identity and Information block [RFC6776]. Measurement Identity and Information Block [RFC6776].
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
Note that if the metric is to be calculated on an Interval basis, Note that if the metric is to be calculated on an Interval basis,
a difference must be taken between the current and preceding a difference must be taken between the current and preceding
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: 16 bits
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 [BGLOSS]. from the RTCP XR Burst/Gap Loss Metrics Block [RFC6958].
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
Burst Duration Variance:16bits Burst Duration Variance: 16 bits
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"
obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. is obtained from the RTCP XR Burst/Gap Loss Metrics Block
[RFC6958].
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
3.2. Burst/Gap Discard Summary Statistics Metrics Block 3.2. Burst/Gap Discard Summary Statistics Block
This Block extends packet loss and discard metrics defined in section This block extends packet loss and discard metrics defined in
4.7.1 of RFC3611. The metrics described here are intended to be used Section 4.7.1 of [RFC3611]. The metrics described here are intended
as described in this section, in conjunction with information from to be used as described in this section, in conjunction with
the Measurement Identity block [RFC6776] (which MUST be present in information from the Measurement Identity Block [RFC6776] (which MUST
the same RTCP packet as the Burst/Gap Discard Summary Statistics be present in the same RTCP packet as the Burst/Gap Discard Summary
block) . Statistics Block).
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 measured at including Burst Discard Rate and Gap Discard Rate, and are measured
the receiving end of the RTP stream using burst gap discard metrics at the receiving end of the RTP stream using burst/gap discard
defined in [BGDISCARD] and other information which is sent together metrics defined in [RFC7003] and other information that is sent
with this report block. together with this report block.
Instances of this Metrics Block refer by Synchronization source Instances of this metrics block use the synchronization source (SSRC)
(SSRC) to the separate auxiliary Measurement Information block to refer to the separate auxiliary Measurement Information block
[RFC6776] which describes measurement periods in use (see [RFC6776] [RFC6776] that describes measurement periods in use (see [RFC6776],
section 4.2). This metrics block relies on the measurement period in Section 4.2). This metrics block relies on the measurement period in
the Measurement Information block indicating the span of the report the Measurement Information Block indicating the span of the report
and SHOULD be sent in the same compound RTCP packet as the and SHOULD be sent in the same compound RTCP packet as the
measurement information block. If the measurement period is not measurement information block. If the measurement period is not
received in the same compound RTCP packet as this Metrics Block, this received in the same compound RTCP packet as this metrics block, this
Metrics Block MUST be discarded. metrics block MUST be discarded.
3.2.1. Report Block Structure 3.2.1. Report Block Structure
0 1 2 3 The structure of the Burst/Gap Discard Summary Statistics Block is as
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 follows.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=BGDSS | I | Reserved | block length | 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
| SSRC of Source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=18 | I | Reserved | Block Length |
| Burst Discard Rate | Gap Discard Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Discard Rate | Gap Discard Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2.2. Definition of Fields in Burst/Gap Discard Summary Statistics 3.2.2. Definition of Fields in Burst/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 A Burst/Gap Discard Summary Statistics Block is identified by the
constant <BGDSS>. constant 18.
Interval Metric Flag (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 In this document, the value I=00 is the reserved value and MUST
NOT be used. 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
skipping to change at page 10, line 9 skipping to change at page 9, line 18
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 In this document, the value I=00 is the reserved value and MUST
NOT be used. 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
ignored by the receiver (See RFC6709 section 4.2). 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].
SSRC of Source: 32 bits SSRC of Source: 32 bits
As defined in Section 4.1 of RFC3611 [RFC3611]. As defined in Section 4.1 of RFC3611 [RFC3611].
Burst Discard Rate: 16 bits Burst Discard Rate: 16 bits
The fraction of packets discarded during bursts since the The fraction of packets discarded during bursts since the
beginning of reception, expressed as a fixed point number with the beginning of reception, expressed as a fixed point number with the
binary point immediately after the left-most bit. This value is binary point immediately after the left-most bit. This value is
calculated by dividing Packets Discarded in Bursts by Total calculated by dividing Packets Discarded in Bursts by Total
Packets expected in Bursts, multiplying the result of the division Packets Expected in Bursts, multiplying the result of the division
by 32768 (0x8000), and keeping only the integer part, according to by 32768 (0x8000), and keeping only the integer part, according to
the formula: the formula:
integer-part( (Packets Discarded in Bursts / Total Packets integer-part( (Packets Discarded in Bursts / Total Packets
expected in Bursts) * 0x8000 ) Expected in Bursts) * 0x8000 )
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
Gap Discard Rate: 16 bits Gap Discard Rate: 16 bits
The fraction of packets discarded during gaps since the beginning The fraction of packets discarded during gaps since the beginning
of reception expressed as a fixed point number with the binary of reception expressed as a fixed point number with the binary
point immediately after the left-most bit. This value is point immediately after the left-most bit. This value is
calculated by dividing the difference between number of packets calculated by dividing the difference between number of packets
discarded and Packets Discarded in Bursts by the difference discarded and Packets Discarded in Bursts by the difference
between Packets Expected and Total Packets expected in Bursts, between Packets Expected and Total Packets Expected in Bursts,
multiplying the result of the division by 32768 (0x8000), and multiplying the result of the division by 32768 (0x8000), and
keeping only the integer part. The maximum value is thus 0x8000. keeping only the integer part. The maximum value is thus 0x8000.
Representing this as a formula: Representing this as a formula:
integer-part( (number of packets discarded - Packets Discarded in integer-part( (number of packets discarded - Packets Discarded in
Bursts) /(Packets Expected - Total Packets expected in Bursts) * Bursts) /(Packets Expected - Total Packets Expected in Bursts) *
0x8000 ) 0x8000 )
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 [DISCARD] and filled with the sum of packets Discard Count Block [RFC7002] and filled with the sum of packets
discarded due to early arrival (DT=1) and packets discarded due to discarded due to early arrival (DT=1) and packets discarded due to
late arrival(DT=2) 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, 2 instances Gap Discard Summary Statistics Block to be meaningful, 2 instances
of the Discard Count block with DT=1 and DT=2 MUST be included in of the Discard Count Block with DT=1 and DT=2 MUST be included in
the same RTCP XR packet as the Burst/Gap Discard Summary the same RTCP XR packet as the Burst/Gap Discard Summary
Statistics Block. Statistics Block.
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
4. Application Level Metrics 4. Application-Level Metrics
4.1. Frame Impairment Statistics Summary Metrics Block 4.1. Frame Impairment Statistics Summary Block
This block extends statistics summary report mechanism defined in This block extends the statistics summary report mechanism defined in
section 4.6 of RFC3611 and reports statistics on which frame type Section 4.6 of [RFC3611] and reports statistics on which frame types
were affected beyond the information carried in the Statistics were affected beyond the information carried in the Statistics
Summary Report Block RTCP packet specified in the section 4.6 of RFC Summary Report Block RTCP packet specified in Section 4.6 of
3611 [RFC3611]. Information is measured at the receiving end of the [RFC3611]. Information is measured at the receiving end of the RTP
RTP stream and recorded about the number of frames received, lost stream and recorded about the number of frames received, lost frames,
frames, duplicated frames and lost partial frames. Such information duplicated frames, and lost partial frames. Such information can be
can be useful for network management and video quality monitoring. useful for network management and video quality monitoring.
4.1.1. Report Block Structure 4.1.1. Report Block Structure
0 1 2 3 The structure of the Frame Impairment Statistics Summary Block is as
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 follows.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=FISS |T| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discarded_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Full_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partial_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.1.2. Definition of Fields in Frame Impairment Summary Statistics 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=19 |T| Reserved | Block Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| discarded_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| full_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| partial_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.1.2. Definition of Fields in Frame Impairment Statistics Summary
Block Block
Block type (BT): 8 bits Block Type (BT): 8 bits
Frame Impairment Statistics Summary Block is identified by the A Frame Impairment Statistics Summary Block is identified by the
constant <FISS>. constant 19.
Frame type indicator (T): 1 bit Frame 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 full_lost_frames, partial_lost_frames, bit is set to 0 if the full_lost_frames, partial_lost_frames,
dup_frames,discarded_frames and Number of frames received fields dup_frames, and discarded_frames fields contain Key frame
contain Key frame (reference frame) counts or 1 if they contain (reference frame) counts or 1 if they contain Derived frame
Derived frame counts. Note that if both the Key frame and counts. Note that if both the Key frame and Derivation frame
Derivation frame report are sent, they should be sent in the same report are sent, they should be sent in the same RTCP compound
RTCP compound packet using two Frame Impairment Summary Statistics packet using two Frame Impairment Statistics Summary Blocks.
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
ignored by the receiver (See RFC6709 section 4.2). ignored by the receiver (see [RFC6709], Section 4.2).
Block Length: 16 bits Block Length: 16 bits
The constant 6, in accordance with the definition of this field in The constant 6, in accordance with the definition of this field in
Section 3 of RFC 3611 [RFC3611]. Section 3 of RFC 3611 [RFC3611].
SSRC of Source: 32 bits SSRC of Source: 32 bits
As defined in Section 4.1 of RFC3611 [RFC3611]. As defined in Section 4.1 of RFC 3611 [RFC3611].
begin_seq: 16 bits begin_seq: 16 bits
As defined in Section 4.1 of RFC 3611 [RFC3611]. As defined in Section 4.1 of RFC 3611 [RFC3611].
end_seq: 16 bits end_seq: 16 bits
As defined in Section 4.1 of RFC 3611 [RFC3611]. As defined in Section 4.1 of RFC 3611 [RFC3611].
Number of discarded frames (discarded_frames): 32 bits Number of discarded frames (discarded_frames): 32 bits
skipping to change at page 13, line 13 skipping to change at page 12, line 34
Number of frames discarded in the above sequence number interval. Number of frames discarded in the above sequence number interval.
Number of duplicate frames (dup_frames): 32 bits Number of duplicate frames (dup_frames): 32 bits
Number of duplicate frames received in the above sequence number Number of duplicate frames received in the above sequence number
interval. interval.
Number of full lost frames (full_lost_frames): 32 bits Number of full lost frames (full_lost_frames): 32 bits
A frame is either split across multiple packets or carried in only A frame is either split across multiple packets or carried in only
one packet.If the whole frame or all the packets of the frame is one packet. If the whole frame or all the packets of the frame
lost, this frame is regarded as one full_lost_frame. The are lost, this frame is regarded as one full_lost_frame. The
full_lost_frames can be inferred from packet(s) that comprise the full_lost_frames can be inferred from packet(s) that comprise the
frame. The full_lost_ frames is equivalent to the number of full frame. The full_lost_frames is equivalent to the number of full
lost frames in the above sequence number interval. lost frames in the above sequence number interval.
Number of partial lost frames (partial_lost_frames): 32 bits Number of partial lost frames (partial_lost_frames): 32 bits
When a frame is split across multiple packets and some packets of When a frame is split across multiple packets and some packets of
the frame are lost, this frame is regarded as one the frame are lost, this frame is regarded as one
partial_lost_frame. The partial_lost_frames can be inferred from partial_lost_frame. The partial_lost_frames can be inferred from
packets that comprise the frame. The value of the packets that comprise the frame. The value of the
partial_lost_frames field is equivalent to the number of partial partial_lost_frames field is equivalent to the number of partial
lost frames in the above sequence number interval. lost frames in the above sequence number interval.
5. SDP Signaling 5. SDP Signaling
RFC 3611 defines the use of SDP (Session Description Protocol) RFC 3611 defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. However XR blocks MAY [RFC4566] for signaling the use of XR blocks. However, XR blocks MAY
be used without prior signaling (see section 5 of RFC3611). be used without prior signaling (see Section 5 of [RFC3611]).
5.1. SDP rtcp-xr-attrib Attribute Extension 5.1. SDP rtcp-xr Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in Section 5.1 of RFC 3611 by providing three additional values of in Section 5.1 of [RFC3611] by providing three additional values of
"xr-format" to signal the use of the report block defined in this "xr-format" to signal the use of the report block defined in this
document. document. The ABNF [RFC5234] syntax is as follows.
xr-format = / xr-bglss-block xr-format =/ xr-bglss-block
/ xr-bgdss-block / xr-bgdss-block
/ xr-fiss-block / xr-fiss-block
xr-bglss-block= "burst-gap-loss-stat" xr-bglss-block = "burst-gap-loss-stat"
xr-bgdss-block = "burst-gap-discard-stat" xr-bgdss-block = "burst-gap-discard-stat"
xr-fiss-block= "frame-impairment-stat" xr-fiss-block = "frame-impairment-stat"
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 [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage of Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. 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 "RTP Control This document assigns three new block type values in the "RTP Control
Protocol (RTCP) Extended Report (XR) Block Type Registry" : Protocol Extended Reports (RTCP XR) Block Type Registry":
Name: BGLSS Name: BGLSS
Long Name: Burst/Gap Loss Summary Statistics Block Long Name: Burst/Gap Loss Summary Statistics Block
Value <BGLSS> Value 17
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 18
Reference: Section 3.2 Reference: Section 3.2
Name: FISS Name: FISS
Long Name: Frame Impairment Statistics Summary Long Name: Frame Impairment Statistics Summary Block
Value <FISS> Value 19
Reference: Section 4.1 Reference: Section 4.1
6.2. New RTCP XR SDP Parameters 6.2. New RTCP XR SDP Parameters
This document also registers three new SDP [RFC4566] parameters for This document also registers three new SDP [RFC4566] parameters for
the "rtcp-xr" attribute in the " RTP Control Protocol (RTCP) Extended the "rtcp-xr" attribute in the "RTP Control Protocol Extended Reports
Report (XR) SDP Parameters Registry ": (RTCP XR) Session Description Protocol (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:
Qin Wu (sunseawq@huawei.com) Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
7. Security Considerations 7. Security Considerations
The new RTCP XR report blocks proposed in this document introduces no The new RTCP XR blocks in this document do not introduce any new
new security considerations beyond those described in RFC 3611. security considerations beyond those described in [RFC3611].
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, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu, Alfred
Jr., Alfred, Klaas Wierenga, Barry Leiba, Robert Sparks, Ralph Droms Morton, Jr., Klaas Wierenga, Barry Leiba, Robert Sparks, Ralph Droms,
and Benoit Claise for their valuable comments and suggestions on this and Benoit Claise for their valuable comments and suggestions on this
document. 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
November 2003. 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.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
using SDES item and XR Block", RFC 6776, August 2012. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
Reporting Using a Source Description (SDES) Item and an
RTCP Extended Report (XR) Block", RFC 6776, October 2012.
[RFC6958] Clark, A., Zhang, S., Zhao, J., and Q. Wu, "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Loss Metric Reporting", RFC 6958, May 2013.
[RFC7002] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol
(RTCP) Extended Report (XR) Block for Discard Count Metric
Reporting", RFC 7002, September 2013.
[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
Discard Metric Reporting", RFC 7003, September 2013.
9.2. Informative References 9.2. Informative References
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New [RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", RFC 6390, October 2011. Performance Metric Development", BCP 170, RFC 6390,
October 2011.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012.
[RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures [RFC6792] Wu, Q., Hunt, G., and P. Arden, "Guidelines for Use of the
for RTP", RFC 6792, November 2012. RTP Monitoring Framework", RFC 6792, November 2012.
Appendix A. Metrics represented using RFC6390 Template
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC Appendix A. Metrics Represented Using the Template from RFC 6390
number, when assigned.
a. Burst Loss Rate Metric a. Burst Loss Rate Metric
* Metric Name: RTP Burst Loss Rate * Metric Name: RTP Burst Loss Rate
* Metric Description: The fraction of packets lost during bursts * Metric Description: The fraction of packets lost during bursts
since the beginning of reception for RTP traffic. since the beginning of reception for RTP traffic.
* Method of Measurement or Calculation: See section 3.1.2, Burst * Method of Measurement or Calculation: See Section 3.1.2, Burst
Loss Rate definition [RFCXXXX]. Loss Rate definition.
* Units of Measurement: See section 3.1.2, Burst Loss Rate * Units of Measurement: See Section 3.1.2, Burst Loss Rate
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3.1, 2nd paragraph [RFCXXXX]. Section 3.1, 2nd paragraph.
* Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] * Measurement Timing: See Section 3.1, 1st paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
b. Gap Loss Rate Metric b. Gap Loss Rate Metric
* Metric Name: RTP Gap Loss Rate * Metric Name: RTP Gap Loss Rate
* Metric Description: The fraction of packets lost during gaps * Metric Description: The fraction of packets lost during gaps
since the beginning of reception for RTP traffic. since the beginning of reception for RTP traffic.
* Method of Measurement or Calculation: See section 3.1.2, Gap * Method of Measurement or Calculation: See Section 3.1.2, Gap
Loss Rate definition [RFCXXXX]. Loss Rate definition.
* Units of Measurement: See section 3.1.2, Gap Loss Rate * Units of Measurement: See Section 3.1.2, Gap Loss Rate
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3.1, 2nd paragraph [RFCXXXX]. Section 3.1, 2nd paragraph.
* Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] * Measurement Timing: See Section 3.1, 1st paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
c. Burst duration Mean Metric c. Burst Duration Mean Metric
* Metric Name: RTP Burst duration Mean * Metric Name: RTP Burst Duration Mean
* Metric Description: The mean duration of the burst periods * Metric Description: The mean duration of the burst periods
that have occurred since the beginning of reception for RTP that have occurred since the beginning of reception for RTP
traffic. traffic.
* Method of Measurement or Calculation: See section 3.1.2, Burst * Method of Measurement or Calculation: See Section 3.1.2, Burst
Loss Rate definition [RFCXXXX]. Loss Rate definition.
* Units of Measurement: This metric is expressed in * Units of Measurement: This metric is expressed in
milliseconds. milliseconds.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3.1, 2nd paragraph [RFCXXXX]. Section 3.1, 2nd paragraph.
* Measurement Timing: See section 3.1, 1st paragraph [RFCXXXX] * Measurement Timing: See Section 3.1, 1st paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
d. Burst duration variance Metric d. Burst Duration Variance Metric
* Metric Name: RTP Burst duration variance * Metric Name: RTP Burst Duration Variance
* Metric Description: The variance duration of the burst periods * Metric Description: The variance duration of the burst periods
that have occurred since the beginning of reception for RTP that have occurred since the beginning of reception for RTP
traffic. traffic.
* Method of Measurement or Calculation: See section 4.1.2, Gap * Method of Measurement or Calculation: See Section 3.1.2, Burst
Loss Rate definition [RFCXXXX]. Duration Variance definition.
* Units of Measurement: See section 3.1.2, Burst Duration * Units of Measurement: See Section 3.1.2, Burst Duration
Variance definition [RFCXXXX]. Variance definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4.1, 2nd paragraph [RFCXXXX]. Section 3.1, 2nd paragraph.
* Measurement Timing: See section 4.1, 1st paragraph [RFCXXXX] * Measurement Timing: See Section 3.1, 1st paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
e. Burst Discard metric e. Burst Discard Rate Metric
* Metric Name: RTP Burst Discard Rate * Metric Name: RTP Burst Discard Rate
* Metric Description: The fraction of packets discarded during * Metric Description: The fraction of packets discarded during
bursts since the beginning of reception for RTP traffic. bursts since the beginning of reception for RTP traffic.
* Method of Measurement or Calculation: See section 3.2.2, Burst * Method of Measurement or Calculation: See Section 3.2.2, Burst
Discard Rate definition [RFCXXXX]. Discard Rate definition.
* Units of Measurement: See section 3.2.2, Burst Discard Rate * Units of Measurement: See Section 3.2.2, Burst Discard Rate
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3.2, 2nd paragraph [RFCXXXX]. Section 3.2, 2nd paragraph.
* Measurement Timing: See section 3.2, 3rd paragraph [RFCXXXX] * Measurement Timing: See Section 3.2, 3rd paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
f. Gap Discard Rate metric f. Gap Discard Rate Metric
* Metric Name: RTP Gap Discard Rate * Metric Name: RTP Gap Discard Rate
* Metric Description: The fraction of packets discarded during * Metric Description: The fraction of packets discarded during
gaps since the beginning of reception for RTP traffic. gaps since the beginning of reception for RTP traffic.
* Method of Measurement or Calculation: See section 3.2.2, Gap * Method of Measurement or Calculation: See Section 3.2.2, Gap
Discard Rate definition [RFCXXXX]. Discard Rate definition.
* Units of Measurement: See section 3.2.2, Gap Discard Rate * Units of Measurement: See Section 3.2.2, Gap Discard Rate
definition [RFCXXXX]. definition.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 3.2, 2nd paragraph [RFCXXXX]. Section 3.2, 2nd paragraph.
* Measurement Timing: See section 3.2, 3rd paragraph [RFCXXXX] * Measurement Timing: See Section 3.2, 3rd paragraph for
for measurement timing and section 3.1.2 [RFCXXXX] for measurement timing and Section 3.1.2 for Interval Metric flag.
Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
g. Number of discarded frames metric g. Number of Discarded Frames Metric
* Metric Name: Number of discarded frames in RTP * Metric Name: Number of discarded frames in RTP
* Metric Description: Number of frames discarded in a certain * Metric Description: Number of frames discarded in a certain
sequence number interval for RTP traffic. sequence number interval for RTP traffic.
* Method of Measurement or Calculation: See section 4.1.2, * Method of Measurement or Calculation: See Section 4.1.2,
Number of discarded frames definition [RFCXXXX]. This metric Number of discarded frames definition. This metric is
is directly measured and can be inferred from packet(s) that directly measured and can be inferred from packet(s) that
comprise the frame. comprise the frame.
* Units of Measurement: This metric is expressed as 32-bit * Units of Measurement: This metric is expressed as a 32-bit
unsigned integer value. unsigned integer value.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4.1, 1st paragraph [RFCXXXX]. Section 4.1, 1st paragraph.
* Measurement Timing: See section 4.1 [RFCXXXX], Number of * Measurement Timing: See Section 4.1, Number of discarded
discarded frames definition, this metric relies on sequence frames definition. This metric relies on the sequence number
number interval and RTCP RR packet of RFC3550 to determine interval and RTCP RR packet of [RFC3550] to determine
measurement timing. measurement timing.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
h. Number of duplicate frames metric h. Number of Duplicate Frames Metric
* Metric Name: Number of duplicate frames in RTP * Metric Name: Number of duplicate frames in RTP
* Metric Description: Number of frames duplicated in a certain * Metric Description: Number of frames duplicated in a certain
sequence number interval for RTP traffic. sequence number interval for RTP traffic.
* Method of Measurement or Calculation: See section 4.1.2, * Method of Measurement or Calculation: See Section 4.1.2,
Number of discarded frames definition [RFCXXXX], This metric Number of duplicate frames definition. This metric is
is directly measured and can be inferred from packet(s) that directly measured and can be inferred from packet(s) that
comprise the frame. comprise the frame.
* Units of Measurement: This metric is expressed as 32-bit * Units of Measurement: This metric is expressed as a 32-bit
unsigned integer value. unsigned integer value.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4.1, 1st paragraph [RFCXXXX]. Section 4.1, 1st paragraph.
* Measurement Timing: See section 4.1 [RFCXXXX], Number of * Measurement Timing: See Section 4.1, Number of duplicate
duplicate frames definition, this metric relies on sequence frames definition. This metric relies on the sequence number
number interval to determine measurement timing. interval to determine measurement timing.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
i. Number of full lost frames metric i. Number of Full Lost Frames Metric
* Metric Name: Number of full lost frames in RTP * Metric Name: Number of full lost frames in RTP
* Metric Description: A frame is either split across multiple * Metric Description: A frame is either split across multiple
RTP packets or carried in only one RTP packet.If the whole RTP packets or carried in only one RTP packet. If the whole
frame or all the packets of the frame is lost, this frame is frame or all the packets of the frame is lost, this frame is
regarded as one full_lost_frame. regarded as one full_lost_frame.
* Method of Measurement or Calculation: See section 4.1.2, * Method of Measurement or Calculation: See Section 4.1.2,
Number of discarded frames definition [RFCXXXX]. Number of full lost frames definition.
* Units of Measurement: This metric is expressed as 32-bit * Units of Measurement: This metric is expressed as a 32-bit
unsigned integer value. unsigned integer value.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4.1, 1st paragraph [RFCXXXX]. Section 4.1, 1st paragraph.
* Measurement Timing: See section 4.1 [RFCXXXX], Number of full * Measurement Timing: See Section 4.1, Number of full lost
lost frames definition [RFCXXXX], this metric relies on frames definition. This metric relies on the sequence number
sequence number interval to determine measurement timing. interval to determine measurement timing.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and Applications: See Section 1.4.
* Reporting model: See RFC3611. * Reporting Model: See RFC 3611.
j. Number of partial lost frames metric j. Number of Partial Lost Frames Metric
* Metric Name: Number of partial lost frames in RTP * Metric Name: Number of partial lost frames in RTP
* Metric Description: When a frame is split across multiple RTP * Metric Description: When a frame is split across multiple RTP
packets and some RTP packets of the frame are lost, this frame packets and some RTP packets of the frame are lost, this frame
is regarded as one partial_lost_frame. is regarded as one partial_lost_frame.
* Method of Measurement or Calculation: See section 4.1.2, * Method of Measurement or Calculation: See Section 4.1.2,
Number of partial lost frames definition [RFCXXXX]. Number of partial lost frames definition.
* Units of Measurement: This metric is expressed as 32-bit * Units of Measurement: This metric is expressed as a 32-bit
unsigned integer value. unsigned integer value.
* Measurement Point(s) with Potential Measurement Domain: See * Measurement Point(s) with Potential Measurement Domain: See
section 4.1, 1st paragraph [RFCXXXX]. Section 4.1, 1st paragraph.
* Measurement Timing: See section 4.1 [RFCXXXX], Number of
partial lost frames definition, this metric relies on sequence
number interval to determine measurement timing.
* Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611.
Appendix B. Change Log
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-summary-stat-11
The following are the major changes compared to 10:
o Incorporate the last proposed change by Barry when his DISCUSS was
cleared.
B.2. draft-ietf-xrblock-rtcp-xr-summary-stat-10
The following are the major changes compared to 09:
o Add appendix to apply RFC6390 template to metrics in this draft.
B.3. draft-ietf-xrblock-rtcp-xr-summary-stat-09
The following are the major changes compared to 08:
o Address comments in the IESG Review.
B.4. draft-ietf-xrblock-rtcp-xr-summary-stat-08
The following are the major changes compared to 07:
o Address comments raised in Sec-DIR review.
B.5. draft-ietf-xrblock-rtcp-xr-summary-stat-07
The following are the major changes compared to 06:
o Add comments raised in PM-DIR review by Al.
B.6. draft-ietf-xrblock-rtcp-xr-summary-stat-06
The following are the major changes compared to 05: * Measurement Timing: See Section 4.1, Number of partial lost
o Move RFC6709 to informative reference. frames definition. This metric relies on the sequence number
interval to determine measurement timing.
B.7. draft-ietf-xrblock-rtcp-xr-summary-stat-05 * Use and Applications: See Section 1.4.
The following are the major changes compared to 04: * Reporting Model: See RFC 3611.
o Editorial changes to get in line with Delay and Burst Gap related
drafts.
Authors' Addresses Authors' Addresses
Glen Zorn Glen Zorn
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
Email: glenzorn@gmail.com EMail: glenzorn@gmail.com
Roland Schott Roland Schott
Deutsche Telekom Deutsche Telekom
Deutsche-Telekom-Allee 7 Deutsche-Telekom-Allee 7
Darmstadt 64295 Darmstadt 64295
Germany Germany
Email: Roland.Schott@telekom.de EMail: Roland.Schott@telekom.de
Qin Wu (editor) 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
Rachel Huang Rachel Huang
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing 210012 Nanjing 210012
China China
Email: Rachel@huawei.com EMail: Rachel@huawei.com
 End of changes. 176 change blocks. 
444 lines changed or deleted 391 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/