RFC 9848 on Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings
rfc-editor@rfc-editor.org Wed, 04 March 2026 05:50 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4B8BCC3EEADA; Tue, 3 Mar 2026 21:50:12 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 1E5312BB3EA; Tue, 3 Mar 2026 21:50:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9848 on Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260304055012.1E5312BB3EA@rfcpa.rfc-editor.org>
Date: Tue, 03 Mar 2026 21:50:12 -0800
Message-ID-Hash: MDR5QTNQW2IIP55Q2I4KE5JPYGMGMJXZ
X-Message-ID-Hash: MDR5QTNQW2IIP55Q2I4KE5JPYGMGMJXZ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/PgTOfkU2aXkV_ZE1sqezr5NLDYo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9848
Title: Bootstrapping TLS Encrypted ClientHello with
DNS Service Bindings
Author: B. Schwartz,
M. Bishop,
E. Nygren
Status: Standards Track
Stream: IETF
Date: March 2026
Mailbox: ietf@bemasc.net,
mbishop@evequefou.be,
erik+ietf@nygren.org
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tls-svcb-ech-08.txt
URL: https://www.rfc-editor.org/info/rfc9848
DOI: 10.17487/RFC9848
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).
This document is a product of the Transport Layer Security Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team