> Obviously, relying on module names does not work if a module defines > multiple datastores. So either the set of datastores is identified > from reading the whole yang-library list or we provide a separate list > (and I think we should provide a separate list).
It seems okay for more than one datastore to be represented by a single module. Presumably the set of them come together as a package (all or none), right? This could be a datastore-designer decision to make. For instance, I2RS talks about priority-ordered planes of glass, so maybe they have a single "ietf-ds-ephemeral" module defining a package of datastores like: plane-1, plane-2, ... plane-8. Yes, we could have a separate explicit list, but it'd be nice if we could reuse what we have... K. _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
