draft-ietf-xrblock-rtcp-xr-summary-stat-01.txt   draft-ietf-xrblock-rtcp-xr-summary-stat-02.txt 
Network Working Group G. Zorn 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: April 18, 2013 Deutsche Telekom Expires: April 25, 2013 Deutsche Telekom
Q. Wu Q. Wu
R. Huang R. Huang
Huawei Huawei
October 15, 2012 October 22, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block 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-01 draft-ietf-xrblock-rtcp-xr-summary-stat-02
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 allows the Report (XR) Blocks and associated SDP parameters that allow the
reporting of loss, duplication and discard summary statistics metrics reporting of loss, duplication and discard summary statistics metrics
for use 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 April 18, 2013. This Internet-Draft will expire on April 25, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3
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 Block . . . . . . . . . 4
3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 4 3.1.1. Report Block Structure . . . . . . . . . . . . . . . . 4
3.1.2. Definition of Fields in Loss Summary Statistics 3.1.2. Definition of Fields in Loss Summary Statistics
Block . . . . . . . . . . . . . . . . . . . . . . . . 4 Block . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 6 3.2. Burst/Gap Discard Summary Statistics Block . . . . . . . . 6
3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 6 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 7
3.2.2. Definition of Fields in Discard Summary Statistics 3.2.2. Definition of Fields inBurst/Gap Discard Summary
Block . . . . . . . . . . . . . . . . . . . . . . . . 7 Statistics Block . . . . . . . . . . . . . . . . . . . 7
4. Application Level Metrics . . . . . . . . . . . . . . . . . . 8 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 8
4.1. Frame Impairment Statistics Summary Block . . . . . . . . 8 4.1. Frame Impairment Statistics Summary Block . . . . . . . . 9
4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . . 9
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 11
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 12
6.3. Contact information for registrations . . . . . . . . . . 12 6.3. Contact information for registrations . . . . . . . . . . 12
skipping to change at page 3, line 8 skipping to change at page 3, line 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 13
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-01 . . . . . . . . 14 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-01 . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
This draft defines three new block types to augment those defined in This draft defines three new block types to augment those defined in
[RFC3611] for use in a range of RTP applications. Freidman, et al. [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 [MONARCH]. These two blocks are intended system metrics defined in Wu, Hunt & Arden
to be used in conjunction with information from the Burst Gap Loss [I-D.ietf-avtcore-monarch]. These two blocks are intended to be used
metric block or Burst Gap Discard metric block, and on which these in conjunction with information from the Burst Gap Loss metric block
two block therefore depends. However the metrics in the Burst Gap or Burst Gap Discard metric block, and on which these two block
Loss block or Burst Gap Discard metric block may be used therefore depend. The metrics in the Burst Gap Loss block or Burst
independently of the metrics defined in the first two blocks.These Gap Discard metric block can be used independently of the metrics
two blocks reflect transient IP problem that affect user experience defined in the first two blocks, however. These two blocks reflect
and can be used to influence sender strategies to mitigate the transient IP problems that affect user experience and can be used to
problem. influence sender strategies to mitigate the problem.
To form an accurate assessment of user quality of experience, it is To form an accurate assessment of users' quality of experience, it is
therefore necessary to know not just overall rates of packet loss/ therefore necessary to know not just overall rates of packet loss/
discard, but also which frame type were affected. The third block discard, but also which frame types were affected. The third block
supports the reporting of detailed statistics for each frame type, supports the reporting of detailed statistics for each frame type,
including the number of received, lost and discarded of each frame including the number of frames received, lost and discarded of each
type in the Group of Pictures (GOP) and additional data allowing the frame type in the Group of Pictures (GOP) and additional data
calculation of statistical parameters (e.g.,the proportion of each allowing the calculation of statistical parameters (e.g.,the
frame type impaired by packet loss and discard). The metrics defined proportion of each frame type impaired by packet loss and discard).
in this block belong to the class of application layer metrics The metrics defined in this block belong to the class of application
defined in [MONARCH]. layer metrics defined in Wu, Hunt & Arden [I-D.ietf-avtcore-monarch].
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:
Picture Type Picture Type
Picture types used in the different video algorithms compose of Picture Types used in the different video algorithms are composed
the key-frame and the Derived frame. Key-frame is also called a of the Key frame and Derived frames. The Key frame is also called
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.
The Derived frame is derived from Key-frame using prediction from Derived frames are derived from a Key frame using a prediction
the reference frame. 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 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 [MEASIDENT] (which MUST be present in the same RTCP Information block [I-D.ietf-xrblock-rtcp-xr-meas-identity] (which
packet as the Burst/Gap Loss block) and also with the metric MUST be present in the same RTCP packet as the Burst/Gap Loss block)
"cumulative number of packets lost" provided in standard RTCP and also with the metric "cumulative number of packets lost" provided
[RFC3550]. in standard RTCP [RFC3550].
These metrics provide information relevant to statistical parameters, These metrics provide information relevant to statistical parameters,
including burst loss rate, gap loss rate, burst duration mean, burst including burst loss rate, gap loss rate, burst duration mean, burst
duration variance and are calculated using burst gap loss metrics duration variance and are calculated using burst gap loss metrics
defined in [BGLOSS] and other information which is sent together with defined in [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss] and other
this report block. 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 47 skipping to change at page 4, line 47
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,
that is, whether the reported values applies to the most recent that is, whether the reported values apply to the most recent
measurement interval duration between successive metrics reports measurement interval duration between successive metrics reports
(I=10) (the Interval Duration) or to the accumulation period (I=10) (the Interval Duration) or to the accumulation period
characteristic of cumulative measurements (I=11) (the Cumulative characteristic of cumulative measurements (I=11) (the Cumulative
Duration) or is a sampled instantaneous value (I=01) (Sampled Duration) or is a sampled instantaneous value (I=01) (Sampled
Value). Value).
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
MUST be ignored by the receiver. SHOULD be ignored by the receiver.
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 RFC3611 [RFC3611].
skipping to change at page 5, line 46 skipping to change at page 5, line 46
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 as follows: Total Packets expected in Bursts as follows:
(number of packets lost - Packets Lost in Bursts) / (Packets (number of packets lost - Packets Lost in Bursts) / (Packets
Expected - Total Packets expected in Bursts) Expected - Total Packets expected in Bursts)
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 [MEASIDENT]. Measurement Identity and Information block
[I-D.ietf-xrblock-rtcp-xr-meas-identity].
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: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 [BGLOSS]. from the RTCP XR Burst/Gap Loss Block
[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 where "Sum of Squares of Burst Durations" and "Number of Bursts"is
Bursts"is obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. obtained from the RTCP XR Burst/Gap Loss Block
[I-D.ietf-xrblock-rtcp-xr-burst-gap-loss].
3.2. Burst/Gap Discard Summary Statistics Block 3.2. Burst/Gap Discard Summary Statistics 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 [MEASIDENT] (which MUST be present in the same RTCP Identity block [I-D.ietf-xrblock-rtcp-xr-meas-identity] (which MUST
packet as the Burst/Gap Discard block) and also with the metric be present in the same RTCP packet as the Burst/Gap Discard Summary
"number of packets discarded" provided in the RTCP XR Discard Block Statistics block) and also with the metric "number of packets
[DISCARD]. The RTCP XR Discard Block SHOULD be sent if the Burst/Gap discarded" provided in the RTCP XR Discard Block
Discard block is sent, but the converse does not apply. [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
using burst gap loss metrics defined in [BGDISCARD] and other using burst gap loss metrics defined in
information which is sent together with this report block. [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard] and other information
which is sent together with this report block.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Discard Rate | Gap Discard Rate | | Burst Discard Rate | Gap Discard Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2.2. Definition of Fields in Discard Summary Statistics Block 3.2.2. Definition of Fields inBurst/Gap Discard Summary Statistics
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>.
Reserved: 8 bits Interval Metric Type (I): 2 bits
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
MUST be ignored by the receiver.
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, that is, whether the reported values applies to the most metrics, that is, whether the reported values applies to the most
recent measurement interval duration between successive metrics recent measurement interval duration between successive metrics
reports (I=10) (the Interval Duration) or to the accumulation reports (I=10) (the Interval Duration) or to the accumulation
period characteristic of cumulative measurements (I=11) (the period characteristic of cumulative measurements (I=11) (the
Cumulative Duration) or is a sampled instantaneous value (I=01) Cumulative Duration) or is a sampled instantaneous value (I=01)
(Sampled Value). (Sampled Value).
Reserved: 6 bits Reserved: 6 bits
This field is used to indicate whether the Burst/Gap Discard This field is reserved for future definition. In the absence of
Summary Statistics metrics are Sampled, Interval or Cumulative such a definition, the bits in this field MUST be set to zero and
metrics, that is, whether the reported values applies to the most SHOULD be ignored by the receiver.
recent measurement interval duration between successive metrics
reports (I=10) (the Interval Duration) or to the accumulation
period characteristic of cumulative measurements (I=11) (the
Cumulative Duration) or is a sampled instantaneous value (I=01)
(Sampled Value).
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].
skipping to change at page 8, line 28 skipping to change at page 8, line 28
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 [DISCARD] and Packets Expected is calculated Discard Count Block [I-D.ietf-xrblock-rtcp-xr-discard] and Packets
as the difference between "extended last sequence number" and Expected is calculated as the difference between "extended last
"extended first sequence number" (Interval or Cumulative) provided sequence number" and "extended first sequence number" (Interval or
in the Measurement Information block [MEASIDENT]. In order for Cumulative) provided in the Measurement Information block
Burst/Gap Discard Summary Statistics Block to be meaningful either [I-D.ietf-xrblock-rtcp-xr-meas-identity]. In order for the Burst/
1. a single instance of the Discard Count block with DT=3 or 2. Gap Discard Summary Statistics Block to be meaningful either
exactly 2 instances of the Discard Count block with DT=1 and DT=2,
respectively MUST be included in the same RTCP compound packet.
In this case,if Discard Count (DT=3) Block is received, "the
number of packet discarded"is be filled with the number of packets
discarded due to both early and late arrival(DT=3); if Discard
Count (DT=3) is not received, "the number of packet discarded" is
calculated as the sum of packet discards due to early arrival
(DT=1)and packet discards due to late arrival(DT=2).
4. Application Level Metrics 1. a single instance of the Discard Count block with DT=3 or
2. exactly 2 instances of the Discard Count block with DT=1 and
DT=2, respectively
MUST be included in the same RTCP compound packet. If a Discard
Count block with DT=3 is received, "the number of packet
discarded" is be filled with the number of packets discarded due
to both early and late arrival; otherwise, "the number of packet
discarded" is calculated as the sum of packet discards due to
early arrival (DT=1) and packet discards due to late arrival
(DT=2).
4. Application Level Metrics
4.1. Frame Impairment Statistics Summary Block 4.1. Frame Impairment Statistics Summary 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 umber of frames received, lost frames Information is recorded about thenumber of frames received, lost
,duplicated frames, lost partial frames. Such information can be frames, duplicated frames and lost partial frames. Such information
useful for network management and video quality monitoring. 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 |I| Reserved | block length | | BT=FISS |I| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 9, line 38 skipping to change at page 9, line 45
4.1.2. Definition of Fields in Frame Impairment Summary Statistics 4.1.2. Definition of Fields in Frame Impairment Summary Statistics
Block Block
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 (I): 1 bit Picture type indicator (I): 1 bit
Picture types used in the different video algorithms compose of This field is used to indicate the frame type to be reported. The
key-frame and derivation frame. This field is used to indicate bit is set to 0 if the lost_full_frames, lost_partial_frames and
the frame type to be reported. Bits set to 0 if the lost_frames dup_frames fields contain Key frame (reference frame) counts or 1
field or dup_frames field contain a key_frame report or reference if they contain Derivation frame counts. Note that if both the
frame report, 1 if the lost_frames field and dup_frames field Key frame and Derivation frame report are sent, they should be
contain other derivation frame report. Note that if both the key sent in the same RTCP compound packet using two Frame Impairment
frame report and derivation frame are sent, they should be sent in Summary Statistics Blocks.
the same RTCP compound packet using two XR 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
MUST 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
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].
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 frames received:32bits Number of frames received:32 bits
A count of the number of frames received, estimated if necessary. A count of the number of frames received in the above sequence
If no frames have been received then this count shall be set to number interval, estimated if necessary. If no frames have been
Zero. received then this count SHALL be set to zero.
Number of discarded frames (discarded_frames): 32 bits Number of discarded frames (discarded_frames): 32 bits
Number of frames discarded in the above sequence number interval. Number of frames discarded in the above sequence number interval.
Number of duplicated frames (dup_frames): 32 bits Number of duplicate frames (dup_frames): 32 bits
Number of duplicated frames in the above sequence number interval. Number of duplicate frames received in the above sequence number
interval.
Number of full frames lost (lost_full_frames): 32 bits Number of full frames lost (lost_full_frames): 32 bits
If one frame is completely lost, this frame is regarded as one If one frame is completely lost, this frame is regarded as one
lost full_frame. The lost_full_frames is equivalent to the number lost full frame. The lost_full_frames is equivalent to the number
of full frames lost in the above sequence number interval. of full frames lost in the above sequence number interval.
Number of partial frames lost (lost_partial_frames): 32 bits Number of partial frames lost (lost_partial_frames): 32 bits
If one frame is partially lost, this frame is regarded as one lost If one frame is partially lost, this frame is regarded as one lost
fractional frame. The lost_partial_frames is equivalent to the fractional frame. The value of the lost_partial_frames field is
number of partial_frames lost in the above sequence number equivalent to the number of partial frames lost in the above
interval. sequence number interval.
5. SDP Signaling 5. SDP Signaling
[RFC3611] 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. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling. without prior signaling.
5.1. SDP rtcp-xr-attrib Attribute Extension 5.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing three additional value of "xr-format" to in Section 5.1 of RFC 3611 by providing three additional values of
signal the use of the report block defined in this document. "xr-format" to signal the use of the report block defined in this
document.
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 [RFC3611] applies. defined in Section 5.2 of RFC 3611 applies.
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 general guidelines on IANA considerations for RTCP XR, refer to RFC
to[RFC3611] . 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 Summsary Statistics Block
Value <BGLSS> Value <BGLSS>
Reference: Section 3.1 Reference: Section 3.1
skipping to change at page 12, line 36 skipping to change at page 12, line 36
* " 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 Glen Zorn
Network Zen Network Zen
227/358 Thanon Sanphawut 227/358 Thanon Sanphawut
Bang Na, Bangkok 10110 Bang Na, Bangkok 10260
Thailand 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 [RFC3611]. 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 Brandenburg, R. (Ray) van for their valuable Hu, Jing Zhao and Ray van Brandenburg for their valuable comments and
comments and suggestions on this document. suggestions on this document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", 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
skipping to change at page 13, line 25 skipping to change at page 13, line 25
[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 9.2. Informative References
[BGDISCARD] [I-D.ietf-avtcore-monarch]
Hunt, G., "RTCP XR Report Block for Burst Gap Discard Wu, W., Hunt, G., and P. Arden, "Guidelines for Use of the
metric Reporting", RTP Monitoring Framework", draft-ietf-avtcore-monarch-22
ID draft-ietf-xrblock-rtcp-xr-burst-gap-discard-09, (work in progress), September 2012.
October 2012.
[BGLOSS] Hunt, G., "RTCP XR Report Block for Burst Gap Loss metric
Reporting",
ID draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04,
October 2012.
[DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard]
Reporting", ID draft-ietf-xrblock-rtcp-xr-discard-09, Clark, A., Huang, R., and W. Wu, "RTP Control
October 2012. 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.
[MEASIDENT] [I-D.ietf-xrblock-rtcp-xr-burst-gap-loss]
Wu, Q., "Measurement Identity and information Reporting Clark, A., Zhang, S., Zhao, J., and W. Wu, "RTP Control
using SDES item and XR Block", Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
ID draft-ietf-xrblock-rtcp-xr-meas-identity-10, Loss metric Reporting",
August 2012. draft-ietf-xrblock-rtcp-xr-burst-gap-loss-04 (work in
progress), October 2012.
[MONARCH] Wu, Q., "Monitoring Architecture for RTP", [I-D.ietf-xrblock-rtcp-xr-discard]
ID draft-ietf-avtcore-monarch-22, September 2012. 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.
[RFC6390] Clark, A., "Framework for Performance Metric Development", [I-D.ietf-xrblock-rtcp-xr-meas-identity]
RFC 6390, January 2011. Clark, A. and W. Wu, "Measurement Identity and information
Reporting using SDES item and XR Block",
draft-ietf-xrblock-rtcp-xr-meas-identity-10 (work in
progress), August 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-01 A.1. 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 00:
o Outdated Reference update o Outdated Reference update
o Add text to clarify the selection of discard count based on o Add text to clarify the selection of discard count based on
discard count metric block. discard count metric block.
o Revise Interval metric flag defintion for consistency. o Revise Interval metric flag defintion for consistency.
o SDP text restructure o SDP text restructure
o Other editorial changes based on comments on the list. o Other editorial changes based on comments on the list.
Authors' Addresses Authors' Addresses
Glen Zorn Glen Zorn (editor)
Network Zen Network Zen
77/440 Soi Phoomjit, Rama IV Road 227/358 Thanon Sanphawut
Phra Khanong, Khlong Toie Bang Na, Bangkok 10260
Bangkok 10110
Thailand Thailand
Phone: +66 (0) 87 502 4274 Phone: +66 (0) 909-201060
Email: gwz@net-zen.net 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 Qin Wu
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. 58 change blocks. 
150 lines changed or deleted 153 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/