On Tue, Sep 13, 2016 at 09:43:53AM -0700, [email protected] wrote:
> I'm going to start in an unusual place: The validation pseudocode in Appendix
> 1. From there I'll go on to other stuff. But I think the pseudocode, done
> right, will be enormously helpful to implementors, so that's going to be
> my starting point.
My repeated admonitions to write up a more detailed state-machine
were an attempt to make the same point you're making. The description
of the requisite client-side logic is far too sketchy.
The description needs to be quite explicit, modulo flexibility on
whether failure policy refresh and retries are synchronous (fetch
new policy and retry immediately) or asynchronous (schedule policy
refresh and defer the mail). Either approach is legitimate.
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
