Re: [dhcwg] Yangdoctors early review of draft-ietf-dhc-dhcpv6-yang-19

[[e-mail]]

Hi Acee,

Many thanks for your review. Working through the review and preparing the update is taking a bit longer than I hoped.

Most of your comments are straightforward and will be in the next update. I do have one comment - please see below.

Ian

> On 5. May 2021, at 23:32, Acee Lindem via Datatracker <[e-mail]> wrote:
> 
> Reviewer: Acee Lindem
> Review result: On the Right Track
> 
> Document: draft-ietf-dhc-dhcpv6-yang-19
> Reviewer: Acee Lindem
> Review Date: May 5, 2021
> Review Type: Early Review
> Intended Status: Standards Track
> Summary: On the right track - Issues and questions need to be resolved.
> 
> Modules: [e-mail]
>         [e-mail]
>         [e-mail]
>         [e-mail]
> 
> Tech Summary: The document contains the base configuration and operational
>              YANG model for the DHCPv6 protocol. The basic structure is
>              very good but the major issues need to be addressed prior to WG
>              last call.
> 
> Major Comments:
> 
>    1. Should the DHCP server, relay, and client functions be enabled by
>       default? It seems they are require specific configuration to be
>       viable.


[if - I’ve removed ‘default enabled’ from server and relay

However, for the client, I think that being enabled by default does make sense.

E.g. if you want to use zero touch provisioning (RFC8572), then DHCPv6 is one
Of the mechanisms that the client can use to start the bootstrapping process
So you can establish NETCONF connectivity. If you are looking to manage 
DHCPv6 clients via YANG, then you you must have DHCP infrastructure
deployed. If the client is disabled by default, then you need another mechanism
For bootstrapping zero touch so you can then configure the client to use DHCP
Via NETCONF. The device may not even be able to get an address so you can
reach it for configuration!]