On Thu, Aug 18, 2022, at 7:57 PM, Martin Thomson wrote:
> On Thu, Aug 18, 2022, at 22:39, Scott Fluhrer (sfluhrer) wrote:
>> Actually, that was our original intention with this draft - to specify
>> the framework, and to have other documents specify the actual pairs.
>> However, I believe that t
On Thu, Aug 18, 2022, at 22:39, Scott Fluhrer (sfluhrer) wrote:
> Actually, that was our original intention with this draft - to specify
> the framework, and to have other documents specify the actual pairs.
> However, I believe that the sense of the working group is that they
> want this draft
Hello, Guys,
I have read the draft-ietf-tls-esni-14, and found the ECH does not protect the
SNI.
Because if the client use the outdated ECH config to encrypted the
ClientHelloInner,
it will not be decrypted by the client facing server.
In order to correct the client, the server will finish the
I investigated this issue and found that TTLS13::Client does not send
EndOfEarlyData when 0-RTT.
The transcript was invalid because it did not contain EndOfEarlyData.
By the way, I still have another question on this.
I understand that if the server has not yet received EndOfEarlyData
and it rec
> -Original Message-
> From: TLS On Behalf Of Martin Thomson
> Sent: Wednesday, August 17, 2022 7:05 PM
> To: tls@ietf.org
> Subject: Re: [TLS] WGLC for draft-ietf-tls-hybrid-design
>
> On Sat, Aug 13, 2022, at 04:13, Scott Fluhrer (sfluhrer) wrote:
> > Well, if we were to discuss some su
