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 before IETF 108, it > would be good if we got this bikeshedding out of the way now. To that > end, if you have an opinion on the name and whether or not we should > change it, please share it!
I don't care as long as it's decided asap. S > > Thanks, Chris (no hat) > > [1] https://github.com/tlswg/draft-ietf-tls-esni/issues/232 > > _______________________________________________ TLS mailing list > TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls >
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
