Hi Jason, > The primary <system> config use cases I see aren't so much interfaces, cards, > etc. It is more for things like built in qos profiles and other handy policy > objects that are more static (e.g. like Kent's JUNOS examples he has > described). I'm not necessarily saying we preclude some of the > resource-based dynamic system config proposed in the draft, but maybe those > parts are more confusing/contentious.
I agree about the primary focus being on the “shared objects”…at least, that’s 90% of what’s in the JUNOS junos-defaults “datastore” (in quotes because it’s not really a datastore). K. _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
