Re: [netmod] WG Last Call: draft-ietf-netmod-schema-mount-07

Hi,

I have read this draft a few times.
I have not implemented the draft but it seems reasonably constrained.

here are some comments.

Sec 1: seems like a lot of background on YANG and then some explanation
of the solution.  The problem statement is never really explained.
Some discussion of building blocks for virtual servers might help.

Sec. 3.3: there are no examples of multiple level schema -mounts.
What is the use-case for this complexity?

Sec. 4: an instance document showing the config for the example would help

Sec. 5: A NETCONF example of an RPC converted to action would help.
Also mention action converted to deeper nested action would help.
Sec. A.4 has a very terse RESTCONF example.

Sec. 8: There are no examples using the mount-point extension-stmt
Why is this restriction in the text? It is not explained.

          The 'mount-point' statement MUST NOT be used in a YANG
          version 1 module, neither explicitly nor via a 'uses'
          statement.

I do not understand why the mount-point subtree is needed twice in the YANG
module.
Why is the list duplicated under each schema entry?
An example showing the entire YANG module would help.
Seems like a lot of duplication of the YANG library.

Why is the entire schema-mounts container config=false?
There is no standard way to configure the schema mounts?
All this data is configured via proprietary models, probably
with even more copies of the YANG library?

Andy

On Fri, Oct 20, 2017 at 2:37 PM, Kent Watsen <kwatsen@juniper.net> wrote:

> All,
>
> This starts a two-week working group last call on
> draft-ietf-netmod-schema-mount-07.
>
> The working group last call ends on November 3.
> Please send your comments to the netmod mailing list.
>
> Positive comments, e.g., "I've reviewed this document
> and believe it is ready for publication", are welcome!
> This is useful and important, even from authors.
>
> Could the authors, explicitly CC-ed on this email,
> please also confirm one more time that they are
> unaware of any IPR related to this draft.
>
> Thank you,
> Netmod Chairs
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>