Juergen,
See below.
On 2/4/2016 7:00 AM, Juergen Schoenwaelder wrote:
> 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/
yes.
>
> 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,
interfaces.
> why
> can I not mount a non-top-level module)?
Good question. This should be added to 5, i.e., a good capability, but
not used by our draft.
> And does 'incorporation of
> the data model' imply 'incorporation of the complete data model'?
to me these two are the same, so yes -- unless you are implying
something I'm missing ;-)
Cheers,
Lou
> /js
>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
