[TLS] Implementations of draft-ietf-tls-flags and draft-ietf-tls-cross-sni-resumption

2022-01-27 Thread Christopher Wood
Hi folks, In preparing to move draft-ietf-tls-flags and draft-ietf-tls-cross-sni-resumption forward in the process, I’m curious if anyone is aware of implementations of either specification. If you know of an implementation, can you please share it here? Thanks, Chris, for the chairs _

Re: [TLS] Two final DTLS 1.3 issues

2022-01-27 Thread Christopher Wood
Apologies for the delay here. The consensus call for these two issues is complete. Based on the discussion below, the chairs will work with the editors to address Martin’s feedback — which does not appear to be a blocker — before getting this back in the RPC editor’s queue. (Martin, please let u

Re: [TLS] OCSP in RFC7525bis - summary of the discussion

2022-01-27 Thread Yaron Sheffer
Thank you all for the lively and far reaching discussion on revocation and OCSP. Let me summarize how the authors of RFC7525-bis read the consensus - UTA WG chairs, please chime in if you disagree. There seems to be consensus that applications should be able to handle certificate revocation. T

Re: [TLS] OCSP in RFC7525bis - summary of the discussion

2022-01-27 Thread Viktor Dukhovni
> On 27 Jan 2022, at 4:45 pm, Yaron Sheffer wrote: > > So our plan moving forward is to essentially keep the new text on OCSP [1] > and add a reference to RFC 7633 (the certificate must-staple extension). But > only as a MAY. In addition, we will add a MUST requirement to perform (some > kind