Re: [xrblock] Burst Discard Count

Qin Wu <> Fri, 27 February 2015 02:06 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4C1E31A1BE4 for <>; Thu, 26 Feb 2015 18:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fziSZcCUelcR for <>; Thu, 26 Feb 2015 18:06:03 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3A3C01A1A4B for <>; Thu, 26 Feb 2015 18:06:02 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BTA68237; Fri, 27 Feb 2015 02:06:00 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 27 Feb 2015 02:05:59 +0000
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Fri, 27 Feb 2015 10:05:52 +0800
From: Qin Wu <>
To: Varun Singh <>, "" <>
Thread-Topic: [xrblock] Burst Discard Count
Thread-Index: AQHQUbgzAJwfIPLdAU2oBVuWXlbyz50Dv1Ww
Date: Fri, 27 Feb 2015 02:05:51 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [xrblock] Burst Discard Count
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Feb 2015 02:06:04 -0000

The argument is correct, but when the burst count for loss and burst count for discard are corresponding to the same reported source, the value for them are probably same.
Also burst gap discard is intended to be sent together with burst gap loss.
See the section 1 of RFC7003:
This block is intended to be used in conjunction with [RFC7002], which provides the
total packets discarded and on which this block therefore depends.
However, the metric in [RFC7002] may be used independently of the
metrics in this block.

发件人: xrblock [] 代表 Varun Singh
发送时间: 2015年2月26日 19:34
主题: [xrblock] Burst Discard Count

Hi all,

While preparing the -01 version of the
draft-ietf-xrblock-rtcweb-rtcp-xr-metrics, I noticed that the
RFC6958 - Burst/Gap Loss reports a "burst count" metric, which indicates the number of bursts  in an reporting interval (cumulative or arbitrary time interval). However, RFC7003 does not report a corresponding burst count metric for discarded packets.

I forget if this was discussed before, but it appears to be an oversight, as arguments for including burst count for loss also apply to burst discards -- unless I am missing something or it is defined elsewhere. How do we fix this?

This may be non-blocking for the rtcweb metrics as we could instead use the burstLossRate and burstDiscardRate which are defined in the summary statistics in RFC7004.

Thanks and Regards,


xrblock mailing list