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

Stuart Cheshire <cheshire@apple.com> Mon, 27 August 2001 21:07 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00500; Mon, 27 Aug 2001 17:07:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04963; Mon, 27 Aug 2001 17:06:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04931 for <dhcwg@ns.ietf.org>; Mon, 27 Aug 2001 17:06:46 -0400 (EDT)
Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00365 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 17:05:25 -0400 (EDT)
Received: from apple.con (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id OAA21545 for <dhcwg@ietf.org>; Mon, 27 Aug 2001 14:06:46 -0700 (PDT)
Received: from scv1.apple.com (scv1.apple.com) by apple.con (Content Technologies SMTPRS 4.2.1) with ESMTP id <T55a0bf056c118064e13a0@apple.con>; Mon, 27 Aug 2001 14:04:53 +0100
Received: from [206.111.147.149] (vpn-gh-1056.apple.com [17.254.140.31]) by scv1.apple.com (8.9.3/8.9.3) with SMTP id OAA02524; Mon, 27 Aug 2001 14:06:45 -0700 (PDT)
Message-Id: <200108272106.OAA02524@scv1.apple.com>
Subject: Re: [dhcwg] Re: Last call for <draft-ietf-dhc-fqdn-option-02.txt>
Date: Mon, 27 Aug 2001 14:06:44 -0700
x-sender: cheshire@mail.apple.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Stuart Cheshire <cheshire@apple.com>
To: "Mark Stapp" <mjs@cisco.com>, <dhcwg@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

>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