Re: [YANG] new pyang errors

Ladislav Lhotka writes:
>Relying on common universal
>defaults would make the system fragile.

As will shipping voluminous defaults.

Visibility into defaults is a distinct issue from carrying the
defaults in the configuration database.  If I have an object with
50 fields where only 2 or 3 are set on each instance, carting around
fully-fleshed configs will be incredibly annoying.

My view of configuration is that if you set it, it should be there.
If you didn't set it, it shouldn't be there.  If you want extra
information, ask for it.  But the normal view of configuration
should be restricted to only what the user or application expressed
configured.

This leads directly to my interpretation of "mandatory".  A mandatory
config statement is one that some user or application must expressly
configure.  If the configuration is valid without the statement,
then it's not mandatory.

The "mandatory"-ness describes the interaction between the device and
applications configuring it.  If the application must create the statement,
then the statement is mandatory.  The "mandatory plus default" interpretation
Andy's using is more of a description of the interaction between the on-box
management software and the other on-box software components.  IMHO this is
less interesting and more internals that YANG should be describing.

Thanks,
 Phil

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang