I do not support adoption of this draft. tl;dr - This draft could have been an email.
In general, there are two reasons for this WG to work on new algorithms: 1. Practical necessity: The algorithm requires additional specification in order to work with TLS, or to be used properly. 2. Process necessity: The algorithm will be registered with Recommended=Y Neither is the case here. The only additional detail that the draft provides is to set the context string, but this is the default in FIPS 205 anyway. And the algorithms are registered with Recommended=N. This draft doesn't do anything that couldn't have been accomplished with an email to IANA. The "refer to an Internet-Draft" objections don't apply, because FIPS 205 is a nice formal stable reference that says everything that is necessary. Just request code points that point to FIPS 205 and move on. This could have been done months ago instead of still being on the WG's agenda. Massive waste of time. --Richard On Tue, Jul 15, 2025 at 12:07 AM Sean Turner <[email protected]> wrote: > We kicked off an adoption call for Use of SLH-DSA in TLS 1.3; see [0]. We > called consensus [1], and that decision was appealed. We have reviewed the > messages and agree that we need to redo the adoption call to get more input. > > What appears to be the most common concern, which we will take from Panos' > email, is that "SLH-DSA sigs are too large and slow for general use in TLS > 1.3 applications". One way to address this concern is to add an > applicablity statement to address this point. We would like to propose that > this (or something close to this) be added to the I-D: > > Applications that use SLH-DSA need to be aware that the signatures sizes > are large; the signature sizes for the cipher suites specified herein range > from 7,856 to 49,856 bytes. Likewise, the cipher suites are considered > slow. While these costs might be amoritized over the cost of a long lived > connection, the cipher suites specified herein are not considered for > general use in TLS 1.3. > > With this addition in mind, we would like to start another WG adoption > call for draft-reddy-tls-slhdsa. If you support adoption with the above > text (or something similar) and are willing to review and contribute text, > please send a message to the list. If you do not support adoption of this > draft with the above text (or something similar), please send a message to > the list and indicate why. This call will close at 2359 UTC on 28 July 2025. > > Cheers, > Deirdre, Joe, and Sean > > [0] https://mailarchive.ietf.org/arch/msg/tls/o4KnXjI-OpuHPcB33e8e78rACb0/ > [1] https://mailarchive.ietf.org/arch/msg/tls/hhLtBBctK5em6l82m7rgM6_hefo/ > [2] https://datatracker.ietf.org/doc/draft-reddy-tls-slhdsa/ > _______________________________________________ > 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]
