Hi,

I think the remnant configuration text needs clarification.
I thought the whole point of the operational datastore for config=true
nodes was to
provide the intended and applied values using the exact same
instance-identifier.

NC/RC/YANG does not allow the old operational value and new operational
value to
exist in the same datastore.  Once the server has the new value to report,
it will overwrite
the old value.

Perhaps you mean other instances will be considered old, but the RD
solution has no way to
correlate the new instances to the old ones. Therefore, YANG validation may
fail on the operational
datastore while updates are being applied. I think the draft should make
this more clear.


Andy


On Thu, May 11, 2017 at 1:22 PM, Martin Bjorklund <m...@tail-f.com> wrote:

> Hi,
>
> This version addresses the comments on the ML, and contains some
> reworked terminiology in order to be consistent.  Further, all open
> issues are resolved.  We have also removed the Appendicies that
> previously were included as placeholders for text that will go into
> other documents.
>
> >From the authors' point of view, this version is ready for WG LC.
>
>
> /martin
>
>
>
>
> internet-dra...@ietf.org wrote:
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the NETCONF Data Modeling Language of the
> IETF.
> >
> >         Title           : Network Management Datastore Architecture
> >         Authors         : Martin Bjorklund
> >                           Juergen Schoenwaelder
> >                           Phil Shafer
> >                           Kent Watsen
> >                           Rob Wilton
> >       Filename        : draft-ietf-netmod-revised-datastores-02.txt
> >       Pages           : 34
> >       Date            : 2017-05-11
> >
> > Abstract:
> >    Datastores are a fundamental concept binding the data models written
> >    in the YANG data modeling language to network management protocols
> >    such as NETCONF and RESTCONF.  This document defines an architectural
> >    framework for datastores based on the experience gained with the
> >    initial simpler model, addressing requirements that were not well
> >    supported in the initial model.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-netmod-revised-datastores/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-netmod-revised-datastores-02
> > https://datatracker.ietf.org/doc/html/draft-ietf-netmod-
> revised-datastores-02
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-
> revised-datastores-02
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
>
> _______________________________________________
> netmod mailing list
> 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