Are there any objections to "ECH" or should we just go with that? (I'd like to update the parameter name in SRVB/HTTPSSVC accordingly based on what gets decided.)
On Wed, May 20, 2020 at 11:37 PM Tommy Pauly <tpa...@apple.com> wrote: > ECH is good. Go for it! > > Tommy > > On May 20, 2020, at 11:34 AM, Erik Nygren <erik+i...@nygren.org> wrote: > > > > ECH works for me. (I really don't care between ECH and ETCH and thing > both are fine.) > > Erik > > > On Wed, May 20, 2020 at 2:20 PM Christopher Wood <c...@heapingbits.net> > wrote: > >> On Tue, May 19, 2020, at 8:18 PM, Filippo Valsorda wrote: >> > As a data point, I was fairly confused when ECHO came up in >> > conversation, and had to stop to ask what it was. I think I would have >> > had a better chance of figuring it out from context or search if it >> > were called ECH, but don't have a strong preference for any specific >> > name. >> > >> > ECH does have a remarkable short Wikipedia disambiguation list, FWIW. >> > https://en.wikipedia.org/wiki/ECH >> >> ECH also works for me. >> >> Best, >> Chris (no hat) >> >> _______________________________________________ >> TLS mailing list >> TLS@ietf.org >> https://www.ietf.org/mailman/listinfo/tls >> > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
