On Thu, Aug 11, 2016 at 09:37:47PM +0200, Daniel Margolis wrote:
> Another option (also, IMO, simpler than multiple versions) is to simply not
> indicate the ID string in the JSON at all, but only in the TXT. It's not
> clear to me why it has to be in the JSON anyway (but I haven't thought this
> through very far).
Yes, the client's cache could store the DNS id seen at the time of
the most recent cache fetch. Then when the DNS id changes, a new
fetch happens, and the new cache entry records that. In this case
there is no id in the policy itself.
Mind you, this can complicate debugging of problems, because the
client's cache id when a problem is encountered, might not uniquely
identify a given server policy. Not a major problem, but something
perhaps to consider.
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
