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

Mark Allman <mallman@icir.org> Wed, 27 May 2009 18:47 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 D11BB3A6998 for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 11:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, 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 bUBpy17PIIFS for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 11:47:08 -0700 (PDT)
Received: from pork.ICSI.Berkeley.EDU (pork.ICSI.Berkeley.EDU [192.150.186.19]) by core3.amsl.com (Postfix) with ESMTP id 941623A6D64 for <tsvwg@ietf.org>; Wed, 27 May 2009 11:47:07 -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 n4RHpaFP014298; Wed, 27 May 2009 10:51:37 -0700
Received: from lawyers.icir.org (unknown [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 798763A5F1F0; Wed, 27 May 2009 13:51:30 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 5A6522979F0; Wed, 27 May 2009 13:51:31 -0400 (EDT)
To: Fernando Gont <fernando@gont.com.ar>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <4A1D7125.20307@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="--------ma32163-1"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 27 May 2009 13:51:31 -0400
Sender: mallman@icir.org
Message-Id: <20090527175131.5A6522979F0@lawyers.icir.org>
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
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 18:47:08 -0000

> > 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.
> 
> Increasing the table might possibly decrease the collision rate, too.
> (i.e., it prevents the system from skipping port numbers
> unnecessarily).  I do not recall what were results of your research in
> this area, though... but will look at your paper again.

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

allman