I'm told (by an AD) that uta-require-tls13 is supposed to apply to all ends of 
a new protocol. 


Shrug. 


Anyway, it's much easier to make an RFC a performance specification (a trade 

term about RFPs) when the document doesn't depend upon some parties just 

ignoring the MUSTs. 


It would be better if the parties were honest and did not claim compliance with 
this draft. 






Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Uta mailing list -- uta@ietf.org
To unsubscribe send an email to uta-le...@ietf.org

Reply via email to