On Mon, Nov 29, 2021 at 03:14:06PM -0800, Andy Bierman wrote: > > IMO the least disruptive solution possible should be used. > There is a use-case for adding "origin" support to the <running> datastore > in the <get-data> operation. > This allows an NMDA client to identify system config that is not being used > in <operational>. >
Looking at Figure 2 of RFC 8342, I wonder how system config gets into running - other than a client writing it into running, at which point the config becomes explicit config subject to the usual update rules of <running>. Conceptually, you can have a system daemon acting as a client updating <running> (perhaps even controllable by NACM). The "origin" was not designed to track from which application config data in <running> is originating, that's to be solved by other mechanisms. /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
