Re: [xrblock] Burst Discard Count
Qin Wu <bill.wu@huawei.com> Fri, 27 February 2015 02:06 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 4C1E31A1BE4 for <xrblock@ietfa.amsl.com>; Thu, 26 Feb 2015 18:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fziSZcCUelcR for <xrblock@ietfa.amsl.com>; Thu, 26 Feb 2015 18:06:03 -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 3A3C01A1A4B for <xrblock@ietf.org>; Thu, 26 Feb 2015 18:06:02 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTA68237; Fri, 27 Feb 2015 02:06:00 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 27 Feb 2015 02:05:59 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Fri, 27 Feb 2015 10:05:52 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Varun Singh <vsingh.ietf@gmail.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] Burst Discard Count
Thread-Index: AQHQUbgzAJwfIPLdAU2oBVuWXlbyz50Dv1Ww
Date: Fri, 27 Feb 2015 02:05:51 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846DA5C2@nkgeml501-mbs.china.huawei.com>
References: <CAEbPqrxHJSNMins8ROMALvAPii7aKphYbWgSOKh61L8Mx_uGOw@mail.gmail.com>
In-Reply-To: <CAEbPqrxHJSNMins8ROMALvAPii7aKphYbWgSOKh61L8Mx_uGOw@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="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/fLpJwDN_64vDX4mlMTSjGl-b5B0>
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: 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. " -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
- [xrblock] Burst Discard Count Varun Singh
- Re: [xrblock] Burst Discard Count Qin Wu
- Re: [xrblock] Burst Discard Count Varun Singh
- Re: [xrblock] Burst Discard Count Qin Wu
- Re: [xrblock] Burst Discard Count Bernard Aboba