Draft: draft-ietf-dhc-dhcpv6-yang-07

Commentary: Fixed spelling , cf issue . 
 I have reviewed your proposed changes . They look good . I 'll let the authors to merge this . 
 Spelling errors : ToC and 6 : Acknowledgements -Acknowledgments 1.1 d cument -document many para -param some missing trailing / closing dots Extra from ( US - English ) ispell : addional relevent Commment learnt adress utlization fulfil configfuration liftime alloated modelled recevied redfining recofigure opiton Opion BOOTFiLE ivariable Uknown Indentifier Defination . Creating a PR for this .
Since the publication of the original DHCPv6 specification, there
have been a large number of addional documents that update the
protocol's operation, add new functions and define new options.  The
YANG model described in this document incorporates all relevent
changes.  A full list of the documents which have been considedered
in the development of this model is included in Appendix A.
IF - Commment - Does anyone have this list?
Since the publication of the original DHCPv6 specification, there
have been a large number of additional documents that update the
protocol's operation, add new functions and define new options.  The
YANG model described in this document incorporates all relevant
changes.  A full list of the documents which have been considered in
the development of this model is included in Appendix A.
IF - Comment - Does anyone have this list?
It is worth noting that as DHCPv6 is itself a device configuration
protocol, it is not the intention of this document to replace the
configuration of DHCPv6 options and parameters using the DHCPv6
protocol with the configuration of DHCPv6 options using NETCONF/YANG.
The DHCPv6 client model is intended for the configuration of the
DHCPv6 client function and also for obtaining read-only state data
from the client which has been learnt via the normal DHCPv6 message
flow.  This gives an operator a better method for managing DHCPv6
clients and simplifies troubleshooting.
It is worth noting that as DHCPv6 is itself a device configuration
protocol, it is not the intention of this document to replace the
configuration of DHCPv6 options and parameters using the DHCPv6
protocol with the configuration of DHCPv6 options using NETCONF/YANG.
The DHCPv6 client model is intended for the configuration of the
DHCPv6 client function and also for obtaining read-only state data
from the client which has been learned via the normal DHCPv6 message
flow.  This gives an operator a better method for managing DHCPv6
clients and simplifies troubleshooting.
A simplified graphical representation of the data model is provided
in this d cument.  For a description of the symbols in these
diagrams, please refer to I-D.ietf-netmod-yang-tree-diagrams.
A simplified graphical representation of the data model is provided
in this document.  For a description of the symbols in these
diagrams, please refer to I-D.ietf-netmod-yang-tree-diagrams.
network-ranges: This model supports a hierarchy to achieve dynamic
configuration.  That is to say we could configure the server at
different levels through this model.  The top level is a global
level which is defined as the container "network-ranges".  The
following levels are defined as sub-containers under it.  The
"network-ranges" contains the parameters (e.g. option-sets) that
would be allocated to all the clients served by this server.
rapid-commit: Setting the value to '1' represents the adress/
prefix pool support the Solicit-Reply message exchange. '0' means
the server will simply ignore the Rapid Commit option in Solicit
message.
rapid-commit: Setting the value to '1' represents the address/
prefix pool support the Solicit-Reply message exchange. '0' means
the server will simply ignore the Rapid Commit option in Solicit
message.
max-pd-space-utilization: Maximum utilization of pd space in this
pool.
relay-opaque-paras: This container contains some opaque values in
Relay Agent options that need to be configured on the server side
only for value match.  Such Relay Agent options include Interface-
Id option, Remote-Id option and Subscriber-Id option.
relay-opaque-params: This container contains some opaque values in
Relay Agent options that need to be configured on the server side
only for value match.  Such Relay Agent options include Interface-
Id option, Remote-Id option and Subscriber-Id option.
relay-if: A relay agent may have several interfaces, we should
provide a way to configure and manage parameters on the interface-
level.  A list that describes specific interfaces and their
corresponding parameters is employed to fulfil the configfuration.
Here we use a string called "if-name" as the key of list.
relay-if: A relay agent may have several interfaces, we should
provide a way to configure and manage parameters on the interface-
level.  A list that describes specific interfaces and their
corresponding parameters is employed to fulfill the configuration.
Here we use a string called "if-name" as the key of list.
client-configured-options: Similar to the server, the client also
need to configure some options to fulfil some desired functions.
This container include all the potential options that need to be
configured at the client side.  The relevant RFCs that define
those options include: RFC3315, RFC4704, RFC5970, RFC6784,
RFC6939.
client-configured-options: Similar to the server, the client also
need to configure some options to fulfill some desired functions.
This container include all the potential options that need to be
configured at the client side.  The relevant RFCs that define
those options include: RFC3315, RFC4704, RFC5970, RFC6784,
RFC6939.
if-other-paras: A client can obtain extra configuration data other
than address and prefix information through DHCPv6 options.  This
container describes such data the client was configured through
DHCPv6.  The potential configuration data may include DNS server
parameters, SIP server parameters and etc.
if-other-params: A client can obtain extra configuration data
other than address and prefix information through DHCPv6 options.
This container describes such data the client was configured
through DHCPv6.  The potential configuration data may include DNS
server parameters, SIP server parameters and etc.