[netmod] kw review of draft-ietf-netmod-schema-mount-09

[Kent Watsen <[e-mail]>]

1: paragraph starting w/ "In some cases", 1st sentence, s/often/sometimes/

2: add ref to RFC 8174

2.1: s/defines a label for/defines the label for/

3.1:
  a) 2nd paragraph, s/defines a label for/defines the label for/
  b) 4th paragraph, add ref to RFC 6020

3.2, 1st paragraph:
 a) 1st sentence, s/parent schema/data model supported by the server/?
 b) 2nd sentence, s#yangmnt:schema-mounts#/yangmnt:schema-mounts#?
 c) 2nd sentence, are mounts as stable as yang library?  It seems that
    if a new LNE were added, that would add a new mount point w/o 
    changing yang library...
 d) perhaps discuss the implications of it being as stable?  E.g.,
    clients only need to check /yangmnt:schema-mounts when yang
    library's checksum changes?

3.2, 2nd paragraph, can you add the section in rtgwg-lne-model that
     has the exception, or some text about the nature of the exception
     defined in that document?

3.2, last paragraph: is "in operational state"

3.3: an example would be helpful

5: end of 2nd paragraph, an example would be nice

6: 2nd paragraph, is the ref to RFC7950 correct?

9: in the ietf-yang-schema-mount module:
 a) in the top-level description stmt, s/specify/specifies/?
 b) in the "mount-point" container's description statement, would it be
    helpful to add that multiple instances of the mount-point may exist
    when the extension statement is used in a 'list' or 'grouping' stmt?
    - this to help with the last paragraph in the description stmts for
      both the inline and shared-schema nodes?
 c) why is "shared-schema" a presence container?
 d) for parent-reference, would it be helpful to note that the reference
    MAY be to nodes that themselves were brought in via a parent ref, for
    the nested schema mount case?

A. shouldn't there be an example parent schema module showing the
   "mount-point" extension statement defining the "root" label?


global:
 a) should "data node" be a term?
 b) nowhere is RFC Editor asked to map XXXX to the assigned RFC number
 c) nowhere is RFC Editor asked to map 2018-03-20 to the published date


Kent // contributor