>I don't understand why the SDOs need this beyond what's in IANA. Maybe TLS WG should send an LS and ask them. AFAIK, 3GPP, GSMA, ETSI, O-RAN Alliance, ISO/IEC, IEEE, and the Broadband Forum all require RFCs for normative references. The TLS WG has already received LSs from ETSI and GSMA requesting PQC RFCs, and 3GPP is currently considering sending a LS to TLS WG requesting PQC RFCs as well.
John From: Watson Ladd <[email protected]> Date: Tuesday, 24 February 2026 at 08:15 To: John Mattsson <[email protected]> Cc: Richard Barnes <[email protected]>, <[email protected]> Subject: Re: [TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt On Mon, Feb 23, 2026 at 10:55 PM John Mattsson <[email protected]> wrote: > > Hi, > > I think people have very different views on what constitutes “unnecessary > work.” For many external SDOs, the TLS WG producing RFCs for NIST FIPS > 203–205 is by far the most important work the TLS WG has undertaken since RFC > 8446. This is reinforced by several liaison statements the TLS WG has > received. I don't understand why the SDOs need this beyond what's in IANA. > > The first goal of the TLS WG is to “improve the applicability and suitability > of the TLS family of protocols for use in emerging protocols and use cases.” > > ISE or AD sponsorship could be a solution. However, there has been > significant frustration when attempting to register algorithms for SSH, with > some arguing that a working group is required. > > Ironically, I think draft-barnes-tls-this-could-have-been-an-email-00 could > have been an email. No it couldn't have been. The whole point is to have a record of group consensus to say "we don't do this, we do that for these reasons" > > Cheers, > John > > From: Richard Barnes <[email protected]> > Date: Tuesday, 24 February 2026 at 01:56 > To: > <[email protected]> > Subject: [TLS] Fwd: New Version Notification for > draft-barnes-tls-this-could-have-been-an-email-00.txt > > Hi TLS folks, > > Those who have worked with me know that I hate doing unnecessary work. It > occurred to me that the TLS WG has been doing a lot of unnecessary work on > drafts that just register crypto algorithms. This draft proposes that we > shouldn't do that. > > Submitted for your consideration, > --Richard > > ---------- Forwarded message --------- > From: <[email protected]> > Date: Mon, Feb 23, 2026 at 2:53 PM > Subject: New Version Notification for > draft-barnes-tls-this-could-have-been-an-email-00.txt > To: Richard Barnes <[email protected]> > > > A new version of Internet-Draft > draft-barnes-tls-this-could-have-been-an-email-00.txt has been successfully > submitted by Richard Barnes and posted to the > IETF repository. > > Name: draft-barnes-tls-this-could-have-been-an-email > Revision: 00 > Title: Stop Doing Cryptographic Algorithm Drafts when Email to IANA is All > You Need > Date: 2026-02-24 > Group: Individual Submission > Pages: 5 > URL: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-barnes-tls-this-could-have-been-an-email-00.txt&data=05%7C02%7Cjohn.mattsson%40ericsson.com%7Ce7a0fb2ffd92449d223b08de73748ba1%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639075141546292700%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uhqiZgwN0yvA2IQiJXaSYBHbnDtNb49QSMqAitHGn9Y%3D&reserved=0<https://www.ietf.org/archive/id/draft-barnes-tls-this-could-have-been-an-email-00.txt> > Status: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-barnes-tls-this-could-have-been-an-email%2F&data=05%7C02%7Cjohn.mattsson%40ericsson.com%7Ce7a0fb2ffd92449d223b08de73748ba1%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639075141546319676%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2v6p%2Fo30u8TBO2NdOzl6t4LioonDu%2FqmnNOzqfWK46s%3D&reserved=0<https://datatracker.ietf.org/doc/draft-barnes-tls-this-could-have-been-an-email/> > HTML: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-barnes-tls-this-could-have-been-an-email-00.html&data=05%7C02%7Cjohn.mattsson%40ericsson.com%7Ce7a0fb2ffd92449d223b08de73748ba1%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639075141546331983%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=9l%2F7OoNd9JTBIyBN8T653M6RwAKqdxH4jJc7dAXAzSE%3D&reserved=0<https://www.ietf.org/archive/id/draft-barnes-tls-this-could-have-been-an-email-00.html> > HTMLized: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-barnes-tls-this-could-have-been-an-email&data=05%7C02%7Cjohn.mattsson%40ericsson.com%7Ce7a0fb2ffd92449d223b08de73748ba1%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639075141546342479%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3Wnw7XqTM%2FBUcBDr3pUBiGJNonCQt3iKL4MiEFVTIyE%3D&reserved=0<https://datatracker.ietf.org/doc/html/draft-barnes-tls-this-could-have-been-an-email> > > > Abstract: > > People keep pitching drafts to the TLS Working Group where the only > thing the draft does is register a code point for a cryptographic > algorithm. Stop doing that. It's unnecessary. Write an email to > IANA instead. > > > > The IETF Secretariat > > > _______________________________________________ > TLS mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Astra mortemque praestare gradatim
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
