Return-Path: <internet-drafts@ietf.org>
X-Original-To: acme@ietf.org
Delivered-To: acme@mail2.ietf.org
Received: from [10.244.9.145] (gaia.k8s.ietf.org [4.156.85.76])
	by mail2.ietf.org (Postfix) with ESMTP id 11BCC136BF9C9;
	Mon,  7 Sep 2026 07:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1788792821; bh=q8h9wz4Aj+dJ/O3EITQqOkShd3k7k3rP9Y2UPpmWy7Q=;
	h=From:To:Cc:Subject:Reply-To:Date;
	b=HChW0PS7UaLeaVX784JaF8W9Ast2yE5tQsAZXPZH4gOqrX/jSqvYybHB8nkIsucIt
	 EyKbv2rpylBwNdpeuGw04c06HT9EcxPqnVpjfqN1H9PccKckJIBeZx40+LSyvDcyug
	 ssGSR/VKoUt2qMhEw+1qeuF4Dv32TylXU7IIdCXk=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: 
 <178879282099.682699.8421453204822125490@dt-datatracker-9769b79f-xztnc>
Date: Mon, 07 Sep 2026 07:53:41 -0700
Message-ID-Hash: GUJLZTCTCV5EC7ZDWFU7FVCRV33R775E
X-Message-ID-Hash: GUJLZTCTCV5EC7ZDWFU7FVCRV33R775E
X-MailFrom: internet-drafts@ietf.org
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: acme@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: acme@ietf.org
Subject: =?utf-8?q?=5BAcme=5D_I-D_Action=3A_draft-ietf-acme-authority-token-jwtclaimc?=
	=?utf-8?q?on-06=2Etxt?=
List-Id: Automated Certificate Management Environment <acme.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/acme/eCeYxVdcLpcFCAI7WPZV74AK0OA>
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>

Internet-Draft draft-ietf-acme-authority-token-jwtclaimcon-06.txt is now
available. It is a work item of the Automated Certificate Management
Environment (ACME) WG of the IETF.

   Title:   JWTClaimConstraints profile of ACME Authority Token
   Authors: Chris Wendt
            David Hancock
   Name:    draft-ietf-acme-authority-token-jwtclaimcon-06.txt
   Pages:   25
   Dates:   2026-09-07

Abstract:

   This document defines an authority token profile for the validation
   of JWTClaimConstraints and EnhancedJWTClaimConstraints certificate
   extensions within the Automated Certificate Management Environment
   (ACME) protocol.  This profile is based on the Authority Token
   framework and establishes the specific ACME identifier type,
   challenge mechanism, and token format necessary to authorize a client
   to request a certificate containing these constraints.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-acme-authority-token-jwtclaimcon/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-acme-authority-token-jwtclaimcon-06

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-acme-authority-token-jwtclaimcon-06

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


