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

Joe Touch <touch@isi.edu> Tue, 02 August 2016 18:05 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 46E2E12D84F; Tue, 2 Aug 2016 11:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.187
X-Spam-Level:
X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 oZfEZBxVU3HQ; Tue, 2 Aug 2016 11:05:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 653A912D84B; Tue, 2 Aug 2016 11:05:02 -0700 (PDT)
Received: from [128.9.184.236] ([128.9.184.236]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u72I4Wsn001879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 2 Aug 2016 11:04:33 -0700 (PDT)
To: Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org>, Gavin McCullagh <gmccullagh@gmail.com>
References: <CAJU8_nU1WzQNFFUn_2o1cACutB01iyQ_hC29PHoutr8TRDKGnA@mail.gmail.com> <CAK6E8=d3psZBS1yX56fRQ-SP7qCN_vem5tNB8O42zPyo0TKj7Q@mail.gmail.com> <CAJU8_nWMBbqLLsYQ3GhqRk8YkptqjCF40h_R7HNSOrqHwLbgxQ@mail.gmail.com> <87wpk7x9v6.fsf@ta.scs.stanford.edu> <CAJU8_nWni5wu2BJLT_j559RjRT=GgrkyurQi2uwE7v8Mo61NHA@mail.gmail.com> <877fc6ycuw.fsf@ta.scs.stanford.edu> <20160727232419.GA45841@cowbell.employees.org> <20160728063754.GA24657@cowbell.employees.org> <CAHQ5LGpOXj3ri92wvUMkDF9pUGmDHvsF5u+DTG0SkJOV6qaBCQ@mail.gmail.com> <20160802082425.GA9117@cowbell.employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <57A0E0B0.7010003@isi.edu>
Date: Tue, 02 Aug 2016 11:04:32 -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: <20160802082425.GA9117@cowbell.employees.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/byaO21W9BiCeK6XBT-bkpxN1XZE>
Cc: tcpinc <tcpinc@ietf.org>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Subject: Re: [tcpinc] [tcpm] 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: Tue, 02 Aug 2016 18:05:03 -0000


On 8/2/2016 1:24 AM, Derek Fawcus wrote:
> On Mon, Aug 01, 2016 at 08:52:43pm -0700, Gavin McCullagh wrote:
>> Just to satisfy my curiosity, how did this work (or did it?) with TCP SYN Cookies?
> The sender of the SYN would simply send the data again once the 3whs completed.
An important point - it would send exactly the same data again (or if it
sent more data, the overlapping portions never changed).

Joe