Hi Dale,
Thanks for confirmation. Regarding the example -
>
> * However, in regard to the new example:
>
> o PCReq with SVEC object with link-diverse bit=1 (LSP1,LSP2) and DAG
> with L=1 (LSP1,LSP3) - link diverse paths between LSP1, LSP2,
> LSP3. But any future change in LSP2 will have no impact.
>
> As far as I can tell, there is a diversity constraint between LSP1 and
> LSP2, and a diversity constraint between LSP1 and LSP3, but there is
> none between LSP2 and LAP3 -- this is not quite the same as "link
> diverse paths between LSP1, LSP2, LSP3". In particular, LSP2 and LSP3
> might be identical.
>
> The final sentence is unclear to me (probably due to my inexperience);
> is it possible to be more exact regarding the reason/manner that such a
> change "will have no impact"?
>
I suggest following change to make it clear -
o PCReq with SVEC object with link-diverse bit=1 (LSP1,LSP2) and DAG
with L=1 (LSP1,LSP3) - link diverse paths between LSP1 & LSP2, and
LSP1 & LSP3. If the DAG is part of the stateful database, any
future change in LSP3 will have an impact on LSP1. But any future
change in LSP2 will have no impact on LSP1, as LSP2 is part of
SVEC object (which is considered once on receipt of the PCReq
message only).
Thanks!
Dhruv
_______________________________________________
Pce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pce
