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

Fernando Gont <fernando@gont.com.ar> Wed, 27 May 2009 17:47 UTC

Return-Path: <fernando.gont.netbook.win@gmail.com>
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 3068E3A6D7A for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 10:47:50 -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=[AWL=0.000, 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 z8Me2sEUxnQF for <tsvwg@core3.amsl.com>; Wed, 27 May 2009 10:47:49 -0700 (PDT)
Received: from mail-gx0-f164.google.com (mail-gx0-f164.google.com [209.85.217.164]) by core3.amsl.com (Postfix) with ESMTP id 4B4FD3A6E56 for <tsvwg@ietf.org>; Wed, 27 May 2009 10:47:13 -0700 (PDT)
Received: by gxk8 with SMTP id 8so658183gxk.13 for <tsvwg@ietf.org>; Wed, 27 May 2009 10:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=NXlaWFP1JetsmcSw+wNHHIFMTVnXnskycfXbmopKNDA=; b=Oswm1llLzbbs5gC23ANkXE+NU6XpxgHuV6rEcxqvLut6o9IqHsFEFt2ccH3dZ8zMzg GlYs/9yWaHhA8T0+UGKOen9VCEKBVI75uCDQgK6yucgcIcmLHfrsmVdq3CCMjPVv7aDt 151iwIIpxOu7zv+VNfM6t+DtZYM9wPVITcq3g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=Mrnzrt6OcBGirMk7E5aPNwoDuL5pXIpvO9aoKcgxu8dhGLc/qzOiFCSYQiWCGFmOYX GVreDAhB53Qxeo/SOv+fzBjPhHd8dH//5xNH/WL3h7vWqw9MK4aHGjoXdIo86eYNHK90 KAAJeC+8CFzTbGRBKb49rtMWEmHy+v/03fIQg=
Received: by 10.90.96.1 with SMTP id t1mr181497agb.57.1243446453156; Wed, 27 May 2009 10:47:33 -0700 (PDT)
Received: from ?168.77.196.154? (154.196.lacnicxii.lacnic.net [168.77.196.154]) by mx.google.com with ESMTPS id 39sm67422agb.71.2009.05.27.10.47.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 27 May 2009 10:47:32 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4A1D7CAC.5020500@gont.com.ar>
Date: Wed, 27 May 2009 14:47:24 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mallman@icir.org
References: <20090527032321.D5908293768@lawyers.icir.org>
In-Reply-To: <20090527032321.D5908293768@lawyers.icir.org>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Alfred Hönes <ah@tr-sys.de>, "James M. Polk" <jmpolk@cisco.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [Tsvwg] interoperability (was Re: 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 17:47:50 -0000

Mark Allman wrote:

>>>   - In 3.1 collisions are discussed as "interoperability problems".  I
>>>     don't think that is quite right.  I think the real issue is that
>>>     there is added delay in getting things setup.
>> If the remaining TIME-WAIT period is larger than the
>> connection-establishment timer, the connection-establishment attempt
>> will fail. (In any case, I consider long delays in
>> connection-establishment attempts as an interoperability
>> problem. e.g., racall the studies on interactive applications
>> referenced in the tcp soft errors I-D/RFC).
>>
>> OTOH, if the TIME-WAIT state is assassinated, packets from a previous
>> incarnation of he connection could result in undetected data stream
>> corruption.
> 
> Well, I still don't buy that you're using the most precise language
> here.  I wouldn't refer to this problem in that way.  But, I see where
> you're going.

Please let me know if you expect a change in the text, or whether it
would be okay to leave the text "as is".

FWIW, I could expand "interoperability problems" to "delays in the
establishment of connections or data corruption" if necessary. -- I just
thought that that was too much detail.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1