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

Randy Stewart <randall@lakerest.net> Thu, 28 May 2009 15:14 UTC

Return-Path: <randall@lakerest.net>
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 57C5B3A69AE for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 08:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level:
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.450, 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 eCHyRwPfKFsM for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 08:14:07 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 335873A6C1B for <tsvwg@ietf.org>; Thu, 28 May 2009 08:14:06 -0700 (PDT)
Received: from [10.1.150.171] (rrcs-24-106-179-126.se.biz.rr.com [24.106.179.126]) (authenticated bits=0) by lakerest.net (8.14.3/8.14.3) with ESMTP id n4SFFWfn078087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 28 May 2009 11:15:34 -0400 (EDT) (envelope-from randall@lakerest.net)
DKIM-Signature: a=rsa-sha1; c=simple/simple; d=lakerest.net; s=mail; t=1243523734; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: X-Mailer; b=GCloM74HO9shl1RWvssTlmfoXrySool5xyu4R4iGh4lAJN2x4s5zNNL Hl9Hh0FJIgt2Fn+4AKa+XZbfW+F/RTQ==
Message-Id: <2CF8190F-ECCB-422A-BA5A-7ED17DFDF33D@lakerest.net>
From: Randy Stewart <randall@lakerest.net>
To: bidulock@openss7.org
In-Reply-To: <20090528145114.GB2677@openss7.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 28 May 2009 11:15:27 -0400
References: <20090415033307.F00C0CD585E@lawyers.icir.org> <4A037030.6040107@isi.edu> <0C53DCFB700D144284A584F54711EC58074EEED6@xmb-sjc-21c.amer.cisco.com> <4A1AB6EE.5080900@gont.com.ar> <0C53DCFB700D144284A584F54711EC58074EEF11@xmb-sjc-21c.amer.cisco.com> <4A1BF56D.3020709@isi.edu> <0C53DCFB700D144284A584F54711EC58074EF74C@xmb-sjc-21c.amer.cisco.com> <4A1D6F4E.2080005@isi.edu> <9F71CBFA-9E70-4CD4-B60D-D15F45842739@lakerest.net> <20090528145114.GB2677@openss7.org>
X-Mailer: Apple Mail (2.935.3)
Cc: tsvwg <tsvwg@ietf.org>, Joe Touch <touch@ISI.EDU>, "Anantha Ramaiah (ananth)" <ananth@cisco.com>, mallman@icir.org, Fernando Gont <fernando@gont.com.ar>, "James Polk (jmpolk)" <jmpolk@cisco.com>
Subject: Re: [Tsvwg] 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: Thu, 28 May 2009 15:14:15 -0000

For a particular port X you have a limit of 2^32
vtags.. yep..

But the BSD implementation would not support that many simultaneous
connections anyway.. I think we have a sysctl limit of about 40,000
associations... it can be raised... but the default is 40k..

So you might have a hard time rolling over that many associations
in the period of time your talking about.

If you don't keep a timed wait, then you could get old packets
injected on a new association.. for example an ABORT could
be tossed at you from an old association where you re-used
the vtag...


R
On May 28, 2009, at 10:51 AM, Brian F. G. Bidulock wrote:

> Randy,
>
> So, by forming and releasing 2^32 associations within 2MSL I can
> rum you out of vtags?  That might be a lot of memory depending on
> how much memory you use for each vtag in this wait state.  What
> do you do when all of the vtags are in wait state?  Can a new
> association form?
>
> --brian
>
> Randy Stewart wrote:                          (Thu, 28 May 2009  
> 10:39:37)
>>
>> Basically for BSD we take a v-tag used in a connection.. call it  
>> 'X',  and
>> we place just the tag 'X' into a "timed-wait" cache for 2MSL. There  
>> is  no
>> restriction on the socket here.. just the tag 'X' will not be used  
>> again
>> with this socket.
>
> -- 
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/
>

-----
Randall Stewart
randall@lakerest.net