Skip to main content

An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
RFC 9115

Revision differences

Document history

Date By Action
2024-01-12
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2023-02-08
(System) Received changes through RFC Editor sync (added Errata tag)
2021-09-29
(System) IANA registries were updated to include RFC9115
2021-09-20
(System)
Received changes through RFC Editor sync (created alias RFC 9115, changed title to 'An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates', …
Received changes through RFC Editor sync (created alias RFC 9115, changed title to 'An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates', changed abstract to '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.', changed pages to 42, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-09-20, changed IESG state to RFC Published)
2021-09-20
(System) RFC published