IETF Logo Mail Archive

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

Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org> Tue, 02 August 2016 08:24 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 3632C12B035; Tue, 2 Aug 2016 01:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level:
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, 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 eCSf2SxEx5qL; Tue, 2 Aug 2016 01:24:28 -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 E4D4612B004; Tue, 2 Aug 2016 01:24:27 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Aug 2016 08:24:26 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E50FE9CC82; Tue, 2 Aug 2016 01:24:25 -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=hwRvknjKwqA+R1ITNIYhqzTRwj0=; b=Tf cuPE0mbb9BjiOQV+P36Fa8ZkLII/ZS2MVT7W+NYh4ZzVWZkiKlE4zyq4cj62TI4E FXGfYx1W/OcKdQU+Mx4OgMAAqCDMAKLwejtJBSQvW5qLPOgJmUk3kdadgaSc+YvA vljf3CYuJDTqG4ty5YkN2NGoRZ5287czyO1sxMX7E=
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=cReV6VGYPTUkSnBH9/Mz5ZrlNS3J 68Wdi+vvnNb0RJ5f75tUP8tu8AJ66yk1wPPVxIjqk8Q1KCSzoWGsMIs9tJSGC30t 6rb5cfn5XBD0bVcgTwOVlHmksCc/HKWAkv2Swf9IR+/nyFHcDdw6f6/gBWaVCxp+ Oq2jTnybYs4LrMA=
Received: by cowbell.employees.org (Postfix, from userid 1736) id D1DC79CC81; Tue, 2 Aug 2016 01:24:25 -0700 (PDT)
Date: Tue, 02 Aug 2016 09:24:25 +0100
From: Derek Fawcus <dfawcus+lists-tcpcrypt@employees.org>
To: Gavin McCullagh <gmccullagh@gmail.com>
Message-ID: <20160802082425.GA9117@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> <20160728063754.GA24657@cowbell.employees.org> <CAHQ5LGpOXj3ri92wvUMkDF9pUGmDHvsF5u+DTG0SkJOV6qaBCQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHQ5LGpOXj3ri92wvUMkDF9pUGmDHvsF5u+DTG0SkJOV6qaBCQ@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/hPDsn4W2VWKF3VdezNibNpx1l_k>
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 08:24:29 -0000

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.

This was before SYN cookies were invented.  As I recall,  I'd stopped using KA9Q
before '96,  which a search indicates is when SYN cookies started.

The KA9Q configuration option was 'tcp syndata',  if you do searches for 'ka9q nos'
you'll find the code if you wish to play (or just read it).

DF

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