Protocol Action: 'TLS Client Authentication via DANE TLSA records' to Proposed Standard (draft-ietf-dance-client-auth-17.txt)
The IESG <iesg-secretary@ietf.org> Thu, 05 November 2026 16:18 UTC
Received: by mx.ietf.org (Postfix) id 1A1195A; Thu, 05 Nov 2026 16:18:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1793895523; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=8bqgsW0ujvRDZEwofNN6ZBoClfcFOXg5EtqoWpvk22c=; b=b92pTh4urYhatZv8KqimSVyJCo78sS+obED9bsPcl3E4L818nCiwmnZ6B9KkhTWZeqSZ3S g8h9ND3u1ziPzNZH0pFFON5EAHdxriLg9OkqpXonk/FoJ3BKUIElQEJVn76ZIUsVfsintr E3JXeUeEpUoKkmsKys8J2VXNII6dWSU=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=iesg-secretary@ietf.org
Received: from [10.244.9.51] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 9F6EB13B91D6D; Thu, 5 Nov 2026 08:18:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'TLS Client Authentication via DANE TLSA records' to Proposed Standard (draft-ietf-dance-client-auth-17.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.82.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179389552259.1504190.6645943024050760978@dt-datatracker-7dc874ff8f-sl5zv>
Date: Thu, 05 Nov 2026 08:18:42 -0800
Message-ID-Hash: 4WMVNZF5R2DYZBHFKFSKPKNHZVOU6IRU
X-Message-ID-Hash: 4WMVNZF5R2DYZBHFKFSKPKNHZVOU6IRU
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf-announce.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, dance-chairs@ietf.org, dance@ietf.org, draft-ietf-dance-client-auth@ietf.org, mcr+ietf@sandelman.ca, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3CToJbaCyVhv3D6X4MucH-cjZYw>
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>
The IESG has approved the following document: - 'TLS Client Authentication via DANE TLSA records' (draft-ietf-dance-client-auth-17.txt) as Proposed Standard This document is the product of the DANE Authentication for Network Clients Everywhere Working Group. The IESG contact persons are Christopher Inacio and Deb Cooley. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-dance-client-auth/ Technical Summary The DANE TLSA protocol describes how to publish Transport Layer Security (TLS) server certificates or public keys in the DNS. This document describes how to use the TLSA record to publish client certificates or public keys, and also the rules and considerations for using them with TLS. In addition, it defines a new TLS extension, DANE Client Identity, to convey the client's domain name identity to the server. Working Group Summary In the early days of this working group, there were many people involved in reviews. By the time it reached working group last call the first time, there were a few hardy souls who agreed it was ready. After the first IETF Last Call, it was recognized that changes were required (changing to (D)TLS1.3 for example). Once this work was finished there was a second wglc. Document Quality There has been a DNSOP review, where the guidance has been incorporated. No YANG, ASN.1, MIB, Media Types or other types of encodings. There are claims that various enterprises want this protocol. But no specific implementations have been listed. Personnel The Document Shepherd for this document is Michael Richardson. The Responsible Area Director is Deb Cooley