[TLS] Re: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt
Thom Wiggers <thom@thomwiggers.nl> Tue, 03 March 2026 08:18 UTC
Return-Path: <thom@thomwiggers.nl>
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 C3819C34246D for <tls@mail2.ietf.org>; Tue, 3 Mar 2026 00:18: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.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=thomwiggers.nl
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 EGmTUzutrvDk for <tls@mail2.ietf.org>; Tue, 3 Mar 2026 00:18:21 -0800 (PST)
Received: from mail-ed1-x543.google.com (mail-ed1-x543.google.com [IPv6:2a00:1450:4864:20::543]) (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 0FA94C342465 for <tls@ietf.org>; Tue, 3 Mar 2026 00:18:21 -0800 (PST)
Received: by mail-ed1-x543.google.com with SMTP id 4fb4d7f45d1cf-65bfc858561so433243a12.2 for <tls@ietf.org>; Tue, 03 Mar 2026 00:18:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thomwiggers.nl; s=google; t=1772525900; x=1773130700; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=m7HK1rQOmi1rSA+B9SPOa/kEgeCt7i0VzrfGiBoOKSw=; b=d6zzACekZUVr0rbOR7levKICDpdOBtEe9UMF8jGpKobjW0D7ljha3Zyk8DUaF0R8m+ PUjECK9TBxtKVNWFx1Qk24yN3POTCM6YilpUT4yQktGd8C/Jji8yOqjqIsQevNNchiTA pDaRgdHJ8mJiNmCDPZ9Ah/pgdTVSa4VL3vYLc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772525900; x=1773130700; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=m7HK1rQOmi1rSA+B9SPOa/kEgeCt7i0VzrfGiBoOKSw=; b=Ha7ZCf6dCS+DDCrKMUgnghDtzX4lQp73vG6W7DsYQgkXHY4LfpJgt6h/lXeu7+zeii Gb/D2OHf7ItjaBXk/QTu4HTe8jStYFgVd6109HJhmTyV9/zkfxGlGrGlXTANVw96SIhK 2TBJhv678Wjgj4jLsSmhHlarDxg2C6Cdrz5INsexliOMyuDLFfqJlZoWVvkzlPsGl6pK HC0hm6W5/myygYEnKvxEDeghkqEvJBLpMf7GC9h2K/H0nmCZGvdWyQpDkXdckRr7jYJ0 LltVfsjndKl+j6OE7BjhgokpIVZbllWs1p6nz0LZeEi99v46961M0NTkJ9bJdbZmAOsi 4mXg==
X-Forwarded-Encrypted: i=1; AJvYcCWrDWPcDJYEXMhAAW5egH0WSWomoiELdsiPjTqYZzrUsB9w6iLiHZZojlLwoZdz9VSqwkw=@ietf.org
X-Gm-Message-State: AOJu0YxSQcIrq2Q9/mH68p4Fh2DGO/iFMCIcODRX/e0wLmLiFksxM9dn LmbvlcjoH2aRqEGG/pF7dCnEWOQchKph2iNSHB0JLQGNBWXEhqlC4lidwaWD4vA274w=
X-Gm-Gg: ATEYQzznUmIHp2hbgfHF3JlYxAkWsWHaHo9NHLfNjKKoy4FhOFLcIupVuhPsKN3YbpM Uzq6GDTTIQTJ2a2Ly49rUgkd1UqHnrnsPZkMtlWulEezLagHr8nQcU9iHI3xpHsqQNMfPY5AM3f 6GJSaRnu18nECtTVutiLnJikC5xUfMYOop11W0+KBsKVKSkIDfgvnZjRf5uBj4xbtUnTFBijzcf HmeqHl+q+ys1Ok31IadlrgJ0h4LLXFdDeIecyzhvDmWIuzopFOlJ7XJ1MgYo5XW9HetBb8EuUbl cZLKcnRgyxEe2lxTlMh4AZteAQkT7VDpp8+KIO9obqMn/ZGM1+zQKITNY3qkfhVyDq4oRHLoBwn GTLRfThqmmFO0hhoQa4dsngTKBAVYaKMOS1kF/YjXpLbTuHpNlkAnbyaNLpxs31xYZyH2t6dWGo uBYuK6dYQXUT3TzlZROoIRpvfhUtKcpsw+g03D+YFa7BMDdI1j83myG2mHra3Wg1oqwkhftSNRb xgmMmALiA==
X-Received: by 2002:a05:6402:3707:b0:660:a23d:4666 with SMTP id 4fb4d7f45d1cf-660a23d4830mr948499a12.18.1772525899843; Tue, 03 Mar 2026 00:18:19 -0800 (PST)
Received: from smtpclient.apple (63-164-187-31.ftth.glasoperator.nl. [31.187.164.63]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-660a96af982sm123323a12.26.2026.03.03.00.18.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Mar 2026 00:18:19 -0800 (PST)
From: Thom Wiggers <thom@thomwiggers.nl>
Message-Id: <2BE41DD1-CA32-40C8-B2CF-C510140E5E0C@thomwiggers.nl>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9021D1CF-9ECD-41AA-B95D-E7BCBC4D967C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Date: Tue, 03 Mar 2026 09:18:08 +0100
In-Reply-To: <CAF8qwaAFY+qyGiV1g89fVMpqT5fSQ6zBEY1-BO4rmLH+Sy+z7g@mail.gmail.com>
To: David Benjamin <davidben@chromium.org>
References: <177189438640.2182161.16660142956175423236@dt-datatracker-6ff7c68975-7k42g> <CAL02cgTob3hYSMmhOgiMiUZu0MfLRM-hV-4zQeAXp3Su=7ckCw@mail.gmail.com> <aaV7geNZYrfmPXpP@LK-Perkele-VII2.locald> <MN2PR17MB40314145C7826B303186845CCD7EA@MN2PR17MB4031.namprd17.prod.outlook.com> <CAF8qwaAFY+qyGiV1g89fVMpqT5fSQ6zBEY1-BO4rmLH+Sy+z7g@mail.gmail.com>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: 3WHU2HWNDFGE3SMHDKPQ4V6OCTOFHDYJ
X-Message-ID-Hash: 3WHU2HWNDFGE3SMHDKPQ4V6OCTOFHDYJ
X-MailFrom: thom@thomwiggers.nl
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: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "<tls@ietf.org>" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt
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/o4QEuXW2nvbFrYiYenZwXy4_eEQ>
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>
As another data point on this, the following is a direct quote from the UK NCSC’s guidance on PQC migration: > These algorithms will need to be implemented in protocols before they can be used on the internet and in other networks. The IETF is in the process of updating the most widely-used security protocols. This includes ensuring that PQC algorithms can be incorporated into key exchange and signature mechanisms in existing protocols such as TLS and IPsec. IETF implementations of post-quantum protocols are subject to change until they are published as RFCs. The NCSC strongly advises that operational systems should use protocol implementations based on RFCs, not on Internet Drafts. https://www.ncsc.gov.uk/whitepaper/next-steps-preparing-for-post-quantum-cryptography, (emphasis theirs) I have a mild preference for not spending lots of time on every possible code point that people might require, but I do strongly feel that we need an “end state” for “this-draft-exists-just-for-a-code-point” that is better than “expired I-D”. Otherwise we’re not believable to external SDOs and regulators. Regards, Thom Wiggers > Op 2 mrt 2026, om 18:13 heeft David Benjamin <davidben@chromium.org> het volgende geschreven: > > > That the endorsement of the IETF matters to so many continues to surprise me. Not a whole lot, but the way that symbolic measures like this act as a substitute for good judgment is one of the great mysteries. > > I'd echo Ben's comments earlier in the thread. While there are certainly silly reasons, the reason Ben cites is more than symbolic. For someone implementing and deploying something, an immutable codepoint isn't sufficient. It's also important to know that the feature is "done" and that the TLS community isn't going to next week define a new codepoint that flips the order of the key shares or whatever. (E.g. the many iterations that led to the final version of ECH.) > > This is critical for the health of the TLS ecosystem. Sure, the big deployments and early movers can move fast, ship experiments, unship them, etc. But if we want TLS to be accessible to the broader internet, we need to keep others in mind. Others are less able to unship things they once shipped. But if every draft iteration of ECH had to survive in TLS libraries because people can't unship them, we would never get anywhere. That means there's a crucial milestone when a TLS feature is safe to ship in more durable contexts, and we need to actually be able to get to those milestones. > > For that to happen, for TLS to serve more than just the major players, the TLS community needs a venue to coordinate on work, roughly agree on when this milestone has been reached, and actually reach that milestone. Historically, that venue has been the TLS WG. > > Moreover, when the milestone is reached, there also needs to be a clear indication of this. Those of us here, paying attention to the group and sifting the through the atmosphere, know the status of things. But TLS touches more people than this group. I work with many, many groups who integrate TLS into their projects. They have the rest of their project to worry about and can't follow the WG. But they need to know, when evaluating X, whether X is ready or not for them. Historically, that indicator has been document publication. > > All this is certainly imperfect, even historically. (E.g. the long time between something being "done" and a final RFC increases the window of uncertainty for folks. And of course this venue can be a bit abrasive.) Unfortunately, this WG has trended even more towards those imperfections, so here we are. These kinds of cryptography drafts seem to be the extreme case, where there is some coordination needed, but it is minimal in comparison to the problems it triggers here. > > Perhaps this WG needs to have fewer responsibilities, as this draft suggests, before it can reverse this trend. But that won't change the need for the coordination work somewhere, and I don't think we should be proud of producing an atmosphere where we need to actively drive that work to other venues. > > On Mon, Mar 2, 2026 at 8:46 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org <mailto:40akamai.com@dmarc.ietf.org>> wrote: >> - TLS Exporter Labels >> - TLS SSLKEYLOGFILE Labels >> - TLS Certificate Types >> - TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs >> - TLS Certificate Compression Algorithm IDs >> >> Most of the entries for registrations in these tables have come from documents that were NOT adopted by the TLS WG. Sometimes other WG drafts, sometimes (mainly ALPN) just using the IANA form. >> _______________________________________________ >> TLS mailing list -- tls@ietf.org <mailto:tls@ietf.org> >> To unsubscribe send an email to tls-leave@ietf.org <mailto:tls-leave@ietf.org> > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-leave@ietf.org
- [TLS] Fwd: New Version Notification for draft-bar… Richard Barnes
- [TLS] Re: Fwd: New Version Notification for draft… Eric Rescorla
- [TLS] Re: Fwd: New Version Notification for draft… Deirdre Connolly
- [TLS] Re: Fwd: New Version Notification for draft… Eric Rescorla
- [TLS] Re: Fwd: New Version Notification for draft… Deirdre Connolly
- [TLS] Re: Fwd: New Version Notification for draft… Eric Rescorla
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Eric Rescorla
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Richard Barnes
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: Fwd: New Version Notification for draft… Nadim Kobeissi
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Nadim Kobeissi
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Muhammad Usama Sardar
- [TLS] Re: Fwd: New Version Notification for draft… Bellebaum, Thomas
- [TLS] Re: Fwd: New Version Notification for draft… Stephen Farrell
- [TLS] Re: Fwd: New Version Notification for draft… Toerless Eckert
- [TLS] Re: Fwd: New Version Notification for draft… Eric Rescorla
- [TLS] Re: Fwd: New Version Notification for draft… Toerless Eckert
- [TLS] Re: Fwd: New Version Notification for draft… Viktor Dukhovni
- [TLS] Re: Fwd: New Version Notification for draft… Eric Rescorla
- [TLS] Re: Fwd: New Version Notification for draft… Viktor Dukhovni
- [TLS] Re: Fwd: New Version Notification for draft… Deirdre Connolly
- [TLS] Re: Fwd: New Version Notification for draft… Bellebaum, Thomas
- [TLS] Re: Fwd: New Version Notification for draft… Deirdre Connolly
- [TLS] Re: Fwd: New Version Notification for draft… Bellebaum, Thomas
- [TLS] Re: Fwd: New Version Notification for draft… Toerless Eckert
- [TLS] Re: Fwd: New Version Notification for draft… Viktor Dukhovni
- [TLS] Re: Fwd: New Version Notification for draft… Muhammad Usama Sardar
- [TLS] Re: Fwd: New Version Notification for draft… Rob Sayre
- [TLS] Re: Fwd: New Version Notification for draft… John Mattsson
- [TLS] Re: Fwd: New Version Notification for draft… Watson Ladd
- [TLS] Re: Fwd: New Version Notification for draft… John Mattsson
- [TLS] Re: Fwd: New Version Notification for draft… Muhammad Usama Sardar
- [TLS] Re: Fwd: New Version Notification for draft… Felix Linker
- [TLS] Re: New Version Notification for draft-barn… Nadim Kobeissi
- [TLS] Re: New Version Notification for draft-barn… John Mattsson
- [TLS] Re: New Version Notification for draft-barn… Richard Barnes
- [TLS] Re: [E] Re: New Version Notification for dr… Choyi, Vinod Kumar
- [TLS] Re: Fwd: New Version Notification for draft… Paul Wouters
- [TLS] Re: Fwd: New Version Notification for draft… Rob Sayre
- [TLS] Re: Fwd: New Version Notification for draft… Ben Schwartz
- [TLS] Re: Fwd: New Version Notification for draft… Rob Sayre
- [TLS] Re: Fwd: New Version Notification for draft… Daniel Van Geest
- [TLS] Re: Fwd: New Version Notification for draft… Stephen Farrell
- [TLS] Re: Fwd: New Version Notification for draft… Simon Josefsson
- [TLS] Re: Fwd: New Version Notification for draft… Martin Thomson
- [TLS] Re: Fwd: New Version Notification for draft… Ilari Liusvaara
- [TLS] Re: Fwd: New Version Notification for draft… Salz, Rich
- [TLS] Re: Fwd: New Version Notification for draft… David Benjamin
- [TLS] Re: New Version Notification for draft-barn… Thom Wiggers
- [TLS] Re: Fwd: New Version Notification for draft… DA PIEVE Fabiana
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: Fwd: New Version Notification… Nadim Kobeissi
- [TLS] Re: Fwd: New Version Notification for draft… John Mattsson