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

Danny Mayer <mayer@ntp.org> Sun, 25 November 2007 02:19 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 1Iw75S-0008M9-Vz; Sat, 24 Nov 2007 21:19:10 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iw75R-0008Ly-U5 for dhcwg@ietf.org; Sat, 24 Nov 2007 21:19:09 -0500
Received: from mx04.gis.net ([208.218.130.12]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iw75R-00051O-Hh for dhcwg@ietf.org; Sat, 24 Nov 2007 21:19:09 -0500
Received: from [10.10.10.101] ([63.209.224.211]) by mx04.gis.net; Sat, 24 Nov 2007 21:19:05 -0500
Message-ID: <4748DAF7.9080705@ntp.org>
Date: Sat, 24 Nov 2007 21:16:23 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Mark Stapp <mjs@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options for DHCPv6
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <4733482A.7020302@sun.com> <A05118C6DF9320488C77F3D5459B17B70634E4E5@xmb-ams-333.emea.cisco.com> <473D0C34.4030507@ntp.org> <1195185173.26090.4.camel@uma> <474114E3.9040309@ntp.org> <474198BA.3000109@sun.com> <4743B902.3030406@udel.edu> <47445863.4000208@cisco.com>
In-Reply-To: <47445863.4000208@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "David L. Mills" <mills@udel.edu>
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

Mark Stapp wrote:
> yes, this is another reason why the DHCP folks have generally used
> addresses in options. it just removes a dependency among the various
> clients in the system, and it doesn't usually have any significant
> drawback.
> 
> there seems to be a concern that delivering addresses via DHCP somehow
> makes them difficult to update over time. just to reiterate: it's often
> the case that the information at the DHCP server is updated. the updated
> information flows out to clients as they renew. if the lease timers were
> very long, a client who got NTP addresses and found itself having
> trouble with them all could also use the INFORMATION-REQUEST message to
> check whether the addresses were still valid, outside of the normal
> renewal timers.
> 
> -- Mark

Mark,

My biggest worry is the "set and forget" attitude of a system admin who
has more than just NTP servers to worry about. The reality is that NTP
is a long-running daemon on the client and unless something happens it
will continue to query the same client, not just for days, but for
months and even years. We can propose that the DHC client updates the
NTP server but I have yet to see anything that proposes to do that. If
the sysadmin sets up the list of NTP servers for the DHC client to use
when is he/she going to go back and check if they are still valid?

Danny


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