Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

[Qi Sun <[e-mail]>]

Hi Simon,

Thanks for your review. Please see inline.
> 
> - The client MUST always include both OPTION_DHCP4_O_DHCP6_ENABLE and OPTION_DHCP4_O_DHCP6_SERVER in the ORO.
> 

[Qi] RFC3315 says that the client SHOULD use unicast if instructed by the server. In this document, if the client doesn't include this option, it can still work (using multicast). So I think it's SHOULD for the OPTION_DHCP4_O_DHCP6_SERVER.

> - The server responds with zero (if DHCPv4-over-DHCPv6 is not available) or one of two options. Never both.
>    - OPTION_DHCP4_O_DHCP6_ENABLE means "multicast".
>    - OPTION_DHCP4_O_DHCP6_SERVER means "unicast".
> 
> If this makes sense, then I would rename the options: s/ENABLE/MULTICAST/ and s/SERVER/UNICAST/. And maybe go further and kill OPTION_DHCP4_O_DHCP6_ENABLE, and just put the multicast address in the payload of OPTION_DHCP4_O_DHCP6_SERVER.

[Qi] The multicast address is a well-known address in RFC3315. The client knows it even you don't tell the client. I don't think it necessary to put the multicast address into the option. 

> 
> By the way, a suggestion for the document: replace all instances of "4o6 Server Address option" with the full option name, "OPTION_DHCP4_O_DHCP6_SERVER". Always using the same terminology makes it much easier to grep the document.

[Qi] Thanks for the suggestion! IMHO, the "4o6 Server Address option" is the name of the option, while the OPTION_DHCP4_O_DHCP6_SERVER is the option code to be assigned by the IANA. What I get from RFC3315 is that when you refer to an option, use the name; if you want to mention the code, then use the uppercase phrase.
But I will check to wording to make sure the document uses the same terminology.

Best Regards,
Qi