[TLS] Re: WG Adoption Call for Post-Quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3

Mike Shaver <mike.shaver@gmail.com> Thu, 27 February 2025 03:42 UTC

Return-Path: <mike.shaver@gmail.com>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8AAF92812B2 for <tls@mail2.ietf.org>; Wed, 26 Feb 2025 19:42:24 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietfa.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietfa.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9ZMxpgvQ-xH for <tls@mail2.ietf.org>; Wed, 26 Feb 2025 19:42:23 -0800 (PST)
Received: from mail-oa1-x32.google.com (mail-oa1-x32.google.com [IPv6:2001:4860:4864:20::32]) (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 D97B32812A5 for <tls@ietf.org>; Wed, 26 Feb 2025 19:42:23 -0800 (PST)
Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-2bcc0c6c149so496257fac.1 for <tls@ietf.org>; Wed, 26 Feb 2025 19:42:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740627742; x=1741232542; 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=+cnrEQ0kteVA9jdq5zCf2gONM7zJYj2xZHio+JBNdQg=; b=MBPyWPFsnDYw7870qM0TVbZXIi/dhpwKMC7LPr3MfIkC7He31q/CL9z1e8BR7KEwWk eGQOVVdfs3fXoGZszG+DOaMwIMLL/kZO8Z3oOKO9W/ppPYOYptNcy+ciCP26Lk6RL0WM 9J2t30oKdMOvW7aKZMZNffo9Qnn3lKBsl6G/wFzoQ+I+Ttoypy8luDJq99vK4CIxG+Hg G8cIc7QIgj6ClI5FV63DpbGsCOyby5OtTsh7QUBys0jcUuX/0z5pOPBivkkFaEsdWJ+M qgAQFCEc7aPk80y5x+CMBNPvMY5cvZQXdc4k4gcHLre4334s+VPkI6OaQaxj+s8+0DJE G3XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740627742; x=1741232542; 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=+cnrEQ0kteVA9jdq5zCf2gONM7zJYj2xZHio+JBNdQg=; b=n+PpVsg2a76OkROPb8vNfT1zWwe2NAiw8MWyRPd0Eax+rgGGUYS7Azefo9rI/2D/Jj RyQJ/p9Te4PRolipTgdlZdi6ZgqYz/R5cd9BIGzSga2uteDvTF/qgxXSvIDWRyot7unZ 4jE2L3S6pYWoeLQ76jrD5vQByCQ3hJYP2hFHyyWRqLtQZbXrYNFtjVZSN5X5G+pk8iML AAUOUsUL/sjVFV+w4evU6aFW9Jn4vOXU7W+LEP39UC4N5JAv9rh73si7SzPCp8EV5i4w lutj5SsWt4q5jqrQj1sorIgcgv37/WfpnI8MpQFhQl2f2ylKKS+rpgSkvxpmHvFPDnWU PpnA==
X-Forwarded-Encrypted: i=1; AJvYcCU4X/4TD3CjTMyA0xrQIdXVgEnXJtztRnmCAxdRaSceWY/TVuBSFkVYY88q+F/gu8vjy80=@ietf.org
X-Gm-Message-State: AOJu0YyJmKNTWXe4/tlSZPNad/g0pgAIN5mruIQgwswjWawoA89Qnjub 92y2uz0RXfwJ1c+ac88iGd1WJZ0MDAnKz8/Ip5Y5/EsrYbgeBlwSaYr7st+QYZhErzb5LKyxS4W NfwhH3qOF7bQgirsX+aKkJbhDdhbXrA==
X-Gm-Gg: ASbGncusqTemlEJOucblCkbBgHCNNddrZgZo4NUGvTwUD4UKe6prqkeLyFvNxF7tPcH ZcWgjQ3y4juXFXQvzABmrke/PYPqebClU3C5pNRuvOjinw+7VPmVgczyQ3TVh3JBoLuwX0dzbcU 3UCAzJYIg=
X-Google-Smtp-Source: AGHT+IEl7RQgv34VoEo986s0VhfrzYziepOngKcEtmmrR/cP7oT2+FU4P8E5SEKuxwTD9yBoGGDeXo6BNQq2RMpVXVo=
X-Received: by 2002:a05:6871:53cb:b0:2c1:3d60:3792 with SMTP id 586e51a60fabf-2c13d609aa2mr2794633fac.35.1740627742498; Wed, 26 Feb 2025 19:42:22 -0800 (PST)
MIME-Version: 1.0
References: <68EDF12D-1C97-4823-AFFE-19BF261D7034@sn3rd.com> <E0D776C8-FD56-4D0B-BDC1-3AB88A8CEE88@heapingbits.net> <Z7-CbKePNWI1FdOH@netmeister.org> <ME0P300MB071318BBC6F7E42D7BC6F85CEECD2@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM>
In-Reply-To: <ME0P300MB071318BBC6F7E42D7BC6F85CEECD2@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM>
From: Mike Shaver <mike.shaver@gmail.com>
Date: Wed, 26 Feb 2025 22:42:11 -0500
X-Gm-Features: AQ5f1Jr1-8Sx0tcWgadNWovV-II1QY3daC006JAP5lAyh01zNDRrH2y9eftTd9A
Message-ID: <CADQzZqttobvF_0ui6c4_sFCBronXeYmk+4APc4+dBPNn9bxCUQ@mail.gmail.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Content-Type: multipart/alternative; boundary="0000000000004726c7062f177ae9"
Message-ID-Hash: VU4VUE2KZVDJ7YOFRHKRGTUX2AYVPNDT
X-Message-ID-Hash: VU4VUE2KZVDJ7YOFRHKRGTUX2AYVPNDT
X-MailFrom: mike.shaver@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Jan Schaumann <jschauma=40netmeister.org@dmarc.ietf.org>, "tls@ietf.org" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Adoption Call for Post-Quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/o-g0_P5_mSJYsrKxLKLqGr2WZAU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

It's interesting, IMO, that there is so much belief that an RFC designation
will drive so much adoption here, but it didn't seem to be the same
consensus that enshrining SSLKEYLOGFILE in an RFC might increase the number
of systems that support key exfil.

To be sure, I don't confidently know which is the case; perhaps both,
though I can't figure out how to reconcile that myself at this point.

Mike

On Wed, Feb 26, 2025 at 10:16 PM Peter Gutmann <pgut001@cs.auckland.ac.nz>
wrote:

> Jan Schaumann <jschauma=40netmeister.org@dmarc.ietf.org> writes:
>
> >It may seem silly to all folks who are directly involved here in these
> >discussions, but many software and service providers view a "draft" as
> >immature, not final, subject to change and may not implement until it has
> an
> >RFC number.
>
> This is standard policy for a number of organisations I deal with: If it's
> not
> a published standard (ISO, IEEE, RFC), it doesn't get considered.  They
> don't
> sell products based on drafts.
>
> (Actually for IEEE stuff at least one of them pre-implements based on
> drafts
> so they're ready for market when it's finalised, but that's splitting
> hairs).
>
> Peter.
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>