Hiya,
Since I was logged into the github web site (as happens
occasionally but not often) and as requested at the TLS
session, I translated the text below into github issues
in the hope that they might be included in discussion.
Links to each below.
On 28/02/2021 17:34, Stephen Farrell wrote:
On Sun, Feb 28, 2021 at 9:35 AM Stephen Farrell
wrote:
>
> - This is *much* harder to implement compared to ESNI as
>it interacts with the rest of the TLS stack/library in
>many more ways. It should be an explicit goal to reduce
>that complexity IMO and not increase it further.
>
I a
Hiya,
On 02/03/2021 21:49, David Benjamin wrote:
On Sun, Feb 28, 2021 at 12:35 PM Stephen Farrell
wrote:
- This is *much* harder to implement compared to ESNI as
it interacts with the rest of the TLS stack/library in
many more ways. It should be an explicit goal to reduce
that co
On Sun, Feb 28, 2021 at 12:35 PM Stephen Farrell
wrote:
> - This is *much* harder to implement compared to ESNI as
>it interacts with the rest of the TLS stack/library in
>many more ways. It should be an explicit goal to reduce
>that complexity IMO and not increase it further. That
>
Hiya,
I've just got my OpenSSL code "working" for draft-09.
The s_client and s_server talk to one another and do
ECH; NSS's tstclnt talks to my s_server and does ECH
and my s_client talks to cloudflare's test server and
does ECH. So this can be made work, which is the good
news. (Thanks to Marti