Re: [YANG] new pyang errors

Just to give you example of the need for fixed values:
Due to our need to map YANG data to LDAP, we need a key on all encapsulating objects. So we 
have to use lists instead of containers, even where we know there will only be one list entry. 
Often the key for such single entry lists is fixed, but still needed.
So this key is config , mandatory, and fixed.
Balazs

Phil Shafer wrote:
> 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 mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang