Re: [dhcwg] DHCPv6: Domain Name in Option 39

["H. Peter Anvin" <hpa at zytor.com>]

Govind Saoji wrote:
> 
> Looking at above format, from implementation perspective, this adds 
> extra overhead on DHCPv6 client and DHCPv6 server even though they have 
> nothing to do with those name...other than passing to DNS. It could have 
> been much simpler if could have just passed Fully Qualified Domain Name 
> in this option as was the case with DHCPv4 protocol where sending FQDN 
> in this format is not MUST clause.
> 

It seems that not making it a MUST clause is insane -- how is the client 
going to know how to parse the reply if it is not a MUST clause??

IMO, the actual implementation really doesn't matter much -- these kind 
of conversions are so simple to do (having written one in assembly, 
myself.)  However, not having an unambiguous encoding format is beyond 
insane -- which one it happens to be is really much less important.

	-hpa

_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg