Automated Certificate Management Environment (ACME) for Subdomains
RFC 9444
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed author "M. Richardson": changed name from "Michael Richardson" to "M. Richardson" |
|
2026-05-20
|
(System) | Changed author "T. Hollebeek": changed name from "Tim Hollebeek" to "T. Hollebeek" |
|
2026-05-20
|
(System) | Changed author "R. Barnes": changed name from "Richard Barnes" to "R. Barnes" |
|
2026-05-20
|
(System) | Changed author "O. Friel": changed name from "Owen Friel" to "O. Friel" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2023-08-23
|
(System) | Received changes through RFC Editor sync (created alias RFC 9444, changed abstract to 'This document specifies how Automated Certificate Management Environment (ACME) can be … Received changes through RFC Editor sync (created alias RFC 9444, changed abstract to '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.', changed pages to 20, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-08-23, changed IESG state to RFC Published) |
|
2023-08-23
|
(System) | RFC published |