IETF Logo Mail Archive

[CFRG] Re: [IPsec] draft-kampanakis-ml-kem-ikev2

Paul Wouters <paul.wouters@aiven.io> Mon, 26 August 2024 18:43 UTC

Return-Path: <paul.wouters@aiven.io>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDED8C14F69C for <cfrg@ietfa.amsl.com>; Mon, 26 Aug 2024 11:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aiven.io
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m39lPrp-ZILN for <cfrg@ietfa.amsl.com>; Mon, 26 Aug 2024 11:43:08 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 0983FC14F6A7 for <cfrg@ietf.org>; Mon, 26 Aug 2024 11:43:07 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5becd359800so5279533a12.0 for <cfrg@ietf.org>; Mon, 26 Aug 2024 11:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; t=1724697786; x=1725302586; 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=HsRa3Ow8bXNexphPULbv4sYRKqP+klhK5BbbxI87SrY=; b=TEtyAHpbwrsfEqeFFWJtfnX1qMksyPyytKF9+qCLN5wPPxKpwO/7MKa6J94QngFWeW 6ZcJJ8vfwOclkhgpnXvMfXwk+eL8w0SOl0HY1aBTgFpoZsfCqsHW6ol7G1CZ6r//hrC7 h+g90Vw/CwgGw8XIHmTXulnHnrU0JXNK2Lt6Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724697786; x=1725302586; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HsRa3Ow8bXNexphPULbv4sYRKqP+klhK5BbbxI87SrY=; b=grCdp2H1kO/nlsGUeD09qx5Pa5s8JJT3vf/4Jg+iJ1QE0DeA6wgSkMrL5i4lyyrF9b xirGUqfc2nevBz6ZHnUatYPpeFnSlMrodAJ7mCZlD8TijOqSt26ZFhHpsKbOLnV9X56x MsTB7H2CwJR+uBB2BZXvBVsip6kcYeSKZeK9pJALje/8IAyuO5EOvoQmrYCz1Eo+Sv6k mzgPsoDAeOdmnAZwpGGALDYXjD87t88ZW9fuAfa/vDOIOXB5MsjoJhiPfNRyYfRW+PbU MrBuTSOhPYsWJ7wDmJFq5HWH5uEjgY2ASbts1EUZPcIV1PyF/lzGR38F+C1Cz5xHSKaI RkRQ==
X-Forwarded-Encrypted: i=1; AJvYcCV8p/o0KD2ujRst3vCmoPcRyVSvz98RZUP0GiwVgeyVVMoLMzupARs+37A7aIZR6PX7yPq/@ietf.org
X-Gm-Message-State: AOJu0Yxjcb9RbGp0DVEW48rUJecY7216eAADpJK7qIXKuZhLOLAtil8V EYYQ7jFnWJSS+duHa1hkvQCwtTrjfGLXENgiCdOmeCtig8VwRUEB9xWrMrreMEob1+ICiE34WxR C3paKIIZmJvLUY1pri1Iyx1xDJSMXEppvYKVkng==
X-Google-Smtp-Source: AGHT+IEV97pIcbpp83S47YSu9If/mp6G5a/OcrhNt8wBwp7mza3yrWCBVP4TgDrM4yBgk8udyXZYcnVbmz1Tl9ukMME=
X-Received: by 2002:a17:907:608a:b0:a86:743e:7a08 with SMTP id a640c23a62f3a-a86e3a58e05mr30518966b.31.1724697785999; Mon, 26 Aug 2024 11:43:05 -0700 (PDT)
MIME-Version: 1.0
References: <CH0PR11MB54448C7AE123A3D909E4EE1DC18B2@CH0PR11MB5444.namprd11.prod.outlook.com>
In-Reply-To: <CH0PR11MB54448C7AE123A3D909E4EE1DC18B2@CH0PR11MB5444.namprd11.prod.outlook.com>
From: Paul Wouters <paul.wouters@aiven.io>
Date: Mon, 26 Aug 2024 14:42:55 -0400
Message-ID: <CAGL5yWajZ5-iJWN1iWiYZUxMemv=cm+3tcqodbA4+nfW5y4oPg@mail.gmail.com>
To: "Scott Fluhrer (sfluhrer)" <sfluhrer=40cisco.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e17e1606209a7ea3"
Message-ID-Hash: QLNXWMKXNX7FA3FXPKRHEHFWTEOKV7LP
X-Message-ID-Hash: QLNXWMKXNX7FA3FXPKRHEHFWTEOKV7LP
X-MailFrom: paul.wouters@aiven.io
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "ipsec@ietf.org" <ipsec@ietf.org>, cfrg@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CFRG] Re: [IPsec] draft-kampanakis-ml-kem-ikev2
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/drg6mXJMrHqv_iuLMdmrtOiypoU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Owner: <mailto:cfrg-owner@irtf.org>
List-Post: <mailto:cfrg@irtf.org>
List-Subscribe: <mailto:cfrg-join@irtf.org>
List-Unsubscribe: <mailto:cfrg-leave@irtf.org>

On Mon, Aug 26, 2024 at 1:51 PM Scott Fluhrer (sfluhrer) <sfluhrer=
40cisco.com@dmarc.ietf.org> wrote:

> I (and I don’t believe I am alone in this) would like to see an ML-KEM RFC
> for IKE; how can we make it happen?
>
>
>
> From what I see, the next step (now that the authors have updated it to
> specify the final version of ML-KEM) would be having it adopted by the
> working group (and while there are a number of steps past that, I don’t
> know if those can proceed before this initial step).
>
>
>
> Is this something that can be done before Dublin?
>

Is CFRG going to have an "how to use ML-KEM in IETF protocols" document,
like it did with RFC 7748 and RFC 7539 ?

I would personally feel much better if there was such a guidance document,
before we finalize the specification at the various protocols itself.

Paul

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