On Tue, Feb 02, 2016 at 02:04:12PM -0500, Lou Berger wrote: > > 5. while our primary requirement is for 'mounting' of top level > modules, mounting of submodules may also be useful. (DT not draft > driven.) >
A YANG submodule is by definition incomplete. For example, a submodule does not have a defined namespace. I think we should not waste effort to expose submodules beyond what they were designed to be used for - to break a really large module into pieces that can be edited more easily independently. If more granular mounts are needed, then we should IMHO _not_ bundle this with the notion of YANG submodules. Perhaps you meant submodules in a more generic way, but then perhaps: s/of submodules/of parts of modules/ Reading the other text again, I am not sure what is meant by the phrase "incorporation of the data model defined by one top-level module". What exactly is a 'top-level module' (and does it matter, why can I not mount a non-top-level module)? And does 'incorporation of the data model' imply 'incorporation of the complete data model'? /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
