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

Joe Touch <touch@ISI.EDU> Thu, 28 May 2009 20:45 UTC

Return-Path: <touch@ISI.EDU>
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 266723A6F91 for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 13:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level:
X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[AWL=0.269, 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 YPQyFGq59Uur for <tsvwg@core3.amsl.com>; Thu, 28 May 2009 13:45:16 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 32E333A69F6 for <tsvwg@ietf.org>; Thu, 28 May 2009 13:45:16 -0700 (PDT)
Received: from [128.9.184.170] ([128.9.184.170]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n4SKke4Q002688; Thu, 28 May 2009 13:46:42 -0700 (PDT)
Message-ID: <4A1EF830.40006@isi.edu>
Date: Thu, 28 May 2009 13:46:40 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
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: <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> <2CF8190F-ECCB-422A-BA5A-7ED17DFDF33D@lakerest.net> <20090528203844.GA18571@openss7.org>
In-Reply-To: <20090528203844.GA18571@openss7.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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 20:45:22 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Brian F. G. Bidulock wrote:
> Randy,
> 
> Randy Stewart wrote:                          (Thu, 28 May 2009 11:15:27)
>> 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...
> 
> I'm not sure that a time-wait will do that either: that is: When
> all the vtags are in timed-wait what will you do?  If you refuse
> the connection there is a DoS attack waiting to be exploited. 

That should only happen for established (opened) connections that then
close (non-established wouldn't generate a time-wait). An endpoint that
wants to exhaust your resources can do worse with an open connection
than to run through connections and close them just to pile on the
time-waits, so it seems like this should be moot.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoe+DAACgkQE5f5cImnZruuRQCfSpBksya4WW3MdU8lfcxBSqSJ
DEYAoItRZbBqBnc9oKLZtad2GHzwwFvh
=l6un
-----END PGP SIGNATURE-----