draft-ietf-xrblock-rtcp-xr-summary-stat-08.txt   draft-ietf-xrblock-rtcp-xr-summary-stat-09.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track R. Schott Intended status: Standards Track R. Schott
Expires: August 10, 2013 Deutsche Telekom Expires: August 26, 2013 Deutsche Telekom
Q. Wu Q. Wu
R. Huang R. Huang
Huawei Huawei
February 6, 2013 February 22, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Summary
Statistics Metrics Reporting Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-summary-stat-08 draft-ietf-xrblock-rtcp-xr-summary-stat-09
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 This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 August 10, 2013. This Internet-Draft will expire on August 26, 2013.
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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
3.1.2. Definition of Fields in Loss Summary Statistics 3.1.2. Definition of Fields in Loss Summary Statistics
Block . . . . . . . . . . . . . . . . . . . . . . . . 5 Block . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7 3.2. Burst/Gap Discard Summary Statistics Metrics Block . . . . 7
3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 8 3.2.1. Report Block Structure . . . . . . . . . . . . . . . . 8
3.2.2. Definition of Fields in Burst/Gap Discard Summary 3.2.2. Definition of Fields in Burst/Gap Discard Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 8 Statistics Block . . . . . . . . . . . . . . . . . . . 8
4. Application Level Metrics . . . . . . . . . . . . . . . . . . 10 4. Application Level Metrics . . . . . . . . . . . . . . . . . . 10
4.1. Frame Impairment Statistics Summary Metrics Block . . . . 10 4.1. Frame Impairment Statistics Summary Metrics Block . . . . 10
4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10 4.1.1. Report Block Structure . . . . . . . . . . . . . . . . 10
4.1.2. Definition of Fields in Frame Impairment Summary 4.1.2. Definition of Fields in Frame Impairment Summary
Statistics Block . . . . . . . . . . . . . . . . . . . 10 Statistics Block . . . . . . . . . . . . . . . . . . . 11
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 12
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 13 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 13 6.1. New RTCP XR Block Type values . . . . . . . . . . . . . . 13
6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13 6.2. New RTCP XR SDP Parameters . . . . . . . . . . . . . . . . 13
6.3. Contact information for registrations . . . . . . . . . . 14 6.3. Contact information for registrations . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 15 9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 15 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-09 . . . . . . . . 15
A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 15 A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-08 . . . . . . . . 15
A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 15 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-07 . . . . . . . . 15
A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 16 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-06 . . . . . . . . 16
A.5. draft-ietf-xrblock-rtcp-xr-summary-stat-05 . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
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 draft defines three new block types to augment those defined in
[RFC3611] for use in a range of RTP applications. [RFC3611] for use in a range of RTP applications.
o Burst/Gap Loss Summary Statistics Metrics Block o Burst/Gap Loss Summary Statistics Metrics Block
skipping to change at page 4, line 19 skipping to change at page 4, line 18
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:
Frame Type Frame Type
A video frame is compressed using different algorithms. Frame In many cases, a video frame is compressed using different
type is used to identify different algorithms for video frames. algorithms. Frame type is used to identify different algorithms
Two frame Types used in the different video algorithms are the Key for video frames. Two frame Types used in the different video
frame and Derived frames. The Key frame is independently coded algorithms are the Key frame and Derived frames. The Key frame is
without prediction from other pictures and used as a reference independently coded without prediction from other pictures and
frame for predicting other pictures. Derived frames are used as a reference frame for predicting other pictures. Derived
predicatively coded and derived from a Key frame using a frames are predicatively coded and derived from a Key frame using
prediction algorithm. a prediction algorithm If there is no video image compression, 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 Metrics Block
The metrics described here are intended to be used as described in This Block extends packet loss and discard metrics defined in section
this section, in conjunction with information from the Measurement 4.7.1 of RFC3611. The metrics described here are intended to be used
Information block [RFC6776] (which MUST be present in the same RTCP as described in this section, in conjunction with information from
packet as the Burst/Gap Loss block) and also with the metric the Measurement Information block [RFC6776] (which MUST be present in
"cumulative number of packets lost" provided in standard RTCP the same RTCP packet as the Burst/Gap Loss block) and also with the
metric "cumulative number of packets lost" provided in standard RTCP
[RFC3550]. Instances of this Metrics Block refer by Synchronization [RFC3550]. Instances of this Metrics Block refer by Synchronization
source (SSRC) to the separate auxiliary Measurement Information block source (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which describes measurement periods in use (see [RFC6776] [RFC6776] which 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.
skipping to change at page 5, line 50 skipping to change at page 5, line 51
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
SHOULD be 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 RFC3611 [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
at the left edge of the field. This value is calculated by immediately after the left-most bit. This value is calculated by
dividing Packets Loss 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 7FFF, with the Bursts, multiplying the result of the division by 32768
maximum value 7FFF, and taking the integer part as follows: (0x8000),and keeping only the integer part. The maximum value is
thus 0x8000. Representing this as a formula:
Packets Loss in Bursts / Total Packets expected in Bursts integer-part( (Packets Lost in Bursts / Total Packets Expected in
Bursts) * 0x8000 )
If the measurement is unavailable, the value 0x8000 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
at the left edge of the field. 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 7FFF, with the maximum value 7FFF, and taking the division by 32768 (0x8000),and keeping only the integer part. The
integer part as follows: maximum value is thus 0x8000. Representing this as a formula:
(number of packets lost - Packets Lost in Bursts) / (Packets integer-part ( (number of packets lost - Packets Lost in Bursts)/
Expected - Total Packets expected in Bursts) (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 0x8000 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:16bits
The mean burst duration is obtained as the quotient: The mean burst duration is obtained as the quotient:
skipping to change at page 7, line 35 skipping to change at page 7, line 38
mean^2 ) / (Number of Bursts - 1) mean^2 ) / (Number of Bursts - 1)
where "Sum of Squares of Burst Durations" and "Number of Bursts"is where "Sum of Squares of Burst Durations" and "Number of Bursts"is
obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS]. obtained from the RTCP XR Burst/Gap Loss Block [BGLOSS].
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 Metrics Block
The metrics described here are intended to be used as described in This Block extends packet loss and discard metrics defined in section
this section, in conjunction with information from the Measurement 4.7.1 of RFC3611. The metrics described here are intended to be used
Identity block [RFC6776] (which MUST be present in the same RTCP as described in this section, in conjunction with information from
packet as the Burst/Gap Discard Summary Statistics block) . the Measurement Identity block [RFC6776] (which MUST be present in
the same RTCP packet as the Burst/Gap Discard Summary 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 calculated at including burst discard rate, gap discard rate and are calculated at
the receiving end of the RTP stream using burst gap discard metrics the receiving end of the RTP stream using burst gap discard metrics
defined in [BGDISCARD] and other information which is sent together defined in [BGDISCARD] and other information which is sent together
with this report block. with this report block.
Instances of this Metrics Block refer by Synchronization source Instances of this Metrics Block refer by Synchronization source
(SSRC) to the separate auxiliary Measurement Information block (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which describes measurement periods in use (see [RFC6776] [RFC6776] which describes measurement periods in use (see [RFC6776]
skipping to change at page 8, line 50 skipping to change at page 9, 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
SHOULD be 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 at the left edge of the field. This value is binary point at the left edge of the field. 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 7FFF, with the maximum value 7FFF, and taking the integer part by 32768 (0x8000), and keeping only the integer part, according to
as follows: the formula:
Packets Discarded in Bursts / Total Packets expected in Bursts integer-part( (Packets Discarded in Bursts / Total Packets
expected in Bursts) * 0x8000 )
If the measurement is unavailable, the value 0x8000 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 at the left edge of the field. This value is calculated by point immediately after the left-most bit. This value is
dividing the difference between number of packets discarded and calculated by dividing the difference between number of packets
Packets Discarded in Bursts by the difference between Packets discarded and Packets Discarded in Bursts by the difference
Expected and Total Packets expected in Bursts, multiplying the between Packets Expected and Total Packets expected in Bursts,
result of the division by 7FFF, with the maximum value 7FFF, and multiplying the result of the division by 32768 (0x8000), and
taking the integer part as follows: keeping only the integer part. The maximum value is thus 0x8000.
Representing this as a formula:
(number of packets discarded - Packets Discarded in Bursts) / integer-part( (number of packets discarded - Packets Discarded in
(Packets Expected - Total Packets expected in Bursts) Bursts) /(Packets Expected - Total Packets expected in Bursts) *
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 [DISCARD] 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 0x8000 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 Metrics Block
This block reports statistics on which frame type were affected This block extends statistics summary report mechanism defined in
beyond the information carried in the Statistics Summary Report Block section 4.6 of RFC3611 and reports statistics on which frame type
RTCP packet specified in the section 4.6 of RFC 3611 [RFC3611]. were affected beyond the information carried in the Statistics
Information is measured at the receiving end of the RTP stream and Summary Report Block RTCP packet specified in the section 4.6 of RFC
recorded about the number of frames received, lost frames, duplicated 3611 [RFC3611]. Information is measured at the receiving end of the
frames and lost partial frames. Such information can be useful for RTP stream and recorded about the number of frames received, lost
network management and video quality monitoring. frames, duplicated frames and lost partial frames. Such information
can be useful for network management and video quality monitoring.
4.1.1. Report Block Structure 4.1.1. Report Block Structure
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=FISS |T| Reserved | block length | | BT=FISS |T| Reserved | block length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| begin_seq | end_seq | | begin_seq | end_seq |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of frames received |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discarded_frames | | Discarded_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dup_frames | | Dup_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Full_lost_frames | | Full_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partial_lost_frames | | Partial_lost_frames |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.1.2. Definition of Fields in Frame Impairment Summary Statistics 4.1.2. Definition of Fields in Frame Impairment Summary Statistics
skipping to change at page 11, line 25 skipping to change at page 11, line 28
contain Key frame (reference frame) counts or 1 if they contain contain Key frame (reference frame) counts or 1 if they contain
Derived frame counts. Note that if both the Key frame and Derived frame counts. Note that if both the Key frame and
Derivation frame report are sent, they should be sent in the same Derivation frame report are sent, they should be sent in the same
RTCP compound packet using two Frame Impairment Summary Statistics RTCP compound packet using two Frame Impairment Summary Statistics
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
SHOULD be ignored by the receiver. ignored by the receiver (See RFC6709 section 4.2).
Block Length: 16 bits Block Length: 16 bits
The constant 7, 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 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:32 bits
A count of the number of frames received in the above sequence
number interval, estimated if necessary. If no frames have been
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 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 is
lost, this frame is regarded as one full lost frame. The 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 partially lost the frame are lost, this frame is regarded as one
frame. The partial_lost-frames can be inferred from packets that partial_lost_frame. The partial_lost_frames can be inferred from
comprise the frame. The value of the partial_lost_frames field is packets that comprise the frame. The value of the
equivalent to the number of partial lost frames in the above partial_lost_frames field is equivalent to the number of partial
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-attrib 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 RFC 3611 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.
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
skipping to change at page 13, line 44 skipping to change at page 13, line 44
Long Name: Frame Impairment Statistics Summary Long Name: Frame Impairment Statistics Summary
Value <FISS> Value <FISS>
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 (RTCP) Extended
Report (XR) SDP Parameters Registry ": Report (XR) SDP Parameters Registry ":
* " burst-gap-loss-stat " * "burst-gap-loss-stat"
* " burst-gap-discard-stat " * "burst-gap-discard-stat"
* " frame-impairment-stat " * "frame-impairment-stat"
6.3. Contact information for registrations 6.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
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 report blocks proposed in this document introduces no
new security considerations beyond those described in RFC 3611. new security considerations beyond those described in RFC 3611.
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Bill Ver Steeg, David R Oran, Ali The authors would like to thank Bill Ver Steeg, David R Oran, Ali
Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang Begen, Colin Perkins, Roni Even, Youqing Yang, Wenxiao Yu, Yinliang
Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton Hu, Jing Zhao, Ray van Brandenburg, Claire Bi, Dan Romascanu , Morton
Jr., Alfred and Klaas Wierenga for their valuable comments and Jr., Alfred, Klaas Wierenga, Barry Leiba, Robert Sparks, Ralph Droms
suggestions on this document. and Benoit Claise for their valuable comments and suggestions on this
document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[BGDISCARD] [BGDISCARD]
Clark, A., Huang, R., and W. Wu, "RTP Control Clark, A., Huang, R., and W. Wu, "RTP Control
Protocol(RTCP) Extended Report (XR) Block for Burst/Gap Protocol(RTCP) Extended Report (XR) Block for Burst/Gap
Discard metric Reporting", Discard metric Reporting",
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in draft-ietf-xrblock-rtcp-xr-burst-gap-discard-08 (work in
skipping to change at page 15, line 34 skipping to change at page 15, line 36
September 2012. September 2012.
[RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures
for RTP", RFC 6792, November 2012. for RTP", RFC 6792, November 2012.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-08 A.1. draft-ietf-xrblock-rtcp-xr-summary-stat-09
The following are the major changes compared to 08:
o Address comments in the IESG Review.
A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-08
The following are the major changes compared to 07: The following are the major changes compared to 07:
o Add comments raised in Sec-DIR review. o Address comments raised in Sec-DIR review.
A.2. draft-ietf-xrblock-rtcp-xr-summary-stat-07 A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-07
The following are the major changes compared to 06: The following are the major changes compared to 06:
o Add comments raised in PM-DIR review by Al. o Add comments raised in PM-DIR review by Al.
A.3. draft-ietf-xrblock-rtcp-xr-summary-stat-06 A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-06
The following are the major changes compared to 05: The following are the major changes compared to 05:
o Move RFC6709 to informative reference. o Move RFC6709 to informative reference.
A.4. draft-ietf-xrblock-rtcp-xr-summary-stat-05 A.5. draft-ietf-xrblock-rtcp-xr-summary-stat-05
The following are the major changes compared to 04: The following are the major changes compared to 04:
o Editorial changes to get in line with Delay and Burst Gap related o Editorial changes to get in line with Delay and Burst Gap related
drafts. drafts.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) 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
 End of changes. 41 change blocks. 
93 lines changed or deleted 102 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/