IETF Logo Mail Archive

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

Jeremy Harris <jgh@wizmail.org> Sat, 30 July 2016 23:33 UTC

Return-Path: <jgh@wizmail.org>
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 2035112D0BC for <tcpinc@ietfa.amsl.com>; Sat, 30 Jul 2016 16:33:38 -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 ckeOjzfykvZT for <tcpinc@ietfa.amsl.com>; Sat, 30 Jul 2016 16:33:36 -0700 (PDT)
Received: from wizmail.org (wizmail.org [IPv6:2a00:1940:107::2:0:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C3D312B057 for <tcpinc@ietf.org>; Sat, 30 Jul 2016 16:33:36 -0700 (PDT)
Received: from [2a00:b900:109e:0:3e97:eff:feb2:e128] (helo=lap.dom.ain) by wizmail.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87_RC110) id 1bTdl8-00019a-Iv for tcpinc@ietf.org (return-path <jgh@wizmail.org>); Sat, 30 Jul 2016 23:33:34 +0000
To: tcpinc@ietf.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> <579BA470.3000405@isi.edu> <CAJU8_nXjhHH1eEXPA3hvhJ3YXsP_v2djGX=X2p9+wyn767Hm5A@mail.gmail.com> <adcaa33a-3bf5-e63a-bd19-fd165b16aa7d@wizmail.org> <87oa5fniu0.fsf@ta.scs.stanford.edu>
From: Jeremy Harris <jgh@wizmail.org>
Message-ID: <9ff12fb6-44f9-b1d0-2e9d-a67683679037@wizmail.org>
Date: Sun, 31 Jul 2016 00:33:33 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <87oa5fniu0.fsf@ta.scs.stanford.edu>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Pcms-Received-Sender: [2a00:b900:109e:0:3e97:eff:feb2:e128] (helo=lap.dom.ain) with esmtpsa
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/musilfnMDhtwWdhJlqWBloxYfWg>
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: Sat, 30 Jul 2016 23:33:38 -0000

On 30/07/16 18:20, David Mazieres wrote:
> No one is suggesting sending data in a SYN segment to a server that does
> not support ENO.  In fact, no one is even suggesting sending data in a
> SYN segment.

I'm confused.  Kyle was talking about it:

On 29/07/16 20:41, Kyle Rose wrote:
> Right, I get that for interoperability with ENO-unaware stacks there is no
> way to change data presented in the SYN.
[...]
> (1) If it is negotiating ENO, it will hand the data off to the chosen TEP,
> which will then indicate back to ENO whether to ACK the data or not.

-- 
Jeremy

v2.37.1 | Report a Bug | By Email | System Status