Re: [YANG] default values

Ladislav Lhotka wrote:
> Assume there is a standard data model urn:ietf:X and a vendor that is
> essentially happy with it, but in their device they want to change a
> certain default value specified in the model. So they are forced to use
> another model, say, urn:vendor:Y. A NETCONF manager that uses urn:ietf:X
> should in principle be able to interoperate smoothly with the device but
> refuses to establish a session because of unknown capability.
> 
> If the model did not specify the behaviour of the device, the vendor
> could use it directly.
> 
> Lada
This only means that the standard body for that particular protocol was not careful enough when 
choosing the default value. Maybe it should have chosen a "SHOULD" type of default that is not 
formally specified in the default statement just included in the description statement.

YANG gives you the possibility to enforce a default. It just gives you this as an option, that 
you might or might not use.

Balazs

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