Hi,

In some of the previous opstate related discussions on this alias, I had some confusion as to which datastore operational state is held in (or whether it is held in a datastore at all :-)

It also seems that the NETCONF/YANG related RFCs are vague on whether operational state is actually held in a datastore, or if so what it is. I've given some snippets below. Is this something that needs to be clarified as errata to those standards (particularly NACM)?

--

rfc6020bis, section 7.21.1.  The config Statement states:

"   If "config" is "false", the definition represents state data. Data
   nodes representing state data are not part of configuration
   datastores."

... which obviously indicates that they are not part of any configuration datastore, but doesn't indicate that they are part of an operational state datastore.

--

rfc6241 (section 1.1 terminology) defines datastore and configuration datastore as:

   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.


The NETCONF RFC then goes on to describe/use configuration datastores in various ways, but makes no further mention of any operational state datastore.

E.g. the one line description of a NETCONF get request is "Description: Retrieve running configuration and device state information."

--

rfc6536 NACM, (section 3.2.  Datastore Access) states:

   Only the standard NETCONF datastores (candidate, running, and
   startup) are controlled by NACM.  Local or remote files or datastores
   accessed via the <url> parameter are not controlled by NACM.


Which implies that if operational state is held in a datastore then it is not controlled by NACM - which presumably can't be right.


Thanks,
Rob






_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to