RFC 9115 on An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
rfc-editor@rfc-editor.org Tue, 21 September 2021 00:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 669413A1754; Mon, 20 Sep 2021 17:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXDFax-Za2Ff; Mon, 20 Sep 2021 17:17:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E1833A174E; Mon, 20 Sep 2021 17:17:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3FCC9F40943; Mon, 20 Sep 2021 17:17:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9115 on An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210921001743.3FCC9F40943@rfc-editor.org>
Date: Mon, 20 Sep 2021 17:17:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/f7MGt8suoT9Kl9_mC45R1KSShrs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 21 Sep 2021 00:17:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9115
Title: An Automatic Certificate Management Environment
(ACME) Profile for Generating Delegated Certificates
Author: Y. Sheffer,
D. López,
A. Pastor Perales,
T. Fossati
Status: Standards Track
Stream: IETF
Date: September 2021
Mailbox: yaronf.ietf@gmail.com,
diego.r.lopez@telefonica.com,
antonio.pastorperales@telefonica.com,
thomas.fossati@arm.com
Pages: 42
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-acme-star-delegation-09.txt
URL: https://www.rfc-editor.org/info/rfc9115
DOI: 10.17487/RFC9115
This document defines a profile of the Automatic Certificate
Management Environment (ACME) protocol by which the holder of an
identifier (e.g., a domain name) can allow a third party to obtain an
X.509 certificate such that the certificate subject is the delegated
identifier while the certified public key corresponds to a private
key controlled by the third party. A primary use case is that of a
Content Delivery Network (CDN), the third party, terminating TLS
sessions on behalf of a content provider (the holder of a domain
name). The presented mechanism allows the holder of the identifier
to retain control over the delegation and revoke it at any time.
Importantly, this mechanism does not require any modification to the
deployed TLS clients and servers.
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