Subject: [netmod] Config true/false Read/Write vs Read Only [was Re: [Netconf] WG adoption of NETCONF NDMA draft]

From: Robert Wilton <[email-masked]>
Date: Fri, 29 Sep 2017 11:45:56 +0100

[Cross posting to Netmod WG]

Hi Michael,

On 26/09/2017 03:27, wangzitao wrote:
>
> Hi WG,
>
> I support adoption of this work. And I have some comments:
>
> ………………………………………………………………………………………………………………………………………………………………………..
>
>          container where {
>
>            description
>
>              "Filter content with the specified criteria.  All given
>
>               criteria are logically AND:ed.";
>
>            leaf config {
>
>              type boolean;
>
>              description
>
>                "Filter for nodes with the given value for their
>
>                 'config' property.";
>
>            }
>
> <Michael>: Here defined config truth/false as a filter’s criteria. 
> According to NMDA revised datastore, there are four type (ct = config 
> true; cf = config false
>
>        rw = read-write; ro = read-only). Why not define the “rw” and 
> “ro” as other criteria?
The ct/cf and rw/ro are reporting two different things are 2 different 
things:

A YANG schema node can be labelled as config true, or config false.
Some YANG datastores can only be read by a client (e.g. <intended> and 
<operational>).
Other YANG datastores can be both read and also written by the client 
(e.g. <running>, <startup>, <candidate>).

Do you think that the NMDA draft is sufficiently clear on this point, or 
does this need to be clarified in some way?

Thanks,
Rob