RFC 9848: Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings
In plain English — editorial summary, not part of the RFC
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 specification provides a mechanism for conveying the ECH configuration information via DNS, using a SVCB or HTTPS resource record (RR).
Document record
- Document ID
- RFC9848
- Published
- March 2026
- Authors
- B. Schwartz; M. Bishop; E. Nygren
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9540Discovery of Oblivious Services via Service Binding RecordsCurrent
February 2024
- RFC 9952Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLSCurrent
March 2026
- RFC 9460Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)Current
November 2023
- RFC 9849TLS Encrypted Client HelloCurrent
March 2026
- RFC 9847IANA Registry Updates for TLS and DTLSCurrent
December 2025
- RFC 9846The Transport Layer Security (TLS) Protocol Version 1.3Current
July 2026
- RFC 9850The SSLKEYLOGFILE Format for TLSCurrent
July 2026
- RFC 9851TLS 1.2 is in Feature FreezeCurrent
July 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?