I've been refreshing myself on the SAIN work, and jumped into this draft before the architecture. I have two comments as I read this.
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? Second, is it intended that health-score-weight of all symptoms' health score weights for a given subservice add to 100? If so, that is not clearly stated. I guess I'm wondering what this might look like in practice if I have a degraded subservice with health 50 and two symptoms of weight 10 and 20 respectively. Obviously, I would look at weight 20 first, but I might then wonder if something unseen is also affecting my subservice. Joe
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
