Received: by mx.ietf.org (Postfix) id 2C1FB46;
	Tue, 27 Oct 2026 20:35:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail;
	t=1793133359;
	h=from:from:sender:sender:reply-to: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=XqbTjkkj02oA3Z1gkbnq0Jyl6ZP/sncZUYeRFu4l5lw=;
	b=Pb29AUoFEsT4FcAB9ETsRwOGGYUqwYLjfUCw5nsqg7bXt+1telxFS+Rq0yLDvnNu694Mj0
	vB7iA9SsleZC/V2w13ZCFRkKNSUlBHT+Uv13fuxcItOYgyJM/owGui2yIOqIabDqWsBLJ9
	r38oNKR31yNAjw9pnnF69TmjVg31e7w=
Authentication-Results: ORIGINATING;
	auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=iesg-secretary@ietf.org
Received: from [10.244.8.89] (gaia.k8s.ietf.org [4.156.85.76])
	by mail2.ietf.org (Postfix) with ESMTP id E93AE13B28354;
	Tue, 27 Oct 2026 13:35:58 -0700 (PDT)
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: Last Call: <draft-ietf-acme-dns-account-label-04.txt> (Automated
 Certificate Management Environment (ACME) DNS Labeled With ACME Account ID
 Challenge) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 12.82.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: 
 <179313335885.492572.16043728092030043705@dt-datatracker-7dc874ff8f-5wfjq>
Date: Tue, 27 Oct 2026 13:35:58 -0700
Message-ID-Hash: NBYNMFXZXF35264LQ3RVMPIM4P7CNWCE
X-Message-ID-Hash: NBYNMFXZXF35264LQ3RVMPIM4P7CNWCE
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: acme-chairs@ietf.org, acme@ietf.org,
 draft-ietf-acme-dns-account-label@ietf.org, mike@ounsworth.ca
X-Mailman-Version: 3.3.10
Reply-To: last-call@ietf.org, acme@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ietf-announce/JXt7GZVCv8TnKiMYoS058pbLc2Q>
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 received a request from the Automated Certificate Management
Environment WG (acme) to consider the following document:
  'Automated Certificate Management Environment (ACME) DNS Labeled With
   ACME Account ID Challenge'
  <draft-ietf-acme-dns-account-label-04.txt> as Proposed Standard

The IESG plans to make a decision on this document in the coming weeks, and
solicits last-call comments. Please send substantive comments to the
last-call@ietf.org mailing list, with acme@ietf.org copied, no later than
2026-11-10.  Please retain the beginning of the Subject line to facilitate
automated sorting.

Abstract

   This document outlines a new DNS-based challenge type for the ACME
   protocol that enables multiple independent systems to authorize a
   single domain name concurrently.  By adding a unique label to the DNS
   validation record name, the dns-account-01 challenge avoids CNAME
   delegation conflicts inherent to the dns-01 challenge type.  This is
   particularly valuable for multi-region or multi-cloud deployments
   that wish to rely upon DNS-based domain control validation and need
   to independently obtain certificates for the same domain.



The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/


No IPR declarations have been submitted directly on this I-D.





