[YANG] mandatory & default

Hi,

I don't think every vendor deals with agent-created defaults in the
same way, and there is zero chance every implementation will converge
on one interpretation.

The important thing to consider is:
   what is important for standards-based configuration?

Here is the bottom line:

  - RFC 4741 requires that *all* config database objects be returned
    in a <get-config> without any filters

  - All data nodes that exist in the configuration have some value
    (consider the value for 'empty' to be present/not-present)

  - An extension is needed (e.g., with-defaults=false) to change the
    behavior of RFC 4741 wrt/ returning a subset of all nodes without
    any filter defined

Phil seems to be arguing that nodes that contain the agent-specified
default value are not really there.   Yet, if the manager
sets a node explicitly to the default value, it is there.
IMO, this is rather confusing, and broken.

The idea of tracking down stacks of offline vendor documentation
to determine the theoretical values of these 'default nodes', instead of
simply asking the agent for the real values, is a non-starter.
That may be good enough for CLI, but not standards based configuration.

Andy

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