> On Feb 23, 2016:10:08 AM, at 10:08 AM, Martin Bjorklund <m...@tail-f.com>
> wrote:
>
> Hi,
>
> In yesterday's meeting, Lou (I think?) mentioned a use case for mount
> that is not documented in draft-rtgyangdt-rtgwg-device-model; the need
> for being able to specify modules to mount directly in the schema.
> Something like this:
>
> container root {
> ymnt:mount-point "lne" {
> ymnt:mount-module "ietf-interfaces";
> }
> }
>
> It would be useful if the use case for this could be described in more
> details. Is it a requirement to be able to specify this in the
> schema, or could it be done (as Chris mentioned) in the RFC text?
>
> The reason I ask is that it is probably not as simple as the example
> above. First, you probably need to specify a revision of the module
> to be mounted. Or a min-revision. Then probably a set of features
> that must be enabled. And so on. It turns out that there is already
> a proposal for specifying such a "conformance profile" - YANG Packages
> (see draft-bierman-netmod-yang-package). Maybe it would be better to
> re-use packages?
A question: is the point to manually/explicitly mount a specific
container/s
or the root of a device? I’d like to understand the use case better here too
because, as you say, it can easily get complicated quickly.
—Tom
>
>
> /martin
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
