[tcpm] Re: New Version Notification for draft-bonica-tcpm-extended-options-04.txt
"Bonica, Ron" <ronald.bonica@hpe.com> Sat, 08 August 2026 20:57 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 5E41E126426A6 for <tcpm@mail2.ietf.org>; Sat, 8 Aug 2026 13:57:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786222622; bh=+2vuu0dhx7qIaujHYh8nPT/IloK80beVAjvaXMooiCI=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=iWYwwyjWvkNf1ZNJm4IGvz9gQ+jELJVbXKR3cou/W4H95mvC5RtQmACH5dAHnkIWV 2tz+NZ5FLEZYYNtuxaqd8Su+t4YyYtst29QzHe69OiIrTWhApSEPxboEumNSO8PGrM j8Q0s2YHFS9Rtv3QnpPJzpkkjxS6M0aQIsJ0IZ4c=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.694
X-Spam-Level:
X-Spam-Status: No, score=-2.694 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, HTTPS_HTTP_MISMATCH=0.1, 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 FLDYdstOzxDH for <tcpm@mail2.ietf.org>; Sat, 8 Aug 2026 13:57:00 -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 3D07D1264269D for <tcpm@ietf.org>; Sat, 8 Aug 2026 13:56:58 -0700 (PDT)
Received: from pps.filterd (m0150241.ppops.net [127.0.0.1]) by mx0a-002e3701.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 678K12uV1564259; Sat, 8 Aug 2026 20:56:49 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=+2vuu0dhx7qIaujHYh8nPT/Ilo K80beVAjvaXMooiCI=; b=UStk7fTZBPzIxMslXUqvczTXyz88rsOrCoPQwcO5nc OCv1JAs2iuJ63EYbgmWqGVwBryhLkjmxpk/z7dd/M80LhN4jHxH0gvsNbwwqbTHZ PrDE70JWQsEq+D1FN1s2gcHF9o/SlJOpl4+w9Os5lO4w9DTJS1juTo9CeqMloyhv ItdGySK7XqXMQu28qeg0V1hMASYpe0W3vzFoXg+cfLfSbHucsSCn/l2a2W2dit44 oqZ56n6Bu+mGmwV5RSLH1ugl3P+pDHJzrXU3rAtz1pXqkLr9buT/cHczMTGgB7Gp lv1xqip0qCzwOP8c25izpCmkoa5yA7hojZppIyuW6b7g==
Received: from p1lg14879.it.hpe.com (p1lg14879.it.hpe.com [16.230.97.200]) by mx0a-002e3701.pphosted.com (PPS) with ESMTPS id 4fx7amth80-1 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sat, 08 Aug 2026 20:56:48 +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 p1lg14879.it.hpe.com (Postfix) with ESMTPS id 86E8312EA9; Sat, 8 Aug 2026 20:56:48 +0000 (UTC)
Received: from p1wg14928.americas.hpqcorp.net (10.119.18.116) 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; Sat, 8 Aug 2026 08:56:43 -1200
Received: from p1wg14928.americas.hpqcorp.net (10.119.18.116) by p1wg14928.americas.hpqcorp.net (10.119.18.116) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Sat, 8 Aug 2026 08:56:43 -1200
Received: from p1wg14921.americas.hpqcorp.net (16.230.19.124) by p1wg14928.americas.hpqcorp.net (10.119.18.116) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43 via Frontend Transport; Sat, 8 Aug 2026 08:56:36 -1200
Received: from DS2PR08CU001.outbound.protection.outlook.com (192.58.206.35) by edge.it.hpe.com (16.230.19.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Sat, 8 Aug 2026 08:56:36 -1200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=xXHpFvkn1ct/+upgbhiK0JZ/EcaPaJuPFOjxOPGoMhdASqlfAeBnnUPcQbhZWIxE8KDHpvwu8+YVnvc+Jj8q+EZeIthhTyP7Bq7YyM1qPaPAoKiqqO5ELYxxx7x0zrzgTIqqNX8P7W8P3IuYeJD1IWjGhBU10p0mOhAle0t3l8pxu7zxrlian9GjngOB9bDYJJbiUd/z2wEbOtddSOHVlwomBmJiHupO9cIqMLHrexll6HuYzUprlGYnaO3YAHI4/YQZSTJdZTb6XStkFxIk6qth+hFW8HWAL0o3s0CmCafrkCxa6m4eKef6aSj+FfN3odWpcsupyK9YJhNXjQ0tIw==
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=+2vuu0dhx7qIaujHYh8nPT/IloK80beVAjvaXMooiCI=; b=nDx0o99hi23fBDWJMVjZNvueg5VvGV6Yt1clNCWOlITxc3aptgkqjs+rELd0k+t9Mz5ptXHPXIlAIbZvtkERg5vbaBmxJ1h53LpiMmgwg/pN259Vpa0Fpyld8cS3sz624ah14eW33zGlbEcHHer5TmZCaxQ+Q+AezJNWnI4ivcXzpR0icndXpChHdQDTPQMVzwe2UOGIHlUdRb+AA+prml/OMhvnbKHZqbjwkx6ypzjciHH6265T0QVJrv7VQ9+txzI05e1q+LfxqhBXK+lWncaxdPORo+itLODLwY61kdFih6lAGnqI0+epoxwD+AgZX7jDRjU5drNcH18OzqhnkQ==
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 SJ0PR84MB3151.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:a03:485::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.292.25; Sat, 8 Aug 2026 20:56:33 +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.0292.018; Sat, 8 Aug 2026 20:56:33 +0000
From: "Bonica, Ron" <ronald.bonica@hpe.com>
To: Joe Touch <touch@beachpine.com>
Thread-Topic: [tcpm] New Version Notification for draft-bonica-tcpm-extended-options-04.txt
Thread-Index: AQHdIWt0Z7q32F/HD0mPe4zWvJqGebaLbdGAgAKDjr2AAALaAIAAVWIegAN7sACAAuif2Q==
Date: Sat, 08 Aug 2026 20:56:33 +0000
Message-ID: <DM4PR84MB231041D0C4980BC636FC42EAF4D02@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> <DM6PR09MB5958A0C4E2F68D2ED19631749FD72@DM6PR09MB5958.namprd09.prod.outlook.com> <CACL_3VH9T_mYREMF0JS6i_NqML-9K-TMCh-S57K2xzENDh+TXQ@mail.gmail.com> <FB9E95B7-CE73-4A63-9121-AF49D582F78B@beachpine.com> <CACL_3VGJvVsjk3yBcECdoXFHZuMomTxYg05Chfd4VdQgU9fdOA@mail.gmail.com> <DM4PR84MB23101847DF04DD43E9A5AD48F4D42@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <9DF27260-C9C1-461E-BA26-58EDB7936181@beachpine.com> <DM4PR84MB2310068CF32B5740FCD051CBF4D42@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <15EF7EE1-9A5D-477E-8E53-FA1D837ABA9F@beachpine.com>
In-Reply-To: <15EF7EE1-9A5D-477E-8E53-FA1D837ABA9F@beachpine.com>
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_|SJ0PR84MB3151:EE_
x-ms-office365-filtering-correlation-id: fc671524-16ee-4514-3402-08def58f8738
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|23010399003|376014|4022899009|1800799024|366016|13003099007|22082099003|18002099003|10067099003|56012099006|4143699003|8096899003|6133799003|3023799007|38070700021;
x-microsoft-antispam-message-info: jiw/x6ER1AjMt9Axn/JFpmzE7spXolE/kVKE0YRLUPUG7Jr+TmKFJCUw5fdjeRiGhjaFwuRY457VQQdWPWeRCiRv0hY09QdZvc7gwujIjZswMBeEve70DWXnGTs0u61eueuy0pq8RRySZvPQKuLovkwhcRAbuXArwOgnKa4l4frj3SSbnK9zUMq8VFlmZCG/r+gTSGD5NdtyMNdKJXQEOgLeTa0yDv0X9i7gDvU3uRcbezAmcJldUmquxFjZC5M3fDbwBuvrJlSkMwqL8DwvR+MpfW6XNBc2tRGv+RwKrB9HM6/sYn/x4vNZ5zUfR8Arf0VA2CP52NfqqvDpF2sG7lemwlQJDmSg44HZgenBPWFvRH8P/s+cehUFci6oyKavXPxe/mC/N2kxTDhaOcw0jNRAkrRM+YIrHvFhpXG6a17EqWILTjrqicPWIjlNMrLP3V8rYMvVgARLF6q2ATtlnDtqFRs3tfmYYLIRbEAV/Ed22fJujc9RbfMVAflXIG4ANPAgIK/BTmvMtJC1poTMTdChBZFAfWCnsj5dDamRi35xCTnrwPVlH5cJ+ldSIfS7SDg3TGx1bBPwbTkeVVuEavotmRDvcXmuNv8CiSzVw/gGXNpTyPdHg/IfuioPaoZah40kY+eOUwFaojxzmO4jXb7fpEp58deJlQ+6MX6Iqjb7y8VEL0bDfidsvD4Ec9qNr9t0u7raq/ia84DNlbcFyeMb/D18dGC463HFRl9V9hA=
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)(23010399003)(376014)(4022899009)(1800799024)(366016)(13003099007)(22082099003)(18002099003)(10067099003)(56012099006)(4143699003)(8096899003)(6133799003)(3023799007)(38070700021);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: wgk2xtP0Y5ZHhNEhnGbJunnFEOfxozNa/zc31rmzWgbpHNkKoeM+fmyN2Qab4b2kYHunjYXCtFa7cGdzxw5/Ic2m/0U6HtBeoKFzpnH0EWNsLsTDOpIFApgBTy4islWgmJZjfdl0BPTj3AIvsIfXNidu313SAgpBWra7eEKAbedn4uB8/rlGifZIu1p7wb5kck64L+9kIWzOgp+8rWwC4lG9+7kImpQ36Jee0Yng3cY9k4dOAIu2UnD8+Z0PcAulitpva8koPrApNMVlllm0Tot6YeIMMIupZtoHgZIElmKSS0vl7i7y13RJOyNWH5n4Jam5MV8femVldYy1oxYpMQXbCjaLeYzmf2OMy1KdqFKAMLYiuu/2wsVx/XhDQoAI/w5ZSTgDb36SxgjS1cuptTb5smxsnp8kkdl9OxEOU2SxKmeLayvTmyuHfuIHk1FwsFy0n8ocq8rJm+BGdwqHgWxYCH75XOdvYINjZZ82kfAZRMFoppNXSt7jpYWwrBvjvhsNVZtic8AuuwSr0oCgBKtTJ857DT37HvzG0XkR2/U8VuwHDQA1OEF7BpEAlm02a0JDLcGWfIcE5Vy7mTBYSjbHROHYFiiqPOs6DudiGPwyBlQA+8L+z6BjD0iomrN45mCOFbfnN1u3lOP67Ro2fBQypFrAz0/rxaVBSvKhiUM5kCb0q0XC/PSn9j/SueQY/DJq0brSPDkE9aIFV2pOoyL8fRB19Sm1OXPm8LYfSvrJ/8QshikOpI4V8TM7+cgoy5nfpJ7eXBbgc1EQ94Q1Y4S85S/AYP1vH353Xf+1B1NiSbsChnN0uPoSg+KxyUWK/SwNU0aWMFgNf8Ia9mRtowjpnbC/gxLKU1sJ16t6UHQ462E0K9Womh/ES7LHz1oyEFBZaxGTZIqXizIn/Lma9XID9G7JP0EpEinCC/DppVLmOKdmPC7tIrdB3PzRVExdLkC3XFstOrb0gwg0EWQ19yMUAjI8rHjy+OLFF/dAArTHjybzWk8QKTiNS13J/88pQCQ4Nl07e+D6TktU7Fg8BZumvBdeyIjyJlp/tKgHS+Qw2mHN8nIKNalWW5GrDtFzqfrei+mo1GMzd4qGoe+DOszvMjHobIrUtmlEEN0pGm0gA1vmFmqG8cQcel9Ve+PtLW1nUskfSFsSt9lrEQNPctFo36oXSUk0eO2RofPZp4gpheRZQM9iQIVcGzVObtkCDwsVAUVH1DFjof2AO3fJekWMjeUTZKey/L4023TJMH8rtY6TLDVqxUb0X2LO2DerWyERTxejyrjCm2EQhenQK9qmxSwB7TGUXK5iS4B9/9ArBiYMFpDprPnaLVDbURCqDXKDgwvEmHZFhqOSE5VHI+cJnCHnsjut5zd3kBp2Tt1mwn4tLSeoj1e8t2SOHxTVD/qgHAKEJryYRRrNhkbCczeewiGZ8jXSgIOf/3UjMTJM3G8BNK1mEVXo0sr2TJxesCcPmy17H5w50Ce8/JPMkVHE8x+1Z+MTK8IkahQCej3gShwJhqgyoZgHCoPKQctVNvn40bAKQ3yAJvblNYPLz3xH6+Kya7VhfQImf2IaHk15VY4gD+VctjW3Hasr+t3UmM3gMKEX2UCG/as95uIKL67tMJIIAzFJLBThlXh8ZK/+K6w4RP2I0ZH5f1rNddnQOcmVEHQhi0gl8K0xTjQ+361fPqVMTSzBJJ5T6nmymNYDqrRB9PB/rdSS446RhKVo
Content-Type: multipart/alternative; boundary="_000_DM4PR84MB231041D0C4980BC636FC42EAF4D02DM4PR84MB2310NAMP_"
MIME-Version: 1.0
X-Exchange-RoutingPolicyChecked: LQSYrnYGE/d+ja12NoxLkrpUbN5O5rEZ/sWE43LEA19KkbLSCwyg7NTfkkoiM/p+xNDnm98bcdHjUjcumMc5xpByJr4C+gP3h5+XyfFHSSTIzYUui/bTkcI1w8oHpRx3JIv/mTNMJVKqK8/N0HTyncW3QV4W0b3UGg4LBPCNEFUZoZ6gwKCGgneb9/CErqruQTR6mwOY/1GTulIBPJbbibkMq15Aks+5pbFlV/EkvalLBlvBQF9qUzZ8Y/yIk6Mx7RkFNaVCx1ge6pDI4mWO99uTpHp3WPZ2uFcDRYFAHMM7QknnF3WAdNqxlcFbhdU0wQzXiD7ouOzqi074jATgQg==
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: fc671524-16ee-4514-3402-08def58f8738
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2026 20:56:33.0910 (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: z6R/IGFV6WurzHXgxVSzCoIlT3vzPp7Q/dOEpRPY9gkIFoT+DltFZTCvd6IKvUNb8q7kyKcP/JImOtf3z2wluw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR84MB3151
X-OriginatorOrg: hpe.com
X-Authority-Analysis: v=2.4 cv=CrGPtH4D c=1 sm=1 tr=0 ts=6a779811 cx=c_pps a=5jkVtQsCUlC8zk5UhkBgHg==:117 a=5jkVtQsCUlC8zk5UhkBgHg==:17 a=z/mQ4Ysz8XfWz/Q5cLBRGdckG28=:19 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=Sv0fKeRqtYgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=gQcMVamqm3wCPoSYhaRC:22 a=_ZmgHqWwjZUDpi_pur5s:22 a=Kc-ASbTGAAAA:8 a=MvuuwTCpAAAA:8 a=ybZZDoGAAAAA:8 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=jJrOw3FHAAAA:8 a=ilg0rRk5AAAA:8 a=-3SVvLdjckQCFHLXyOMA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=yFPkOKj2xmDEZSghsngA:9 a=YfzWViKfLUIJF5U3:21 a=frz4AuCg-hUA:10 a=_W_S_7VecoQA:10 a=Xdwl-z73i2P83JJfqHXF:22 a=0RhZnL1DYvcuLYC8JZ5M:22 a=K9BYLGeYLFBMybfUDB75:22
X-Proofpoint-Spam-Info: AW1haW4tMjYwODA4MDE4MSBTYWx0ZWRfX0l9T+UY4CvEP B/pJQ+zueoQx6Bb0F3NKuESDw3aFnsAby3SJY+BjWpwrOO3o16b68/pFbUfYY3p/zG3Wazeo740 WmiQXxZud5YTL2Ozr3HCbL5wdz/haMc=
X-Proofpoint-GUID: Mh4mWD4QFlYJcMlY_19Z4JqxTUIqZJqm
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwODA4MDE4MSBTYWx0ZWRfX+hL79MbFCrZj DyEW4x8RNLp9BbcOT8LXqbAxZ8vw6+g93d8Qv9XX0JoScXD2GErm+CUqPM92TIw216DqfVHG3c4 c711+/wupkWgzwO+nq1aYMyXb1Cegaz1irBF2yk+fmnX+rmfQoj6FmTp0LbTaY2jZ2UzUwaPFSC 8X+/GAcT2yhx2k826yLGtuzpUe+c22MdkvjVQk9zGjKqbBmy+aA8sPNDC67V+WeqcRk74XoymQr L/vjDvpPNR9BBhBTvcl3u73mh4YEY338FGJXjOyxhRIggERn+rQ59lrJ/9SekVU3ZWEvRLfPqK1 dIdTAnvFPTL0i4UNPahQPLP8mN5KDGJtvWRoQd2bZwg+hOWLYUCioVgw1ZcFxzu5i8DF8vJhJMq zP8y9dgtmssEFdak9PDJyvHouqXYnBcPi2V2Vs4G+GZYCwtrIhLZPom1tQ/XyLds4Jt3nGSBe/P 6ybWuUv/7bLQm/SNh3Q==
X-Proofpoint-ORIG-GUID: Mh4mWD4QFlYJcMlY_19Z4JqxTUIqZJqm
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-08_07,2026-08-07_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 suspectscore=0 lowpriorityscore=0 bulkscore=0 impostorscore=0 spamscore=0 malwarescore=0 adultscore=0 priorityscore=1501 clxscore=1015 phishscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2606150000 definitions=main-2608080181
Message-ID-Hash: NOZBPVBMTWFPB7AAADXDEDKHGNDQGEZE
X-Message-ID-Hash: NOZBPVBMTWFPB7AAADXDEDKHGNDQGEZE
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 <tcpm@ietf.org>, Tony Li <tony1athome@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tcpm] Re: New Version Notification for draft-bonica-tcpm-extended-options-04.txt
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/sqP-B4Vb0yWkshEbzcX6ZaXIhAM>
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>
+1
________________________________
From: Joe Touch <touch@beachpine.com>
Sent: Thursday, August 6, 2026 8:31 PM
To: Bonica, Ron <ronald.bonica@hpe.com>
Cc: tcpm <tcpm@ietf.org>; Tony Li <tony1athome@gmail.com>
Subject: Re: [tcpm] New Version Notification for draft-bonica-tcpm-extended-options-04.txt
Any system susceptible to any “segment of death” is a system that should be known to be hazardous.
Anyone who runs such a system is a victim of the vendor, not the protocol.
Joe
On Aug 4, 2026, at 12:23 PM, Bonica, Ron <ronald.bonica=40hpe.com@dmarc.ietf.org> wrote:
The Segment-of-Death is a very effective DoS attack. It can keep a victim off the air for hours.
________________________________
From: Joe Touch <touch@beachpine.com<mailto:touch@beachpine.com>>
Sent: Tuesday, August 4, 2026 10:14 AM
To: Bonica, Ron <ronald.bonica@hpe.com<mailto:ronald.bonica@hpe.com>>
Cc: C. M. Heard <heard@pobox.com<mailto:heard@pobox.com>>; tcpm <tcpm@ietf.org<mailto:tcpm@ietf.org>>; Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>
Subject: Re: [tcpm] New Version Notification for draft-bonica-tcpm-extended-options-04.txt
It’s a bug - a bad one, but what’s the “security” vulnerability?
Just because something doesn’t work doesn’t make it a security issue.
Joe
On Aug 4, 2026, at 7:11 AM, Bonica, Ron <ronald.bonica=40hpe.com@dmarc.ietf.org<mailto:ronald.bonica=40hpe.com@dmarc.ietf.org>> wrote:
Folks,
I feel obliged to comment on implementations that crash when receiving packets with DO=0.
These implementations have a serious security vulnerability. As we have discussed this problem openly on the mailing list, it is no longer a well-kept secret. They should be fixed or decommissioned immediately.
Ron
________________________________
From: C. M. Heard <heard@pobox.com<mailto:heard@pobox.com>>
Sent: Sunday, August 2, 2026 7:40 PM
To: Joe Touch <touch@beachpine.com<mailto:touch@beachpine.com>>
Cc: tcpm <tcpm@ietf.org<mailto:tcpm@ietf.org>>; Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>>; Bonica, Ron <ronald.bonica@hpe.com<mailto:ronald.bonica@hpe.com>>
Subject: Re: [tcpm] New Version Notification for draft-bonica-tcpm-extended-options-04.txt
Greetings everyone,
Please see responses inline below.
On Fri, Jul 31, 2026 at 9:08 PM Joe Touch <touch@beachpine.com<mailto:touch@beachpine.com>> wrote:
It’s difficult to understand the logic below, given tcp-syn-ext-opt uses a packet format that also is silently ignored by legacy endpoints. They’re simply ignored in different ways.
Syn-ext-opt uses a packet that is not defined by TCP, thus is implicitly not invalid, but not otherwise defined.
That's true, and I admit that I had not noticed that. However, in my defense, I intended the main thrust of my comments to contrast differences between the approaches in draft-ietf-tcpm-tcp-edo and draft-bonica-tcpm-extended-options.
Ron’s method defines a packet format that is invalid by current TCP standards, thus - IMO - much more likely to trigger unexpected behavior, e.g., from accelerators and other devices.
Actually, I think that the opposite is likely to be true. If those accelerators and other devices don't understand the EDO option but still attempt to participate in the connection, and they assume that RFC 9293 means what it says about unknown options, i.e., requirement MUST-6:
Feature
ReqID
MUST
SHOULD
MAY
SHOULD NOT
MUST NOT
TCP Options
Support the mandatory option set
MUST-4
X
Receive TCP Option in any segment
MUST-5
X
Ignore unsupported options
MUST-6
X
then they will misinterpret any TCP packets with an EDO option specifying a data offset larger than that specified in the main TCP header, resulting in corrupted data being passed to the user. That's definitely a bad outcome.
On the other hand, although this is admittedly not an explicit requirement of RFC 9293, it is commonly assumed that the great majority of implementations will check the data offset (DO) field in the main TCP header for basic format errors and thus will, as a rule, silently discard packets with DO=0. In this case the connection fails entirely, but at least passing corrupted data to the user does not happen.
I do understand that this benign behavior cannot be assumed to be universal: during the recent IETF meeting, Richard Scheffenegger pointed out at the mic that certain implementations are known to crash when receiving packets with DO=0 (seehttps://youtu.be/pS7dKMeaHeE?t=2064<https://urldefense.com/v3/__https://youtu.be/pS7dKMeaHeE?t=2064__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrDWJa3CPA$>) and as he says, if an experiment based on draft-bonica-tcpm-extended-options is conducted, it's probably wise to determine how prevalent this is. And though this is not really an issue for draft-bonica-tcpm-extended-options, it may also be incumbent on the WG to publish an update to RFC 9293 with text modelled after that in RFC 1814 Section 5.2.2<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/rfc1812*section-5.2.2__;Iw!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrAta3lqHw$> (I admit that I was surprised not to find this in the RFC already). To be perfectly frank, that crashing behavior reminds me somewhat of the Ping O'Death bug that was found around 30 years ago to be widespread, but once found it was quickly fixed in mainstream implementations. Barring extraordinary circumstances, I'm not very sympathetic to suggestions that useful innovations should be stifled by the existence of defective TCP implementations that don't check the DO field.
After the initial handshake, they both use similar “ignore the header length, use this instead” option in subsequent packets and both have the same underlying issue that prevented EDO from moving forward - they are always still incompatible with TCP accelerators, which violate TCP semantics by aggregating packets even for options they do not understand.
In fact, draft-bonica-tcpm-extended-options specifically required the use of the DO=0 format during the three-way handshake, and that is where its big operational advantage over EDO comes from: it can accommodate long options in every packet, including the initial SYN, SYN-ACK, and ACK.
And no, EDO has not been abandoned per se - it’s just silly to waste time doing in-place updates of a draft when the draft hasn’t changed.
Understood, and I was not claiming that. Rather, I am suggesting that it has been overtaken by events.
Thanks,
Mike Heard
Joe
On Jul 31, 2026, at 8:52 PM, C. M. Heard <heard@pobox.com<mailto:heard@pobox.com>> wrote:
Greetings TCPM,
I would like to advocate for a view somewhat at odds with the one that RichardScheffenegger presents below. Specifically, I see EDO and similar approaches that strive to maintain backward compatibility with legacy implementations as a dead end that ought to be abandonedafter decades of failure to gain traction. Rather than attempting to do both EDO (possibly augmented by something like draft-touch-tcpm-tcp-syn-ext-opt) and the approach in draft-bonica-tcpm-extended-options, the WG should pick one approach and run with it. I am admittedly an outsider to the TCP world, but I see the approach in draft-bonica-tcpm-extended-options as technically superior to that of EDO and its companion draft-touch-tcpm-tcp-syn-ext-opt. Slide #7 of Ron's presentation sums it up pretty well:
•TCP-O and TCP-U are incompatible
•Legacy TCPs silently discard SEG-U
• Including the SYN-U that initiates a TCP-U
• Three-way handshake between TCP-U and TCP-O times out
•This is a feature, not a bug
• TCP-U behavior cannot be used as an attack vector against a legacy TCP
It's actually more than that: seeing DO=0 immediately tells both endpoints and snooping / meddling middleboxes that the packet format is different that the standard one, WITHOUT having any state and WITHOUT parsing the options. A modest advantage, to be sure, but IMO real nonetheless.
I'm agnostic about the coding of option length; either the proposal in the draft or Richard's alternative would be fine. Given the need to make checks that unused bits are zero or at least mask them off, I'm not sure there's a whole lot of difference.
Respectfully,
Mike Heard
From: Richard Scheffenegger <rs.ietf@gmx.at<mailto:rs.ietf@gmx.at>>
Sent: Thursday, July 23, 2026 6:17 AM
To: tcpm@ietf.org<mailto: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.
+------------------+--------------+-----------------+--------------=2D--+
| 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<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org><mailto:internet-drafts@=etf.org>
Sent: Friday, June 26, 2026 7:45 AM
To: Bonica, Ron <ronald.bonica@hpe.com<mailto:ronald.bonica@hpe.com>>; Boni=a, Ron <ronald.bonica@hpe.com><mailto:ronald.bonic=@hpe.com>; 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=//www.ietf.org/archive/id/draft-bonica-tcpm-extended-options-04.txt<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bonica-tcpm-extended-options=04.txt__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrDUu12vuQ$>
Status: https=//datatracker.ietf.org/doc/draft-bonica-tcpm-extended-options/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-bonica-tcpm-extended-option=/__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrBF5WU9FQ$>=br> HTML: https=//www.ietf.org/archive/id/draft-bonica-tcpm-extended-options-04.html<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bonica-tcpm-extended-options=04.html__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrByk28lJw$><=span>
HTMLized: https=//datatracker.ietf.org/doc/html/draft-bonica-tcpm-extended-options<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-bonica-tcpm-extended-o=tions__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrAoBC-q_w$>
Diff: https=//author-tools.ietf.org/iddiff?url2=draft-bonica-tcpm-extended-options-=4<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-bonica-tcpm-exte=ded-options-04__;!!NpxR!kGM5Ms--h2s9vCgHiAOj78NTw7BERKUhAqen5hjStxAY7Gm8H9p5CxkErVKtqs19wOFlWrAC6kgj0g$>
Abstract:
A TCP header accommodates only 40 octets of TCP optio=s. In the
future, applications may require more than 40 octets =f TCP options.
For example, an application may require a TCP Authent=cation Option
(TCP-AO) with a 384-bit MAC. This option requir=s 52 octets of
option space.
This document defines a TCP extension that accommodat=s up to 1,016
octets of TCP options while maintaining backward compatibility with
legacy implementations.
The IETF Secretariat
_____________________________=_________________
tcpm mailing list -- tcpm@ietf.org<mailto:=cpm@ietf.org>
To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org>
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.
_______________________________________________
tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org>
To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org>
_______________________________________________
tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org>
To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org>
_______________________________________________
tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org>
To unsubscribe send an email to tcpm-leave@ietf.org<mailto: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