[netmod] Using an empty type in a list key

2016-08-30 Thread Sterne, Jason (Nokia - CA)
Hi all, I saw the addition of empty types in list keys in YANG 1.1 but had troubles finding more details in the NETMOD list. Is it discussed in the YANG 1.1 issues page (and if so, where is that now ? I tried an old link and it didn't work) ? If I take this example where I have a set of a

Re: [netmod] How to constrain a leaf to a read-only list of supported values?

2016-08-30 Thread Dale R. Worley
Balazs Lengyel writes: > Problem: how do you restrict values for (3) - file-compression so that > it is one of the nodes-supported-compression-types. The natural solution > would be to use a must expression or a leaf-ref, but as > nodes-supported-compression-types

Re: [netmod] How to constrain a leaf to a read-only list of supported values?

2016-08-30 Thread Jan Lindblad
Balazs, > We have the following design pattern. > > 1) An enumeration or a set of identities are defined that define a set of > options generally supported by Ericsson products. (e.g. supported > compression algorithms) > 2) The specific node sets in run-time a leaf-list indicating the set of

[netmod] Fwd: RE: Regarding IEEE/IETF coordination draft draft-wilton-netmod-intf-vlan-yang

2016-08-30 Thread Benoit Claise
Dear all, As discussed with the IEEE, here is a way to progress draft-wilton-netmod-intf-vlan-yang Rob, please update your draft with an Informational intended status. Regards, Benoit Forwarded Message Subject: RE: Regarding IEEE/IETF coordination draft

Re: [netmod] derived-from-or-self leads to circular import

2016-08-30 Thread Ladislav Lhotka
"Bogaert, Bart (Nokia - BE)" writes: > [ Unknown signature status ] >> On 29 Aug 2016, at 09:17, Bogaert, Bart (Nokia - BE) > wrote: >> >> Just taking another approach on this: why do we have the restriction >> on circular imports? Is this