[Acme] RFC 9444 on Automated Certificate Management Environment (ACME) for Subdomains
rfc-editor@rfc-editor.org Thu, 24 August 2023 01:13 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF41FC17CEAC; Wed, 23 Aug 2023 18:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.533
X-Spam-Level:
X-Spam-Status: No, score=0.533 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 CUIHXRbHRP-f; Wed, 23 Aug 2023 18:13:26 -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 A5C38C17CEAB; Wed, 23 Aug 2023 18:13:26 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7BDABAFB45; Wed, 23 Aug 2023 18:13:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20230824011326.7BDABAFB45@rfcpa.amsl.com>
Date: Wed, 23 Aug 2023 18:13:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/dLbdnRmG4SNDb9ak60L4L0dsfx0>
Subject: [Acme] RFC 9444 on Automated Certificate Management Environment (ACME) for Subdomains
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Aug 2023 01:13:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9444
Title: Automated Certificate Management Environment (ACME)
for Subdomains
Author: O. Friel,
R. Barnes,
T. Hollebeek,
M. Richardson
Status: Standards Track
Stream: IETF
Date: August 2023
Mailbox: ofriel@cisco.com,
rlb@ipv.sx,
tim.hollebeek@digicert.com,
mcr+ietf@sandelman.ca
Pages: 20
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-acme-subdomains-07.txt
URL: https://www.rfc-editor.org/info/rfc9444
DOI: 10.17487/RFC9444
This document specifies how Automated Certificate Management
Environment (ACME) can be used by a client to obtain a certificate
for a subdomain identifier from a certification authority.
Additionally, this document specifies how a client can fulfill a
challenge against an ancestor domain but may not need to fulfill a
challenge against the explicit subdomain if certification authority
policy allows issuance of the subdomain certificate without explicit
subdomain ownership proof.
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