Are you referring to this text in 6.1.6 or something else? "If none of the values provided in "retry_configs" contains a supported version, or an earlier TLS version was negotiated, the client can regard ECH as securely disabled by the server, and it SHOULD retry the handshake with a new transport connection and ECH disabled."
-Ekr On Mon, Sep 19, 2022 at 11:20 AM Safe Browsing <safebrowsing...@gmail.com> wrote: > Good day, > > The ECH draft describes a method for securely disabling ECH - at the cost > of an extra round trip. Is there a client and server implementation that > supports this functionality already - securely disabling ECH? > > SB > _______________________________________________ > 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
