> If anything, that's a symptom of the web browser monoculture and the > fact that people interested in conformance prefer deploying RFCs, not I-Ds
Two counterarguments: 1. Many libraries rely on OpenSSL, and openssl s_client google.com:443 will happily negotiate X25519MLKEM768 for me. I believe this could have significant impact. 2. There is no RFC currectly, and neither is there a *guarantee* that this I-D is stable. -- 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]
