Re: [netmod] XPath questions about revised datastores

Andy,

in the past, there was the assumption that the operational value and
the configured value are always the same. This is not really a
'change' but much more a clarification what the expression means in
cases where the values differ.

/js

On Fri, Jun 16, 2017 at 10:24:19AM -0700, Andy Bierman wrote:
> The draft should make it clear that this change is being made.
> Before there was no way to access the operational value.
> Now there is only oerational value and no way to access the configured
> value.
> 
> 
> Andy
> 
> 
> On Fri, Jun 16, 2017 at 10:18 AM, Phil Shafer <phil@juniper.net> wrote:
> 
> > Andy Bierman writes:
> > >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.
> >
> > The XPath will refer to the current operational value, which is
> > better defined and more consistent behavior.  During the lack when
> > data is flowing between <intended> and <operational> as system
> > components read and follow new incoming configuration data, the
> > operational value should be guiding the constraints, not the
> > unrealized incoming value.
> >
> > The XPath continues to work in a backwards compatible manner, but
> > the outcome is more crisply defined and the <operational> datastore
> > will have better odds of being self-consistent.
> >
> > Thanks,
> >  Phil
> >

> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
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/>