Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension
draft-aaron-acme-ari-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Aaron Gable | ||
| Last updated | 2022-07-26 | ||
| Replaced by | draft-ietf-acme-ari | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-acme-ari | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies how an ACME server may provide suggestions to ACME clients as to when they should attempt to renew their certificates. This allows servers to mitigate load spikes, and ensures clients do not make false assumptions about appropriate certificate renewal periods. Current Implementations Draft note: this section will be removed by the editor before final publication. Let's Encrypt's Staging environment (available at [lestaging], source at [boulder]) implements this draft specification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)