Re: [dhcwg] Call for adoption for draft-cui-dhc-dhcpv6-yang-04

Hi, all

I think the DHCPv6 (and also DHCPv4) YANG model is necessary work, and DHC WG should be the most suitable place to work on it. So I support this adoption.

And we have some comments to the current draft:

General comments:
1. The Server, Relay, Client are defined as three containers in one DHCPv6 module in the draft. But considering the three roles are actually independent from each other, we thought maybe defining them as three separated YANG modules (still in one draft) is more proper. This might be more convenient to maintain and use them. 

Besides, do you also consider making address pool a separated module? Since the address pool could be considered as a common resource that might be utilized by functions other than DHCP.

(I think this comment also applies to the current DHCPv4 YANG model draft.)

2. (This is also a question to the WG) Do you consider this DHCPv6 YANG Model as a universal model focusing on the standard functions, or you consider it as a specific usage, e.g. HGW?
My personal opinion tends to agree with the former one.

Specific comments:
1. In Client model, the "client-interfaces" container seems redundant? I think the "list client-if" could be directly under the "client" container.
2. In Server model, Do you consider to support a feature that multiple DHCPv6 servers could be grouped together? This is an important feature in carrier networks.
3. There are lot of stings defined without assigned length.
4. There are some description still empty, need to be filled.

Best regards,
Bing

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tomek
> Mrugalski
> Sent: Friday, September 25, 2015 8:42 PM
> To: dhcwg
> Subject: [dhcwg] Call for adoption for draft-cui-dhc-dhcpv6-yang-04
> 
> Hi,
> Authors of draft-cui-dhc-dhcpv6-yang-04 requested adoption. This draft has
> been presented twice and received favourable comments. It defines a YANG
> data model for configuration and management of the DHCPv6 server, client
> and relay agent. This I-D is over 80 pages long, but most of the text is taken
> by formal YANG definition.
> 
> This mail initiates a call for adoption of draft-cui-dhc-dhcpv6-yang-04 as a
> WG item. If you would like the working group to work on this document,
> please say so. If you would like the WG to not adopt, please state your
> technical objections.
> 
> There are currently no IPR claimed against this draft.
> 
> Bernie and I will determine the consensus after Oct. 9th.
> 
> Bernie & Tomek
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg