RFC 9115: An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9115
- Published
- September 2021
- Authors
- Y. Sheffer; D. López; A. Pastor Perales; T. Fossati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 42
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 7736Content Delivery Network Interconnection (CDNI) Media Type RegistrationCurrent
December 2015
- RFC 9706TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass AudiencesCurrent
January 2025
- RFC 8007Content Delivery Network Interconnection (CDNI) Control Interface / TriggersCurrent
December 2016
- RFC 8006Content Delivery Network Interconnection (CDNI) MetadataCurrent
December 2016
- RFC 7937Content Distribution Network Interconnection (CDNI) Logging InterfaceCurrent
August 2016
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 6770Use Cases for Content Delivery Network InterconnectionCurrent
November 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?