Re: [tcpm] I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt

Jan Rüth <Jan.Rueth@comsys.rwth-aachen.de> Mon, 22 February 2021 10:46 UTC

Return-Path: <Jan.Rueth@comsys.rwth-aachen.de>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA643A1334 for <tcpm@ietfa.amsl.com>; Mon, 22 Feb 2021 02:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 Li6woSOpUmRs for <tcpm@ietfa.amsl.com>; Mon, 22 Feb 2021 02:46:06 -0800 (PST)
Received: from mail-out-2.itc.rwth-aachen.de (mail-out-2.itc.rwth-aachen.de [IPv6:2a00:8a60:1:e501::5:47]) (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 B33243A13A2 for <tcpm@ietf.org>; Mon, 22 Feb 2021 02:46:02 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CcAwD5ijNg/xUN4oliHAEBAQEBAQcBARIBAQQEAQFAgU+BU4E5FYFBCgGENpEzJQOIe4IokScLAQEBAQEBAQEBCAEdDQgCBAEBhE0CF4F2AiU4EwIQAQEGAQEBAQEGBIZSDYZEAQEBAwEBASEROgsFCwIBCA4KAgImAgICJQsVEAIEDgWCawGCZiABDq0ldoEyhD8BgRiDY4EIgQ4qhn2GRCaCHoE4DAMNgiI1PoJdAQEBgV6DFjSCKwSBS4EXTFEBAVsYEhiBFBqQJINPpV4HgWyBEok+j2WCdQMfgzGBNI5gMo9Nn36SIIQ5AgQCBAUCFoFrgXpxTyoBgj4JRxcCDY4rFohhhUVzAjYCBgEJAQEDCXyKCAGBDgEB
X-IPAS-Result: A2CcAwD5ijNg/xUN4oliHAEBAQEBAQcBARIBAQQEAQFAgU+BU4E5FYFBCgGENpEzJQOIe4IokScLAQEBAQEBAQEBCAEdDQgCBAEBhE0CF4F2AiU4EwIQAQEGAQEBAQEGBIZSDYZEAQEBAwEBASEROgsFCwIBCA4KAgImAgICJQsVEAIEDgWCawGCZiABDq0ldoEyhD8BgRiDY4EIgQ4qhn2GRCaCHoE4DAMNgiI1PoJdAQEBgV6DFjSCKwSBS4EXTFEBAVsYEhiBFBqQJINPpV4HgWyBEok+j2WCdQMfgzGBNI5gMo9Nn36SIIQ5AgQCBAUCFoFrgXpxTyoBgj4JRxcCDY4rFohhhUVzAjYCBgEJAQEDCXyKCAGBDgEB
X-IronPort-AV: E=Sophos;i="5.81,197,1610406000"; d="scan'208";a="136040737"
Received: from lists.comsys.rwth-aachen.de ([137.226.13.21]) by mail-in-2.itc.rwth-aachen.de with ESMTP; 22 Feb 2021 11:46:00 +0100
Received: from hermes-mbx.win.comsys.rwth-aachen.de (hermes-mbx.win.comsys.rwth-aachen.de [137.226.13.41]) by lists.comsys.rwth-aachen.de (Postfix) with ESMTPS id 31093C09C0; Mon, 22 Feb 2021 11:46:00 +0100 (CET)
Received: from HERMES-MBX.win.comsys.rwth-aachen.de (2a00:8a60:1014::41) by HERMES-MBX.win.comsys.rwth-aachen.de (2a00:8a60:1014::41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Feb 2021 11:45:59 +0100
Received: from HERMES-MBX.win.comsys.rwth-aachen.de ([fe80::e198:7509:269a:ddb6]) by HERMES-MBX.win.comsys.rwth-aachen.de ([fe80::e198:7509:269a:ddb6%11]) with mapi id 15.01.2106.002; Mon, 22 Feb 2021 11:45:59 +0100
From: Jan Rüth <Jan.Rueth@comsys.rwth-aachen.de>
To: Matthew Luckie <mjl@caida.org>
CC: "Scheffenegger, Richard" <rs.ietf@gmx.at>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Thread-Topic: [tcpm] I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt
Thread-Index: AQHW+o8yGOYm9cbOy0arauEwq/YkeKpHgXAAgADbe4CAAAebAIAArBiAgAWxSYCAAAgbgIAVP+uA
Date: Mon, 22 Feb 2021 10:45:59 +0000
Message-ID: <04723570-93E7-4BB8-821E-BC3672A42F15@comsys.rwth-aachen.de>
References: <161233469809.31214.294457730576935197@ietfa.amsl.com> <CAAK044QYBiGXKm+D+=edc8TWhjzAadBxER5VRFmJOdW8hdXFKg@mail.gmail.com> <244FE3E7-7B83-4884-B11B-028F7167B549@strayalpha.com> <CAAK044RKtJ_PpDXH9pmS90wqUZNK9unDggiDjVLUBK00cxhYnA@mail.gmail.com> <8C6762C8-2A22-4CC7-AF53-1D13FC3DC268@strayalpha.com> <C591EED6-210A-4AEB-94D6-D3B77130596E@strayalpha.com> <CAAK044SxMF1p-BzyOYWYkhYYrToLg+8Ybx8ZB-GeADGkayexGQ@mail.gmail.com> <274785c8-004e-71bb-828b-8d8d0ee95af8@gmx.at> <YCG4EQ9BCAvucdN1@sorcerer.cms.waikato.ac.nz>
In-Reply-To: <YCG4EQ9BCAvucdN1@sorcerer.cms.waikato.ac.nz>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.226.13.22]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BDC2BAF974582346A5E9769B300B5D31@comsys.rwth-aachen.de>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/5iL9CX1g9CoPCKLUUxGitNcYjhQ>
Subject: Re: [tcpm] I-D Action: draft-nishida-tcpm-agg-syn-ext-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 10:46:11 -0000

Hi everyone,

maybe I can add to the measurements that Matthew cited.
We performed these only once. But we are doing other measurements that we do more frequently.

From these I can report further numbers that we never got around to actually publish.

We look for TFO support on port 80 and we send TFO cookie requests to all of IPv4.
We get roughly 3.2M valid replies with TFO cookies (as of late 2019), which rose from 500k (mid 2017).

Regarding the mirrored options, we see around 70k - 80k empty cookie replies (essentially, we get our cookie request back) that have the same behavior as outlined in Olivier’s blogpost, this number is rather stable, sometimes 10k more or less.
This behavior is focussed on IPs residing in Chinese autonomous systems.
Our assumption has always been that this mirroring is performed by some middlebox and not an end-host.

If there is interest, I can perform these measurements with an unassigned TCP option number.

Best
 Jan


> On 8. Feb 2021, at 23:15, Matthew Luckie <mjl@caida.org> wrote:
> 
> Hi Richard,
> 
> On Mon, Feb 08, 2021 at 10:46:45PM +0100, Scheffenegger, Richard wrote:
>> Hi Yoshi,
>> 
>> Sorry to nitpick - in your draft, you mention that some hosts reflect
>> back unknown tcp options, which is why you are using different GID
>> mappings between SYN and SYN,ACK.
>> 
>> I did read about this behavior concerning TCP header flags / reserved
>> bits - but have not come across a paper where this behavior is described
>> for unknown TCP options (or I may have missed that aspect in the various
>> studies around TCP option investigations done by MPTCP and other groups).
> 
> There is some discussion of systems that seem to reflect TCP options here:
> 
> http://blog.multipath-tcp.org/blog/html/2018/12/19/which_servers_use_multipath_tcp.html
> 
> Matthew_______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm