Hi Juergen,
My intention is only to get clarity about what is the meaning of implementing a
module in a data-store, as it used in below places,
" It must be possible to NOT implement a module or feature in
<operational>, even if it is implemented in some other datastore"
" 2. A dynamic configuration datastore must be able to implement a
module or feature that is not implemented in the conventional
configuration datastores."
A module having only "ro" nodes , can be considered to be implemented in any
data-store ? operational/ephemeral etc
A module having "rw" nodes, what is the rules for it to be considered
implemented in a data-store ?
RFC 7950 is quite clear for the rules for when a module is considered
implemented. Please clarify implementation with respect to data-store also.
With Regards,
Rohit R Ranade
-----Original Message-----
From: Juergen Schoenwaelder [mailto:[email protected]]
Sent: 30 May 2018 11:10
To: Rohit R Ranade <[email protected]>
Cc: Robert Wilton <[email protected]>; [email protected]
Subject: Re: [netmod] draft-ietf-netconf-rfc7895bis-06 deviation query
On Wed, May 30, 2018 at 05:21:29AM +0000, Rohit R Ranade wrote:
>
> Also what does it mean that state-modules have been "implemented" in the
> <running> data-store ?
>
The server implemented an empty set of objects. No client should have an issue
with that and a server may choose to report this (for example if the server
wants to have a single schema for all datastores).
I do not see why making this illegal would simplify anything. It seems making
this illegal just adds complexity for no value.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
