Re: [tcpm] More TCP option space in a SYN: draft-briscoe-tcpm-syn-op-sis-02

Joe Touch <touch@isi.edu> Thu, 25 September 2014 14:53 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438DA1A6F56 for <tcpm@ietfa.amsl.com>; Thu, 25 Sep 2014 07:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.986
X-Spam-Level:
X-Spam-Status: No, score=-4.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1lyw_AR2Xc0 for <tcpm@ietfa.amsl.com>; Thu, 25 Sep 2014 07:53:25 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3A731A00F9 for <tcpm@ietf.org>; Thu, 25 Sep 2014 07:53:25 -0700 (PDT)
Received: from [128.9.176.34] (c1-vpn4.isi.edu [128.9.176.34]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s8PEr0Co018241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 25 Sep 2014 07:53:00 -0700 (PDT)
Message-ID: <54242C4D.9000804@isi.edu>
Date: Thu, 25 Sep 2014 07:53:01 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Bob Briscoe <bob.briscoe@bt.com>
References: <201409222045.s8MKjZdD002071@bagheera.jungle.bt.co.uk> <542344DA.9020905@isi.edu> <201409250956.s8P9uae9013452@bagheera.jungle.bt.co.uk>
In-Reply-To: <201409250956.s8P9uae9013452@bagheera.jungle.bt.co.uk>
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
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/HR1g2XUmqkffsJNjNfG4Q2RmkHw
Cc: tcpm IETF list <tcpm@ietf.org>
Subject: Re: [tcpm] More TCP option space in a SYN: draft-briscoe-tcpm-syn-op-sis-02
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Sep 2014 14:53:27 -0000


On 9/25/2014 2:56 AM, Bob Briscoe wrote:
> Joe,
> 
> At 23:25 24/09/2014, Joe Touch wrote:
>> Hi, Bob (et al.),
>>
>> It's good to have a more detailed description of the proposal.
>>
>> I still find a dual-SYN solution untenable, though, as it has been for
>> other upgrade paths in the past (e.g., IPv6).
> 
> That's why I prefer syn-op-sis because it only uses 2 SYNs for transition.
> 
> I've included a new section on ways to use only 1 SYN during transition
> (building a white-list) and ultimately moving to 1 SYN in the future,
> only falling back to the legacy SYN in series rather than parallel if
> you hit a legacy listener.
> 
> The other two in tcp-syn-ext-opt have to be 2-SYN for ever.

But they don't both use two SYNs. One (that I prefer) uses an additional
out-of-band segment.

IMO, using two SYNs is problematic - regardless of whether the upgraded
system uses both or just one.

IMO, we're going to be dealing with legacy TCPs for a *very* long time.

Time for others to jump in ;-)

Joe