Hi, Jürgen,
Although RFC 8342 avoids it, the problem remains in the real world: The client has the desire to reference system defined nodes, Must the referenced system configuration always be copied to <running>? Does the entire system-generated list entry need to be copied, or it is just the list with at least the key? What if the system configuration changes and a stale copy ends up in <running>? How does the client overwrite a system-provided value? Or how to configure the descendant nodes of system configuration? Is the copy needed? Some system configurations are defined solely as a convenience (e.g., some system provided policies), one of the objectives is to avoid re-creating system configuration in <running>. I think the current design makes the interplay between system configuration and client-provided configuration clear (e.g., allows <running> references system config without requiring it to be copied into <running>). Best Regards, Qiufang -----Original Message----- From: Jürgen Schönwälder [mailto:[email protected]] Sent: Monday, December 2, 2024 5:22 PM To: Kent Watsen <[email protected]> Cc: maqiufang (A) <[email protected]>; Jason Sterne <[email protected]>; [email protected] Subject: Re: [netmod] origin "system" in system-config-09 On Sun, Dec 01, 2024 at 06:25:34PM +0000, Kent Watsen wrote: > > > Another option that comes to mind is that the system datastore does > > not feed into anything. Instead, it just exposes the (current) > > system configuration and if someone wants to use it, that someone > > can copy it into running and then takes responsibility for it. > > I do not favor this because it leads to stale definitions. > How can something that is not feeding into anything lead to stale definitions? The argument was that the system may change and such a change my cause <running> to become invalid if <system> is merged into <intended>. This was the reason why <system> in RFC 8342 is _not_ feeding into <intended>. Hence, I proposed that if people want to expose system, they do it in a way such that <system> is accessible but not automatically used. To use it, "something" taking over responsiblity has to make definitions explicit config in <running>. /js -- Jürgen Schönwälder Constructor University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
