Hi Martin,

Removed some extra ones on which we agree.
See in line.

- Terminology:
   The following terms are defined in [RFC6241
   <https://tools.ietf.org/html/rfc6241>]:

     ...

     o  configuration datastore: a configuration datastore is an
        instantiated data tree with configuration data

     o  datastore: an instantiated data tree

RFC6241 has different definition for "configuration datastore" and
"datastore".
I would just provide the pointer to the RFC 6241 definitions.
If you intend to provide an adapted definition for the YANG mappings,
then you should say so.
How about:

OLD:

     o  configuration datastore: a configuration datastore is an
        instantiated data tree with configuration data

     o  datastore: an instantiated data tree

NEW:

     o  configuration datastore: When modelled with YANG, a configuration
        datastore is an instantiated data tree with configuration data

     o  datastore: When modelled with YANG, an instantiated data tree

This issue is with "The following terms are defined in [RFC6241]", but
you re-define those terms.
So give a warning about the redefinition to the readers.
Yes, that's what my proposed text does.  It says that "datastore" is
defined in 6241, and when YANG is used, it means the instantiated data
tree.
OLD:

  The following terms are defined in [RFC6241
  <https://tools.ietf.org/html/rfc6241>]:

NEW:

  The following terms are defined in [RFC6241
  <https://tools.ietf.org/html/rfc6241>], but re-defined in this document in 
YANG context:



- Section 4.1

     YANG models can describe constraints to be enforced on the data,
     restricting the appearance or value of nodes based on the presence or
     value of other nodes in the hierarchy.

I was looking for an example of appearance.
NEW?
     YANG models can describe constraints to be enforced on the data,
     restricting the appearance (for example, with the "when" statement)
     or value of nodes based on the presence or value of other nodes in
     the hierarchy.
This is very early in the document, and the text tries to give a very
high level function overview.  I am not sure that mentioning "when" at
this time actually helps a first time reader.
The first time I read this, I was wondering how YANG data models can
describe constraints on HOW data appear, while you wanted to express
WHETHER a data appear. Maybe "when" is not the best way to help the
first time user, but something is needed.
How about "restricting the presence or value of nodes"?
Yes, thank you.

Regards, Benoit

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to