Re: [tcpinc] TCP's treatment of data in SYN packets

Joe Touch <touch@isi.edu> Fri, 29 July 2016 20:04 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7D312D144 for <tcpinc@ietfa.amsl.com>; Fri, 29 Jul 2016 13:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
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 rlvBhAUimzam for <tcpinc@ietfa.amsl.com>; Fri, 29 Jul 2016 13:04:47 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A892112D1A9 for <tcpinc@ietf.org>; Fri, 29 Jul 2016 13:04:47 -0700 (PDT)
Received: from [128.9.184.41] ([128.9.184.41]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u6TK3vYe010822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 29 Jul 2016 13:03:58 -0700 (PDT)
To: David Mazieres expires 2016-10-27 PDT <mazieres-w53ip7iu6xqerwrmugqqq2s39i@temporary-address.scs.stanford.edu>, Kyle Rose <krose@krose.org>
References: <CAJU8_nU1WzQNFFUn_2o1cACutB01iyQ_hC29PHoutr8TRDKGnA@mail.gmail.com> <579A4669.7030600@isi.edu> <87lh0lselg.fsf@ta.scs.stanford.edu> <CAJU8_nUPrm9JJMrrMbL5+FpP-9CKC6EkidCry9UuZA5ZfyJtoA@mail.gmail.com> <579A8223.8050308@isi.edu> <CAJU8_nXSxr7ykC1TwptBmyP8pNccz52ozq=hF7-EYiaMdDeLBQ@mail.gmail.com> <8737mtqkf5.fsf@ta.scs.stanford.edu> <579BA4C5.2040004@isi.edu> <87oa5gl02w.fsf@ta.scs.stanford.edu>
From: Joe Touch <touch@isi.edu>
Message-ID: <579BB6AB.4010101@isi.edu>
Date: Fri, 29 Jul 2016 13:03:55 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <87oa5gl02w.fsf@ta.scs.stanford.edu>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u6TK3vYe010822
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/3dB2c3Q15t8krX7PUB14X_1-P_c>
Cc: tcpinc <tcpinc@ietf.org>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Subject: Re: [tcpinc] TCP's treatment of data in SYN packets
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for adding encryption to TCP." <tcpinc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpinc/>
List-Post: <mailto:tcpinc@ietf.org>
List-Help: <mailto:tcpinc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2016 20:04:48 -0000


On 7/29/2016 12:24 PM, David Mazieres wrote:
> Joe Touch <touch@isi.edu> writes:
>
>> FWIW, IMO the best wording would:
>>
>> - start with the simplest case, i.e., NOT trying to optimize EDO to use
>> SYN data
>>
>> - present the use of SYN data with EDO as an optimization
>>         that optimization might be a MAY or SHOULD, but not a MUST
>>
>> Otherwise, you're needlessly complicating your spec for an optimization.
> I'm not sure I follow.  The issue here is about application data that
> needs to be decrypted, acked, and delivered in order.  EDO would seem to
s/EDO/ENO/

Joe