IETF Logo Mail Archive

Re: [tcpm] usage for timestamp options in the wild

Praveen Balasubramanian <pravb@microsoft.com> Wed, 26 September 2018 18:21 UTC

Return-Path: <pravb@microsoft.com>
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 8C4D9130E3B for <tcpm@ietfa.amsl.com>; Wed, 26 Sep 2018 11:21:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.467
X-Spam-Level:
X-Spam-Status: No, score=-0.467 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 JYNsp_kcOBaL for <tcpm@ietfa.amsl.com>; Wed, 26 Sep 2018 11:21:18 -0700 (PDT)
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-eopbgr710102.outbound.protection.outlook.com [40.107.71.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1724F130E41 for <tcpm@ietf.org>; Wed, 26 Sep 2018 11:21:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jAYIJYXqhN2Q9ob9u5mUtE8o56liVKlyYoKK2aGffWA=; b=nM4OeV9WOXszaY2hkSFTIh9Fh73v5EzscdqtcYPh7aToQgyxt8u2SwFrvu+uCc9GICpDIc6vgst66S5HhaA1vjo9+eZ4rTNbBVKIb40dUvCeoaCJ0tPYyMkuI51lNSfwgYXcBIofodQVfltQ6UlAfi/YsdUNnDdbXe10i2Kb5F4=
Received: from MWHPR21MB0191.namprd21.prod.outlook.com (10.173.52.137) by MWHPR21MB0768.namprd21.prod.outlook.com (10.173.51.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1207.9; Wed, 26 Sep 2018 18:21:15 +0000
Received: from MWHPR21MB0191.namprd21.prod.outlook.com ([fe80::5443:2f41:bcd:634f]) by MWHPR21MB0191.namprd21.prod.outlook.com ([fe80::5443:2f41:bcd:634f%5]) with mapi id 15.20.1207.006; Wed, 26 Sep 2018 18:21:15 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] usage for timestamp options in the wild
Thread-Index: AQHUVcFDBUenX6MW2Ui5madIUzPkvaUC3v1A
Date: Wed, 26 Sep 2018 18:21:15 +0000
Message-ID: <MWHPR21MB019123F8820BE88FEAA2A9FBB6150@MWHPR21MB0191.namprd21.prod.outlook.com>
References: <CAO249yd-3PBzjtO+Jgpz-qDTROgoKJEQetJTxiepJ34LPqZG+w@mail.gmail.com>
In-Reply-To: <CAO249yd-3PBzjtO+Jgpz-qDTROgoKJEQetJTxiepJ34LPqZG+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e8:3:8e1c:417:2114:339b]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0768; 6:AwmI/PNnTkRMVJT3HjETT7s8B7aPkvw+hNc3ZXN9++k1fSZfXlhOjtGiPT6TcfQyGQiB/Uc0uTRpPEcIX7Bh0sC6YHai8GT2q1njyoUfW9A+CkapryurmWH2xPPLlktjgVlUXvgt3K/n/Kix/SrNSWAoJx5C7qntNxszUsCnoeQ17w++OXv+fvM1H9WEyMvn5jGP0viqsrrKSg3zGr2dpKxP9Fx/20wql+ZWs3eeYzAtsnfYXuKLRhEZJwI0mQ1Sdl68DZVinMfT5cqVcGA03F9edkfyls9ItkCGEVC2tM89TiA/n/AvS8TIo9k7PyFCMtd4KW0rWU6w53tlP5C7W65+nnyogRPX8Dw83u025y6aNCvae48y7WzZWbwblpDDgUs+91Q4B5AgOpKR3laYbJ0w3DphzQTAd3JZNNNNhpu9/kGXQZCHa0wzNq7ZQWIh6vcCH0sZrjQXkPFdIKWZSA==; 5:dsLVgxUlhsIZycI7KBtx2IHg8ZJAbt/zi3oJYQUeztzpAhubCCztRZSvQTzOms6cUCHI6xsAY5BffTZ0f6CMXtO8617CJWeB1Uy2yVez/1iOFkF/OOLokmZRsgm3FzpEbPGk+eVIwYan8ZqfZ6rwa2FTMvBf1faS1GB0smJ+jBg=; 7:iyvbKKK7irXD/UK4tayC/gg3aQeK4Xz8CEaQ7nrRIa0fPuMk2IlLRvNt2HISXFyyvZpIzwfmynGPxE5+P6dr3nkSkgimbSjgI7UIMe1xjtNvCKsXf6gTI14M8gY9PKSLBDhLOPXJNpboejU1HkaaymiI0jlfGlaiwWRqAfplAVck64HGbFBjR57i/pbFANRfJ1+BJ94VotIuhy2Fl9tujYQ7+VN/n4QSn3yHJb4Bev2O2s0wvfhdD/T/jQ1WMRjY
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 56d77270-7ff2-4492-de98-08d623dcd8ae
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534165)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:MWHPR21MB0768;
x-ms-traffictypediagnostic: MWHPR21MB0768:
x-microsoft-antispam-prvs: <MWHPR21MB0768B168DC18C5EDA995F2D6B6150@MWHPR21MB0768.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155)(28532068793085)(190501279198761)(227612066756510)(219752817060721)(189930954265078);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231355)(944501410)(52105095)(2018427008)(6055026)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(201708071742011)(7699051)(76991041); SRVR:MWHPR21MB0768; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0768;
x-forefront-prvs: 08076ABC99
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(346002)(396003)(39860400002)(376002)(366004)(199004)(189003)(186003)(25786009)(6506007)(476003)(10090500001)(86362001)(7736002)(34290500001)(5660300001)(11346002)(19609705001)(97736004)(110136005)(71200400001)(71190400001)(6246003)(46003)(33656002)(102836004)(316002)(86612001)(446003)(6346003)(486006)(7696005)(8990500004)(22452003)(53546011)(99286004)(76176011)(74316002)(5250100002)(6306002)(478600001)(9686003)(54896002)(236005)(106356001)(10290500003)(105586002)(606006)(2501003)(229853002)(55016002)(6436002)(2906002)(6116002)(53936002)(68736007)(2900100001)(14444005)(256004)(8936002)(790700001)(8676002)(81166006)(81156014)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0768; H:MWHPR21MB0191.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com;
x-microsoft-antispam-message-info: Gle6WQ2RndMvxXZ8+lZ5MGSlzSlwpDo0GPf0Z8CUF7Xp8rQ64tvxBN4ADWfNXl1wVOdUN26UOFpdFkjWZMR76XRqT1VBhBrn1O+ccUlL6Rl31m6/G3a+aq3cgYLvW6GTD/fg3nkV1knq2RVlk8w/qORDUMTTZoj3qDIxjnI/4jmv76GttLHo+QP8kN0CjZ0Ey82dshNUn9QNTjFaITMfKhNDIFUjYasZdh5VjnzSNo7QvKKcPWySAo6wP5p9CLQ69ytHTqj3CW4E/hXqbblG3z4Uw4H/iPm2cMoLcdstDAmALthg5H/TXhFfdSU0uMjo0a4BEypSmNcQScyldG7IJ94QIKpXc0Xnnzqwz6ofGI8=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB019123F8820BE88FEAA2A9FBB6150MWHPR21MB0191namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 56d77270-7ff2-4492-de98-08d623dcd8ae
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2018 18:21:15.3526 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0768
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/UZc9JAggjzV-93txAstwo4auDtQ>
Subject: Re: [tcpm] usage for timestamp options in the wild
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: Wed, 26 Sep 2018 18:21:22 -0000

