IETF Logo Mail Archive

Re: [P2PSIP] AD evaluation: draft-ietf-p2psip-diagnostics-17

Alissa Cooper <alissa@cooperw.in> Mon, 30 November 2015 20:06 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 1FF391B3050 for <p2psip@ietfa.amsl.com>; Mon, 30 Nov 2015 12:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 5vJXF3wLs857 for <p2psip@ietfa.amsl.com>; Mon, 30 Nov 2015 12:06:27 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02681B304A for <p2psip@ietf.org>; Mon, 30 Nov 2015 12:06:26 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2D5B020BBD for <p2psip@ietf.org>; Mon, 30 Nov 2015 15:06:25 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 30 Nov 2015 15:06:25 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=AciAu NZuWv6JS1RYSOK+XlRhjc8=; b=qKbYWFvAi16vIWNsBXQUN2FcEP5pLwVzlPV0C tSPA49TC3t1fZBaOQeQkCLiLsvmWlmZfBJ8xJV2T48qphlrvIrhjaIHatPe+gMGM V3WtM1MBmiaC51wBsuU7qaLaZF0KCiqTGU8Esps/AjEZGlrIQlvJyjRQEZgqLmo3 y7bw0s=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=AciAuNZuWv6JS1RYSOK+XlRhjc8=; b=QCNr2 YjADvymZTaVpXhPt+3W+ehv+2OLn+vkiyxpemQr26M6IPMQsp52tGPePuOV1lXd3 litriuDEo//crMpHwY5prYgV4k/nhhGbtNBgdL3eOoZdC20bj+2a+vwL3Na+TImv ZzuyxzJQjliaF5ZvjEa34H+nhxwhOb9fLStwWM=
X-Sasl-enc: Sep/XPtH116q4EM0y6T0It3ulDIAQi9eqZQccORlnKHz 1448913984
Received: from dhcp-171-68-20-106.cisco.com (dhcp-171-68-20-106.cisco.com [171.68.20.106]) by mail.messagingengine.com (Postfix) with ESMTPA id D4AEA680087; Mon, 30 Nov 2015 15:06:23 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E8C082E-BA70-419A-A655-5B07A1F94068"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F653D773B@nkgeml501-mbs.china.huawei.com>
Date: Mon, 30 Nov 2015 12:06:22 -0800
Message-Id: <0F1001E5-3C1F-4275-A748-06332B5B5FAF@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> <E33E01DFD5BEA24B9F3F18671078951F653C3123@nkgeml501-mbs.china.huawei.com> <B5CD85FC-275F-421D-85C6-04E6EC67D7B7@cooperw.in> <AD6208DA-94C8-4390-B6C7-FA922D4CC451@cooperw.in> <E33E01DFD5BEA24B9F3F18671078951F653CD77A@nkgeml501-mbs.china.huawei.com> <E33E01DFD5BEA24B9F3F18671078951F653D773B@nkgeml501-mbs.china.huawei.com>
To: "Songhaibin (A)" <haibin.song@huawei.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/Cutm9Nb_52IrY2NOKeh5LSLacas>
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
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: Mon, 30 Nov 2015 20:06:33 -0000

Thanks. Last call has been initiated. Still looking for answers below.

>> 
>> 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?

Alissa


> On Nov 26, 2015, at 6:25 PM, Songhaibin (A) <haibin.song@huawei.com> wrote:
> 
> Dear Alissa,
>  
> I have submitted a new version with changes to the diagnostic information authorization part, and leave the  EWMA_BYTES_SENT and EWMA_BYTES_RCVD for discussion during IETF last call. 
>  
> Best Regards!
> -Haibin

v2.23.0 | Report a Bug | By Email