On Wed, Jun 21, 2017 at 10:03:21AM +0100, Robert Wilton wrote:
>
> We found that trying to define what "configuration is, or isn't", is hard,
> but still regard having a definition is important.
>
> In the end, I see that the real core of the definition is actually the
> config true sentence. I.e. the intention of the draft is to define
> configuration as the nodes in the YANG schema that are labelled as config
> true, and hence it is the marking of the node as config true that actually
> makes it configuration (at least in the context of this draft and
> NETCONF/YANG).
>
> So, do you think that it would help if the definition text was reordered to
> make the binding to YANG config true first and foremost?
>
> E.g.
>
> Old:
> o configuration: Data that determines how a device behaves. This
> data is modeled in YANG using "config true" nodes. Configuration
> can originate from different sources.
>
> New:
> configuration: All data that is modelled in YANG using "config
> true" nodes. Configuration is used to instruct how a device behaves.
> Configuration can originate from different sources.
>
I think this was true at some point of the internal discussions but I
think it is not true any longer. I believe the fix is this (moving the
config true statement to the definition of conventional
configuration):
NEW:
o configuration: Data that determines how a device behaves.
Configuration can originate from different sources.
o conventional configuration: Configuration that is stored in any of
the conventional configuration datastores. This data is modeled in
YANG using "config true" nodes.
---8<--- snip ---8<---
In the current NMDA draft, configuration is a combination of
conventional configuration, dynamic configuration, learned
configuration, system configuration, and default configuration.
Perhaps we need to create more figures:
configuration
|
+ conventional configuration (origin intended)
+ dynamic configuration (origin dynamic)
+ learned configuration (origin learned)
+ system configuration (origin system)
+ default configuration (origin default)
I am not sure whether dynamic configuration (e.g., coming from an I2RS
subsystem) or system configuration is necessarily restricted to config
true nodes. By moving the config true statement to the definition of
the term conventional configuration, we state something where we are
sure the statement is correct.
/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/>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
