Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor DHCPv6

Ted Lemon <mellon@fugue.com> Sun, 25 November 2007 23:30 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwQwF-0005gy-G7; Sun, 25 Nov 2007 18:30:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwQwE-0005gn-0a for dhcwg@ietf.org; Sun, 25 Nov 2007 18:30:58 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwQwA-0002PS-Is for dhcwg@ietf.org; Sun, 25 Nov 2007 18:30:57 -0500
Received: from [10.0.1.2] (cpe-67-9-133-15.austin.res.rr.com [67.9.133.15]) by toccata.fugue.com (Postfix) with ESMTP id 6286BBC43ED; Sun, 25 Nov 2007 16:30:53 -0700 (MST)
Message-Id: <3D222556-27E9-4EFA-87E0-A43A3C5E9E16@fugue.com>
From: Ted Lemon <mellon@fugue.com>
To: Brian Utterback <brian.utterback@sun.com>
In-Reply-To: <4749E7F6.8010709@sun.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor DHCPv6
Date: Sun, 25 Nov 2007 17:30:52 -0600
References: <20071121052610.DD3EF39E3F@mail1.ntp.org> <4748DAB1.2030506@ntp.org> <6EDC6595-CD66-490F-90FD-A730E4BF3360@fugue.com> <4748F4C4.1090407@ntp.org> <47496F73.8040206@sun.com> <000701c82f6e$03795350$6401a8c0@tsg1> <4749D28D.8090505@sun.com> <00af01c82fa5$8a9acfd0$6401a8c0@tsg1> <4749E7F6.8010709@sun.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ntpwg@lists.ntp.org, TS Glassey <tglassey@earthlink.net>, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>, dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Nov 25, 2007, at 3:24 PM, Brian Utterback wrote:
> If a client is served an IP address at start up time, it has no  
> choice but to use that address for the
> entire time it is up and running.

This is simply not true.   The client would get the currently- 
configured NTP server IP address every time it renews its lease.    
It's true that some NTP clients may not bother to check their  
configuration information for updates, but it is not true that they  
have no choice - checking for configuration updates is trivial.

Indeed, I would say that at this late date, a network service that  
gets its configuration information from the DHCP client, but does not  
follow updates to that information, is broken.  Information provided  
by the local DHCP server will most likely change when the client moves  
from network to network.   The information that worked on one network  
may not work at all on another.   This is true whether the information  
is a domain name or an IP address.


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