On Sun, Mar 19, 2017 at 06:11:35PM +0000, Kent Watsen wrote: > > Wait, I think you're mixing things up. I'm not talking about using YANG > Library to identify which datastores a module can be accessed in, so much as > knowing which datastores are implemented in the first place. > > For instance, assuming the "ephemeral" datastore example example in the > draft, a client knows a server implements it because ietf-ds-ephemeral is > listed in YANG Library. And so it is with all dynamic datastores, but not > so for built-in (non-dynamic) datastores (e.g. intended) because there isn't > a module to advertise for them (yet). >
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). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
