IETF Logo Mail Archive

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

Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org> Thu, 28 July 2016 06:37 UTC

Return-Path: <dfawcus@employees.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 601E012D0A1; Wed, 27 Jul 2016 23:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level:
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=dfawcus+lists-tcpcrypt@employees.org header.d=employees.org
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 mCgZhjnnQwPu; Wed, 27 Jul 2016 23:37:58 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A273A12D616; Wed, 27 Jul 2016 23:37:57 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jul 2016 06:37:56 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E134F9CC81; Wed, 27 Jul 2016 23:37:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=date:from :to:cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=selector1; bh=UIXpADeMEICvPc04cV340HiOwN8=; b=f0 KLhHinpijUqnAEsRNJdn5wfbWHUDwMY1/2bPKc9Gsc4dvei11WoYCH8z4e6gLIUr Tu4CsOB+Vn90oNDTUFQB5MazaeNHQ1YcWnEt73gPYMZznhCKhcRtXHzt2ux3WM2t t3dexi/UF12/1u1qbNYasXK1PbTcIbpEsYc6RomCE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=date:from :to:cc:subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=selector1; b=K4VjCYx8to3c0Iu+U1CzvTQQmpnF rOQgZbnlpZ/wOA9sO89tbu7+3KXsKtn6+8KBf7Uej49aRWcSkVn05dU32atdCFMZ k7TnfGsfOJtx0PHzMz26Rq4yJ+VVV4vsNqa7aHHBQKFURVy+DHc9fP+0y7bHoclz S9nIFNNeJD8wX3Q=
Received: by cowbell.employees.org (Postfix, from userid 1736) id CD83A9CC4F; Wed, 27 Jul 2016 23:37:54 -0700 (PDT)
Date: Thu, 28 Jul 2016 07:37:54 +0100
From: Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org>
To: Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org>
Message-ID: <20160728063754.GA24657@cowbell.employees.org>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160727232419.GA45841@cowbell.employees.org>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/7uyKQaHte1ZiNCWpmMrikA9PcMA>
Cc: tcpinc <tcpinc@ietf.org>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, Kyle Rose <krose@krose.org>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, Yuchung Cheng <ycheng@google.com>, David Mazieres expires 2016-10-25 PDT <mazieres-5mehvxfqtr38mvjvf6tfwgcy62@temporary-address.scs.stanford.edu>, Christoph Paasch <cpaasch@apple.com>
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: Thu, 28 Jul 2016 06:37:59 -0000

On Thu, Jul 28, 2016 at 12:24:19am +0100, Derek Fawcus wrote:
> 
> Implying that a passive opener which chose to ack such data bytes would
> have to buffer such data until the handshake completes;  but I'm not
> aware of any stack which actually works that way.

Except the old KA9Q NOS,  which was tickling my memory...

It did have the ability to send such SYN data.

DF

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