Hi Joe,
On 3/24/2022 11:48 AM, Joe Clarke (jclarke) wrote:
On 3/9/22 11:13, Jean Quilbeuf wrote:
Hi Joe,
Thanks for your comments.
First, what is the purpose of assurance-graph-version? It's a 32-bit counter
that can increment when something goes in and out of maintenance (+2). I can
easily see this wrapping fir services with a lot of churn. What is the impact
of that? Is this version number required if we have a last modified timestamp?
The purpose of assurance-graph-version is to enable a consumer of this module
to quickly check if they have the last version. It probably makes sense to use
a larger counter. I'll modify it.
How does it do that. If I get a version of 324523457273456, how do I
know that's the latest?
MdT on-change.
It seems to me the date is as useful as that
number. I still don't _know_ I have the latest version, but I can be
more confident if I have one from a couple of seconds ago, it's recent.
Regards, Benoit
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
