On Fri, May 1, 2020, at 14:51, Martin Thomson wrote:
> Thanks to some good work from Felix Günther, Marc Fischlin, Christian
> Janson, and Kenny Paterson we now have a new result to share about the
> integrity limits in QUIC.
>
> There is a long write-up in
> https://github.com/quicwg/base-draf
Erik raises some compelling reasons to change the name from ECHO to...
something else less confusing or misleading [1]. Candidates from the PR include
ETCH (Encrypted TLS Client Hello), ECH, and EHELLO. Since the HTTPSSVC draft
aims for WGLC before IETF 108, it would be good if we got this bikes
ECHO is more fun to say, but I do see how it can be confusing (sounding like
some sort of ping) when out of the context of TLS.
To that end, I’d have a minor preference for “ETCH”.
Thanks,
Tommy
> On May 7, 2020, at 3:52 PM, Christopher Wood wrote:
>
> Erik raises some compelling reasons to c
On 07/05/2020 23:52, Christopher Wood wrote:
> Erik raises some compelling reasons to change the name from ECHO
> to... something else less confusing or misleading [1]. Candidates
> from the PR include ETCH (Encrypted TLS Client Hello), ECH, and
> EHELLO. Since the HTTPSSVC draft aims for WGLC be
'ELLO
On Thu, May 7, 2020 at 7:03 PM Tommy Pauly
wrote:
>
> ECHO is more fun to say, but I do see how it can be confusing (sounding like
> some sort of ping) when out of the context of TLS.
>
> To that end, I’d have a minor preference for “ETCH”.
>
> Thanks,
> Tommy
>
> > On May 7, 2020, at 3:52
Agree with Tommy, but don't care all that much if another gets consensus.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
+1 on sooner rather than later
tim
terrible at picking colors
On Thu, May 7, 2020 at 7:06 PM Stephen Farrell
wrote:
>
>
> On 07/05/2020 23:52, Christopher Wood wrote:
> > Erik raises some compelling reasons to change the name from ECHO
> > to... something else less confusing or misleading [1].
On Thu, May 07, 2020 at 03:52:43PM -0700, Christopher Wood wrote:
> Erik raises some compelling reasons to change the name from ECHO to...
> something else less confusing or misleading [1]. Candidates from the
> PR include ETCH (Encrypted TLS Client Hello), ECH, and EHELLO. Since
> the HTTPSSVC dr
> On May 7, 2020, at 19:03, Tommy Pauly
> wrote:
>
> To that end, I’d have a minor preference for “ETCH”.
If we could just work an “a" and “sketch” into the name … I am all in.
More seriously, let’s knock this decision out by end of next week, i.e., the
15th.
spt
__
