Paul
Thanks you for your review. I have created a PR that addresses a number of
these.
https://github.com/tlswg/draft-ietf-tls-esni/pull/632
Detailed responses below:
> Section 1
>
> that allows clients to encrypt their ClientHello to such a
deployment.
>
> What is "such a deployment"
AD review draft-ietf-tls-esni-22
Thanks for this document. It is a very interesting technology and I want
to thank everyone who worked on this. As expected, I found no major issues
in it :-) I do have a few minor questions and nits below:
Section 1
that allows clients to encrypt their C
Dear Deirdre Connolly,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
tls Session 1 (2:00 requested)
Friday, 8 November 2024, Session II 1300-1500 Europe/Dublin
Room Name: The Auditorium [Break
I've been working on support for the ML-KEM hybrid key exchanges in
tlsfuzzer[1,2], and I've noticed that the error handling is underspecified:
both key shares (client and server) and both constituent parts (pqc and
classic)
can have key shares are are invalid.
Also, the ECDH key exchange can e
