RFC 9848: Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings

To use TLS Encrypted ClientHello (ECH), the client needs to learn the ECH configuration for a server before it attempts a connection to the server. This…

Read RFC 9848 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 1034: Domain names - concepts and facilities
Normative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 9364: DNS Security Extensions (DNSSEC)
Normative reference — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normative reference — RFC 9849: TLS Encrypted Client Hello
Informative reference — RFC 8792: Handling Long Lines in Content of Internet-Drafts and RFCs
Informative reference — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Informative reference — RFC 9001: Using TLS to Secure QUIC
Informative reference — RFC 7838: HTTP Alternative Services

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 9849: TLS Encrypted Client Hello
Informatively referenced by — RFC 9934: Privacy-Enhanced Mail (PEM) File Format for Encrypted ClientHello (ECH)