Re: [dhcwg] Re: Last call for <draft-ietf-dhc-fqdn-option-02.txt>

>I agree with you about the purpose of the bit, but I'm a little confused by 
>your last paragraph. Do you mean that even if the server was configured by 
>you, and it asked your client not to update grosse.fugue.com, you'd like 
>your client to update that zone anyway?

How would Ted's DHCP client *know* that the server was configured by Ted?

When Ted's sitting in Starbucks with his laptop and the Starbucks DHCP 
server tells it not to update "grosse.fugue.com.", how can Ted's DHCP 
client distinguish that case from Ted's own DHCP server telling it not to 
update "grosse.fugue.com."?

Furthermore, if Ted's laptop has the software and the credentials to 
safely update "grosse.fugue.com.", why would Ted *ever* set his DHCP 
server to tell his client not to?

Surely Ted will want his laptop to *always* ignore the "don't update" 
bit, because he knows that if the bit is ever set, it will be from a DHCP 
server that has no authority to tell him not to update his own domain?

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer
 * Chairman, IETF ZEROCONF
 * www.stuartcheshire.org

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg