draft-ietf-xrblock-rtcp-xr-burst-gap-loss-00.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: April 19, 2012 Telchemy Expires: July 22, 2012 Telchemy
S. Zhang, Ed. S. Zhang, Ed.
J. Zhao
STTRI STTRI
Q. Wu Q. Wu
Huawei Huawei
October 17, 2011 January 19, 2012
RTCP XR Report Block for Burst/Gap Loss metric Reporting RTCP XR Report Block for Burst/Gap Loss metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-loss-00.txt draft-ietf-xrblock-rtcp-xr-burst-gap-loss-01.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of Burst and Gap Loss metrics for use in a range of RTP reporting of Burst and Gap Loss metrics for use in a range of RTP
applications. 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 38
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 19, 2012. This Internet-Draft will expire on July 22, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 46 skipping to change at page 3, line 46
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [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 draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block that
MUST be used as defined in [RFC3550] and [RFC3611]. MUST be used as defined in [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [PMOLFRAME] provides guidance on The Performance Metrics Framework [RFC6390] provides guidance on the
the definition and specification of performance metrics. Metrics definition and specification of performance metrics. Metrics
described in this draft either reference external definitions or described in this draft either reference external definitions or
define metrics generally in accordance with the guidelines in define metrics generally in accordance with the guidelines in
[PMOLFRAME]. [RFC6390].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a range of RTP applications. These metrics are applicable to a range of RTP applications.
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",
skipping to change at page 6, line 12 skipping to change at page 6, line 12
percent loss rate), and gaps, which are periods during which lost percent loss rate), and gaps, which are periods during which lost
packets are infrequent and hence quality is generally acceptable. packets are infrequent and hence quality is generally acceptable.
3. Burst/Gap Loss Block 3. Burst/Gap Loss Block
Metrics in this block report on Burst/Gap Loss in the stream arriving Metrics in this block report on Burst/Gap Loss in the stream arriving
at the RTP system. at the RTP system.
3.1. Report Block Structure 3.1. Report Block Structure
Delay metrics block Burst/Gap Loss metrics block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NDEL |I| resv. | block length = 5 | | BT=NBGL |I|C| resv. | block length = 5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold | Sum of Burst Durations (ms) | | Threshold | Sum of Burst Durations (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Lost in Bursts | Total... | | Packets Lost in Bursts | Total... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Packets expected in bursts | Number of bursts | Sum of| | ...Packets expected in bursts | Number of bursts | Sum of|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Squares of Burst Durations (ms-squared) | | ...Squares of Burst Durations (ms-squared) |
skipping to change at page 7, line 5 skipping to change at page 7, line 5
Interval Metric flag (I): 1 bit Interval Metric flag (I): 1 bit
This field is used to indicate whether the Packet Delay Variation This field is used to indicate whether the Packet Delay Variation
metrics block is an Interval or a Cumulative report, that is, metrics block is an Interval or a Cumulative report, that is,
whether the reported values apply to the most recent measurement whether the reported values apply to the most recent measurement
interval duration between successive metrics reports (I=1) (the interval duration between successive metrics reports (I=1) (the
Interval Duration) or to the accumulation period characteristic of Interval Duration) or to the accumulation period characteristic of
cumulative measurements (I=0) (the Cumulative Duration). cumulative measurements (I=0) (the Cumulative Duration).
Loss and Discard Combination flag (C): 1 bit
The 'C' flag is used to indicate whether combining loss/discard
report is needed. This field MUST be set to '1' if the burst gap
loss report is present in conjunction with the burst gap discard
report in the same compound RTCP packet and MUST be set to '0'
otherwise. If the burst gap discard is not sent with burst gap
loss, then the receiver should discard burst gap loss with 'C'
flag set to 1. If the 'C' flag is set to 0, then receiver should
not discard burst gap loss metric block when burst gap discard is
not received.
Reserved (resv): 7 bits Reserved (resv): 7 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
block length: 16 bits block length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the Delay block, the block length is equal to 5. the Delay block, the block length is equal to 5.
skipping to change at page 8, line 34 skipping to change at page 8, line 47
If the measured value exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE If the measured value exceeds 0xFFFFFFFFD, the value 0xFFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the SHOULD be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFFFFF SHOULD be measurement is unavailable, the value 0xFFFFFFFFF SHOULD be
reported. reported.
3.3. Derived metrics based on reported metrics 3.3. Derived metrics based on reported metrics
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 (which MUST be present in the same RTCP packet as Information block [MEASID] (which MUST be present in the same RTCP
the Burst/Gap Loss block) and also with the metric "cumulative number packet as the Burst/Gap Loss block) and also with the metric
of packets lost" provided in standard RTCP [RFC3550]. "cumulative number of packets lost" provided in standard RTCP
[RFC3550].
These metrics provides information relevant to statistical These metrics provides information relevant to statistical
parameters, including: parameters, including:
o The fraction of packets lost during bursts o The fraction of packets lost during bursts (i.e., Burst Loss Rate
in [SUMSTAT])
o The fraction of packets lost during gaps o The fraction of packets lost during gaps (i.e., Gap Loss Rate in
[SUMSTAT])
o burst duration mean o burst duration mean [SUMSTAT]
o burst duration variance o burst duration variance [SUMSTAT]
The details on calculation these parameters in the metrics are The details on calculation these parameters in the metrics are
described in [SUMSTAT]. described in [SUMSTAT].
4. Considerations for Voice-over-IP applications 4. Considerations for Voice-over-IP applications
This metric block is applicable to a broad range of RTP applications. This metric block is applicable to a broad range of RTP applications.
Where the metric is used with a Voice-overIP (VoIP) application, the Where the metric is used with a Voice-overIP (VoIP) application, the
following considerations apply. following considerations apply.
skipping to change at page 10, line 24 skipping to change at page 10, line 24
which are periods during which lost packets are infrequent and hence which are periods during which lost packets are infrequent and hence
call quality is generally acceptable. call quality is generally acceptable.
If Voice Activity Detection is used the Burst and Gap Duration shall If Voice Activity Detection is used the Burst and Gap Duration shall
be determined as if silence frames had been sent, i.e. a period of be determined as if silence frames had been sent, i.e. a period of
silence in excess of Gmin frames MUST terminate a burst condition. silence in excess of Gmin frames MUST terminate a burst condition.
The recommended value for the threshold Gmin in [RFC3611] results in The recommended value for the threshold Gmin in [RFC3611] results in
a Burst being a period of time during which the call quality is a Burst being a period of time during which the call quality is
degraded to a similar extent to a typical PCM Severely Errored Second degraded to a similar extent to a typical PCM Severely Errored Second
[SDES]. [PSES].
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] 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.
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
skipping to change at page 16, line 26 skipping to change at page 16, line 26
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
10.2. Informative References 10.2. Informative References
[DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric [DISCARD] Hunt, G., "RTCP XR Report Block for Discard metric
Reporting", ID draft-ietf-rtcp-xr-discard-02, May 2009. Reporting", ID draft-ietf-rtcp-xr-discard-02, May 2009.
[MEASID] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-01,
October 2011.
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-04, August 2011. ID draft-ietf-avtcore-monarch-04, August 2011.
[PMOLFRAME] [PSES] "URL", http://www.its.bldrdoc.gov/projects/devglossary/
Clark, A. and B. Claise, "Framework for Performance Metric
Development", ID draft-ietf-pmol-metrics-framework-12,
July 2011.
[SDES] "", URL http://www.its.bldrdoc.gov/projects/devglossary/
_severely_errored_second.html, October 2011. _severely_errored_second.html, October 2011.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, July 2011.
[SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics [SUMSTAT] Zorn, G., "RTCP XR for Summary Statistics Metrics
Reporting", ID draft-zorn-xrblock-rtcp-xr-al-stat-03, Reporting", ID draft-zorn-xrblock-rtcp-xr-al-stat-03,
October 2011. October 2011.
Authors' Addresses Authors' Addresses
Geoff Hunt Geoff Hunt
Unaffiliated Unaffiliated
Email: r.geoff.hunt@gmail.com Email: r.geoff.hunt@gmail.com
skipping to change at page 17, line 28 skipping to change at page 17, line 28
Email: alan.d.clark@telchemy.com Email: alan.d.clark@telchemy.com
Sunshine Zhang (editor) Sunshine Zhang (editor)
Shanghai Research Institure of China Telecom Corporation Limited Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road No.1835,South Pudong Road
Shanghai 200122 Shanghai 200122
China China
Email: zhangyx@sttri.com.cn Email: zhangyx@sttri.com.cn
Jing Zhao
Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road
Shanghai 200122
China
Email: zhaojing@sttri.com.cn
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
 End of changes. 21 change blocks. 
24 lines changed or deleted 51 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/