Visual RFC.
ALL RFCs / RFC 8555
Read the RFC ↗
RFC 8555 / MECHANISMS

An order is a state machine

01

An order becomes ready only after its required authorizations are satisfied.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 8555 · § 7.1.6EXAMPLE
3 / 3
An order is a state machineAn order becomes ready only after its required authorizations are satisfied. Current state: processing → valid.An order is a state machinependingreadyvalidauthorizations satisfiedCSR → issueprocessingThe order must be ready before finalization.
03
processing → valid

Submit the CSR, then wait for issuance and a certificate URL.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 8555 HTTP/DNS challengesRFC 8737 § 3

A later companion specification adds tls-alpn-01, a dedicated TLS challenge using the acme-tls/1 ALPN identifier; it does not replace ACME.

Read the updated RFC section ↗
KEY POINT

An account key authenticates the ACME client.

  • An account key authenticates the ACME client.
  • Orders describe requested identifiers and link authorizations.
  • A certificate is issued only after the server accepts the required validation and finalization.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. An order is a state machine
  2. One nonce for one signed request
  3. HTTP proves control of a path
  4. DNS proves control of a record
  5. CSR, certificate, and revocation
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