Re: [netmod] [netconf] Comments on draft-ietf-netconf-nmda-netconf-05

Hi All, I plan to implement this draft and hence had some implementation related clarifications. 1. I feel that there should be more text added about "origin" filtering mechanism. I am not clear about some aspects of origin filtering. RFC 8342 : NMDA RFC provides the below example

Re: [netmod] yang-data-ext issues

> People want to use YANG to define the schema for an XML or JSON > representation of a stand-alone document. Agreed > The only data needed must be module + local-name. Or maybe: module + local-name + context, where context is one of: - data nodes - RPC/actions - notifications -

Re: [netmod] yang-data-ext issues

On Mon, Apr 23, 2018 at 1:08 PM, Martin Bjorklund wrote: > Andy Bierman wrote: > > > > > > > > > > > I do not understand the need for a yang-data structure that > represents > > > data > > > > that can be instantiated anywhere and everywhere. > > > > >

Re: [netmod] yang-data-ext issues

On Tue, 2018-04-24 at 16:36 +0200, Martin Bjorklund wrote: > Ladislav Lhotka wrote: > > Martin Bjorklund writes: > > > > > Hi, > > > > > > I am not sure what this statement tells us re. the issue in this email > > > thread. > > > > It tells us that, in my view,

Re: [netmod] yang-data-ext issues

Robert Wilton wrote: > > > On 23/04/2018 21:08, Martin Bjorklund wrote: > > Andy Bierman wrote: > >>> > I do not understand the need for a yang-data structure that represents > >>> data > that can be instantiated anywhere and everywhere. >

Re: [netmod] yang-data-ext issues

Ladislav Lhotka wrote: > Robert Varga writes: > > > On 23/04/18 18:51, Juergen Schoenwaelder wrote: > >> Some people will say that the cost of a new language version is high. > >> (Well, when we did 1.1, some people said it will never be deployed.) > >> Anyway, not

Re: [netmod] yang-data-ext issues

Ladislav Lhotka wrote: > Martin Bjorklund writes: > > > Hi, > > > > I am not sure what this statement tells us re. the issue in this email > > thread. > > It tells us that, in my view, the approach taken in this document is a > bad idea. Do you mean that the WG

Re: [netmod] yang-data-ext issues

Martin Bjorklund writes: > Hi, > > I am not sure what this statement tells us re. the issue in this email > thread. It tells us that, in my view, the approach taken in this document is a bad idea. Lada > > > /martin > > > Juergen Schoenwaelder

Re: [netmod] yang-data-ext issues

Robert Varga writes: > On 23/04/18 18:51, Juergen Schoenwaelder wrote: >> Some people will say that the cost of a new language version is high. >> (Well, when we did 1.1, some people said it will never be deployed.) >> Anyway, not bumping the YANG version number but having instead

Re: [netmod] Extensions vs new YANG versions [was Re: yang-data-ext issues]

Robert Wilton writes: > [Renaming the thread because this doesn't seem to be directly applicable > to the yang-data extension.] > > I think that extensions are great in the sense that they allow YANG to > evolve more quickly without requiring a fork lift version upgrade that

Re: [netmod] yang-data-ext issues

On 23/04/2018 21:08, Martin Bjorklund wrote: Andy Bierman wrote: I do not understand the need for a yang-data structure that represents data that can be instantiated anywhere and everywhere. AFAIK noone is proposing that. I do not want to break existing tools

[netmod] Extensions vs new YANG versions [was Re: yang-data-ext issues]

[Renaming the thread because this doesn't seem to be directly applicable to the yang-data extension.] I think that extensions are great in the sense that they allow YANG to evolve more quickly without requiring a fork lift version upgrade that may take a long time to produce. I agree that