Re: [netmod] [Netconf] LC of NDMA NETCONF/RESTCONF drafts

[Andy Bierman <[e-mail]>]

On Wed, Jan 31, 2018 at 12:11 AM, Juergen Schoenwaelder <
[e-mail]> wrote:

> On Tue, Jan 30, 2018 at 12:35:33PM -0800, Andy Bierman wrote:
> > Hi,
> >
> > I have some questions about these drafts.
> >
> > 1) what if datastore set to "conventional"?
> >     There are many places where a datastore-ref type is used.
> >     However, "conventional" is valid for base "datastore", even though
> >     it is ambiguous as a datastore selector.
>
> We can add explicit text that an identity that does not resolve to a
> datastore implemented by the server results in an invalid value error.
>
>

OK



> > 2) origin filter is limited to 1 source
> >    This filtering seems rather limited.  A client must retrieve
> > <with-origin> and check
> >     all the values in use, then make repeated requests for each source
> as a
> > different
> >     <origin-filter> leaf
>
> If the client does <with-origin>, then it has all origin information
> and it can filter locally. That said, we could make origin-filter a
> leaf-list which is logically ORed so that one can retrieve
> origin-filter=or:system or origin-filter=or:learned in one request.
>
>

OK


> > 3) with-defaults broken
> >     The operational datastore does not support with-defaults.
> >      Instead, the client must use origin-filter=or:default or with-origin
> >      and check all the origin attributes.  Since a client needs to use
> >      with-defaults for other datastores, this special handling of
> > <operational>
> >      seems unhelpful.
>
> I think the with-defaults semantics for conventional configuration
> datastores are much more complicated than necessary for the
> operational state datastore. Note that that the operational state
> datastore reports in-use values not really defaults:
>
>   <leaf or:origin='default'>foo</leaf>
>
> This reports that the value 'foo' is in use and that it originates
> from a default value. Note that this could also be
>
>   <leaf or:origin='intended'>foo</leaf>
>
> in case the intended configuration datastore configured the value
> 'foo' (despite this value matching the default). The with-defaults
> solution is pretty complex because it tries to handle how different
> systems deal with configuration defaults. The idea is to not carry
> this complexity over to in-use values in the operational state
> datastore.
>
>

Before NMDA, the client could decide if it wanted to retrieve default nodes
or not.
This client-choice has been removed from NMDA, which is a problem.




> /js
>
>
Andy


> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   [phone]         <https://www.jacobs-university.de/>
>