IETF Logo Mail Archive

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

"Brian F. G. Bidulock" <bidulock@openss7.org> Thu, 28 May 2009 14:50 UTC

Return-Path: <bidulock@openss7.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 B06E03A6E87 for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 07:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level:
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 JpInyCJW3GDU for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 07:50:17 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id C7A393A6F29 for <tsvwg@ietf.org>; Thu, 28 May 2009 07:50:12 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (IDENT:ADoeHIhEN2HAVJy2eNchQpx3+u+mpbKj@ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.13.8/8.13.8/Debian-3) with ESMTP id n4SEpNTR032127; Thu, 28 May 2009 08:51:23 -0600
Received: from wilbur.pigworks.openss7.net (IDENT:811P1AORBlosuogBtMjisgxcwJ5fg4sp@localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Debian-3) with ESMTP id n4SEpNkq007752; Thu, 28 May 2009 08:51:23 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Submit) id n4SEpEYN007749; Thu, 28 May 2009 08:51:14 -0600
Date: Thu, 28 May 2009 08:51:14 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Randy Stewart <randall@lakerest.net>
Message-ID: <20090528145114.GB2677@openss7.org>
Mail-Followup-To: Randy Stewart <randall@lakerest.net>, Joe Touch <touch@ISI.EDU>, "James Polk (jmpolk)" <jmpolk@cisco.com>, "Anantha Ramaiah (ananth)" <ananth@cisco.com>, tsvwg <tsvwg@ietf.org>, mallman@icir.org, Fernando Gont <fernando@gont.com.ar>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9F71CBFA-9E70-4CD4-B60D-D15F45842739@lakerest.net>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
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
Reply-To: bidulock@openss7.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: Thu, 28 May 2009 14:50:18 -0000

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/

v2.23.0 | Report a Bug | By Email