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

Randall Stewart <rrs@lakerest.net> Wed, 27 May 2009 09:11 UTC

Return-Path: <rrs@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 6D0433A6C2D for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 02:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 gIAWnCotWVcP for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 02:11:16 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id DBF0B3A6E56 for <tsvwg@ietf.org>; Wed, 27 May 2009 02:11:05 -0700 (PDT)
Received: from [192.168.1.108] (cpe-066-057-254-179.nc.res.rr.com [66.57.254.179]) (authenticated bits=0) by lakerest.net (8.14.3/8.14.3) with ESMTP id n4R9COvW099099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 27 May 2009 05:12:26 -0400 (EDT) (envelope-from rrs@lakerest.net)
DKIM-Signature: a=rsa-sha1; c=simple/simple; d=lakerest.net; s=mail; t=1243415548; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: X-Mailer; b=BoZpc92E7MYMQWaGsRm6T0buJ9xdYFJEy0LmALKsSSVGc56zNQ7/GHA fC/5Kwb/8loyFnb9aEzV8v7jsnnzLdQ==
Message-Id: <C240732A-D48D-4D96-85BD-2E3C090682C3@lakerest.net>
From: Randall Stewart <rrs@lakerest.net>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A1BF56D.3020709@isi.edu>
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: Wed, 27 May 2009 05:12:19 -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>
X-Mailer: Apple Mail (2.935.3)
Cc: "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>
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: Wed, 27 May 2009 09:11:18 -0000

On May 26, 2009, at 9:58 AM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Anantha Ramaiah (ananth) wrote:
>>
>>
>>> -----Original Message-----
>>> From: Fernando Gont
>>> [mailto:fernando.gont.netbook.win@gmail.com] On Behalf Of
>>> Fernando Gont
>>> Sent: Monday, May 25, 2009 8:19 AM
>>> To: Anantha Ramaiah (ananth)
>>> Cc: Joe Touch; mallman@icir.org; James Polk (jmpolk); tsvwg
>>> Subject: Re: [Tsvwg] WGLC for Port Randomization starts now
>>> (April 1st)
>>>
>>> Anantha Ramaiah (ananth) wrote:
>>>
>>>> Hmm.. I missed this one.. The draft which we had put out
>>> more than an
>>>> year ago DOES talk about keeping state at the peer to minimize
>>>> collisions. It lists a few algorithms to that effect as well.
>>> They probably mean that additional work is required only on
>>> the side that performed the passive close. (i.e., half of the
>>> work is already done).
>>
>> Any RFC compliant TCP implementation will honor TIME-WAIT requirement
>> and that involves keeping state at the side which initiated the
>> connection close.
>
> It's worth noting that many implementations aren't RFC compliant in  
> this
> regard, though.
>
>> It is also well known that the side-effect of
>> TIME-WAIT requirement leads for the 4-tuple (socket-pairs) to be  
>> locked
>> for some time.
>
> That is not a "side effect", that is the *desired* effect.
>
>> It needs to be pointed out at that, other transport
>> protocols like SCTP doesn't have the TIME-WAIT requirement since the
>> protocol supports in-built mechanisms to deal with the need for the
>> same.
>
> SCTP has a TIME WAIT state for its connection IDs (socket pair and
> vtags), just as TCP has for its (socket pair). The difference is that
> SCTP has a larger connection ID space, that's *all*.


Joe:

Technically you are correct... there is a timed-wait on vtags. The
BSD implementation (the reference implementation) does properly  
implement
this. However the space is so large most implementations do not do so.

I guess other developers have felt its not worth the trouble with such
a large space....

R



>
>
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkob9W0ACgkQE5f5cImnZrseiQCfZEJ3sWltiyvMmSnTkwyyWooy
> J5IAoMhmJQBfK5rsxmJeOnUXgsXpGOR8
> =OWYf
> -----END PGP SIGNATURE-----
>

------------------------------
Randall Stewart
803-317-4952 (cell)
803-345-0391(direct)