The concept does indeed solve an important problem, but also introduces a new dependency in an environment that uses explicit proxies (mostly enterprise networks). In that environment this proposal, alongside ECH, introduces DNS queries at the TLS client endpoint where previously the DNS control point was limited to the proxy. It would be good to mention that in the document.
—Roelof > On May 3, 2024, at 6:09 PM, David Benjamin <david...@chromium.org> wrote: > > Unsurprisingly, I support adoption. :-) > > On Fri, May 3, 2024 at 6:05 PM Joseph Salowey <j...@salowey.net > <mailto:j...@salowey.net>> wrote: >> This is a working group call for adoption for >> draft-davidben-tls-key-share-prediction. This document was presented at IET >> 118 and has undergone some revision based on feedback since then. The >> current draft is available here: >> https://datatracker.ietf.org/doc/draft-davidben-tls-key-share-prediction/. >> Please read the document and indicate if and why you support or do not >> support adoption as a TLS working group item. If you support adoption >> please, state if you will help review and contribute text to the document. >> Please respond to this call by May 20, 2024. >> >> Thanks, >> >> Joe, Deidre, and Sean >> _______________________________________________ >> TLS mailing list >> TLS@ietf.org <mailto: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
