+1 on support for SHA3, NIST is really putting the thumb on the scales here with their choices of PQC algorithm. Everything is built around SHAKE as the cryptographic primitive...
On the BLAKE3 thing, the problem here is the IETF got into a position where assignment of code points is taken as an endorsement. because we are the people who dole them out (except that is actually IANA). That is a problem, but we already have policy for dealing with that problem: Let anyone with a spec get a code point without looking at the security of their proposal, just filter out duplicates. That is the right policy because after all, there is a whole rack of algorithms the WG approved in days of yore that are now considered awful. It may not be the ideal choice but it is the best available.
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
