IETF Logo Mail Archive

[TLS] Re: PQ Cipher Suite I-Ds: adopt or not?

Sean Turner <sean@sn3rd.com> Wed, 26 February 2025 01:53 UTC

Return-Path: <sean@sn3rd.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 8CCCE17D967 for <tls@mail2.ietf.org>; Tue, 25 Feb 2025 17:53:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietfa.org (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 hnYeOxcSLNJ2 for <tls@mail2.ietf.org>; Tue, 25 Feb 2025 17:53:20 -0800 (PST)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 5070D17D960 for <tls@ietf.org>; Tue, 25 Feb 2025 17:53:20 -0800 (PST)
Received: by mail-qk1-x735.google.com with SMTP id af79cd13be357-7c04df48a5bso620574785a.2 for <tls@ietf.org>; Tue, 25 Feb 2025 17:53:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1740534799; x=1741139599; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :from:to:cc:subject:date:message-id:reply-to; bh=y73sAcD943TdsUBR5CYeYa2o1NaWs0v3ps5IKfT/Ltw=; b=LK5VZt3b3CtP11IOxB1sW5eg53u6R2QOhUuxzw5iXqDb0uWKLwhaMgncu3lTuZuaIx 0dXM7+6r2P03JZNFhBZhVsB44++T2NGGlX6UZCUqgnHgJSuESPBgV9nocy3Hrhhi6pJC Sl7UOZX31Tye986FEVVyttJ8sQG6mEje7RQlk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740534799; x=1741139599; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=y73sAcD943TdsUBR5CYeYa2o1NaWs0v3ps5IKfT/Ltw=; b=LzlnQf1sE57xHJUrNMBUCDROeQyIwxR7pJc9yz/vrXnlWPmgxS4PIjIwtjp/F28d7A fH1HA6gdldV0BejIqs13ys0z7ZndmPuXBYNbN/xVItYPXWU6H+CIwLFL/I7Xq540RQ3v ER2E+eZxuFJacNGLU30jghq4op+2Ucr3RqKUFx22VrZHZZIJoMUTEXOv5T4JedKWNvE0 9Ybk3u2kPyS5hKYVUW24at0ON5ryB1g6CbFEHSl6g+Tw54SHt664nB49yilmSKGjUxeA 6eABbXG1uDAfZU0kLH4VnMIPjRfJUhBn2rX2blxD9/EyLtRHJM9R2Bp4QEPTW9uxATT4 vXWw==
X-Gm-Message-State: AOJu0Yy7ZGDMPC+wbEnGW4zmmy6usUQnJV6c+z4MSyGHUj+S0gMCojSu OPkfad4NJouGwSrcus1LfCOtePAPrymcuGU7zuXeG5FaZaVlrkDfAD5QmLMIZ+ygOtkSDfA7U68 HSbM=
X-Gm-Gg: ASbGncvwyvBW1uOUCCmeO3K08cOSLOySM218dyDZmOYXN6ylvd+ewO7vJWk5N/HYBM2 mYvIuFpGq0JeOoaqPYThOricr1kLT2/ribY38dx0z/5QRI3LCUYRCzlFNASlW6sFjhuikW/N3nl RkjnXZWrNWB2b8w1c2jLa8PYJUkGow0yyiSUg/Xl55dEWqSw0pdurnuXVGyOU1Ac28VF18xZYM8 kDlIxdmbFg2aNKFV1j3acHAvTgVGEDGzaY10lg0pLORIZZa3/kdnZUWpWHvgZ1lvrVaAzCHtVIq Sqp2R7uvJOl79z5KPZuuaNu+8cmVOccfnKKOYdfEXBmCUGY=
X-Google-Smtp-Source: AGHT+IHllyospxs6HgEIGezrCb0FsDUsL7GyjcttxCVzpdCANwFP4qUw0A2CbQUmoaMtfsFT325Nng==
X-Received: by 2002:a05:620a:404a:b0:7c0:a0ba:2029 with SMTP id af79cd13be357-7c247fcbc16mr312770785a.40.1740534799339; Tue, 25 Feb 2025 17:53:19 -0800 (PST)
Received: from smtpclient.apple ([2600:4040:252a:8d00:f43f:d972:5be3:bc15]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7c23c299294sm183078685a.17.2025.02.25.17.53.17 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Feb 2025 17:53:18 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3FAF92C2-3111-4236-B4FA-ECC896B77C36"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Tue, 25 Feb 2025 20:52:57 -0500
References: <10A06A24-8126-47B9-B187-55F4288DBBF2@sn3rd.com>
To: TLS List <tls@ietf.org>
In-Reply-To: <10A06A24-8126-47B9-B187-55F4288DBBF2@sn3rd.com>
Message-Id: <8905AC0A-D728-42C3-857F-64F8BC4E63C6@sn3rd.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: 74CEDNTEYUWXK5X5QHSWVFC2MPCK6RV5
X-Message-ID-Hash: 74CEDNTEYUWXK5X5QHSWVFC2MPCK6RV5
X-MailFrom: sean@sn3rd.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: PQ Cipher Suite I-Ds: adopt or not?
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/KMOTm_lE5OIAKG8_chDlRKuav7c>
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>

<!--- Responding to my own message here that started the thread. --->

Hi! The chairs gathered a lot of information from this thread. Thanks for that. We have also noted PQ-related discussions in other WGs. Based on all of this, Joe and I [0] are going to begin to issue WG calls for adoption in this order one roughly right after the after:

- draft-kwiatkowski-tls-ecdhe-mlkem
 <https://datatracker.ietf.org/doc/draft-kwiatkowski-tls-ecdhe-mlkem/>- draft-connolly-tls-mlkem-key-agreement
 <https://datatracker.ietf.org/doc/draft-connolly-tls-mlkem-key-agreement/>- draft-tls-westerbaan-mldsa
 <https://datatracker.ietf.org/doc/html/draft-tls-westerbaan-mldsa-00>- draft-reddy-tls-slhdsa
 <https://datatracker.ietf.org/doc/draft-reddy-tls-slhdsa/>- draft-reddy-tls-composite-mldsa

 <https://datatracker.ietf.org/doc/draft-reddy-tls-composite-mldsa/>This is our plan for a couple of reasons:
1. “Harvest now, decrypt later” seems to be the pressing need
2. Community support
3. Not wanting to moderate all the discussions (**cough fights**) all at once

A couple of things worth noting:

1. Individual I-Ds are a starting point; the I-D does not need to be perfect before it is adopted
2. Working I-Ds are under change control of the WG
3. These I-Ds specify code points (some are already assigned), but they do not specify mandatory-to-implement algorithms for TLS; see rfc8446/-rfc8446bis
4. Let’s keep it civil while we proceed

Stay tuned.

Cheers,
Joe and Sean

[0] In case you are wondering why we are not including Deirdre here, Deirdre has one of the I-Ds under discussion.

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