Are challenge retries still supported? If so, how will retries affect the state transitions? What state would a server use to indicate that something had an error but could be retried later?
Sincerely, Logan Widick On Mar 2, 2018 08:04, "Richard Barnes" <r...@ipv.sx> wrote: Hey all, We had a couple of GitHub issues and mailing list posts expressing confusion about the "status" field in ACME objects. To try to clear all of that up, I've posted a PR that lays out required state transitions and aligns the field descriptions with that description. All the description should look very familiar. The only innovation is to introduce a "ready" state on orders, to give clients an easy way to know when to finalize. https://github.com/ietf-wg-acme/acme/pull/400 As you're probably aware the I-D deadline is Monday, so please send comments ASAP. If I don't hear anything back from this list, I'll confer with my fellow editors and we'll make a unilateral decision for us to discuss in London (and obviously roll back if needed). Thanks, --Richard _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme