aarongable / draft-acme-ari

Internet Draft for the Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension

aarongable/draft-acme-ari Issues

Update `alreadyReplaced` to `replaces` or similar
Closed a month ago3
Provide URL to replacing order on `alreadyReplaced` errors
Updated a month ago
Return HTTP 409 "Conflict" when the certificate identified by 'replaces' has already been replaced
Closed a month ago16
Support `replaces` without `renewal-info` resource
Closed 2 months ago9
Conveying renewal urgency on a per-account basis
Closed 2 months ago9
Consider recommending clients log and audit "immediate renewal" scenarios as a best-practice
Closed 2 months ago8
When to poll again if server does not send Retry-After?
Closed 2 months ago2
Recommended algorithm may lead to renewals outside of suggested window
Closed 5 months ago2
Clarification of Retry-After, wake times, and polling intervals
Closed 5 months ago1
A couple alternatives to consider instead of a window
Closed 5 months ago3
Criteria for "has not already been marked as replaced"
Closed 6 months ago2
Advice to clients: Can the same "clear predecessor certificate" be identified in multiple New Order requests?
Closed 7 months ago3
What exactly does "share identifiers" mean?
Closed 7 months ago2
Wordsmithing the suggested uses of `replaces` by a server
Closed 7 months ago2
Note up-from that this document assumes RFC 5280 profile
Closed 7 months ago
Certificate Renewal, Re-Key, Modification
Closed 7 months ago2
Update endpoint
Closed 8 months ago2
Serial number encoding ambiguity
Closed 8 months ago2
Consider adding a "batch" endpoint, which returns ARI info for all certs under a single account
Closed 8 months ago2
Nit; small incongruence with quoting
Closed 8 months ago
Encourage clients to retry as often as possible
Closed 8 months ago
Consider including renewalInfo inside finalized Order objects
Closed 8 months ago2
UPDATE addition
Closed a year ago
Replace POST updates with field in newOrder requests
Closed a year ago
Consider changing URL construction away from OCSP CertID
Closed a year ago2
Improve the IANA Considerations section
Closed a year ago
Query: Conforming clients MUST select a uniform random time within the suggested window
Closed 2 years ago2
Add zero duration windows to the malformed response example
Closed 2 years ago
Consider adding caching guidance
Closed 2 years ago
Typos/wording suggestions
Closed 2 years ago2
signatureAlgorithm should be hashAlgorithm?
Closed 2 years ago
Does the renewal-info URL need to use RFC6960 certIDs?
Closed 2 years ago1
Consider a "This has been renewed" endpoint
Closed 3 years ago2
Consider `base64url(CertID)` for url slug
Closed 3 years ago
URL Construction is Under-Specified
Closed 3 years ago1
Include justification of sha1 in Security Considerations
Closed 3 years ago1
Motivation: place more emphasis on non-revocation use-cases
Closed 3 years ago1
Clarify client and server behavior around malformed renewalInfo stanzas
Closed 3 years ago
How often to retry in the face of errors
Closed 3 years ago
Add draft-only section for Current Implementations
Closed 3 years ago
Cleanups: use backticks everywhere appropriate
Closed 3 years ago
Show Retry-After header in example response
Closed 3 years ago
Make renewalInfo URLs third-party constructable
Closed 3 years ago
Consider disallowing POST-as-GET for renewalInfo
Closed 3 years ago2