aarongable/draft-acme-ari

Issues

• Support `replaces` without `renewal-info` resource

  #72 opened 2 months ago by Radranic
  0

• Conveying renewal urgency on a per-account basis

  #65 opened 2 months ago by djc
  9

• Consider recommending clients log and audit "immediate renewal" scenarios as a best-practice

  #46 opened 2 months ago by jvanasco
  8

• When to poll again if server does not send Retry-After?

  #69 opened 2 months ago by mholt
  2

• Recommended algorithm may lead to renewals outside of suggested window

  #71 opened 4 months ago by mholt
  2

• Clarification of Retry-After, wake times, and polling intervals

  #70 opened 4 months ago by mholt
  1

• A couple alternatives to consider instead of a window

  #44 opened 4 months ago by mholt
  3

• Criteria for "has not already been marked as replaced"

  #66 opened 5 months ago by robstradling
  2

• Advice to clients: Can the same "clear predecessor certificate" be identified in multiple New Order requests?

  #60 opened 6 months ago by robstradling
  3

• What exactly does "share identifiers" mean?

  #57 opened 6 months ago by robstradling
  2

• Wordsmithing the suggested uses of `replaces` by a server

  #61 opened 6 months ago by robstradling
  2

• Note up-from that this document assumes RFC 5280 profile

  #59 opened 6 months ago by aarongable
  0

• Certificate Renewal, Re-Key, Modification

  #58 opened 6 months ago by robstradling
  2

• Return HTTP 409 "Conflict" when the certificate identified by 'replaces' has already been replaced

  #56 opened 7 months ago by beautifulentropy
  14

• Update endpoint

  #55 opened 7 months ago by mholt
  2

• Serial number encoding ambiguity

  #52 opened 7 months ago by robstradling
  2

• Consider adding a "batch" endpoint, which returns ARI info for all certs under a single account

  #41 opened 7 months ago by aarongable
  2

• Nit; small incongruence with quoting

  #40 opened 7 months ago by beautifulentropy
  0

• Encourage clients to retry as often as possible

  #13 opened 7 months ago by aarongable
  0

• Consider including renewalInfo inside finalized Order objects

  #42 opened 7 months ago by aarongable
  2

• UPDATE addition

  #25 opened a year ago by icing
  0

• Replace POST updates with field in newOrder requests

  #50 opened a year ago by aarongable
  0

• Consider changing URL construction away from OCSP CertID

  #43 opened a year ago by aarongable
  2

• Improve the IANA Considerations section

  #47 opened a year ago by aarongable
  0

• Query: Conforming clients MUST select a uniform random time within the suggested window

  #26 opened 2 years ago by robplee
  2

• Add zero duration windows to the malformed response example

  #36 opened 2 years ago by beautifulentropy
  0

• Consider adding caching guidance

  #20 opened 2 years ago by aarongable
  0

• Typos/wording suggestions

  #28 opened 2 years ago by robplee
  2

• signatureAlgorithm should be hashAlgorithm?

  #30 opened 2 years ago by osirisinferi
  0

• Does the renewal-info URL need to use RFC6960 certIDs?

  #27 opened 2 years ago by robplee
  1

• Consider a "This has been renewed" endpoint

  #15 opened 2 years ago by aarongable
  2

• Consider `base64url(CertID)` for url slug

  #17 opened 2 years ago by aarongable
  0

• URL Construction is Under-Specified

  #18 opened 2 years ago by AGWA
  1

• Include justification of sha1 in Security Considerations

  #16 opened 2 years ago by aarongable
  1

• Motivation: place more emphasis on non-revocation use-cases

  #19 opened 2 years ago by aarongable
  1

• Clarify client and server behavior around malformed renewalInfo stanzas

  #9 opened 3 years ago by aarongable
  0

• How often to retry in the face of errors

  #8 opened 3 years ago by jsha
  0

• Add draft-only section for Current Implementations

  #10 opened 3 years ago by aarongable
  0

• Cleanups: use backticks everywhere appropriate

  #6 opened 3 years ago by aarongable
  0

• Show Retry-After header in example response

  #7 opened 3 years ago by aarongable
  0

• Make renewalInfo URLs third-party constructable

  #4 opened 3 years ago by aarongable
  0

• Consider disallowing POST-as-GET for renewalInfo

  #3 opened 3 years ago by aarongable
  2