icing
Any roadmap to support ACME Renewal Info (ARI)?
Just curious if you plan to support ARI. If so any timeline? If not is that likely permanent restriction?
ARI is supported by a number of ACME Servers including Let's Encrypt, Google Trust Services, ZeroSSL, and Buypass. Likely others I am not aware of.
Let's Encrypt has this guide: https://letsencrypt.org/2024/04/25/guide-to-integrating-ari-into-existing-acme-clients/
That guide walks through a cron based ACME Client so your implementation likely different. I know Caddy server supports ARI so maybe that is better reference.
https://datatracker.ietf.org/doc/draft-ietf-acme-ari/
Thanks for any status you may provide.
This is on my todo list which I hope to get to this summer. I read that ARI had almost been accepted by the ACME group but there was some last minute things someone wanted to change. That is why I held back.
Just saw Aaron Gable say it is nearly done. At this late stage it is manual interactions between him and the editors. Did not sound like much longer for that to complete. He did not mention any changes to the spec since draft 08.
I fully appreciate anyone wanting to wait for that. Even though I personally did not :)
We recommend it often at the LE community so just happy to know it is planned. Thanks
@icing You sound well-informed so apologize if this is redundant. But, ARI RFC was issued today: https://www.rfc-editor.org/rfc/rfc9773.html