Re: [Tsvwg] table size (was Re: WGLC for Port Randomization starts now (April 1st))

Fernando Gont <fernando@gont.com.ar> Wed, 27 May 2009 19:48 UTC

Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37D2F3A694A for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 12:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cDej966oavY for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 12:48:12 -0700 (PDT)
Received: from mail-gx0-f164.google.com (mail-gx0-f164.google.com [209.85.217.164]) by core3.amsl.com (Postfix) with ESMTP id 4DE363A677D for <tsvwg@ietf.org>; Wed, 27 May 2009 12:48:11 -0700 (PDT)
Received: by gxk8 with SMTP id 8so668228gxk.13 for <tsvwg@ietf.org>; Wed, 27 May 2009 12:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=KLubeteWUPuabg9o5ax+TX5Wonp6du6R/VbE3fk0XVQ=; b=w7HBXrjBTGkpjWYrAGTFG7FiRfoQGx2tvYoESudIGnxaGPg/i/D4V0CfILVObfwvOX bybiHFsIpRYUzkhR1Io+IAonCvtPJutLVTGnloKO1Qb031cuYjcVI7en+l3kIYCw153h in9b4vgc4YNl2CvfYx6KW32/93mdu2LZxR2Qk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hCNwpCzB5hA9bdhY65ppWPouXF/5C6mKwucaiQ+LPv2c6g82GrlBRsITZ20wS7AJn0 pTYWst9eV3562l4EduUf3Y28hZa3gC3Yb2Df1HhSFB6FFZ2CQ9UZdvk5pEIikUa7B9VA m6bXrRADpIOtfnTD757m3EK23gIIHyhmvrPKk=
Received: by 10.90.81.11 with SMTP id e11mr246841agb.119.1243453761652; Wed, 27 May 2009 12:49:21 -0700 (PDT)
Received: from ?168.77.196.154? (154.196.lacnicxii.lacnic.net [168.77.196.154]) by mx.google.com with ESMTPS id 17sm12337381agd.26.2009.05.27.12.49.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 27 May 2009 12:49:20 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4A1D9937.6030703@gont.com.ar>
Date: Wed, 27 May 2009 16:49:11 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mallman@icir.org
References: <20090527175131.5A6522979F0@lawyers.icir.org>
In-Reply-To: <20090527175131.5A6522979F0@lawyers.icir.org>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Alfred Hönes <ah@tr-sys.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [Tsvwg] table size (was Re: WGLC for Port Randomization starts now (April 1st))
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2009 19:48:13 -0000

Mark Allman wrote:

> As I **said above**, I found that a table of 10 entries works fine for
> collision **avoidance**.
> 
> You can likely dream up some scenario whereby a bigger table size does
> in fact reduce the collision rate.  Or, perhaps whereby you can reduce
> the collision rate to less than zero.  I prefer just looking at the
> data, but realize YMMV.
> 
> Again, I am not asking you to say a table size of 10 is somehow ideal.
> I am just saying that we have some data that suggests it is OK in some
> environments and that plus a note that increasing the size increases the
> obfuscation seems perfectly reasonable to me.  

I agree with this. In particular, when the sentence includes the phrase
"in some environments". That's the only thing I was arguing.


> I don't see how pulling
> some number out thin air is better.  I don't see how your number is
> justified.  If you want to use it, great, I don't care.  But, I don't
> see why we need to be recommending or suggesting this completely made up
> value.

I had already agreed that I would be removing the value 1024. I was only
arguing that "a table of 10 is enough" is misleading. Something along
the lines of "[Allman] has found that in some environments a table size
of 10....". That's all.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1