On Fri, May 02, 2014 at 11:40:36AM -0400, Jeffrey Haas wrote: > On Fri, May 02, 2014 at 08:29:00AM -0700, Andy Bierman wrote: > > I picture the operational state as the mixing bowl for the 2 config sources > > and data learned from protocols and system events. It seems > > both NETCONF and I2RS would be able to pick the data is cares about > > out of that. > > I think this is what I'd like to see personally. > > > This is a weakness in YANG that may get improved in YANG 1.1. > > Since it is officially just for NETCONF, there are no mechanisms > > (other than vendor extensions) to tag the data as specific to > > some subset of protocols. > > As I mentioned elsewhere, I'm hoping we don't go down the path of "editable > operational state", instead configuration semantics for our purposes.
At some point in time, we need to get the terminology sorted out. NC has well defined configuration datastores and YANG has a well defined concept of configuration data (config true). NC kind of assumes that data in configuration datastores has an associated concept of persistence (e.g., changes to <running/> persist unless you have an explicit <startup/>, <candidate/> is a temporary scratch pad). We are talking about another writable datastore (or potentially multiple of them). Some call the data in this writable datastore configuration, others prefer to use a different term to avoid a clash with what NC and YANG consider configuration. If we could find a good name for such writable datastores, I likely make communication much simpler. And yes, I think the model that the contents of the configuration datastore, the writable datastore(s) as well as the information learned dynamically from various control plane protocols all lead to the final operational state. (In fact, one could consider a model where control plane protocols all conceptually come into the system via additional control protocol specific writable datastores.) So, can we find a name for these 'other writable datastores' and then use that term instead of 'writable operational state', 'ephemeral config', 'i2rs datastore', etc.? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
