Re: [netmod] Using an empty type in a list key

> On 09 Sep 2016, at 16:07, Andy Bierman wrote: > > > > On Fri, Sep 9, 2016 at 6:44 AM, Ladislav Lhotka wrote: > "Dale R. Worley" writes: > > > Andy Bierman writes: > >> Using a key of type empty is utterly

Re: [netmod] Using an empty type in a list key

On Fri, Sep 9, 2016 at 6:44 AM, Ladislav Lhotka wrote: > "Dale R. Worley" writes: > > > Andy Bierman writes: > >> Using a key of type empty is utterly pointless unless the point > >> is to make the instance identifier longer. > > > > IMO

Re: [netmod] Using an empty type in a list key

"Dale R. Worley" writes: > Andy Bierman writes: >> Using a key of type empty is utterly pointless unless the point >> is to make the instance identifier longer. > > IMO using a key of type empty (or any type with only one value) is > *pointless* but

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

"Dale R. Worley" writes: > 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

Re: [netmod] WG Last Call for draft-ietf-netmod-routing-cfg-23 (until Sep 9, 2016)

Kent Watsen writes: >>Then you probably already know what the solution is going to be. I don't. > > It’s not that I know the exact solution. It’s that I see this > approach offering good options for graceful migration to an opstate > compliant solution (for which I’m on