On Fri, Jun 16, 2017 at 09:40:21AM -0700, Andy Bierman wrote:
> >
> > ,,,,
> > > >
> > > Sec 5.1 of the RD draft does not mention config=true nodes.
> >
> > The operational state datastore's schema is all config true and all
> > config false nodes.
> >
> >
> This actually changes the behavior of YANG XPath.
>
> container foo {
> leaf A { type int8; }
> leaf B {
> when "../A > 3";
> type int8;
> config false;
> }
> }
>
>
> It has always been OK for a config=false data node's XPath expression to
> point at a config=true data node.
> But this has always meant the configured value. RD changes this behavior
> because the new opstate datastore
> contains only the operational values of config=true nodes. Now there is no
> way for such an XPath expression
> to test the configured value.
>
Having something in the operational state dependent on a configured
value that has not yet been applied is broken. If you set A in
<running> to 5 but the operationally used value of A is still 2, then
we believe B should not be there.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
