IETF Logo Mail Archive

[IPsec] Re: Call for adoption: draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03 (Ends 2026-02-09)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 22 January 2026 21:08 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipsec@mail2.ietf.org
Delivered-To: ipsec@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3B239ABAC08E for <ipsec@mail2.ietf.org>; Thu, 22 Jan 2026 13:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=sandelman.ca
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 GrklRivxxLv9 for <ipsec@mail2.ietf.org>; Thu, 22 Jan 2026 13:07:59 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AD444ABABF51 for <ipsec@ietf.org>; Thu, 22 Jan 2026 13:06:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 192F318021; Thu, 22 Jan 2026 16:06:45 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id nWUXdjE5-As3; Thu, 22 Jan 2026 16:06:42 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1769116002; bh=R9raFLbDoIbN0aQkMUNjbGe/8qqhjPE2tBjD4vsXYOs=; h=From:To:Subject:In-Reply-To:References:Date:From; b=IRAiRKilg4I0snCUQjL19YFmZtTnOs4fMBK2jHX8JJ7DvQ3M7C5HGMM5pfjVYjPe0 dmLSDHHugt5b4ygY3whKr5ZBP15q//yZ1sZIT+eCIzyaOBonkZzcEn+gClB/aJgDPP twcJi9hUx6TKS+eCiRI0GocZlGANzjAJ+fxI0tUwQLmZGYMxlcRUfYaNl5GTbAA5b8 RHw5IcpJlQ/KdHZAczIos+lmqJcWmwwhdUDV8+zuRjUAroLni2dQTwGoksLWGarAiH oi4LCb8ExPT4ceOND/ZZq6b/nSo35Wnq6ruJj/1F/yRu95XYctZ/h9el3+/zsBZqQd M/QKojLAg20qw==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D5A261801F; Thu, 22 Jan 2026 16:06:42 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8FC6F1AE; Thu, 22 Jan 2026 16:06:42 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Thom Wiggers <thom@thomwiggers.nl>, ipsec@ietf.org
In-Reply-To: <064BDB29-C00E-43D1-ACD2-542ACFF0311F@thomwiggers.nl>
References: <176824138819.764059.17372501962377307239@dt-datatracker-5656579b89-r5kdq> <064BDB29-C00E-43D1-ACD2-542ACFF0311F@thomwiggers.nl>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 22 Jan 2026 16:06:42 -0500
Message-ID: <20460.1769116002@obiwan.sandelman.ca>
Message-ID-Hash: TME5T7QJ7H6PYCGJU3DCPBM3B7VM7IXX
X-Message-ID-Hash: TME5T7QJ7H6PYCGJU3DCPBM3B7VM7IXX
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipsec.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: [IPsec] Re: Call for adoption: draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03 (Ends 2026-02-09)
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/9lSOOShRJv_gAAVsjIMx92NQiCk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Owner: <mailto:ipsec-owner@ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Subscribe: <mailto:ipsec-join@ietf.org>
List-Unsubscribe: <mailto:ipsec-leave@ietf.org>

Thom Wiggers <thom@thomwiggers.nl> wrote:
    > Title:
    > I do strongly feel that “hybrid” should be removed from the title of
    > the draft, because I think it will lead to confusion on what this draft
    > achieves in terms of security. Namely, “hybrid” commonly means PQ/T
    > hybrids, but this draft can be used perfectly fine with ML-KEM-512 in
    > the IKE_SA_INIT key exchange. While I do agree that this would still
    > give us a (PQ/PQ) “hybrid”, I don’t think that this matches
    > expectations surrounding the word “hybrid”.

I agree strongly.
RFC9370 defines multiple key exchanges, so linking it in that way makes more sense.

    > I don’t think “hybrid” adds much either, other than (to experts)
    > hinting that this needs to be done in IKE_INTERMEDIATE exchanges. So if
    > that is the intended message, I suggest renaming the draft to something
    > like “FrodoKEM for IKE_INTERMEDIATE IKEv2 Key Exchanges”.

Or, maybe "Using FrodoKEM in Multiple IKEv2 Key Exchanges"


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.38.3 | Report a Bug | By Email | System Status