Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Alex Campbell
Hi, 'when' does not affect schema nodes, only data nodes. The schema nodes is essentially the YANG itself, without reference to any particular instance data. Given an example YANG fragment: list widgets { key name; leaf name {type string;} leaf can-frob {type

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Martin Bjorklund
Ladislav Lhotka wrote: > On Mon, 2017-12-04 at 18:22 +0100, Juergen Schoenwaelder wrote: > > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote: > > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > > > > Ladislav Lhotka wrote: > > > > >

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Juergen Schoenwaelder
On Mon, Dec 04, 2017 at 07:09:51PM +0100, Ladislav Lhotka wrote: > > Well, according to draft-ietf-netmod-revised-datastores-07: > >o datastore schema: The combined set of schema nodes for all modules > supported by a particular datastore, taking into consideration any >

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Ladislav Lhotka
On Mon, 2017-12-04 at 09:36 -0800, Andy Bierman wrote: > > > On Mon, Dec 4, 2017 at 9:22 AM, Juergen Schoenwaelder university.de> wrote: > > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote: > > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Ladislav Lhotka
On Mon, 2017-12-04 at 18:22 +0100, Juergen Schoenwaelder wrote: > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote: > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > > > Ladislav Lhotka wrote: > > > > Hi, > > > > > > > > if we have > > > > > > > >

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Andy Bierman
On Mon, Dec 4, 2017 at 9:05 AM, Ladislav Lhotka wrote: > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > > Ladislav Lhotka wrote: > > > Hi, > > > > > > if we have > > > > > > augment "/target/node" { > > > when "..."; > > > ... > > > } > > > > > >

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Andy Bierman
On Mon, Dec 4, 2017 at 9:22 AM, Juergen Schoenwaelder < j.schoenwael...@jacobs-university.de> wrote: > On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote: > > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > > > Ladislav Lhotka wrote: > > > > Hi, > > > > >

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Robert Wilton
Hi Lada, On 04/12/2017 17:05, Ladislav Lhotka wrote: On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: Ladislav Lhotka wrote: Hi, if we have augment "/target/node" { when "..."; ... } is the "when" expression supposed to be evaluated separately in each

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Juergen Schoenwaelder
On Mon, Dec 04, 2017 at 06:05:58PM +0100, Ladislav Lhotka wrote: > On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > > Ladislav Lhotka wrote: > > > Hi, > > > > > > if we have > > > > > > augment "/target/node" { > > > when "..."; > > > ... > > > } > > > > > > is

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Ladislav Lhotka
On Mon, 2017-12-04 at 17:34 +0100, Martin Bjorklund wrote: > Ladislav Lhotka wrote: > > Hi, > > > > if we have > > > > augment "/target/node" { > > when "..."; > > ... > > } > > > > is the "when" expression supposed to be evaluated separately in each > > datastore, > > and

Re: [netmod] evaluation of "when" under NMDA

2017-12-04 Thread Martin Bjorklund
Ladislav Lhotka wrote: > Hi, > > if we have > > augment "/target/node" { > when "..."; > ... > } > > is the "when" expression supposed to be evaluated separately in each > datastore, > and the augment applied only in those datastores where the result is true? Yes. > RFC

[netmod] evaluation of "when" under NMDA

2017-12-04 Thread Ladislav Lhotka
Hi, if we have augment "/target/node" { when "..."; ... } is the "when" expression supposed to be evaluated separately in each datastore, and the augment applied only in those datastores where the result is true? RFC 7950 says in sec. 7.21.5 that the context node for XPath evaluation is

Re: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00

2017-12-04 Thread Martin Bjorklund
Hi, I don't think that our documents reference the guidelines document, and I don't think they need to. RFC 7223 does not reference RFC 6087, for example. /martin Qin Wu wrote: > I have read this draft and believe it is ready for publication. > One question I have is

[netmod] *one* week 2nd WG Last Call: draft-ietf-netmod-revised-datastores-07

2017-12-04 Thread Lou Berger
All, This starts a second working group last call on draft-ietf-netmod-revised-datastores. As this is a 2nd LC that is focused on changes since the last LC, it closes in *one* week. The working group last call ends on December 11. Please send your comments to the netmod mailing list. At this

Re: [netmod] WG Last Call: draft-ietf-netmod-rfc7223bis-00

2017-12-04 Thread Martin Bjorklund
Alex Campbell wrote: > On page 37, "duplex" is mistyped as "duplexx". Thanks, now fixed. /martin > > Other than this minor error, I believe this draft is ready for publication. > > > From: netmod

Re: [netmod] WG Last Call: draft-ietf-netmod-rfc7277bis-00

2017-12-04 Thread Martin Bjorklund
Alex Campbell wrote: > Hi, > > I noticed the table in section 3 has been mangled - it has extra > blank lines, entries in the wrong side of the table, and a missing > pipe in the bottom right corner. Thanks, now fixed. The table now looks like this:

Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]

2017-12-04 Thread Balazs Lengyel
On 2017-12-01 18:49, Andy Bierman wrote: On Fri, Dec 1, 2017 at 3:37 AM, Balazs Lengyel wrote: Hello,

Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]

2017-12-04 Thread Balazs Lengyel
On 2017-12-01 23:41, Randy Presuhn wrote: Hi - On 12/1/2017 3:37 AM, Balazs Lengyel wrote: Hello, https://tools.ietf.org/html/rfc7950#section-7.21.2     o  "deprecated" indicates an obsolete definition, but it permits    new/continued implementation in order to foster interoperability