Re: [netmod] update on "rdns" URN for enterprise YANG models

2016-05-26 Thread Alex Campbell
> From: netmod on behalf of Ing-Wher (Helen) Chen > > Sent: Thursday, 21 April 2016 2:40 a.m. > To: Juergen Schoenwaelder > Cc: netmod@ietf.org > Subject: Re: [netmod] update on "rdns" URN for enterprise YANG models > > > -Original Message- > > From: Juergen Schoenwaelder [mailto:j.sch

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Andy Bierman
Hi, I ran a test on a module with these 2 statements: container top { list mand-list { key name; min-elements 1; leaf name { type string; } leaf-list vlan-id { type uint32; } } } choice top-ch { default A; case A { list mand-list { key

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Andy Bierman
On Thu, May 26, 2016 at 6:51 AM, Martin Bjorklund wrote: > Andy Bierman wrote: > > On Thu, May 26, 2016 at 6:26 AM, Martin Bjorklund > wrote: > > > > > Andy Bierman wrote: > > > > Hi, > > > > > > > > Our compiler generates a "top-level mandatory" warning for something > > > > like this: > > >

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Martin Bjorklund
Andy Bierman wrote: > On Thu, May 26, 2016 at 6:26 AM, Martin Bjorklund wrote: > > > Andy Bierman wrote: > > > Hi, > > > > > > Our compiler generates a "top-level mandatory" warning for something > > > like this: > > > > > >container top { > > > list foo { > > > min-elements 1;

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Andy Bierman
On Thu, May 26, 2016 at 6:44 AM, Ladislav Lhotka wrote: > > > On 26 May 2016, at 15:29, Andy Bierman wrote: > > > > > > > > On Thu, May 26, 2016 at 6:26 AM, Martin Bjorklund > wrote: > > Andy Bierman wrote: > > > Hi, > > > > > > Our compiler generates a "top-level mandatory" warning for someth

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Ladislav Lhotka
> On 26 May 2016, at 15:29, Andy Bierman wrote: > > > > On Thu, May 26, 2016 at 6:26 AM, Martin Bjorklund wrote: > Andy Bierman wrote: > > Hi, > > > > Our compiler generates a "top-level mandatory" warning for something > > like this: > > > >container top { > > list foo { > >

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Andy Bierman
On Thu, May 26, 2016 at 6:26 AM, Martin Bjorklund wrote: > Andy Bierman wrote: > > Hi, > > > > Our compiler generates a "top-level mandatory" warning for something > > like this: > > > >container top { > > list foo { > > min-elements 1; > > ... > > } > >} > > >

Re: [netmod] NP-container and min-elements

2016-05-26 Thread Martin Bjorklund
Andy Bierman wrote: > Hi, > > Our compiler generates a "top-level mandatory" warning for something > like this: > >container top { > list foo { > min-elements 1; > ... > } >} > > A customer is saying this is incorrect. RFC6020bis is confusing on this > issue.

[netmod] NP-container and min-elements

2016-05-26 Thread Andy Bierman
Hi, Our compiler generates a "top-level mandatory" warning for something like this: container top { list foo { min-elements 1; ... } } A customer is saying this is incorrect. RFC6020bis is confusing on this issue. Terms:: o mandatory node: A mandatory nod

Re: [netmod] update on "rdns" URN for enterprise YANG models

2016-05-26 Thread Juergen Schoenwaelder
On Wed, Apr 20, 2016 at 04:47:55PM +0200, Martin Bjorklund wrote: > > If you really want to limit it to YANG module namespaces, maybe it > should be called urn:yang-rdns: or something. I tend to agree, if this is YANG specific, it should say so. Perhaps it should be: "rdns" URN ::= urn: