Robert Wilton <rwil...@cisco.com> wrote:
> 
> 
> On 06/02/2016 00:41, Andy Bierman wrote:

[...]

> > IMO, this solution is a non-starter.
> OK, and yet my understanding is that the folks requesting a solution
> to the opstate problem are saying that the applied datastore approach
> is also a non-starter, or at least very undesirable.

But the key to finding a solution that works for everyone is to
understand *why* a datastore is a non-starter.  As I noted in a
previous email, both your solution and the datastore solution rely on
the assumption that the server internally knows the difference between
the "intended" and "applied" value for the config true nodes.

> (Note - I don't
> actually know whether they regard the solution in
> draft-wilton-netmod-opstate-yang to be any more palatable.)

Right; so if their objection is that the server cannot know the
difference between "intended" and "applied" for the config true leafs,
neither of our solutions work.

And if their objection is that their proprietary protocol does
can/does not encode the datastore in the "get" request, then
I suspect that their protocol also does not know your proposed
encoding.

> From a clients operational perspective I can see how the OpenConfig
> model, with separate intended config and applied config leaves that
> are co-located in the schema tree makes life easy for the client in a
> way that having a separate applied configuration datastore doesn't
> seem to.

I can see how the applied datastore model makes life easier for the
client, e.g., a diff can be done w/o any data model knowledge at all.


/martin


> 
> Rob
> 
> 
> >
> >
> >     /js (stating a clear opinion as a technical contributor)
> >
> >     --
> >     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/>
> >
> >
> >
> > Andy
> >
> >     _______________________________________________
> >     netmod mailing list
> >     netmod@ietf.org <mailto:netmod@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/netmod
> >
> >
> 

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

Reply via email to