Re: [P2PSIP] AD evaluation: draft-ietf-p2psip-diagnostics-17 - crazy send math ....

Alissa Cooper <alissa@cooperw.in> Sun, 13 December 2015 17:49 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5E621B2AB6 for <p2psip@ietfa.amsl.com>; Sun, 13 Dec 2015 09:49:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 XrXMKH9sUrkC for <p2psip@ietfa.amsl.com>; Sun, 13 Dec 2015 09:49:02 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03D851B2AB5 for <p2psip@ietf.org>; Sun, 13 Dec 2015 09:49:01 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3315A2045D for <p2psip@ietf.org>; Sun, 13 Dec 2015 12:49:01 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 13 Dec 2015 12:49:01 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=YtDgQcxCCnpxSk+GvZiUgqYeJrQ=; b=yMbzMb gsKWV513P/7CGNgn/sHVDrGEeSwTDIhj+Z/LzqrW59BkT6sJuEOSCNy6mFegpzkr pgeibbVQjdbBeSIvnDX5WiIYUmYxGHCh2TJe54wJXke1kt/NdI6csrvEyoYMwEHG 4OsxrsLwvdtizgWWVsw7yhrv8YynIiW7aQWFM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=YtDgQcxCCnpxSk+ GvZiUgqYeJrQ=; b=T8pAKRsANWHIhb8zbnNt/DNCvLyxR5TodDR+oSrgIqnirzs VFhCvmi8mit3hbqOzU78pgMGmTcniqcDFvxb8/REOZIM9l3lT+ldZfVC6h332hWh SuMNRy28k+jPJlGw171kHQ11lmY+gDcpkeiEuj08+MPHSVyNeGye/MR1et8Q=
X-Sasl-enc: 7+XTHeHch6JU4NfzQAcanwg7WWQrNkbAFmFXFf5yOW8Q 1450028940
Received: from sjc-alcoop-8815.cisco.com (unknown [128.107.241.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 5C956C016C4; Sun, 13 Dec 2015 12:49:00 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4541D978-85FB-483A-A66C-F8D22D8619F7@cisco.com>
Date: Sun, 13 Dec 2015 09:48:58 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AAB9C16-3E6E-42E7-849B-195F1BAD6737@cooperw.in>
References: <37059182-6C51-49E3-83A0-D27F2C15A366@cooperw.in> <CADqQgCQ_hEacxApiauKLYD0Y+ahkXGDi9uXFvLN1XjqLpzjh0Q@mail.gmail.com> <5C131A2D-2519-4CD5-AAB0-1E01563C9665@cooperw.in> <E33E01DFD5BEA24B9F3F18671078951F65345644@nkgeml501-mbs.china.huawei.com> <B30B3C53-F230-4607-878F-12BFBBE2D277@cooperw.in> <EE06F5C7-0499-49A1-86A7-2234C54D3EB1@cooperw.in> <E33E01DFD5BEA24B9F3F18671078951F653A9E39@nkgeml501-mbs.china.huawei.com> <52C1D77C-4E21-4C1B-A16E-D20B638B38FF@cooperw.in> <4541D978-85FB-483A-A66C-F8D22D8619F7@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/AjZJJMr8JpCIC21fn6Qf-XekRFk>
Cc: p2psip <p2psip@ietf.org>, "draft-ietf-p2psip-diagnostics@tools.ietf.org" <draft-ietf-p2psip-diagnostics@tools.ietf.org>
Subject: Re: [P2PSIP] AD evaluation: draft-ietf-p2psip-diagnostics-17 - crazy send math ....
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Dec 2015 17:49:03 -0000

> On Dec 8, 2015, at 8:10 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> 
> 
>> On Nov 11, 2015, at 4:09 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>> 
>>> 
>>> The definitions of EWMA_BYTES_SENT and EWMA_BYTES_RCVD seem problematic.
>>> 
>>> sent = alpha x sent_present + (1 - alpha) x sent
>>> rcvd = alpha x rcvd_present + (1 - alpha) x rcvd
>>> 
>>> As written these equations are not right because sent/rcvd appear on both sides. It would be clearer to use last_sent and last_rcvd or some such on the right-hand side of these equations. But this begs some bigger questions:
>>> 
>>> - Does this place a requirement on all nodes implementing this specification to have to calculate these values every 5 seconds?
>>> - How are the values calculated the first time?
>>> - How was the value of 5 seconds chosen?
>>> 
>>> [Haibin] This is incorporated from the early RELOAD document. Maybe some author of the RELOAD protocol can give a better explanation.
>> 
>> This still has not been explained.
>> 
> 
> I'm sure I know what this was meant to represent when it was written .... 
> 
> sent for time period t should be set to the value of alpha times the amount sent in this time period plus (1-alpha) times the value of send for the previous time period.
> 
> The value sent for the very first time period should simply be the amount that was sent in that time period. That is not computable before the end of the time period. I doubt anyone cares what the values before the end of the first time period. Note that alpha is a constant that is probably compiled into the application and not something we expect end users to set. 

Thanks Cullen.

I think the draft needs some text to explain the above. Haibin, do you think you could draft something up?

Alissa

> 
> Basically this is a somewhat crappy infinite impulse response (IIR) filter approximation of finite impulse response (FIR) filter for computing the weighted moving average of the data transmission rate. 
> 
> Dito for rcvd.
> 
> Hope that helps, 
> 
> Cullen
> 
> 
> As an irrelevant side note  .. In practice, I have found that just reporting the raw totals number of bytes sent since the box booted then letting the management system filter and smooth that values works out better than using this
> 
> 
> 
> 
>