> A new version of the document will have to be made. It will have to be on the > Montreal agenda. And then a new WGLC. Then a few weeks of discussion, > probably repeating the same arguments we are seeing now. That adds up > quickly. As opposed to saying “WGLC done, here’s the shepherd writeup, submit > to IESG” this week.
Thanks for the clarification :) So we are basically weighing the potential damage from delayed publication (and thus more non-PQ traffic) against the potential damage from faulty and more complex ECC implementations (and insecure servers and potentially less deployment should the NIST curves get more standard in hybrids, which currently seems likely due to ML-KEM1024 combos). Many voices in this LC seem to either advocate for recommendation changes or be sold on a particular set of combinations already. If the current document was able to pass WGLC, then changes to the recommended column should not change this. So why go through Montreal? Couldn't we have another WGLC tomorrow? That would just move the deadline by the duration of a LC. -- TBB ===== IETF Stuff ===== This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
