On Fri, May 09, 2014 at 11:16:21AM +0100, t. petch wrote: > > > > Tom, > > > > RFC 6241 says: > > > > o datastore: A conceptual place to store and access information. > A > > datastore might be implemented, for example, using files, a > > database, flash memory locations, or combinations thereof. > > > > o configuration datastore: The datastore holding the complete set > of > > configuration data that is required to get a device from its > > initial default state into a desired operational state. > > > > Note the distinction between a datastore and a configuration > > datastore. > > Juergen > > Thanks for the correction. I note that the YANG RFC does not draw the > distinction and that all NETCONF RPC refer to configuration datastores > so while we could use datastore unqualified to mean something different, > such as a set of I2RS data, I would rather avoid that usage. >
All I can tell is that N/Y documents try to make a distinction between the concept of a datastore and a configuration datastore. The word datastore shows up 13 times in RFC 6020 and in a number of the occurances the context is rather clear whether a configuration datastore or a general datastore is meant I think. But yes, the YANG RFC might not have gotton the wording right everywhere. That said, I believe at least one widely deployed commercial implementation supports the notion of non-configuration datastores. But your mileage might vary. /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
