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
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:
> > > > >
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
>
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
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
> > > >
> > > >
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 "...";
> > > ...
> > > }
> > >
> > >
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,
> > > >
>
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
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
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
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
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
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
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
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
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:
On 2017-12-01 18:49, Andy Bierman
wrote:
On Fri, Dec 1, 2017 at 3:37 AM,
Balazs Lengyel
wrote:
Hello,
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
18 matches
Mail list logo