What does "must be a subset" mean?
There are actuyally levels of that which I think the I2RS work could
accept. Prohibiting I2RS from starting OSPF when it was not running is
probably reasonable.
On the other hand, prohibiting I2RS from creating a new static route to
a destination is clearly not workable.
But both of those are creating a new portion of the tree, within an
existing tree (namely the whole configuration.)
So this "simplification" does not seem to mean anything.
One of the nice things abotu Juergen's proposal is that it does not say
"I2RS can not do X." Rather it, says "to do X, I2RS must use mechanism
Y".
Yours,
Joel
On 10/1/14, 11:08 AM, Thomas D. Nadeau wrote:
On Oct 1, 2014:7:43 AM, at 7:43 AM, Joel M. Halpern <[email protected]>
wrote:
I can live with that model.
Simplified and repeated:
If an object is deleted in running, and the object itself was not created as a
whole in I2RS, then the object, and any changes to elements within the object,
is also deleted in the I2RS ephemeral store, even if some I2RS clients had
written some of those elements.
This is another simplification: the I2RS objects MUST be a subset of
what is available in the normal/running config.
I would expect I2RS to generate notifications of those deletions.
Or just define notifications on the store as you normally can in the yang model.
Is there really a need for special "i2rs" notifications or just
config-change-related ones?
This gives us a consistent operating paradigm, with a means for I2RS clients to
be more explicit about their intent, without creating significant complexity.
Lets try! 8)
--Tom
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
