Re: [tcpm] New Version Notification for draft-touch-tcpm-tcp-edo-01.txt

Bob Briscoe <bob.briscoe@bt.com> Fri, 23 May 2014 10:03 UTC

Return-Path: <bob.briscoe@bt.com>
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 BFD581A03E4 for <tcpm@ietfa.amsl.com>; Fri, 23 May 2014 03:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 5CW6S0xTJGp1 for <tcpm@ietfa.amsl.com>; Fri, 23 May 2014 03:03:42 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D9901A03EE for <tcpm@ietf.org>; Fri, 23 May 2014 03:03:34 -0700 (PDT)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR65-UKRD.bt.com (10.187.101.20) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 23 May 2014 11:03:31 +0100
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.348.2; Fri, 23 May 2014 11:03:28 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) with Microsoft SMTP Server id 14.3.181.6; Fri, 23 May 2014 11:03:27 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.232.89]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4NA3PAB005137; Fri, 23 May 2014 11:03:26 +0100
Message-ID: <201405231003.s4NA3PAB005137@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 23 May 2014 11:03:25 +0100
To: Joe Touch <touch@isi.edu>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <537E66A7.4080907@isi.edu>
References: <20140425221257.12559.43206.idtracker@ietfa.amsl.com> <2586_1398464386_535ADF82_2586_915_1_535ADF56.9050106@isi.edu> <CF8D8E25-E435-4199-8FD6-3F7066447292@iki.fi> <5363AF84.8090701@mti-systems.com> <5363B397.8090009@isi.edu> <CAO249yeyr5q21-=e6p5azwULOh1_jUsniZ6YPcDYd69av8MMYw@mail.gmail.com> <DCC98F94-EA74-4AAA-94AE-E399A405AF13@isi.edu> <655C07320163294895BBADA28372AF5D2CFE36@FR712WXCHMBA15.zeu.alcatel-lucent.com> <20140503122950.GM44329@verdi> <655C07320163294895BBADA28372AF5D2D009E@FR712WXCHMBA15.zeu.alcatel-lucent.com> <201405221710.s4MHAY4S002037@bagheera.jungle.bt.co.uk> <537E3ACD.5000308@isi.edu> <537E48CE.8040704@mti-systems.com> <537E66A7.4080907@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/6nCr9BKVNtMVUduSZlGenUavM-A
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] New Version Notification for draft-touch-tcpm-tcp-edo-01.txt
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: Fri, 23 May 2014 10:03:43 -0000

Joe, and everyone else who wants to work on this,

Just because it's easier to make a chocolate teapot than a cast-iron 
one, doesn't imply that there is any need for chocolate teapots.

IOW, we will be asking the IESG to spend reviewer time on EDO, so we 
need to give some plausible indication that someone might find it 
useful and it's not just an academic exercise. The current draft 
solely gives SACK + MPTCP + TCP-AO as an example, but is that really 
something that can't be done today?

Adding more complexity to the TCP stack (with the potential for more 
vulnerabilities) is only worthwhile if there's an identifiable 
benefit, otherwise few production stacks are going to implement it anyway.



Bob



At 22:05 22/05/2014, Joe Touch wrote:


>On 5/22/2014 11:58 AM, Wesley Eddy wrote:
>>On 5/22/2014 1:58 PM, Joe Touch wrote:
>>>>2) However, I think the main problem is that many important cases will
>>>>need as large or larger TCP option space on the SYN as on non-SYNs.
>>>
>>>Oh, I certainly agree with this. The point of this proposal is twofold:
>>>
>>>      a) (primary) to put to bed the notion that 'there is a way'
>>>      to extend SYN option space without contaminating connections to
>>>      legacy hosts
>>>
>>>      b) (secondary) to do the only extension possible - post-SYN.
>>
>>
>>I agree with this.  In my view, we actually have had consensus
>>for a long time that extending the SYN is "really hard" (requiring
>>some creativity),
>
>Well, AFAICT we've also known for a long time that it's basically 
>impossible when needed - i.e., to new endpoints, without impacting 
>legacy endpoints (i.e., making their connections to new systems slow 
>or misinterpreting option info as user data).
>
>Yes, there are a few other potential solutions that need to be 
>discussed as non-viable, but IMO that's an important part of this doc.
>
>At the very least, even if it's not provably impossible, the obvious 
>solutions don't work and it's harder than it looks.
>
>Joe

________________________________________________________________
Bob Briscoe,                                                  BT