Eric Rescorla <[email protected]> writes: > On Fri, May 16, 2025 at 9:27 AM Simon Josefsson <simon= > [email protected]> wrote: > >> I support adoption -- I think it is important to have conservatively >> designed PQ-safe cryptographic algorithms (Sphincs+, Classic McEliece, >> etc) widely available as fallback. Having them available takes away >> some arguments against deploying less conservative designed PQ >> algorithms that I'm seeing. >> > > Following up on Rich and Richard, I'd like to push on what "available" means > in this context. In what way will publishing an RFC make this algorithm > more available? For instance, are there entities who will implement and/or > deploy SL-DSA in that case that would not otherwise? If so, I'd like to hear > from them.
I intend to work on both of the above for GnuTLS and would like to see RFCs for these. I hope people will deploy these extensions even if IETF block RFC publication, but getting RFCs published helps and some may have processes in place that would need to be changed to allow use of this if there is no RFC available. /Simon > -Ekr > > >> /Simon >> >> Sean Turner <[email protected]> writes: >> >> > We are continuing with our WG adoption calls for the following I-D: >> > Use of SLH-DSA in TLS 1.3 [1]; see [2] for more information about this >> > tranche of adoption calls. If you support adoption and are willing to >> > review and contribute text, please send a message to the list. If you >> > do not support adoption of this draft, please send a message to the >> > list and indicate why. This call will close at 2359 UTC on 30 May >> > 2025. >> > >> > Reminder: This call for adoption has nothing to do with picking the >> mandatory-to-implement cipher suites in TLS. >> > >> > Cheers, >> > Joe and Sean >> > >> > [1] https://datatracker.ietf.org/doc/draft-reddy-tls-slhdsa/ >> > [2] >> https://mailarchive.ietf.org/arch/msg/tls/KMOTm_lE5OIAKG8_chDlRKuav7c/ >> > _______________________________________________ >> > TLS mailing list -- [email protected] >> > To unsubscribe send an email to [email protected] >> _______________________________________________ >> TLS mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >>
signature.asc
Description: PGP signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
