I do support adoption, but the agree that the IANA registrations should already have been done. OpenSSL 3.5 has already shipped with the Values 0x0911 – 0x91C that are in the draft. What are the authors waiting on?
From: Filippo Valsorda <fili...@ml.filippo.io> Date: Monday, 19 May 2025 at 11:36 To: Richard Barnes <r...@ipv.sx> Cc: TLS List <tls@ietf.org> Subject: [TLS] Re: WG Adoption Call for Use of SLH-DSA in TLS 1.3 2025-05-16 17:46 GMT+02:00 Richard Barnes <r...@ipv.sx<mailto:r...@ipv.sx>>: It would also be useful to understand why an RFC adds value over just having an IANA code point. Since the registry is Specification Required and FIPS 205 exists, someone could send email to IANA today and get code points as soon as Yoav/Rich/Nick response to email. Indeed. I don't support adoption and would like to see this alternative path get better use: register a codepoint, deploy it, and then if appropriate come back with adoption and performance data for a Recommended = Y RFC. I will note that to make that path viable we need to collectively agree not to make backwards-incompatible changes (without assigning a new codepoint) to things that have non-experimental IANA codepoints, otherwise deployments will always want an RFC for stability.
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
