Re: [netmod] JSON encoding of anyxml

On Mon, Nov 16, 2015 at 3:55 AM, Juergen Schoenwaelder < j.schoenwael...@jacobs-university.de> wrote: > On Sat, Nov 14, 2015 at 09:05:00AM -0800, Andy Bierman wrote: > > > > YANG 1.1 is going to take 2 more years if we slowly revisit every issue. > > I thought the whole point of the issue tracker

Re: [netmod] JSON encoding of anyxml

> On 16 Nov 2015, at 14:40, Juergen Schoenwaelder > wrote: > > On Mon, Nov 16, 2015 at 01:09:20PM +0100, Ladislav Lhotka wrote: >> >>> On 16 Nov 2015, at 12:55, Juergen Schoenwaelder >>> wrote: >>> >>> On Sat, Nov

Re: [netmod] JSON encoding of anyxml

On Mon, Nov 16, 2015 at 01:09:20PM +0100, Ladislav Lhotka wrote: > > > On 16 Nov 2015, at 12:55, Juergen Schoenwaelder > > wrote: > > > > On Sat, Nov 14, 2015 at 09:05:00AM -0800, Andy Bierman wrote: > >> > >> YANG 1.1 is going to take 2 more years if we

Re: [netmod] derived-from() and derived-from-or-self() arguments

Hi, William Lupton wrote: > Hi, > > I'm sure there's an obvious reason for this, but could someone explain why > these functions need a separate module-name argument rather than just using > that module's prefix on the identity-name argument? The only reason is that there are

Re: [netmod] JSON encoding of anyxml

On Sat, Nov 14, 2015 at 09:05:00AM -0800, Andy Bierman wrote: > > YANG 1.1 is going to take 2 more years if we slowly revisit every issue. > I thought the whole point of the issue tracker was to prevent this sort > of thing. The rule should be "what new details have emerged that > should cause

[netmod] review of model-classification draft

Have a quick review of draft-bogdanovic-netmod-yang-model-classification-05, I have a few comments as follows: 1. This document introduce several terms to provide consistent classification yang models in IETF and other SDOs, e.g.,standard model, vendor specific model, I am wondering if