Re: [xrblock] Burst Discard Count

Qin Wu <bill.wu@huawei.com> Sat, 28 February 2015 02:41 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB6D1A1B64 for <xrblock@ietfa.amsl.com>; Fri, 27 Feb 2015 18:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1xrtn7YfZr4c for <xrblock@ietfa.amsl.com>; Fri, 27 Feb 2015 18:41:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BCEF1A1B60 for <xrblock@ietf.org>; Fri, 27 Feb 2015 18:41:06 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPS20439; Sat, 28 Feb 2015 02:41:04 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 28 Feb 2015 02:41:03 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Sat, 28 Feb 2015 10:40:59 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Varun Singh <vsingh.ietf@gmail.com>
Thread-Topic: [xrblock] Burst Discard Count
Thread-Index: AQHQUbgzAJwfIPLdAU2oBVuWXlbyz50Dv1WwgAAaNwCAAX/+cA==
Date: Sat, 28 Feb 2015 02:40:59 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846DAAFD@nkgeml501-mbs.china.huawei.com>
References: <CAEbPqrxHJSNMins8ROMALvAPii7aKphYbWgSOKh61L8Mx_uGOw@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA846DA5C2@nkgeml501-mbs.china.huawei.com> <CAEbPqrzi+LPg3La-pBGpjo4rpwKXyj8JZuY+-1yfnHieDy8yfQ@mail.gmail.com>
In-Reply-To: <CAEbPqrzi+LPg3La-pBGpjo4rpwKXyj8JZuY+-1yfnHieDy8yfQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/UrhfgkyJYb12mbIlnFlJ2lGZxAc>
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] Burst Discard Count
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2015 02:41:08 -0000

-----邮件原件-----
发件人: Varun Singh [mailto:vsingh.ietf@gmail.com] 
发送时间: 2015年2月27日 19:36
收件人: Qin Wu
抄送: xrblock@ietf.org
主题: Re: [xrblock] Burst Discard Count

Hi Qin,

On Fri, Feb 27, 2015 at 4:05 AM, Qin Wu <bill.wu@huawei.com> wrote:
> 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.

To confirm, the burstCount indicates the number of intervals where bursts occur, and not the packets in an individual bursts.

I think the implicit assumption is that losses and discards are correlated, and that discards may occur before losses. However, consider a congestion control algorithm that is sensitive to discards may correct before any losses occur. Then the burstCount measuring only losses would not increase  and hence burst discards count will not correspond to burst loss count.

[Qin]: Somebody questioned the usefulness of burst gap discard report. Therefore Combined loss/discard report was proposed to address this issue.
http://www.ietf.org/mail-archive/web/xrblock/current/msg00172.html
http://www.ietf.org/mail-archive/web/xrblock/current/msg00264.html

> 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.
> "
>
> -Qin
> -----邮件原件-----
> 发件人: xrblock [mailto:xrblock-bounces@ietf.org] 代表 Varun Singh
> 发送时间: 2015年2月26日 19:34
> 收件人: xrblock@ietf.org
> 主题: [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,
> Varun
>
>
> --
> http://www.callstats.io
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock



--
http://www.callstats.io