[Acme] Re: Status of draft-ietf-acme-dns-account-label ?

Antonis Chariton <daknob@daknob.net> Wed, 13 May 2026 09:28 UTC

Return-Path: <daknob@daknob.net>
X-Original-To: acme@mail2.ietf.org
Delivered-To: acme@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5C7BAEDA5F27; Wed, 13 May 2026 02:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778664498; bh=EMuaWFKTTInvYIYAl/n/ehBkD3NseuMcuBJFSyQCFE8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=S7/P+MIWK0q8RM4ssybz0pbZmwOJLnP04aOs3xIwIEEdCVK2QmYQ7qRuOo6HcqGUH eQIf8+8LMDQR4RnLB10GDLAYMCahX8BU9UGuY8qKkHJ3K0mg9/qlMHS/FWLN98ff0I lq1U6INzPaUczKrSFdMphWomXwHuvpG9yNAgMJ9s=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=daknob.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzf6i0UyS9RD; Wed, 13 May 2026 02:28:14 -0700 (PDT)
Received: from dione.s.daknob.net (dione.s.daknob.net [159.100.255.27]) (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 78570EDA5D7F; Wed, 13 May 2026 02:26:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daknob.net; s=dione0; t=1778664364; bh=EMuaWFKTTInvYIYAl/n/ehBkD3NseuMcuBJFSyQCFE8=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=HjFdkKSQnj6ugSmcUe1KrTjtq9DQXAZth1lxdhlPJxT89/pRrmb0G2xgNZFzgVx+o q8IKc7+eRM4lBBLhUIQTKQhzDcLpM1B3F727tkaooUpI0TAAIoytms1xZhLtNDDRfm I1r4dQAtgV6oqZ/+x/1fPcmSf6Dm/NSg9IMqtAkvXLCWKRpzUjJ1TkJGCaLuGx0Tp1 p+HetVecu7dWyqfRXvHYqy1NTA/VGqd7EX4OrkTWYELPY5nIeOW3RM+i+xWqo4Phq9 LzQJzTbAcmn7ZFCWE0KSSMGu6KMXF2V51qk0K29P8oObYRoapwVijFD1AWRUVunlu9 BWzbFTb2JsATQ==
Received: from smtpclient.apple (unknown [IPv6:2a0d:3dc0:200:0:8409:99ad:69f2:fbc8]) by dione.s.daknob.net (Postfix) with ESMTPSA id 8BDFD86A27; Wed, 13 May 2026 09:26:04 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: Antonis Chariton <daknob@daknob.net>
In-Reply-To: <CAKZgXHoi7hNT9-7FkkYSQWJjgZz_A8pBrTVd3=0yXLqVs-Tizg@mail.gmail.com>
Date: Wed, 13 May 2026 11:25:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <78B9C32C-BBF2-4447-906C-114FE982E529@daknob.net>
References: <CAKZgXHoi7hNT9-7FkkYSQWJjgZz_A8pBrTVd3=0yXLqVs-Tizg@mail.gmail.com>
To: Mike Ounsworth <ounsworth+ietf@gmail.com>
X-Mailer: Apple Mail (2.3864.500.181)
Message-ID-Hash: EKUPBYX6IK22HBAOZ3JFGAFZ4AQWDGPK
X-Message-ID-Hash: EKUPBYX6IK22HBAOZ3JFGAFZ4AQWDGPK
X-MailFrom: daknob@daknob.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-acme.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-acme-dns-account-label@ietf.org, IETF ACME <acme@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Acme] Re: Status of draft-ietf-acme-dns-account-label ?
List-Id: Automated Certificate Management Environment <acme.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/Wrewsms2l9FjzXNJSIInJJRoiZc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Owner: <mailto:acme-owner@ietf.org>
List-Post: <mailto:acme@ietf.org>
List-Subscribe: <mailto:acme-join@ietf.org>
List-Unsubscribe: <mailto:acme-leave@ietf.org>

Hello Mike,

Here’s the current status as far as I'm aware of:

- We have incorporated all of this feedback and finished that process a few years ago
- The current spec has been added to the CA/B Forum BRs and issuance by publicly trusted CAs is allowed with the text as-is
- At least 3 CAs that I know of have deployed this
- There are at least 2 different interoperable implementations on the server side
- There are at least 3 different interoperable implementations on the client side

We have asked for this to proceed once, but it didn’t go into a vote.

I will be at IETF in Vienna, but at this point I am not sure what else is required from us. This is already being used for certificates by CAs for years, and it seems to have been stuck in IETF for a while.

Any help appreciated to move this forward by anyone on this list would be appreciated.

Thanks,
Antonis

> On 12 May 2026, at 14:47, Mike Ounsworth <ounsworth+ietf@gmail.com> wrote:
> 
> Hi authors of draft-ietf-acme-dns-account-label,
> 
> I notice that the draft is due to expire within the week. Could you please give a status update on this draft? Are there active deployments? Are there open issues and active work being done on the document?
> 
> -Mike Ounsworth
> ACME Co-Chair