RFC 9849: TLS Encrypted Client Hello
In plain English — editorial summary, not part of the RFC
This document describes a mechanism in Transport Layer Security (TLS) for encrypting a message under a server public key.
Document record
- Document ID
- RFC9849
- Published
- March 2026
- Authors
- E. Rescorla; K. Oku; N. Sullivan; C. A. Wood
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 44
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9848Bootstrapping TLS Encrypted ClientHello with DNS Service BindingsCurrent
March 2026
- RFC 9850The SSLKEYLOGFILE Format for TLSCurrent
July 2026
- RFC 9851TLS 1.2 is in Feature FreezeCurrent
July 2026
- RFC 9847IANA Registry Updates for TLS and DTLSCurrent
December 2025
- RFC 9852New Protocols Using TLS Must Require TLS 1.3Current
July 2026
- RFC 9846The Transport Layer Security (TLS) Protocol Version 1.3Current
July 2026
- RFC 9853Return Routability Check for DTLS 1.2 and 1.3Current
March 2026
- RFC 9838Group Key Management Using the Internet Key Exchange Protocol Version 2 (IKEv2)Current
November 2025
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?