Hi,
        I have a suggested minor clarification below.


----------
On April 11, 2018 2:47:24 AM Martin Bjorklund <m...@tail-f.com> wrote:

Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
On Tue, Apr 10, 2018 at 10:58:00PM +0200, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> wrote:
> > On Tue, Apr 10, 2018 at 04:15:46PM +0200, Martin Bjorklund wrote:
....
> Ok.  How about adding two sentences at the end of the last paragraph
> in section 3.3, giving:
>
>   The mounted schema is determined at run time: every instance of the
>   mount point that exists in the operational state MUST contain a copy
>   of YANG library data that defines the mounted schema exactly as for
>   a top-level schema. A client is expected to retrieve this data from
>   the instance tree, possibly after creating the mount point.  In the
>   "inline" case, instances of the same mount point MAY use different
>   mounted schemas, whereas in the "shared-schema" case, all instances
>   MUST use the same mounted schema.  In the "inline" case, if two
>   instances have the same YANG library checksum it is not guaranteed
>   that the YANG library contents are equal for these instances.

This text says "A client is expected to retrieve this data from the
instance tree, possibly after creating the mount point.", which seems
a bit odd. How does a client create a mount point? First, a mount
point is created by defining it in a YANG module, so this is
specification time not runtime. Perhaps you mean 'instantiated' rather
than 'created' but even then it is somewhat unclear how a client does
that in general. Perhaps simple drop ', possibly after creating the
mount point'.

Ok, I will do that.


I suggest adding to text to make it unambiguous that the MUST applies to the same mount point nodes in a schema, perhaps:
OLD
   all instances MUST
NEW
   all instances of the same mount point MUST

Lou


/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

Reply via email to