On Thu, May 08, 2014 at 06:45:34PM +0100, t. petch wrote:
> Sue
>
> I am afraid I cannot parse this e-mail to see where the text is yours
> and where it is something earlier and where the questions are
> unanswered:-(
>
> Datastores in NETCONF/YANG are a NETCONF construct and define a set of
> configuration information. YANG has no concept of where data is or its
> persistence except to a limited extent when it is applying validation
> logic, as in RFC6020 s7.5.3 (which probably does not make much sense in
> isolation - my I-D might help).
>
> So a datastore is a set of 'config true' data nodes stored somewhere.
> Move away from configuration and there is no other concept, apart from
> everything else, all the statistics, routing tables and so on. Hence my
> suggestion that I2RS will need a YANG substatement to mark out the data
> of interest to I2RS, perhaps with a name attached so that there can be
> multiple sets of I2RS data, to read, to write, to copy and so on as a
> meaningful unit; it would probably be a mistake to call that a datastore
> given the more specific meaning that that term has acquired in NETCONF,
> of a unit of configuration data.
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.
/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
