My apologies to the ACME WG for not making it to the IETF 121 session. Below is the material that I intended to present; my slides are also attached.
Since IETF 120, two new versions of draft-ietf-acme-ari have been published. Draft -05 <https://datatracker.ietf.org/doc/draft-ietf-acme-ari/05/> introduced the "alreadyReplaced" error type that we discussed at IETF 120. It also added the restriction that clients must not provide the "replaces" field if the server they are talking to does not advertise an ARI endpoint, to prevent compliant clients from confusing servers that haven't adopted ARI yet. Draft -06 <https://datatracker.ietf.org/doc/draft-ietf-acme-ari/06/> included just a small typo fix and some advice to server operators regarding the values they should set in the Retry-After header. In that time, the draft has also completed Working Group Last Call. Thank you to everyone who reviewed the document during that time and expressed your support for it! You may have seen the email <https://mailarchive.ietf.org/arch/msg/acme/v7VHPO_kB5CZb0jdFetgbWVC_NE/> and github PR <https://github.com/aarongable/draft-acme-ari/pull/82> from Jacob Hoffman-Andrews, one of the authors of the original RFC 8555. He's suggesting adding a new section of instructions for clients on how often to poll the renewalInfo endpoint, and how best to respect the Retry-After header. It is my intention to accept a (lightly workshopped) version of this language, but I wanted to make sure that everyone had an opportunity to comment (either on that thread, this thread, or on the github PR directly) before I incorporate it and publish draft -07. Thanks again, Aaron
ACME WG IETF 121 2024-11-06 ARI.pdf
Description: Adobe PDF document
_______________________________________________ Acme mailing list -- acme@ietf.org To unsubscribe send an email to acme-le...@ietf.org
