IETF Logo Mail Archive

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

Joe Touch <touch@isi.edu> Fri, 29 July 2016 19:35 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 1563612D833 for <tcpinc@ietfa.amsl.com>; Fri, 29 Jul 2016 12:35:55 -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 vFMplhJNfxax for <tcpinc@ietfa.amsl.com>; Fri, 29 Jul 2016 12:35:53 -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 B7818127071 for <tcpinc@ietf.org>; Fri, 29 Jul 2016 12:35:53 -0700 (PDT)
Received: from [10.76.219.53] (mobile-166-171-121-001.mycingular.net [166.171.121.1]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u6TJZHpX005517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 29 Jul 2016 12:35:19 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@isi.edu>
X-Mailer: iPhone Mail (13G34)
In-Reply-To: <5459b95c-0932-0af0-13f8-ad2c703806c4@mti-systems.com>
Date: Fri, 29 Jul 2016 12:35:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <93EFE433-42AE-4314-BBFF-D6EE95773C61@isi.edu>
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> <5459b95c-0932-0af0-13f8-ad2c703806c4@mti-systems.com>
To: Wesley Eddy <wes@mti-systems.com>
X-MailScanner-ID: u6TJZHpX005517
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/D0nGE3CLdBokV8__IIorkEXw2V8>
Cc: tcpinc@ietf.org
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 19:35:55 -0000

Yeah - ENO. 



> On Jul 29, 2016, at 12:18 PM, Wesley Eddy <wes@mti-systems.com> wrote:
> 
>> On 7/29/2016 2:47 PM, Joe Touch wrote:
>> 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.
> 
> Just to be clear, this is actually talking about ENO, and not EDO, correct?  (I'm assuming a repeated typo in your message)
> 
> SYN data with EDO does not need any special discussion, because EDO only alters DO semantics for later (non-SYN) segments.  So, how a stack deals with data on SYN is un-related to EDO (but more critical for ENO).
> 
> 
> 
> 
> _______________________________________________
> Tcpinc mailing list
> Tcpinc@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpinc

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