[tcpm] Re: Additional Security Algorithms For Use With TCP-AO

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Mon, 02 February 2026 13:20 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
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 67B24B096FAF for <tcpm@mail2.ietf.org>; Mon, 2 Feb 2026 05:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=hs-esslingen.de
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 ibJTojkycZAf for <tcpm@mail2.ietf.org>; Mon, 2 Feb 2026 05:20:29 -0800 (PST)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 40BADB096F95 for <tcpm@ietf.org>; Mon, 2 Feb 2026 05:20:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 2D88825A34; Mon, 2 Feb 2026 14:20:22 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.9.1 mail.hs-esslingen.de 2D88825A34
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=20240206; t=1770038422; bh=Bqzj/8lHvSCtxmJ1QuCY5YaapDJrscGRBT1awP079lU=; h=From:To:Subject:Date:References:In-Reply-To:From; b=PuHRf78UdjhL58Yx9hVOpccOExx4vxRrz4sU53SffY0wQtaaPuUMZtPDzsLYshle1 woaUUSSFnUMip+StvCw3cFLzdP5DD0/pf7b5268KwjsP2dkNUohMk4JnyjNJBF3YzP 6IFfo0w6GmE0FOMY4+iMHX9lW8CuXmdeCCaYG3HXG30ULRquTbHRwR67ZH4F+WqkB4 mH2QR0tz5vLwcXGOGWDppdq9luIfG2IKj5QX09SSC4JhOx0l9iZA96Bwpj0iTumFzL YFrCFeO1cYYnJZzCzm4PRJIAVNurM5gKlrjJ/Fr5zrHw8e4aOQOKi54iKFM7gbkt4h yX9whC4r9AbcA==
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y-_3UJbSbfYu; Mon, 2 Feb 2026 14:20:21 +0100 (CET)
Received: from rznt8211.rznt.rzdir.fht-esslingen.de (rznt8211.hs-esslingen.de [134.108.48.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Mon, 2 Feb 2026 14:20:21 +0100 (CET)
Received: from rznt8211.rznt.rzdir.fht-esslingen.de (134.108.48.176) by rznt8211.rznt.rzdir.fht-esslingen.de (134.108.48.176) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.35; Mon, 2 Feb 2026 14:20:20 +0100
Received: from rznt8211.rznt.rzdir.fht-esslingen.de ([fe80::13e5:178a:57f8:5230]) by rznt8211.rznt.rzdir.fht-esslingen.de ([fe80::13e5:178a:57f8:5230%5]) with mapi id 15.02.2562.035; Mon, 2 Feb 2026 14:20:20 +0100
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: "Bonica, Ron" <ronald.bonica=40hpe.com@dmarc.ietf.org>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Thread-Topic: Additional Security Algorithms For Use With TCP-AO
Thread-Index: AQHcjlGvT/nl/6yjnEeI7lhCk4H0PLVvaRPA
Date: Mon, 02 Feb 2026 13:20:20 +0000
Message-ID: <e1db8b109b2c45dcb81dee1569ff9292@hs-esslingen.de>
References: <DM4PR84MB2310F06DF364B70C1A570970F492A@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To: <DM4PR84MB2310F06DF364B70C1A570970F492A@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
msip_labels:
x-originating-ip: [134.108.140.249]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0049_01DC944F.0F6114A0"
MIME-Version: 1.0
Message-ID-Hash: K43JTFJDHCM4AOEZ62BAXZNFQKQV44HM
X-Message-ID-Hash: K43JTFJDHCM4AOEZ62BAXZNFQKQV44HM
X-MailFrom: Michael.Scharf@hs-esslingen.de
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: Additional Security Algorithms For Use With TCP-AO
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/amwGWa10qi71H-4r10GwkatRDsQ>
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>

Hi all,



Three comments regarding past TCPM discussions in this space:



1/ This drafts seems to overlap with draft-nayak-tcp-sha2-03 
(https://datatracker.ietf.org/doc/html/draft-nayak-tcp-sha2-03) which was 
discussed in TCPM about 5 years from now. As far as I recall, it was presented 
once or twice in face-to-face meetings. By that time, there was little 
interest in this draft other than by the authors. At first sight, 
draft-nayak-tcp-sha2 includes as a small subset similar algorithms.



2/ There are a number of very well-known and widely deployed TCP-AO 
implementation, typically with TCP stacks optimized for routers. Amongst 
others, there was quite some useful implementer feedback regarding the TCP-AO 
part of the TCP YANG model (RFC 9648). When discussing TCP-AO in TCPM, it 
seems particularly important to get feedback from the typical users of TCP-AO, 
in order to ensure that there is consensus in industry. This in particular 
includes the question how to deal with limited TCP option space.



3/ TCPM owns TCP-AO, but many contributors are no experts in crypto 
algorithms. In the past, it was useful to get early reviews from the SEC area 
(e.g., SEC-DIR).



I am not a user of TCP-AO, but personally I believe that specifying further 
security algorithms is useful. (Actually, that even applied to the past 
draft-nayak-tcp-sha2 draft.)



Regarding extending the question whether and how to extent the TCP option 
space for TCP-AO, I would really be interested in feedback from _other_ users 
of TCP-AO. As discussed for example not only for EDO but also for AccECN, I am 
personally not a big fan of experiments with the TCP header, i.e., I believe 
changes of the TCP header should ideally be done on standards track. If there 
were multiple interoperable implementations running in production networks, 
the bar for standards track is actually not too high.



Michael





From: Bonica, Ron <ronald.bonica=40hpe.com@dmarc.ietf.org>
Sent: Monday, January 26, 2026 12:26 AM
To: tcpm@ietf.org Extensions <tcpm@ietf.org>
Subject: [tcpm] Additional Security Algorithms For Use With TCP-AO



Folks,



Please review 
<https://www.ietf.org/archive/id/draft-bonica-tcmp-tcp-ao-algs-00.txt> 
Additional Security Algorithms For Use With TCP-AO and comment.



                                                                        Ron