[tcpm] Re: Additional Security Algorithms For Use With TCP-AO
Yoshifumi Nishida <nsd.ietf@gmail.com> Sun, 08 February 2026 10:54 UTC
Return-Path: <nsd.ietf@gmail.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 B47D8B39992F for <tcpm@mail2.ietf.org>; Sun, 8 Feb 2026 02:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 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, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mq21o8X7CtG1 for <tcpm@mail2.ietf.org>; Sun, 8 Feb 2026 02:54:46 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1EF57B39992A for <tcpm@ietf.org>; Sun, 8 Feb 2026 02:54:46 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-383153e06d6so32424931fa.0 for <tcpm@ietf.org>; Sun, 08 Feb 2026 02:54:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1770548085; cv=none; d=google.com; s=arc-20240605; b=MeKaQhlGFj1y5AKT7I4ZduPN8zJ9WIxOk/6rmuoiKdTGIQhMAYPS9XzvefNpsPjzBo ph4MmJ9+Y89FMeT/uoAd77o2oNritZviG1ignQhOExwHmCDXB1fkv3vLd/MFPgsQ7z4Q HSXYAPKU8YC+jGDWlmHOZjzgq3HTC2X+RasShNSWuNmEfqScVYMMhRI7cQu/cnb+FU4A dMGKqPi/DCpO9ENyakKaZ14pG+RenPCti7QjE+3tPKfEJtQ950vB7hfMudWoCzu1PDuq ORLpjshxoEjRyI1h8ch2dXH3xK779CCa5VAN2Zsyb2392o8/pDGsYE0kbyDQqHpnFwaY woYw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=Ah9CFwI3Lpjp2KzGnN1nsW3khj57XFwkKpLuonEaYyk=; fh=ABww6tzNWig21CaekBwnOF1iHpfTtfpYtAgQLJLUosI=; b=LCrrkL7sz/Hmlq/NG50OA2fHHeZJmrdb0xQNT6lrViIOQmLM5zzToHPxXgAKbtIlZp e059HnRvzs7GHJKu4YrDyBcAe5nVNFlDHejZfe/EOQl3IDuJ3rCggJ3SJ/O8AcNLSowZ 5JFiwz0IH4PgVMcCHRg2VUQgRHQJXXGq81RMP1jlt4F+BSR96gjUUhKTjJ3Tl4PoMnP3 NzFym56FIXpSULpZGmYD9WtuqpSAbUBHJjdTzSAMDG6TS8D2Ba8ELnR4Jwj7iCS/1EkF HW63u//btkCTtIdUm99A9On9UdqlLltFd3xhHKUU9gJUWcS71CklfhdKoGfTn65OfC8S NbMA==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770548085; x=1771152885; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Ah9CFwI3Lpjp2KzGnN1nsW3khj57XFwkKpLuonEaYyk=; b=TIpV//iXKx6rVTYT2FVpkwGABzwr5CECFkpQJTTpq/mRD+edboR++VrH3+hoygI/Pe 8tiZPiA/ZTKiAdg5kIWM6zrzbm1ewLdolNGAnbKD/mIiUehFcZEFuuVCy7mRRUc/EwCS rHSxVb4yrME58i8BYKwQQ3UqFk8V1hHyKNwOU9gVZugs7sH40YigEJWSWtJgwma0UxYe samnbpkY0qopBVC/rBmSJV1/boaQHksi2vpIPDzHTvyyynxLvFYTF+Xl2AyAPHx7oqfL Pbk4zkz4TLLzlGbZz9Y3SOfPWWBx7OyLpwyVyZgUJ0ZeGkm2NwB05xLH6Yl1vKcMiJHO HnPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770548085; x=1771152885; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Ah9CFwI3Lpjp2KzGnN1nsW3khj57XFwkKpLuonEaYyk=; b=fTgyVh4im9zc2mNgTuA+/TP4eyboYzKLx0ugsO36h/OWNJVDCv13ixVegQCZWOBdRH TRBosHVs/DkouEwTMFJ37Kb3hvzTUtVHPuu7MYjlZOnEQFRTu4ttxFs7yCKz7c1C/MwW lReTF6JvJZ0loa5y4unXM9Ry3GSj8I9TKZWX/ysB0KGnX95U9FveTteStqEpSQ2Dxaqk LO8QXBMKnIXbay+eybC9JXmJjV5DC9ctRJWVkSLY2Yz+PrqtdYvcuV6s2tsjurX+hq2B xJ8yze50LVyFibXreY6zxSU/ij3+OG0kDffQvt4f50FAL8W0kNTLaFFZeiY+f2Veqvza hbDA==
X-Forwarded-Encrypted: i=1; AJvYcCXWGimCb/llHGPzAERn189LGPZ/eckb3sH+9NjxRieIEPaJVYJolFuMEi2tNUCYbv3DEtli@ietf.org
X-Gm-Message-State: AOJu0Yxd82RgoGEpvW+tJ5TGA+/zLxFrmpGJVBuaEf9unLWmU9p8kZLQ tE6t2FX0gkQiZRDMP7gfP3KN1E9aB/wwGaC9ltMTSJvGb97m8zmcyAXyC3iMFTBuIz4xmi6LSko 9QpwEBjFyGHxomD47OKJhlvCb10T3KjU=
X-Gm-Gg: AZuq6aJWYsBrIrOsT2+nB4jEiyhtoM1+DkQtg33S7f3g40fCCzQ4fpOxuVl+e2JFFUG eYmY5ntqmqYvp1C7vuoqc2lihGzS2aLWW1FGSJK3CUmDMifO5RJDQsdA2bE1eGntX0CtgQ8hXl9 Q2fZoG8XA5J2YBcKMkFTHRP2aPTdtx4E2zOuNwcF3NHSykd0p6AUN0f4mmLsMjI096VSKsePdAm wswfwXB7NplIiJbEaCAktMW0rNiSTBfJMxzm20oEViM2B1Tpw+nC0CxrxrSyPfvDNRgUo2nyG2v NtpSrlzBbg9HQNf8D3HFJQEMSQjx
X-Received: by 2002:a2e:ad12:0:b0:386:8ea2:ef7 with SMTP id 38308e7fff4ca-386b5139f04mr29299821fa.32.1770548084449; Sun, 08 Feb 2026 02:54:44 -0800 (PST)
MIME-Version: 1.0
References: <DM4PR84MB2310F06DF364B70C1A570970F492A@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM> <D2C73FF4-F60A-4EAC-8AA9-66936E3A0F68@strayalpha.com> <19EACEAC-A6DA-4DF0-B044-81888778121C@eggert.org> <7B90805D-646C-4B93-9C16-F9DF3A933416@tony.li> <3562FA6F-C968-42E0-8D2E-A3B655E059D1@strayalpha.com> <8C55B505-C579-4CF8-84B8-D078888D25A1@tony.li> <CAAK044SFKh65EDCQPo3M13JB1ACET7CG-EDBmheAMOsP_Df7Vg@mail.gmail.com> <DM4PR84MB2310FDAB355AB38D1BB48675F466A@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM>
In-Reply-To: <DM4PR84MB2310FDAB355AB38D1BB48675F466A@DM4PR84MB2310.NAMPRD84.PROD.OUTLOOK.COM>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Sun, 08 Feb 2026 02:54:33 -0800
X-Gm-Features: AZwV_Qjx8gEqtG4h7IT_xnDeJDfqOkYebHvjYsZoIPeOzs_UQNkpXdXazm5OgCg
Message-ID: <CAAK044T72UHaFdeps5yWp7YtkY47cOUM5QAFNJxpDRQySJrVBQ@mail.gmail.com>
To: "Bonica, Ron" <ronald.bonica@hpe.com>
Content-Type: multipart/alternative; boundary="000000000000a1a642064a4dd9a8"
Message-ID-Hash: A4ZBI4X5HKH4BUNAHWRQG5P3NHEKDUKP
X-Message-ID-Hash: A4ZBI4X5HKH4BUNAHWRQG5P3NHEKDUKP
X-MailFrom: nsd.ietf@gmail.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: Tony Li <tony.li@tony.li>, Joe Touch <touch@strayalpha.com>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
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/ncwZ30Wu4AqHf3xSKa0QThZj_3g>
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 Ron, Thanks for the comments, I basically support using non truncated MACS. I am just wondering if we can allow to use truncation only for SYN. In this way, I think we don't need to think about extending SYN option space which is very tricky. In the meantime, I think we might be able to utilize EDO for extending option space in data segments to avoid truncation. The current drawback of EDO is that it needs to disable GSO/GRO, however, if we use EDO with TCP-AO, this won't be an issue. -- Yoshi On Fri, Feb 6, 2026 at 12:47 PM Bonica, Ron <ronald.bonica@hpe.com> wrote: > Yoshifumi, > > Sorry for the slow response. I have been on holiday. > > draft-bonica-tcpm-extended-options and draft-bonica-tcmp-tcp-ao-algs seek > to satisfy the following customer requirement: > > > - Authenticate *every* segment in a long-lived TCP session with > algorithms like HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512 > > > The solution is negotiable, but the customer requirement is not. > > The customers realize that it is very difficult to increase the size of > the TCP Options field. So, they are willing to accept truncated MACS as an > expedient (e.g., HMAC-SHA512-128). So, draft-bonica-tcmp-tcp-ao-algs how to > use such algorithms with TCP-AO. > > However, truncation is only an expedient. Furthermore, this degree of > truncation can violate the guidance offered in Section 5 of RFC 2104. > > While I have great respect for existing work, I think that the customer > requirement is reasonable. I don't think that pushing back on any part of > the requirement is a viable option. > > Ron > > > > > ------------------------------ > *From:* Yoshifumi Nishida <nsd.ietf@gmail.com> > *Sent:* Monday, February 2, 2026 5:39 AM > *To:* Tony Li <tony.li@tony.li> > *Cc:* Joe Touch <touch@strayalpha.com>; Lars Eggert <lars@eggert.org>; > Bonica, Ron <ronald.bonica@hpe.com>; tcpm@ietf.org Extensions < > tcpm@ietf.org> > *Subject:* Re: [tcpm] Re: Additional Security Algorithms For Use With > TCP-AO > > > > On Sat, Jan 31, 2026 at 5:04 PM Tony Li <tony.li@tony.li> wrote: > > > > > However, it’s been a decade and the former remains in-process and the > latter has not been adopted by the WG. > > > It would seem that there is no interest. > > > I personally think there are some interests. But, extending option space > is not an easy issue for TCP especially for SYN segments. > > One thing I am wondering is if this draft can always fit the option into > SYN packets without extending option space. This is because extending SYN > option space is quite controversial. > OTOH, in my personal opinion, EDO which extends option space for non-SYN > segments could proceed it. > > The last time I presented Kuniyuki's linux implementation for EDO ( > https://datatracker.ietf.org/meeting/121/materials/slides-121-tcpm-tcp-extended-data-offset-option > <https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/121/materials/slides-121-tcpm-tcp-extended-data-offset-option__;!!NpxR!hx2dG4QMuB9n-YWoo7KXCmEIZbwR1Wwaiiz1Uvz9da6Ug_laE9wjPfCpncAxL0R9e4mCdB5ULs3ajMe3zg$> > ), > Some folks disagreed proceeding EDO because we will need to turn of > GSO/GRO. However, TCP-AO implementation already does the same things. > > If the blocking point of EDO draft is disabling GSO/GRO, it seems we have > a realistic use case by using it for new TCP-AO even with this drawback. > -- > Yoshi > > >
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Additional Security Algorithms For Use Wit… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Lars Eggert
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Re: Additional Security Algorithms For Use… Lars Eggert
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Gorry Fairhurst
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Re: Additional Security Algorithms For Use… Joe Touch
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Yoshifumi Nishida
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… John Mattsson
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Yoshifumi Nishida
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Yoshifumi Nishida
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Yoshifumi Nishida
- [tcpm] Re: Additional Security Algorithms For Use… Wesley Eddy
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Lars Eggert
- [tcpm] Modern crypto for TCP-AO: (was Additional … Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Magnus Westerlund
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Magnus Westerlund
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… C. M. Heard
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Yoshifumi Nishida
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… C. M. Heard
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Yoshifumi Nishida
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… C. M. Heard
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… Bonica, Ron
- [tcpm] Re: Modern crypto for TCP-AO: (was Additio… C. M. Heard
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Lars Eggert
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Joe Touch
- [tcpm] Re: Additional Security Algorithms For Use… Martin Duke
- [tcpm] Re: Additional Security Algorithms For Use… Michael Tuexen
- [tcpm] Re: Additional Security Algorithms For Use… Martin Duke
- [tcpm] Re: Additional Security Algorithms For Use… Michael Tuexen
- [tcpm] Re: Additional Security Algorithms For Use… Lars Eggert
- [tcpm] Re: Additional Security Algorithms For Use… Tony Li
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… touch@strayalpha.com
- [tcpm] Re: Additional Security Algorithms For Use… Haas, Jeffrey
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron
- [tcpm] Re: Additional Security Algorithms For Use… Scharf, Michael
- [tcpm] Re: Additional Security Algorithms For Use… Bonica, Ron