Hi Rich! I am sympathetic to how long this has taken and share responsibility in that. More inline ...
> -----Original Message----- > From: Salz, Rich <[email protected]> > Sent: Wednesday, June 3, 2020 12:32 PM > To: Roman Danyliw <[email protected]>; [email protected] > Subject: Re: [Trans] Summary of DISCUSS items for draft-ietf-trans-rfc6962-bis > > > o An Online Certificate Status Protocol (OCSP) [RFC6960] response > > extension (see Section 7.1.1), where the OCSP response is provided > > in the "CertificateStatus" message, provided that the TLS client > > included the "status_request" extension in the (extended) > > "ClientHello" (Section 8 of [RFC6066]). [...] > > > > This is not quite a TLS 1.3-compliant formulation -- TLS 1.3 does not > use the > > "CertificateStatus message", but rather uses the encoding of that > structure > in a > > status_request extension in the CertificateEntry. > > draft-ietf-trans-rfc6962-bis > > I haven't seen discussion of Ben's DISCUSS feedback > > Oh come on now. > > This draft has sat with no action for a very long time, and now someone is > supposed to rouse the authors, and the working group, to address a new RFC > that didn't exist (drafts did, yes). I'm happy to process with this document in whatever way the working group wants. It is the one thing keeping the group open. > Compare the timelines of the two documents. Do you mean the telechat date of this document vs. RFC8466? I'm not following the thinking as the final publication of TLS 1.3 predates the original telechat review of this document by a number of months. Should this have been found earlier, perhaps. ** Ben's DISCUSS = 03/13/2019 for the 03/14/2019 telechat ** RFC8466 = 08/2018 > Close the group, and let the draft lie or publish the damn thing. What's > going > on now is just cruel. We can't publish it without clearing the final two discusses. I appreciate the authors clearing Alissa, Mirja and Adam DISCUSS points in with -32, -33 and -34. Roman _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
