Hi Aaron. What are you planning to do with the 4 open Issues and 1 open PR at https://github.com/aarongable/draft-acme-ari ?
________________________________ From: Aaron Gable <aaron=40letsencrypt....@dmarc.ietf.org> Sent: 16 July 2024 20:04 To: acme@ietf.org <acme@ietf.org> Subject: [Acme] Re: I-D Action: draft-ietf-acme-ari-04.txt CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi everyone, I have not received any feedback on this -04 version of the draft, so just like to re-request your review prior to IETF 120, in just a week and a half, where I plan to present these very minor changes and ask for WG last call. Thanks, Aaron On Fri, May 31, 2024 at 6:40 PM Aaron Gable <aa...@letsencrypt.org<mailto:aa...@letsencrypt.org>> wrote: Hi all, This update is entirely improvements to the phrasing of various prose, no changes to the wire protocol. It does address the one remaining open question we discussed at IETF 119, namely what to do if a client identifies an already-replaced (or already-in-the-process-of-being-replaced) certificate in a newOrder request. My thanks to Rob Stradling for helping with the phrasing there. I've also updated the Current Implementations with a large list of implementations. At IETF 119, the group said that we believed this document would be ready for WG Last Call once that last question was addressed. I believe that it is now ready, and look forward to the rest of your feedback! Thanks, Aaron On Fri, May 31, 2024 at 6:35 PM <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> wrote: Internet-Draft draft-ietf-acme-ari-04.txt is now available. It is a work item of the Automated Certificate Management Environment (ACME) WG of the IETF. Title: Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension Author: None Name: draft-ietf-acme-ari-04.txt Pages: 11 Dates: 2024-05-31 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. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-acme-ari/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-acme-ari-04.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-acme-ari-04 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ Acme mailing list -- acme@ietf.org<mailto:acme@ietf.org> To unsubscribe send an email to acme-le...@ietf.org<mailto:acme-le...@ietf.org>
_______________________________________________ Acme mailing list -- acme@ietf.org To unsubscribe send an email to acme-le...@ietf.org
