[tcpm] Re: TCP Option Length Bit Shifting
"Bonica, Ron" <ronald.bonica@hpe.com> Tue, 04 August 2026 18:37 UTC
Return-Path: <ronald.bonica@hpe.com>
X-Original-To: tcpm@mail2.ietf.org
Delivered-To: tcpm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 810B81239A030; Tue, 4 Aug 2026 11:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785868678; bh=TMfMFGgh7F7auojF2owmONt771pjfak416/E+0q3Yxk=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=SRIwkOLwn2kbgyu9Q1jbh2JcuJn3wv5Hn7Kj5IpV1eJBjdS1duvx++2aK/15N7bUI Cums5ElPlslr18ZaxHvTod6JiehpLdoaSRtsRGwrtk/IY2wCd5OwrtYvNhsRtMjJQD RRAY9qTP9DVpglQ9bFvc0eUrhLhgjbx8+Z5aoL1c=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.794
X-Spam-Level:
X-Spam-Status: No, score=-2.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=hpe.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gETrdPupjTUx; Tue, 4 Aug 2026 11:37:56 -0700 (PDT)
Received: from mx0a-002e3701.pphosted.com (mx0a-002e3701.pphosted.com [148.163.147.86]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8A10D1239A028; Tue, 4 Aug 2026 11:37:54 -0700 (PDT)
Received: from pps.filterd (m0148663.ppops.net [127.0.0.1]) by mx0a-002e3701.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 674G7odP1528944; Tue, 4 Aug 2026 18:37:54 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=pps0720; bh=5/O5T2fIgVx4qQqOcWpd9HtFLf STbAzA1ato8A6lNPI=; b=jyX1h6BNyQ7fBaSR7UOgZXR6pwfhADFSY91xMmOs10 V3oRNSNHEtAGh6O84NsS+a2rOvcde4cmP5AzR5IBubRNvtD9+Y5SxfwXTh40eD8z JCjr/am1ek8OM5FUMoAfIG6o7stksclam71/TKcvsyWLezl5cSC6AtZ6hBfJSI5w XDcGakWBwaUidXwkmzdEApI1exGncebiK0wf/nRLF4wu6wNOEvIh3y2phTvDCQXb osL3MvtnOziPRmZmpSCW1wr8L1JA8/tUIQaDqjxIMLT220RbVSyxMgxdn46VILU5 g0QcT3Tdybr6AZKgvfVmQVigi7TvEg+w3zVf12sBI9Xg==
Received: from p1lg14880.it.hpe.com (p1lg14880.it.hpe.com [16.230.97.201]) by mx0a-002e3701.pphosted.com (PPS) with ESMTPS id 4fukb4u5vb-1 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 04 Aug 2026 18:37:53 +0000 (GMT)
Received: from p1wg14924.americas.hpqcorp.net (unknown [10.119.18.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by p1lg14880.it.hpe.com (Postfix) with ESMTPS id A694180019C; Tue, 4 Aug 2026 18:37:52 +0000 (UTC)
Received: from p1wg14923.americas.hpqcorp.net (10.119.18.111) by p1wg14924.americas.hpqcorp.net (10.119.18.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Tue, 4 Aug 2026 06:37:28 -1200
Received: from P1WG14918.americas.hpqcorp.net (16.230.19.121) by p1wg14923.americas.hpqcorp.net (10.119.18.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43 via Frontend Transport; Tue, 4 Aug 2026 06:37:28 -1200
Received: from SN1PR07CU001.outbound.protection.outlook.com (192.58.206.35) by edge.it.hpe.com (16.230.19.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Tue, 4 Aug 2026 18:37:28 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=s0uVMyKU93h6gGSvcBd5uS6FqJbckL6D4PZ/VN1jsuIvsPt6LpOtdD78/DdlFWj05QdRm8VTSlgkpwpsPRdi5ID45WSaevWdYZjXzEu48MK7+0UdLDSDNa5r9xrHaDaf/xx+SheA6CpYBzF3S12FqduZsV78VJ8CJJGHpT8DJo7n83vn1vbkSkYQs/t6ivkE5+AqfKrB2MmHSbDrZ1PCc0OWxQoOcpQcfHwQK1bm0gXKeNtkBShM8vAyYOwivduPp+vQA2ck5DjGGwb0TLRmdTY5rnbS6+alMqv3QGAUrO1LgDIdRdMZQpNACTOiyLWHrym+y1WRyHAR4FBNNgyELQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5/O5T2fIgVx4qQqOcWpd9HtFLfSTbAzA1ato8A6lNPI=; b=AOy2A5H8OKQ4E7mmWQRHixQOxG8J+VcYACamsrRpPD5QJdRZoCKe10hxaysepe5kzp1iHf/BcKoMpLB6Adodmtbml7NRQQuublei2xGUbmK+sRWZ8rU87+g1VCQIFe5ap4GHJXgz5Xz9QcKeDw6IxpKJfqOmUKILOCGVev5xHsIrfWIrO3c0AV3YqLvwO2BZCXM8i+4SYSl/DlOJOKSICniVrK2iJbIkrls9u03rtmyxlIi1JeEdaR3///ocolYMwcSmGhCe/hViQp5bxEA6n25eQTliAXGVDLU0w8MZ0Xf2XFbXjjBbLA7XGXkBea4ZiWW/OA02in0SOoMlqhka8A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none
Received: from DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:8:51::18) by DM3PR84MB3715.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:0:44::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.292.15; Tue, 4 Aug 2026 18:37:26 +0000
Received: from DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM ([fe80::f9b2:4189:25fa:bd66]) by DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM ([fe80::f9b2:4189:25fa:bd66%6]) with mapi id 15.21.0270.017; Tue, 4 Aug 2026 18:37:25 +0000
From: "Bonica, Ron" <ronald.bonica@hpe.com>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>, Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org>
Thread-Topic: [tcpm] Re: TCP Option Length Bit Shifting
Thread-Index: AQHdIsGsOBGAFmZU10qMY/+nfOaLGraMfdUAgAEhpgCAAB/BgIAAdJJB
Date: Tue, 04 Aug 2026 18:37:25 +0000
Message-ID: <DM4PR84MB23100E65D202E0DC2B7CB19EF4D42@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM>
References: <178247435258.1809941.9081592875087275710@dt-datatracker-f9b87776f-8pmmg> <DM4PR84MB231000F604E508DE0EAEF63FF4EB2@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <3c6ef75b-0594-46b4-b748-478b48013a54@gmx.at> <DM4PR84MB2310CADFC4C807797E59CE54F4D62@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <ea2925c3-ce08-4112-8628-d0859a83ee07@gmx.at> <27D880C5-609C-4DAB-A0F5-974F2175FB5F@lurchi.franken.de> <1b5663e6-08b5-4797-abeb-4bebccdf5204@gmx.at> <BCC6E037-2680-4F33-90E6-21E2C168BDA2@lurchi.franken.de>
In-Reply-To: <BCC6E037-2680-4F33-90E6-21E2C168BDA2@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DM4PR84MB2310:EE_|DM3PR84MB3715:EE_
x-ms-office365-filtering-correlation-id: 6eb06407-ec3a-4f8e-014f-08def2576e36
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|4022899009|23010399003|376014|1800799024|366016|13003099007|38070700021|10067099003|8096899003|4143699003|56012099006|4133799003|3023799007|18002099003|22082099003|6133799003;
x-microsoft-antispam-message-info: xO3BmfvZQAW085BuZm9jg9VJfJBUmK4rdkyJ7KD+SVSANBmjMANZEYWC/xaMQyTeveC6YEGJlYPWpDSb67MG5pRwSFbdD/dhtcFh+bnkIsdJcCk6L4wOxmMSZWg2pfZ0DqrbBVUBxxk3+KSTQD8EW6R/H9o5ouHCNLufAL7hnj2WLC/YDdQlIeGghBFgDwQepIGaNb2gALOImIpVKW/CxyFu/gwys7aNPqhz7PwWJpHdIK/KvYEV7OcXTbL6Q70wKh+9L2/yQOFLqcxjygPc5f8zNVoXChaf8JlLaZgp+fqv5g7dZRQa9sIKIOvcvnChivRzRLGxXFuwFnixk3EcHz2SFCQhlLTI8l8mOHNxYx4rYy/IoEeEuGAfevg0im2G4nj0g3Lb4UFCXtrIPFpZW2Uxk+Casv1dJVrBTACGSLNpXzKaqoqSj2feDuoHToiHYnX5aRn6OuKDIl4hCj6XLdBKvc7gNJQK1CbV7U+CwW6J8AJUbtr9ZJFPH3z0b67NtVv/AoPgbXOWRKmKgzBY/4mpHsDJE7vkRtR7QZRmjNCrxX0A3t6m0ZGzzGA6HMmQimSt4eHDiAzeOYqhvHuytsJ5HsgZ5cK9A2vr0GH7t5AqEn0vaNN6nCA4fUZxE/x1rrNe+NVFcx3z19GZ7Orp6Y+CZHfowDJL/1fZ0ylWiH1ZZUcP+fL+xqDIDATiKEv8Yu187NN9e9kddcHnV+yskGO122Y6KWZRZDIG7mQS8oY=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(4022899009)(23010399003)(376014)(1800799024)(366016)(13003099007)(38070700021)(10067099003)(8096899003)(4143699003)(56012099006)(4133799003)(3023799007)(18002099003)(22082099003)(6133799003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: ewh/uKDKfc+7HG0Cw74UPJG91YGieMrpN2/xBMxZDYzyLpQXtW0EB9e3gcquYpgjukMrzNzhaA718LriCCuEihWW6TUbGYHmrJs2nZKCEvr3QpAuYRVMu3I1pTbKu6M7m24uSDWDLjR7Bec/42yVXhArIJev1NCsU4aC8BoHN//cXJMohztWT13no6BeOQqVCt8EvaVAgCLZs8EXmteXc20EOAUA72RB4LfLSPL9qnAvQB1CrsDMRkDU9TtkhiLpFm81/qL9dau9fiORELMZoRo5D4b0fyCGMY5n8QFHsv037sOAmEQhPpbvbBtcHpWBenNmuwDk8vyG6uKs9sE0v4TRy8rhYu8QSTG3cPZEi8E6oX/QG3jpXx0eumPauZY8+3XUJvkQxOf3RsawXae7wiXY+A8feblapImCA2CuppRgaA0suaEpsq4TXfy3Ie6HcKCw2oj7c17Ujno33zuz3/BgnLglc4RcZOKPX32GpTNbQ9DIMiTZ/VXwT1fPW+DdH0h89515BwQ6kkpSDqpGEetxPl+/3r5abGy2jeP+ikAEZam2a96y5WVKYsWDM3FPaNTgVcJBwQAMDYICY6SZoK+rWwmivztJKKhWGbSIcWLMp4KGqH4WKYgzTjM2MtR+I2usAXRn873CvnaIdTZbEN2bl0ObpNFU/8COio0kezl5D0nd+r91vSWQPedI4UujZ2eIUKfTl+Jb6yUHNr+Z0Sfzbp0I9i+cDbUjt4L5FFoxeY7/7zxzr3b/JATy3lm9ug9hAYVrs982JbIbvLKkzaC2drnrEH0IoI5Zu2ZbzOi/NrpJFMt5diXyyxtGagiFbprT1bLHFIjmLuPKHOt/Al5CkHEoRPkbbuH3zWoyUpk7K7RI1FlYi13dVIDHj2JwTdLZUMWerfZH7nfpIINFLka48uipUKvhih2l5acVxB9McliaMkN26rLwgWlBhU6BUzUOYdM6D0Y5KBJYwdIweqxoXYJWygrXzHaEa2AkcS0d8/vRvEBV6cv90/VogtCM9FEJeX0D0GFz+5WyIgATzeciX1/5Mfll+IipPkxF3aD1B8PZMYg4COP+CqKkAPxvysYFnK4UHy/uVLDISFz1HdITghMuqt0uCUXJaYHeuEzu47Wag0YSG/NQIEl8QLAz3CfyLFAxbDYAhvStD0wZuzHF/AnsQxTxkr7SXOYBjB3wUTft+DDfnPIuwDSgbJJ3E52UT+MI705g97QoJvszEVCZs2NFkhPgbLP5nqdMW49ycDxcwZq58VDv272xgQiDbvOIdfk4ThjGtfI2hd5+sV/nZHwyGyO9B1wBxel7a2slHdozy4xPsF2a4wYAs4N2pYMkazQBi5OyLGaPUWN/U0/c51jYXflzmzl0TZUvyO45smHK16+h/CY4yMtpn4r5C1tL8e9tPBbj2BH99KGk7C+5lipQs0iTXJRZepawHaXEJYj7j1moFfr5Wr10QOChdw8+DLWMA4l6lCPNxO1DI/i4ZHsAZEFvzsjtoKL5Ai5E4njs5TmwXSm5gnmkRIRSRqAh2QSjnikhXu3oW5hMcHNBGv7HPfBPCFMY+lk19cnLfqYK/epM16WdKtz4FRR6dOpW1nEPF/lV5qdw+8X6TBAj71HRQxTUM8F4ZflTUmSSX7SdxV7LzgIhatKZtCK0paiMcQ1Kgrj1DR/1azgLZMF6gIVevRY/kKQ/KW3BfPTNe3z61bxbTDmS5VGtCRJN
Content-Type: multipart/alternative; boundary="_000_DM4PR84MB23100E65D202E0DC2B7CB19EF4D42DM4PR84MB2310NAMP_"
MIME-Version: 1.0
X-Exchange-RoutingPolicyChecked: XUZHfEPcjhWjh+AlhJ3p3bshKUDWtjxs45QebRBEJKESTxjCfG1CnK2Em3y0BlhD0kKQABHXqyK18MGILTGswtCMZz/JRC6i08WXhDBzxFj1hHj2JfNw/qNXuMcbeTpT4oDABp554IIC127/FjmdXC3JGai3tL6kTV7qmdz1zl+Dq2Ydsjl9oCrZSFSqtdErAAcUDontl1LwkBGsiJ5FleLwDPcIsgd9M203321fyvHkn8yonGLFot0kh1Va4mDgj5ClanrKlOD7Vk4dyeYa+BUatH4Tn+1jZ1XvpEistyGIRCnXxxo5/8j+RRxLgTyUHj/opAUEQup7PIVTpcfejg==
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 6eb06407-ec3a-4f8e-014f-08def2576e36
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2026 18:37:25.8217 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SDY1ZNeN8Zgff8UM8jOwYJ36UFECuCOCvU8FQnIRXsSkrFrDEZBPQWtvNpECeDy7dxfed5VZgNFGBX7XzzJRBQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM3PR84MB3715
X-OriginatorOrg: hpe.com
X-Proofpoint-Spam-Info: AW1haW4tMjYwODA0MDE1MCBTYWx0ZWRfX80CdLKYnmah3 p5Juk8aNNvehpa4LgtxOyT1X1JbG+4kGb14FUbpqW5cZtwg44x50OCUDNeoXhri4/mygQWDN687 xx/tg4UW5zpYfxfDHsrwSucwUHu7k8A=
X-Proofpoint-ORIG-GUID: 0W-26JdBA6U2dftTGsDFHsv1fsc7gfHM
X-Proofpoint-GUID: 0W-26JdBA6U2dftTGsDFHsv1fsc7gfHM
X-Authority-Analysis: v=2.4 cv=Y/zIdBeN c=1 sm=1 tr=0 ts=6a723181 cx=c_pps a=A+SOMQ4XYIH4HgQ50p3F5Q==:117 a=A+SOMQ4XYIH4HgQ50p3F5Q==:17 a=z/mQ4Ysz8XfWz/Q5cLBRGdckG28=:19 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=Sv0fKeRqtYgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=gQcMVamqm3wCPoSYhaRC:22 a=6_mrDcixewTG61oOsKN3:22 a=48vgC7mUAAAA:8 a=MvuuwTCpAAAA:8 a=r4Jc01jffy3l8mamJRwA:9 a=pILNOxqGKmIA:10 a=P6Zaj40_Cc_uYSuHwxEA:9 a=04bJ_JvlMDK4bbaV:21 a=frz4AuCg-hUA:10 a=_W_S_7VecoQA:10
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwODA0MDE1MCBTYWx0ZWRfX6wAm9oQxhOQb b4152kc5CQ3uXva1n/wx1a2Vepno210tfEdPvipXwuftXs9cnXOkHYwv9co+qqiWU06SZvD+Sh9 A/EI10nk1hq5nME4JFQsTPJp7BakuRmraBxm/uHZGDSBoWm0CI+05gHunr6HrwuIhWRTtFZvrwt J8HEmfssKjETg/nysAG1KQabuLSgH6T0O99YQ7Mmm3dMdxhwJ5GK/5BpObbA/+d1QPN5FKw/fYU 3r+pR/tU0oxez632IrbXUXNT/FsAH48ftw9UgP4+f6pNI9LyWxmRHR6zxEAFZNK3LbuvkVt4wLc r9W3yGIhXFQqjumOkqRDneCMo/J+YxM151yRdsngSW9lqlDz7Cm0yly5iB23Fdrx7Mh2CrxvUuE MVHnPJzg3AoxqVzvS4dstWSDOPpQKurwK4boYSfwFWa65BXJwjdj4uhSLiKuy24ndkM1i61jpGX 7tOGWN44vcmeAGr2SCA==
X-HPE-SCL: -1
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1176,Hydra:6.1.134,FMLib:17.12.100.49 definitions=2026-08-04_03,2026-08-04_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 lowpriorityscore=0 phishscore=0 adultscore=0 clxscore=1015 priorityscore=1501 bulkscore=0 impostorscore=0 spamscore=0 malwarescore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2606150000 definitions=main-2608040150
Message-ID-Hash: VRBDSPZAVX4KRVX22NMHR5LMZB6EH73I
X-Message-ID-Hash: VRBDSPZAVX4KRVX22NMHR5LMZB6EH73I
X-MailFrom: ronald.bonica@hpe.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "tcpm@ietf.org" <tcpm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tcpm] Re: TCP Option Length Bit Shifting
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/J-SYguTqxJEP6hiEvSReXL35oho>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>
Folks,
What problem are we trying to solve with the magic number / pseudo-option. I am not sure that I follow the motivation.
Ron
________________________________
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
Sent: Tuesday, August 4, 2026 7:14 AM
To: Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org>
Cc: tcpm@ietf.org <tcpm@ietf.org>
Subject: [tcpm] Re: TCP Option Length Bit Shifting
> On 4. Aug 2026, at 11:20, Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org> wrote:
>
>
> My thought process was to have not "just" the TCP Data Offset == 0 being the only indicator of the longer TCP options (LAO)...
Can you say which nodes you want to help? Nodes which implement LAO? Nodes which don't and don't look at the Data Offset? How do you expect these nodes process TCP options at all for a segement
with data offset 0?
>
>
> With a magic number, or maybe even specified as a new TCP option code actually, followed by a length field of up to 252 for 32-bit alignment, a TCP receiver which ignores the Data Offset but does parse the TCP options could deal with a subset of these long options.
I don't follow here.
The option length can be up to 255. How do you get to 252?
>
> This is subtly different from how EDO is defined, but I suspect will be more compatible, as there are more points where sanity checks have an option to discard the packet before delivering a corrupted tcp data stream as header options may leak in...
>
> To summarize:
>
> (long authentication option) has
>
> Data Offset == 0
>
> and a pseudo-option
>
> +-------+---------------+---------+------+
> | TBD | Len <= 252 | Full Length |
> +-------+---------------+---------+------+
>
> (Len == 0 if Full Length > 252).
I could see the possibility of a new option-kind, followed by an option-len, which is limited
by 255, followed by a number of bytes which is smaller than 253.
If some receiver parses the options it will (hopefully) figure out that the option
is longer than the available data and drop the segment.
However, this assumes that the receiver decides that there are some options even
if data offset is not larger than 5. How would this work?
I could imaging bugs where incoming TCP segments with a data offset of less than or
equal to 5 are handled as TCP segments without options. In this case whatever you
do would not work.
But for the use case we have in mind, the client would send a SYN with extended
option space using TCP AO. Assume server which does not support LAO and incorrectly
accepts the TCP segment. It would look like a SYN with data. It might reply with a
SYN ACK, but without providing TCP AO. So it would be dropped.
Best regards
Michael
>
>
> More changes that a packet that can not be decoded properly, gets discarded rather than corrupting delivered data...
>
> (If this spec uses a full 32 bit block, better make good use of all the available bits).
>
>
> And one comment - the problematic TCP receiver is in a hardware-centric implementation with an incorrect TCP header parser; I too consider that a bug and misbehavior - and we shouldn't stifle developments because of such things but have to be aware (in a security considerations / deployment considerations section) that those problems may exist and operators should be aware to use LAO only over paths where the behavior of all devices in between is benign.
>
> Best regards,
>
> Richard
>
>
> Am 03.08.2026 um 18:03 schrieb Michael Tuexen:
>>> On 2. Aug 2026, at 22:58, Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org> wrote:
>>>
>>>
>>> You are also reserving a full 4-octet block, with 3 octets reserved...
>>> 0 1 2 3
>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | Length | Reserved |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | :
>>> : Individual Options :
>>> : :
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> Figure 2: SEG-U TCP Options
>>>
>>>
>>> I was thinking more like a scheme like
>>>
>>> 0 1 2 3
>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | Magic | Reserved | non-shifted length |
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>> | :
>>> : Individual Options :
>>> : :
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> Figure 2: SEG-U TCP Options
>>>
>>>
>>> The theoretical maximum size of an IP packet is 64kB (RFC2675 can be considered historic, as there is no support any more for that), and 16 bits would allow that full size to be used. And indeed, alignment may lead to the least significant bits to be zero.
>> I guess we want to require 32-bit alignment. This means a receiver has to check that
>> the lowest 2 bits are zero and drop the packet otherwise. I prefer encodings, which
>> don't allow things to be encoded wrong.
>>
>> What is your intention with the magic number? Do you want that a receiver not checking
>> the Data Offset does find some options there? Like 0 indicating End of Option List Option?
>> Why have a reserved field? In case you need in the future some other encoding, we have
>> Data Offset 1, 2, 3, and 4, which are all invalid...
>>
>> What do we want to do:
>> 1. Encode a length, which is always a multiple of four.
>> 2. Use for the encoding a length, which is a multiple of 4 and which is as short as possible.
>> So it is 4.
>>
>> What else do we want?
>>
>> Best regards
>> Michael
>>> I think the leading octet should be a magic number (two, if we consider reserved as must-be-filled-with-zero / End-of-Option-List TCP option number) to further reduce the chance of a packet getting misinterpreted even though that change is low.
>>> Sorry I didn't include this clearly.
>>>
>>>
>>>
>>> Am 02.08.2026 um 22:46 schrieb Bonica, Ron:
>>>> Richard,
>>>>
>>>> Thanks for your comments on the draft. Because your final point is likely to generate some debate, I have created a new thread to address it.
>>>>
>>>> In version 04 of the draft, the TCP Options field contains an 8-bit length attribute. The length attribute represents the length of TCP Options, including the Length and Reserved fields. It is measured in 4-octet units.
>>>>
>>>> You suggest that the length should be measured in single octet units instead of 4-octet units. The following is a very superficial analysis.
>>>>
>>>> • If we use 4-octet units, the TCP header can accommodate 1KB of options. However, if we use single octet units, the TCP header can accommodate 252 bytes of options.
>>>>
>>>> • If we use 4-octet units, the TCP Data field is guaranteed to be 32-bit aligned. If we use 4-octet units, the TCP Data field is not guaranteed to be 32-bit aligned.
>>>>
>>>> I think that 252 bytes of TCP options is enough. So, maximum option length does not motivate 4-unit measurement
>>>>
>>>> I don't know how much we value 32-bit alignment of the Data field. Maybe the WG can provide guidance?
>>>>
>>>> Ron
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org>
>>>> Sent: Thursday, July 23, 2026 9:17 AM
>>>> To: tcpm@ietf.org <tcpm@ietf.org>
>>>> Subject: [tcpm] Re: Fw: New Version Notification for draft-bonica-tcpm-extended-options-04.txt
>>>>
>>>>
>>>> After the discussions in todays meetings, I propose the following:
>>>> a) rename the draft to something with a higher hamming distance in the TLA to EDO (extended data offset). For example Long Authentication Offset (LAO). This will help to reduce confusion when discussing these two different approaches.
>>>> b) since this approach has a very clearly described applicability (BGP/TCP authentication), clearly descibing that and NOT claim general applicability for any TCP application can also help focus the work. This also would allow avoiding intricate discussion around middlebox behavor, when the expected use case is dominated by back-to-back connectivity (TTL 1 or 2).
>>>>
>>>> From a protocol design perspective, with the 32bit field (1 octet for option-length>>2, 3 reserved).. Is the bit-shifting really needed? Also, a byte in the option value of 0 is "EOL" (end-of-list), putting that in the first octet may have some merit.
>>>> E.g.
>>>> +------------------+--------------+-----------------+-----------------+
>>>> | must be zero | Reserved | 16 bit length without shift|
>>>>
>>>>
>>>> Am 26.06.2026 um 13:50 schrieb Bonica, Ron:
>>>>
>>>> Please review and comment
>>>>
>>>>
>>>> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
>>>> Sent: Friday, June 26, 2026 7:45 AM
>>>> To: Bonica, Ron <ronald.bonica@hpe.com>; Bonica, Ron <ronald.bonica@hpe.com>; Tony Li <tony.li@tony.li>
>>>> Subject: New Version Notification for draft-bonica-tcpm-extended-options-04.txt
>>>>
>>>> A new version of Internet-Draft draft-bonica-tcpm-extended-options-04.txt has
>>>> been successfully submitted by Ron Bonica and posted to the
>>>> IETF repository.
>>>>
>>>> Name: draft-bonica-tcpm-extended-options
>>>> Revision: 04
>>>> Title: TCP Extended Options
>>>> Date: 2026-06-26
>>>> Group: Individual Submission
>>>> Pages: 13
>>>> URL: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bonica-tcpm-extended-options-04.txt__;!!NpxR!nkeptgtvaaYOCsHEmJvkkOMDfl0_zjG2uD8TyCw1ceG6L6x8vyAu-Cr4RAPM9iJMetMjjdU4BUHWcydpQM2esCphWAXjqzueaV4$
>>>> Status: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-bonica-tcpm-extended-options/__;!!NpxR!nkeptgtvaaYOCsHEmJvkkOMDfl0_zjG2uD8TyCw1ceG6L6x8vyAu-Cr4RAPM9iJMetMjjdU4BUHWcydpQM2esCphWAXjsWeW2Bs$
>>>> HTML: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bonica-tcpm-extended-options-04.html__;!!NpxR!nkeptgtvaaYOCsHEmJvkkOMDfl0_zjG2uD8TyCw1ceG6L6x8vyAu-Cr4RAPM9iJMetMjjdU4BUHWcydpQM2esCphWAXjNihm-vA$
>>>> HTMLized: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-bonica-tcpm-extended-options__;!!NpxR!nkeptgtvaaYOCsHEmJvkkOMDfl0_zjG2uD8TyCw1ceG6L6x8vyAu-Cr4RAPM9iJMetMjjdU4BUHWcydpQM2esCphWAXj9fdQK6o$
>>>> Diff: https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-bonica-tcpm-extended-options-04__;!!NpxR!nkeptgtvaaYOCsHEmJvkkOMDfl0_zjG2uD8TyCw1ceG6L6x8vyAu-Cr4RAPM9iJMetMjjdU4BUHWcydpQM2esCphWAXj93loaQE$
>>>>
>>>> Abstract:
>>>>
>>>> A TCP header accommodates only 40 octets of TCP options. In the
>>>> future, applications may require more than 40 octets of TCP options.
>>>> For example, an application may require a TCP Authentication Option
>>>> (TCP-AO) with a 384-bit MAC. This option requires 52 octets of
>>>> option space.
>>>>
>>>> This document defines a TCP extension that accommodates up to 1,016
>>>> octets of TCP options while maintaining backward compatibility with
>>>> legacy implementations.
>>>>
>>>>
>>>>
>>>> The IETF Secretariat
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> tcpm mailing list -- tcpm@ietf.org
>>>> To unsubscribe send an email to tcpm-leave@ietf.org
>>>>
>>> _______________________________________________
>>> tcpm mailing list -- tcpm@ietf.org
>>> To unsubscribe send an email to tcpm-leave@ietf.org
>>
>> _______________________________________________
>> tcpm mailing list -- tcpm@ietf.org
>> To unsubscribe send an email to tcpm-leave@ietf.org
>
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org
_______________________________________________
tcpm mailing list -- tcpm@ietf.org
To unsubscribe send an email to tcpm-leave@ietf.org
- [tcpm] Fw: New Version Notification for draft-bon… Bonica, Ron
- [tcpm] Re: Fw: New Version Notification for draft… C. M. Heard
- [tcpm] Re: Fw: New Version Notification for draft… Joseph Touch
- [tcpm] Re: Fw: New Version Notification for draft… Richard Scheffenegger
- [tcpm] Re: Fw: New Version Notification for draft… Tony Li
- [tcpm] Re: Fw: New Version Notification for draft… C. M. Heard
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… C. M. Heard
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… C. M. Heard
- [tcpm] Re: New Version Notification for draft-bon… Joseph Touch
- [tcpm] Re: New Version Notification for draft-bon… Joseph Touch
- [tcpm] Re: New Version Notification for draft-bon… Michael Tuexen
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… Michael Tuexen
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… Bonica, Ron
- [tcpm] Re: New Version Notification for draft-bon… C. M. Heard
- [tcpm] Re: New Version Notification for draft-bon… Michael Tuexen
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… Bonica, Ron
- [tcpm] Re: New Version Notification for draft-bon… Joe Touch
- [tcpm] Re: New Version Notification for draft-bon… Bonica, Ron
- [tcpm] TCP Option Length Bit Shifting (was: New V… Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting Richard Scheffenegger
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting Richard Scheffenegger
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting Richard Scheffenegger
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting C. M. Heard
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting C. M. Heard
- [tcpm] Re: TCP Option Length Bit Shifting Michael Tuexen
- [tcpm] Re: TCP Option Length Bit Shifting Bonica, Ron
- [tcpm] Re: TCP Option Length Bit Shifting C. M. Heard
- [tcpm] Re: TCP Option Length Bit Shifting Richard Scheffenegger
- [tcpm] Re: TCP Option Length Bit Shifting (was: N… Michael Tuexen