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]
