I was tyring to understand the descriptions being used.
After looking back at the email, and talk to folks, there seem to be two
different issues.
The first one is what happens the complete running config disappears.
As far as I am concerned, the device can do anything it wants, and
whatever it does is probably wrong. After all, for the running config
to disappear there have to be very serious problems.
The second issue is what happens when something (foo) is deleted from
the running config, but some property of that thing (foo/a) has been set
by I2RS. Unfortunately,as far as I can tell, there is not a good
general rule.
Some examples:
If the operator takes down BGP, and deletes the full BGP configuration,
then the presence of I2RS policy rules should not cause BGP to keep running.
On the other hand, if foo is a static route create by operations, and
then I2RS modified the next hop for that route, I tend to suspect that
the route I2RS has "created" by doing so should stay around even if the
operator goes in a deletes the static route.
I suspect that the issue is determining what scope is being created when
I2RS writes b/c/d/foo/a. I don't think it is obvious or that there is a
consistent rule.
Yours,
Joel
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
