Re: [netmod] yang-data-ext issues

Hi, this is a slippery slope. If we want to turn YANG into a general-purpose schema language, it should IMO be done the other way around: design a general-purpose schema language with a sound architecture, and then use it for defining schemas of datastores, protocol messages or whatever. YANG

[netmod] comments on draft-ietf-netmod-module-tags-01

Hi, Here are my comments for this draft. I hope it can be completely quickly. * sec 3.2: Vendor Tags however, it is recommended that the vendor consider including extra identification in the tag name to avoid collisions (e.g., vendor:super-duper-company:...). - Suggest standard

Re: [netmod] draft-ietf-netmod-acl-model

[just back from PTO] I'll be doing the shepherd write-up shortly. Kent // shepherd = original message = status on this draft? ___ netmod mailing list netmod@ietf.org

Re: [netmod] yang-data-ext issues

On Mon, Apr 16, 2018 at 9:46 AM, Robert Wilton wrote: > > > On 16/04/2018 17:07, Andy Bierman wrote: > > > > On Mon, Apr 16, 2018 at 8:44 AM, Robert Wilton wrote: > >> Don't groupings have a somewhat similar concern? >> >> E.g. if two groupings define the

Re: [netmod] yang-data-ext issues

On 16/04/2018 17:07, Andy Bierman wrote: On Mon, Apr 16, 2018 at 8:44 AM, Robert Wilton > wrote: Don't groupings have a somewhat similar concern?  E.g. if two groupings define the same data node name and are used at the same point

Re: [netmod] yang-data-ext issues

Andy Bierman wrote: > On Mon, Apr 16, 2018 at 8:44 AM, Robert Wilton wrote: > > > Don't groupings have a somewhat similar concern? > > > > E.g. if two groupings define the same data node name and are used at the > > same point then you would get a

Re: [netmod] yang-data-ext issues

On Mon, Apr 16, 2018 at 8:44 AM, Robert Wilton wrote: > Don't groupings have a somewhat similar concern? > > E.g. if two groupings define the same data node name and are used at the > same point then you would get a namespace clash, but YANG does not disallow > the groupings:

Re: [netmod] yang-data-ext issues

Don't groupings have a somewhat similar concern?  E.g. if two groupings define the same data node name and are used at the same point then you would get a namespace clash, but YANG does not disallow the groupings: grouping foo_widget { leaf name { type string;

Re: [netmod] yang-data-ext issues

Hi, Andy Bierman wrote: > On Mon, Apr 16, 2018 at 6:33 AM, Joe Clarke wrote: > > > On 4/16/18 08:56, Martin Bjorklund wrote: > > > Hi, > > > > > > While preparing draft-ietf-netmod-yang-data-ext-02, it turned out that > > > it is not clear what, if any,

Re: [netmod] yang-data-ext issues

On Mon, Apr 16, 2018 at 6:33 AM, Joe Clarke wrote: > On 4/16/18 08:56, Martin Bjorklund wrote: > > Hi, > > > > While preparing draft-ietf-netmod-yang-data-ext-02, it turned out that > > it is not clear what, if any, restrictions should be enforced for > > yang-data structures.

Re: [netmod] yang-data-ext issues

Hi, Andy Bierman wrote: > Hi, > > I am strongly opposed to this change because it breaks the rule in YANG 1.1 > that there cannot be 2 sibling nodes defined in the same module namespace. > > IMO since any yang-data nodes are ALLOWED to be used at the top-level, > then these

Re: [netmod] yang-data-ext issues

Hi, I am strongly opposed to this change because it breaks the rule in YANG 1.1 that there cannot be 2 sibling nodes defined in the same module namespace. IMO since any yang-data nodes are ALLOWED to be used at the top-level, then these top-level nodes cannot have conflicting names. It is very

Re: [netmod] yang-data-ext issues

On 4/16/18 08:56, Martin Bjorklund wrote: > Hi, > > While preparing draft-ietf-netmod-yang-data-ext-02, it turned out that > it is not clear what, if any, restrictions should be enforced for > yang-data structures. Even among the authors we have different ideas > for how this should work. > >

[netmod] yang-data-ext issues

Hi, While preparing draft-ietf-netmod-yang-data-ext-02, it turned out that it is not clear what, if any, restrictions should be enforced for yang-data structures. Even among the authors we have different ideas for how this should work. Background: In 8040, the original yang-data extension had