RFC 9849 specifies the TLS Encrypted Client Hello (ECH) mechanism, which encrypts the ClientHello message under a server public key to prevent metadata leakage. The spec details how a client-facing server processes incoming ECH extensions: it collects candidate ECHConfig values, attempts decryption using HPKE (SetupBaseR/context.Open), verifies cipher suite and version compatibility, and forwards the decrypted ClientHelloInner to the backend server. It also covers HelloRetryRequest handling, fallback behavior when decryption fails (including GREASE ECH), and requirements for retry_configs in EncryptedExtensions. Servers must abort with specific alerts for malformed or inconsistent ECH parameters.

6m read timeFrom rfc-editor.org
Post cover image
Table of contents
7.1. Client-Facing Server

Sort: