Skip to main content

Automated Certificate Management Environment (acme)

WG Name Automated Certificate Management Environment
Acronym acme
Area Security Area (sec)
State Active
Charter charter-ietf-acme-01 Approved
Status update Show Changed 2018-07-19
Document dependencies
Additional resources Issue tracker, Wiki, Zulip Stream
Personnel Chairs Deb Cooley, Deb Cooley, Yoav Nir
Area Director Roman Danyliw
Mailing list Address acme@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/acme
Archive https://mailarchive.ietf.org/arch/browse/acme/
Chat Room address https://zulip.ietf.org/#narrow/stream/acme

Charter for Working Group

Historically, issuance of certificates for Internet applications
(e.g., web servers) has involved many manual identity validation steps
by the certification authority (CA). The ACME WG will specify
conventions for automated X.509 certificate management, including
validation of control over an identifier, certificate issuance,
certificate renewal, and certificate revocation. The initial focus of
the ACME WG will be on domain name certificates (as used by web
servers), but other uses of certificates can be considered as work
progresses.

ACME certificate management must allow the CA to verify, in an
automated manner, that the party requesting a certificate has authority
over the requested identifiers, including the subject and subject
alternative names. The processing must also confirm that the requesting
party has access to the private key that corresponds to the public key
that will appear in the certificate. All of the processing must be done
in a manner that is compatible with common service deployment
environments, such as hosting environments.

ACME certificate management must, in an automated manner, allow an
authorized party to request revocation of a certificate.

The ACME working group is specifying ways to automate certificate
issuance, validation, revocation and renewal. The ACME working
group is not reviewing or producing certificate policies or
practices.

The starting point for ACME WG discussions shall be draft-barnes-acme.

Milestones

Date Milestone Associated documents
Jul 2021 End user client and code signing certificates extension submitted to IESG or abandoned draft-ietf-acme-client
Apr 2021 Delay-Tolerant Networking (DTN) extensions submitted to IESG draft-ietf-acme-dtnnodeid
Apr 2021 ACME integration with with EST, BRSKI and TEAP use cases submitted to IESG draft-ietf-acme-integrations

Done milestones

Date Milestone Associated documents
Done Profile for delegated STAR certificates submitted to IESG draft-ietf-acme-star-delegation
Done S/MIME extension submitted to IESG draft-ietf-acme-email-smime
Done TNAuthlist extension submitted to IESG draft-ietf-acme-authority-token
draft-ietf-acme-authority-token-tnauthlist
Done Submit working group draft to IESG as Proposed Standard draft-ietf-acme-acme
Done Initial working group draft