Hi Michael,
The comments have been addressed in https://github.com/aarongable/draft-acme-ari/pull/86 in the github working copy, and will be published in the next draft version shortly.
Thank you for the feedback!
Aaron
On Fri, Dec 6, 2024 at 3:00 AM Michael Tüxen via Datatracker <noreply@xxxxxxxx> wrote:
The sixth step in the algorithm described in Section 4.2 is ambiguous in my
view:
Otherwise, sleep until the Retry-After period has passed, or until the next
normal wake time, and return to Step 1.
Assume the Retry-After period is 6 hours (21600 seconds) as stated in the
example and assume that the normal wake time is 1 second. Depending on how the
sixth rule is interpreted, the client might retry in 6 hours or in one second.
Choosing the 1 second results in sending 21600 requests in 6 hours instead of
one. Therefore I think it makes sense to be more specific here such that you
send only one request...
This is a good point. This phrasing (specifically "or until the next normal wake time") was included when the algorithm was less rigidly specified, and before the new advice regarding setting and respecting Retry-After was added. I think it makes sense to simply remove this carveout, and say that the algorithm is simply to sleep to the end of the Retry-After period. I've made a change to this effect.
There is one typo in Section 4.2:
regulatory enviornment -> regulatory environment
Fixed (by virtue of rephrasing this section in response to feedback from other reviewers).
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
