> 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. For example, the <system> datastore may define a bag of trust anchor certificates, i.e., <system> implements RFC9641. The bag as a whole is referenced by <running>, but the bag's contents may change, e.g., when the device’s software is updated. Kent _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
