On Wed, Oct 01, 2014 at 09:54:12AM -0400, Alia Atlas wrote: > Thanks for the explanation. It matches with what I understand for > configuration. > Where I am confused is why I2RS - which is doing ephemeral only and matches > closer to the direct proprietary APIs directly to > the routing processes - is being tied up in this.
The annoying fact is that we have to reconcile what we want to do with the semantics of existing netconf/yang. The property of being able to override some bit of local config with ephemeral config implies at least another data store in those semantics. Otherwise you'd have to redefine the existing semantic as "a given writer may SET a value of a higher visibility priorty and it's allowed to go away and reveal the original value of lower visibility priority". This makes sense as a merge/patch operation, but less so with a single object store. -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
