RFC 9447 on Automated Certificate Management Environment (ACME) Challenges Using an Authority Token
rfc-editor@rfc-editor.org Wed, 13 September 2023 04:23 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2A55C151088; Tue, 12 Sep 2023 21:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbgf_bvwItYM; Tue, 12 Sep 2023 21:23:09 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0010FC151060; Tue, 12 Sep 2023 21:23:08 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D8243196F37D; Tue, 12 Sep 2023 21:23:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9447 on Automated Certificate Management Environment (ACME) Challenges Using an Authority Token
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, acme@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230913042308.D8243196F37D@rfcpa.amsl.com>
Date: Tue, 12 Sep 2023 21:23:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-OxHO9ELS_bMHXYSt3d_L3ITFCI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2023 04:23:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9447
Title: Automated Certificate Management Environment (ACME)
Challenges Using an Authority Token
Author: J. Peterson,
M. Barnes,
D. Hancock,
C. Wendt
Status: Standards Track
Stream: IETF
Date: September 2023
Mailbox: jon.peterson@team.neustar,
mary.ietf.barnes@gmail.com,
davidhancock.ietf@gmail.com,
chris-ietf@chriswendt.net
Pages: 11
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-acme-authority-token-09.txt
URL: https://www.rfc-editor.org/info/rfc9447
DOI: 10.17487/RFC9447
Some proposed extensions to the Automated Certificate Management
Environment (ACME) rely on proving eligibility for certificates
through consulting an external authority that issues a token
according to a particular policy. This document specifies a generic
Authority Token Challenge for ACME that supports subtype claims for
different identifiers or namespaces that can be defined separately
for specific applications.
This document is a product of the Automated Certificate Management Environment 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
Association Management Solutions, LLC