>> The new dynamic datastores are (per this draft) advertised by being >> listed in YANG Library. Only the "built in" datastores wouldn't have >> a module-backing. > > Actually, in the current draft, each module has a leaf-list of all > datastores (not only dynamic) where the module is implemented. > > We have discussed various variations on this theme, but the current > leaf-list is probably the simplest.
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). K. _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
