Cool. I might leave that for a different PR, but if something along those lines
seems obvious or necessary, I'll go ahead and do it.
> On Jun 23, 2021, at 4:37 PM, Martin Thomson wrote:
>
> Whatever you can do to improve the readability of this document would be
> greatly appreciated. It's
+1 to new readers! I think a chronological description would be a good
starting point, though like MT, I suspect there would be rearranging to do
afterwards that would break with a strictly chronological description.
Chris P.
On Wed, Jun 23, 2021 at 4:48 PM Stephen Farrell
wrote:
>
>
> On
On 24/06/2021 00:37, Martin Thomson wrote:
Whatever you can do to improve the readability of this document would
be greatly appreciated.
+1 though I have to admit I've really been mostly looking
at diffs at this stage - probably some new readers/coders
are needed,
S.
It's a complicated
Whatever you can do to improve the readability of this document would be
greatly appreciated. It's a complicated design and I always spend far too much
time trying to find answers to my questions. A better structure would be
appreciated.
I do find that questions aren't always about
I support adopting #443. For the server side, I have a weak preference for
#457 (2) over #313 (3) because it makes it easier to implement a complete
solution. I have not yet assessed how hard it is to implement ... perhaps
it would be best if we all tried it out in our respective stacks and report
Hi all,
I'm bringing https://github.com/tlswg/draft-ietf-tls-esni/issues/412 to the
list since it looks like we're (hopefully) getting close to the end game with
ECH.
The ECH draft is currently organized such that it describes all client behavior
and then all server behavior. Personally, I
