> Hopefully, some of the people who did the analyses will > chime in on the WGLC though, it'd be good if they had the > time to do that.
I am not sure this specific case was covered in our analysis, but I will confer with our co-authors. Best, Karthik > > Cheers, > S. > >> thanks, >> Rob >> On Mon, Mar 11, 2024 at 6:12 PM Stephen Farrell <stephen.farr...@cs.tcd.ie> >> wrote: >>> >>> >>> On 12/03/2024 00:49, Rob Sayre wrote: >>>> On Mon, Mar 11, 2024 at 5:21 PM Christopher Patton < >>> cpat...@cloudflare.com> >>>> wrote: >>>> >>>>> I don't believe there were any changes from draft 13 to 18 that would >>>>> invalidate security analysis for draft 13: >>>>> >>>>> >>> https://author-tools.ietf.org/iddiff?url1=draft-ietf-tls-esni-13&url2=draft-ietf-tls-esni-18&difftype=--html >>>>> >>>> >>>> Hmm. It does look like there are few substantial changes in that diff >>> that >>>> might be worth re-checking, but I'm not trying to delay things with >>>> nitpicking. If others feel the analysis of -13 is enough, then let's go. >>> >>> Not quite answering the question, but I don't recall any code >>> changes affecting the crypto plumbing or interop since -13. >>> >>> Cheers, >>> S. >>> >>>> >>>> thanks, >>>> Rob >>>> >>>> >>>> _______________________________________________ >>>> TLS mailing list >>>> TLS@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tls >>> > <OpenPGP_0xE4D8E9F997A833DD.asc>_______________________________________________ > TLS mailing list > TLS@ietf.org <mailto:TLS@ietf.org> > https://www.ietf.org/mailman/listinfo/tls
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
