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

Mark Allman <mallman@icir.org> Wed, 27 May 2009 03:21 UTC

Return-Path: <mallman@icir.org>
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 2FF743A6D68 for <tsvwg@core3.amsl.com>; Tue, 26 May 2009 20:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level:
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160, 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 HkNKGE1y0vyV for <tsvwg@core3.amsl.com>; Tue, 26 May 2009 20:21:38 -0700 (PDT)
Received: from pork.ICSI.Berkeley.EDU (pork.ICSI.Berkeley.EDU [192.150.186.19]) by core3.amsl.com (Postfix) with ESMTP id 2C4403A6D5C for <tsvwg@ietf.org>; Tue, 26 May 2009 20:21:38 -0700 (PDT)
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id n4R3NHDj017108; Tue, 26 May 2009 20:23:18 -0700
Received: from lawyers.icir.org (unknown [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id A3A4E3A59F6A; Tue, 26 May 2009 23:23:11 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 6791A293735; Tue, 26 May 2009 23:23:12 -0400 (EDT)
To: Fernando Gont <fernando@gont.com.ar>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <4A1C6D04.2090709@gont.com.ar>
Organization: International Computer Science Institute (ICSI)
Song-of-the-Day: Lawyers, Guns and Money
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="--------ma45600-1"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 26 May 2009 23:23:12 -0400
Sender: mallman@icir.org
Message-Id: <20090527032312.6791A293735@lawyers.icir.org>
Cc: Alfred Hönes <ah@tr-sys.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: [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
Reply-To: mallman@icir.org
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 03:21:39 -0000

> >   - Section 3.3.4: It'd be nice to see some reasoning about why a table
> >     size of 1024 is being recommended.  It seems like this is
> >     arbitrarily pulled out of the air.  I think it'd be fine to leave
> >     this to the implementer.  I.e., note that [Allman] shows 10 entries
> >     will work fine for collision avoidance and increasing the table size
> >     increases the obfuscation and leave it at that.  If you pick a
> >     number then at least motivate it somehow.
> 
> I agree with you. The 1024 value is pulled out of the air. The point
> is that for a general purpose system, because of memory availability
> and cost, you probably won't choose a table size in such a
> fine-grained way.  But... this is me being pragmatic and
> non-academic. Also, a value of 10 was enough for that *specific*
> network scenario/traffic (this is something that should be clarified,
> btw)... that's why I'd personally pick a larger number.

I think my formulation is better:

   I.e., note that [Allman] shows 10 entries will work fine for
   collision avoidance [to the extent that the data in [Allman] has legs
   outside those environments, of course] and increasing the table size
   increases the obfuscation and leave it at that.

That doesn't say "don't increase the number".  That just says what we
know.  You, Fernando, then choosing 1024 is perfectly fine if that is
where your comfort level is.  I am not quibbling with your particular
gut feeling here.  I just don't see why we should encode that in the
document. 

allman