Re: [YANG] new pyang errors

Ladislav Lhotka writes:
>My definition of mandatory: mandatory configuration parameters are those
>that are essential for device or protocol operation. It doesn't matter
>whether they are set by the user/application, supplied from non-volatile
>memory or perhaps even hardwired.

Why would you need or want to mark is as mandatory if the value
is hardwired?  What are you trying to say by calling a parameter
"mandatory" and who are you trying to say it to?

If the application need do nothing with such hardwired parameters,
why does it need to distinquish them?

If the device need to nothing <ditto>?

YANG defines constraints on the XML that passes between the client and
server.  Nearly every statement in a YANG module defines a rule which
that XML must follow, both during protocol operations and the valid
configuration being built.

Mandatory is such a constraint, and should be an indication to the
NETCONF client application that it needs to do something explicit
to satisfy this constraint.  If the mandatory parameter isn't set,
the configuration isn't valid.

If we allow this mandatory constraint to be satisfied via mechanisms
that do not involve the client and server, why have it?  How is the
application to discern the difference between a real constraint and
a parameter that the fairy god mother daemon fills in?

>A (full) configuration is valid only
>if it contains all values that are declared as mandatory in the DM. 

This is a definition that both sides of the debate can love, which
is a problem.

Thanks,
 Phil

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