[tcpm] Re: TCP Option Length Bit Shifting
Richard Scheffenegger <rs.ietf@gmx.at> Wed, 05 August 2026 11:11 UTC
Return-Path: <rs.ietf@gmx.at>
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 7302B12406CA5 for <tcpm@mail2.ietf.org>; Wed, 5 Aug 2026 04:11:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785928313; bh=avWbnftT0tiM0taVW9xfSUFyGnr3loRHzEQzy0znCk0=; h=Date:Subject:To:References:From:In-Reply-To; b=wigLfOTG74QTegFpVDItoXe3dHz3bdo7tS3m0yH5gJr1XOO4t12u8Y+g8cDk/eJu+ 83NLAikEHIIsvW5u/7kqd24tPYGzq6/yMJmEdezR2ioyFG7LEogwNvfH/8IUknALfL +swVgkG1RJT90Y4Ov1gfxndyqyLCR1flx9OZ8vnw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.at
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 jXPlSDL9SfJP for <tcpm@mail2.ietf.org>; Wed, 5 Aug 2026 04:11:52 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3965412406C95 for <tcpm@ietf.org>; Wed, 5 Aug 2026 04:11:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.at; s=s31663417; t=1785928305; x=1786533105; i=rs.ietf@gmx.at; bh=hHgkOyz0LmGxcAZDIPEOIWMbDY89T37EnUCa4xwWeJE=; h=X-UI-Sender-Class:Message-ID:Date:MIME-Version:Subject:To: References:From:In-Reply-To:Content-Type: Content-Transfer-Encoding:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=U9qT0ilcn88PQin/vC/zMIF4+qWC90As5ozx7mKK9nLnDzKE/P+rELYn3XeXUiOt smOFqeE0iLRawiUCFEhmkhRS55XQzooKj8n31gO3TtXzQiuPMgIwYeJ/ZV1cdbD78 SJ0XYXvDhzoOKKqSjJtA1L6qrSvJc81yYFwaTGQdv+fgOEm12n7nDnFrH5Z2hRSua bwM0ughUx3gZgXwGh6hHz/9NxQO+PGqfrUBkr6bmLTGMN4McM4sbbUqFtGf8oa7BW HrhB6xqR/mrOj4ZG+zLEIbaCfOhn1eyfoQiR7kfI5uKQ7tCFPcQV3qcPwpn8eDvox mSmhVPpyz2gMSWRwRQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from client.hidden.invalid by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MVeI8-1wSNfh0MbM-00OeYv for <tcpm@ietf.org>; Wed, 05 Aug 2026 13:11:45 +0200
Message-ID: <d7dd34cc-ca34-4026-8d2c-1f9b0f3dd6fe@gmx.at>
Date: Wed, 05 Aug 2026 13:11:44 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tcpm@ietf.org
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> <DM4PR84MB23100E65D202E0DC2B7CB19EF4D42@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <B892A9C9-0D44-4914-8D8C-39F18E820EA8@lurchi.franken.de> <DM4PR84MB2310FB277064BECB24C5AAB5F4D42@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <79D794C4-F51E-4C8F-A198-D81CEF662289@lurchi.franken.de>
From: Richard Scheffenegger <rs.ietf@gmx.at>
In-Reply-To: <79D794C4-F51E-4C8F-A198-D81CEF662289@lurchi.franken.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:HtHZVRLMTmyOCgTT7mG4C5tunV6CCh2Wp5HjtCBciCrYjq18jJv 0vyVFLS3XsaUlF9sYWxgj1Wg7d427TeR5nUZwo2Hw89Z+jmg3sXEDJmKOPG7bdchhlf62Je /vRkaSiUozHl8GDLtSJAq49+x2hvTR/LWZ2HSZ0pWgBzTQE5VYn5dgVfPL8y+agtcpLe/fF qxeAcqTXshhZHbnlCMfJg==
UI-OutboundReport: notjunk:1;M01:P0:YsH48yOs4vA=;N3YGi5H/M909SJWyVp1mSGcXXNT tg5JEgYjwlfr6cF1aMAkjKGgaxxbamX5TCERAc0v5EUl229StDYtd0up8MqU4USTunWUVVNZ6 7xLTsRd3LPg08sr6AvCuSwbqdbw/wAuKX78HC7UEq54PpMCvMWS6VhlzSihb9dRPXZMqtGmkc 2GT/PhB+KO4tA9UrDqtoYKXhUvXMdU2Ypf7zx7QzdT6x2ud+tZy8HnqZe6MS0DpaxLe4jXnE0 RL8U8wpyRRtRddbZQvOIzVT5jEMNrtZiik5IekHrzU8FJmK8iKB3pke3IxqBgHKxYN3fSqj1T todsd6hZAXCzWe4/2VT4CUJ1PZI8idklgVrZr8A2eiDzctRBdytlMDYm9rgwG+t4hG6nxrwyi fQZBHs5I8yo3uBrdBLXVmaNWSDIlHGhwOHKEZPvp8r58nareOxmNc/Dx8xA3kZjPNwOaVoOyv PtuHdBEyoQH2b5n0VedtD/KiearxkPSau7945lX7ydlG/8VJBZXmj/YbP3p0zGZ6LJoeKj6mw Apqp38+cg+4VnmG0dUNNw5HeRltGhS2zcwLgJt3AkTb1lJLU9NCSGgPy04K6na37QMghSVRy8 ZKTM4mdUe/vS/CbynaJKlGxpwBO34RfKQ06aWB8RscneTXLw/PQmplxfy+TnqSsz27u86fZ4a hepKT17j4Ctw/LbV4ll545/eaIKIAQP2Cz8FU8JEMRifcw7On7d1AEs6hg9xRzwNdY7vAuy2Y Nq9/xEWHTSZ0sqOmrI/JTNe/lpdvLhuoj6hHqqxKrySJrIx6sMMNm94QWcIopc9DyD+F729eA whj21kapeTYWZ0BgHBRlhp8dScxm2yiZ4PyhYSaY7hJhHs0H5/uDqsrYhExTpy+ie6Apsl5ki DnerGqmtbrcOBMahVhoHpEJaw/x7PmnHZTXCX0/wuJuaYlKVij4nj1nEYUEAwJT4zrBEs70Pc YvOan17b0tWnWw0jnKq4kgdk7xbFAKJbtF+8RLr2jtTKx1mzICd2lOV640cnrILj78tcszSYj q7iQFNH3DWQZLeOuh+IofQhZowMBTcQkGbc6oSrPt6aJNE9QPoMx6a1QOrpZdCPGkri6u0N52 Xe/llv6h4/O3rAdmWUP+ySb800AmFaWPBVGmA1A+Pm4CV1h80s89fLRekZo+G/WjHvzNxdgvS G9D9JqL0VF1RdwbGgqWMYfzgtET0TZ+qr3kSkIEUpNZvCQrAQoZU9KlnRzH0xXDMvqQpLCs1j cSlDZ5UWNMWj1Yw/fvgDkdN6x+YeQAlN7e9mjQ8OwYBhfQAV2Gn7m4+jUcruIKaG4Y6HKci3p 2dhPwJyA7uSpXpCZQV9lgjB54wvuL2xruL6kxQbTy6xXMC/2tHdobqpIdd1fa5eyuSFUFYaIt hbPZ182avWgxc1vrfTefWPUeWxesDoTYFxDba3HzYbWAVv+ahq7Wgnj9QIm4L/9+Iah51PCeQ C1G+tyPvp2TvX8Ygi+iLSQTblBF8ZGOfqexC+ls+mCHmT1TZU09SaGMJ5sovNyuEHTgphbeeX vOUZ2kVSwGVBZkpWAqR1aCFJWY4fw7A9Unax/pUzci2vjPf4t5c908sGF8DZ79KeUuOE4z3fN R6ZMgQ4EOIE1Q4ZJyTbb8tzFPchKF/WcRoxQgzNC/z2yf3Z/5X93BcAMtgKGZAGdCNWLaAJ93 geX4OJi9xNwMvOIimsdqw432OHg5CrJaDp06gwkk52nZ8sdeMq9cR5ZBJjrmk4+ztAIqNJiYV u9an77+Ysot0Lwwa14MD4Tmff85Vaio1u+YbCw70Ng4oZxh8zyOeEOSp49a5E+l6N5PTeW4fQ V+suDvOTVPiE3R86Z547i6xb6ZGbRPiIyu6hdzgL0cNABtbYFBtlxwqvpIdZtXvWUSvbfj5pq +yfrmgzDwH8B1PdD1Fk98uy1hC0PcTlfaFSTq69innztw06UqkL0JRCIAdOHiupW+SSBU/wGt oZu5q51fEDxefzcD+o0fymrtAJ5AJU/jsb7SDRWJdvWeiGpkmJNeFySsoSPWsdeFfqVMN/DSA MEvFCbZ7+UNfdYFwAHoRoeXc0s93kpLnxXu4Pm9tISrB/9dzkwh2FquVh8HtWsrmhexU2Owja VNr90rOr3qP/CMnDFKEr+aT42XgaqaEo0R+nakGGWnC4WNr7RP2oB34cKVbMdg27Ji8Ps1mKF SUmDxRoX/9czyA/gW+hhuKuUCxtiQ6DckaRlodW6QVRpIk8UiQvrDAMWseMCWtj6/VVL9+8fa 242Fh8ZQKwBwZonCbTKEAm8P4F/UWaUKjjRMNW5D1l6Nmz4fFJlqESL01I9VqtlvxKy+Lk0FN 5Jz1PXcxMAf47pW3/LOjqOksSHtpKjqVyAgKdJPORtOY1rE+ptiGnI0s21aaFyqqPBuXkYH6z aU0zBfvoyEXapHijP2yR23Tlp7K/90lmzBrZ24BRszusfFpzL7boB33GsZ2769Ur02WjVp7+3 1KDxcsRzPgqTFDes0cqea9RwCDu6nW9qY9g6FWXDzaVpPh/G2Dg0SG826+eVkLMTnCAb7k/zv 9VcZQUr+Yt0QJqtVc+WfxkyH4VMUIytBXvPYg7988YocnBBJwkQBVH96Cv5Cy8lmXGpsBF4+O FpJPSchZq4dooW4ndSucV44JDW8Bgtb8nYyHisbgqgBRYecye7QmmvnS8816BF3ROAVHMlc25 sPsDdA0eJvfTKceyB51L53EakE6753cZmcLK4gVrRXXncf6V+010zz55hxKVXinlJEGo1KcSo +ZHH5rFBLooLKx/SNIBIQO0PoqKOmApCkOowDJThDTKPIhwHx12X+IPmaGsyoT9rrQahuK6lv PVAIs6XaGOaxzM58SwahDbvAykB54dAJgNNKrtFfeBuUBfT64RcZTvXhYcENRO5ljoI43br/Y FvOmAZI4rYh/XLRdyD3J5hRpdzTqq4htDYZE5qlq7ACITu0HQSkCqTm+fp8z/pIbSmxdaosVn w4FDewog5W296BIIZk0sIqxCVW1J+2VwturScfFVo6980EbPbN/WhHo7XifOsVjrkVjAX+L1G XDz1sv5PRtyAugJdxLdv5AhU/1ab/RL1fjcNkvdZCsYM4pW4nH42tUQ+DSHYOpyDyQcPkqexy 97iqd6XP/SWqbKUnMk3OhG9Y0C4Fn7gXzZY5hOlNj9rMbmrNica2lG43GHW4h4TAaOtm0j7F0 woJEeKxxdUEGiSr5pxv6L5pwqiafHAKo9p+cLrUmH8cQUIp+/THvWymC1UxnwXXApipr+XQ/X wPZxm1b90xt1bTnttODN/KmZZqYPwa8FzRXn/f6wXqyJngdwJ7alSlfs1DgPD5g/ymu+/K53o bvINGsfTGJmpWNNNYpWjQiqNm1HlIMjM+O6wbysJcAF+CpISJ+BEixQzDBFN0X3Ev9YqReJ4q a0sETUP5H9CjLMElHGK7XhAzXUXcmBFCMYCF4sCitG1YjpWaoGWtPnU8+pmMTHK1AUWU7YpuJ HYhnrK9VRpYoVKIJ9c8IxG+pj5qUe+N09ccgIoC3p4LoZbU4O0dXC1AnCGsHQCixYzJFly/qJ hoLJW4efpij1Qe292Ksihqt+DIOnF9hAEIiEx1ux8f8xzvpJF7lpAMM1nYT+253+fKbmFkcdd 9qFLWs19L63Yez/6L8SVrjuG3gxRDv1zbfdeCwcp5lJyFIYlqhGv9BwDfHbXjPtjsWeNTFL1d AQD3dsaSNkaryO3ltgKh2qc5ludBxaxoZhXbtCKM244PKq6d5RS3Hm3VpMBDe0k4Eyt2s/cCv AeUu3H/ltLY32eU2FblUG9pNo3pRAxGKIXEsdo2bifBVq0PVEt02waqtz7Ihqb9lwreqaHikL BvRWd+hfV0FTgNWCJZCLb+93F/yE8jcL90Nckz3X55IIbopLQFeX3sH7EqotwzNQmoUtnkxLP aRvs88+8pzhm8LLFsMNmc2U5HiQUeT1/BjXsmPsqSpKAS1FtTqyHDMYv7HtNqiHgB91gC5pP7 m8f2+aXhl2X00v8KVKOsRx4/JudUdFX/27/l8i1tXvp6WbXxVyzxFgpO5Q0haH6+mdq7tgYdp 8La+8zGnbpVcfTlppVIoZyy3b67w37UZxgu2IrNnYlkDhzGk4bCNH6tqidHpdUZ3deAJFQmdu 52FF/pOWTHB6MLdl+vqk7QMr7YrdKpNzmKMZ4slQXUeO3in6I1Vpb3rXaTF4DN+3uGFKLtN2X /lDUjujYVFvTIpM0Z8odT2G48jt1vMjAWc3P3neZH8SQRL5/aKQT9RRuzo4S/zUIwZ9YR+U5n G02Wgss6FIP7naRYQVxf3nKWbj8m+rYA3I/7bnY7bwdO7N3aQkVP7llELDnlFvvfXditlnMG6 156HkWR6fdcWkdcke2FUv1oLAsqnc1Q2LGS62JY7fRyNJZRAstgE8rFuPCzDhJBA5yoPV97VS 6E1soxtPCt2WF1shxRViVZT1sm89bVocuhOe5fAEoiNQTnJzRJZ4aTCJDCuYvSOWP6jj0zSh7 irWnnG57TptY5tXcdIzqKH1TG7WumCqB5x1TVjjD/fujyHVtRpd9Zvztxsloq8FHQoPYlDBBI bMX4LR7g2b81IfeyC+zKH/ZkuSA8FPKP9YTHK/bJx/zu/iwALPFW7flo+I+p8sJ8HYeMg/+SV CU25/6WiHD2R5zsSqIiMiGA9M3346wyPnzJFWLLIBvC4xxcP1W7jJGnRtHOGm9hfp6zc72b4f WBJ3fLy1CCUbhHXWT8wa1N31H8x2YPXL1jcVA7vrjOOhg+jAzTyb8Kc8C9yKKIiiavLtyLP/W rfAb/4yu+ChV+jpFS/C/7Tq17hGa2Wa7v0ksDCpkR+HtGgntG68vNpc+Q9CNEtd6KUrcamBWR /6uD5z3Q3eH7gZbBuFaQtDO2R6SiS21sKGcTz+R4iGJrSOT8iu+JA6jI9bbg0pxg1QHIbw5x6 OwPSpdsyBOrWp4/czj1Jr0HbHwPKcr2gHXskJkmIB2E71Ru91Y1hpNpegpKT/SMXtD+FHDX0U GoGYfqMJULwYuZpiKGDUVbFCazcSYPRWO/QMRQRxYZh1gWvobX7FI4tX2QFoQ2jdNpZtzC9sc rFgB7L9WEnB2BEmwVVGu7SIWCKgpr7eSFVNXB/InA59SYgPgVmXrFUav2wljIVUa8zyFVezQ3 gib32WdBKIGPXiW+l2ddAv7DEgwhhSDzorxcNeigu+YROU2dqD/7ebYWRTI9t00P1bH52p6qd OIG4OksMmO1InNr0/fDNWyau33EljlL1iHcY+ovfe6QYXVsBzVt/gyUd2NlbztYF3n9oMvpPe sGO5kpw0O187kvw77+B4PNm/tIY5DtDc7EjXW+8C4sudOcb35+fl5CjkBPCbnKXtzbl8Zit6U 4e3FZyxpig2jaEWPikz06i7BN/XsASF/IxuMrKl6AHuKdW4RBNCGF0fdv55S0/D2byIDZ8KuU ZnwACDP8j/LahXLHaN0uELEcZzg7SCmXB3ZCZS37rjfHRDPDp4T/oS8DgMadLIqAdp/a6QrCc wT+GSfOEER7+oypmNcFy4Ec/1+cjEl29H4vZsL1RfnDjWwR68cVCe9bDr49C4uNpKyhtbTnlf WAfTpV2YqlJSjuh3Iu/zlZlIXh8IUc90XOjeEsF6EuwsjCHAS1aTWEr2xSb7ZW3y9dndRiuie dyHUhXBTU+HJYfWnBUiumw4uvH4vqjrSEXSkUmAWZ83MwHVRekbN+OZcBMGeXfFs9YSczXDYA Viq5HDRibwWgI62Mm2bSliPQhGqtq7e77cZzZkokL943WnK4wzDiJIgt1351gl1cJX8U2mJuo qcyb7Cfmeg/REsHvvb/x6VLbYgCpukLwqmz0uh+PGyTJTblpAhmad+L5/UmcO7CirWHMmKhX3 +2V/JXMl2LsnP01VKutMi7PDvqDXeInlqVkhNHSCIr8ZBpphfkNoreBEtXv2K9/tBNW+hW9En 0T+rH02ZVkOpEtQ3WKFk/xjLB2fXbFNI6S14op6e2txL/v5otMGAS/b02vw6nixe0FhbnEaQq dncgyIuuaDyEL2LQ==
Message-ID-Hash: CCECGXNSGWX2F3LO4EAMRSRXEVDFHA2R
X-Message-ID-Hash: CCECGXNSGWX2F3LO4EAMRSRXEVDFHA2R
X-MailFrom: rs.ietf@gmx.at
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
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/6hKzLYeVeCIY82WZQdsCsodpQXA>
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>
How confident are we, that the DO==0 will not be "normalized" on-path... (that is, filled out with 0x5..0xF by a helpful meddlebox). My intention was, if we are going to use up 32 bits right after the end of the standard TCP header anyway, to use those bits in a more effective way than just defining 8, and reserving 24 - to be filled with zero. Placing something there which appears like an oversized (>40 length) TCP option doesn't burn additional bits which were not going to be reserved anyway, but may improve the resilience of LAO. But I admit, maybe I have been seeing too many odd behaviors in the wild, to be biased towards a "belt-and-suspenders" approach when it comes to data integrity and backwards compatibility. Richard Am 04.08.2026 um 23:05 schrieb Michael Tuexen: >> On 4. Aug 2026, at 22:20, Bonica, Ron <ronald.bonica@hpe.com> wrote: >> >> Michael, >> >> Do we really want to protect buggy endpoints? Or do we want to protect compliant endpoints from buggy peers? > I guess this is a question for Richard, since he came up with the > idea. > > Best regards > Michael >> Ron >> >> From: Michael Tuexen <michael.tuexen@lurchi.franken.de> >> Sent: Tuesday, August 4, 2026 3:03 PM >> To: Bonica, Ron <ronald.bonica@hpe.com> >> Cc: Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org>; tcpm@ietf.org <tcpm@ietf.org> >> Subject: Re: [tcpm] TCP Option Length Bit Shifting >> > On 4. Aug 2026, at 20:37, Bonica, Ron <ronald.bonica@hpe.com> wrote: >>> Folks, >>> >>> What problem are we trying to solve with the magic number / pseudo-option. I am not sure that I follow the motivation. >> Neither me. >> >> I guess the goal is to protect end points which do process TCP segments >> with data offset equals 0, but do not support the extension you are >> proposing. I would consider them buggy endpoints... >> Before going down that road I would like to understand which kind >> of buggy endpoints would benefit. >> >> Best regards >> Michael >>> 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 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