[netmod] kw comments on draft-voit-netmod-yang-mount-requirements

[Kent Watsen <[e-mail]>]

[As a contributor]

Note: this is a -00 document, but only because the draft's name changed.  In reality this is like a draft-voit-netmod-peer-mount-requirements-04.    Looking at the diffs, there aren't many changes, mostly cleanup and adding the "schema mount" concept.   That is, the new "yang mount" term is use to cover all of "schema mount", "alias mount", and "peer mount".

My comment is mostly high-level.   I'm wondering about the need for this draft to include schema mount at all.   That is, a schema mount solution draft is now an adopted WG item, and I'm unsure if the authors of that draft are looking to this one to define requirements.  Perhaps the goal is to define the umbrella term "yang mount", but to be honest, I don't really see a need to have a term that spans both schema and data mounts.   I'm not sure how others feel about this, but my thoughts are that we should define terms like:

- scheme-mount
- data-mount
- remote data mount   (a.k.a. peer mount)
- local data mount        (a.k.a. alias mount)

More so than:

yang-mount
- scheme-mount
- alias-mount
- peer-mount


I realize that the full-impact of this change would impact draft-clemm-netmod-mount, but I'd like us to settle on long-term terms as soon as possible.

My other high-level thought is, assuming the schema-mount requirements are removed from this draft, would there really be a need for this requirements draft?  - is it expected to get published or would it be allowed to expire, as soon as the WG adopts draft-clemm-netmod-mount, as then it's purpose would've been served?   I realize that we have a precedent with opstate-reqs, but I might claim that that doc was necessary as we (the WG) really didn't understand the requirements and we had to document them.  In this case, it seems that alias/peer/data-mount has fewer parties involved and, in fact, is partially documenting an existing implementation (ODL).  Maybe my question is, would it make long-term sense to merge the requirements text into draft-clemm-netmod-mount?

Thanks,
Kent