Windows doesn’t do timestamp option by default. It’s 10 byte per packet overhead for marginal benefits.

From: tcpm <tcpm-bounces@ietf.org> On Behalf Of Yoshifumi Nishida
Sent: Wednesday, September 26, 2018 10:49 AM
To: tcpm@ietf.org
Subject: [tcpm] usage for timestamp options in the wild

Hello,
this is just out of my curiosity.
I've checked traffic archives in CAIDA (https://data.caida.org/datasets/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata.caida.org%2Fdatasets%2F&data=02%7C01%7Cpravb%40microsoft.com%7Ccba356afa7e34779babf08d623d86481%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636735809644749695&sdata=wUz0HExJ2m3RePYxM0abwYwPhl2UeANaV8NAg%2ByKk9c%3D&reserved=0>) and WIDE (http://mawi.wide..ad.jp/mawi/<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmawi.wide.ad.jp%2Fmawi%2F&data=02%7C01%7Cpravb%40microsoft.com%7Ccba356afa7e34779babf08d623d86481%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636735809644759707&sdata=XgSjCziCC%2BuoJAynXixBQObdqmAk%2FlBxZ%2FTR2CMF3Gk%3D&reserved=0>) on a whim and tried to see how many connections utilize timestamps.

As far as I've checked some archives recently captured, it seems that around 60-70% TCP connections use timestamp option. But, this ratio seems to be a bit lower as I thought most of implementations these days support TS option and activate it by default.
Does anyone have some ideas about it? Am I looking at uncommon data? Or there are still many old implementations around? Or, many users have disabled the option for some reasons?
--
Yoshi

v2.23.0 | Report a Bug | By Email