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

Brian Utterback <brian.utterback@sun.com> Tue, 27 November 2007 13:55 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 1Ix0uQ-00012K-50; Tue, 27 Nov 2007 08:55:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix0uO-000109-At for dhcwg@ietf.org; Tue, 27 Nov 2007 08:55:28 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix0uN-0005PN-V5 for dhcwg@ietf.org; Tue, 27 Nov 2007 08:55:28 -0500
Received: from dm-east-02.east.sun.com ([129.148.13.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lARDtQEm003604; Tue, 27 Nov 2007 13:55:26 GMT
Received: from [129.148.226.11] (sr1-unsh01-01.East.Sun.COM [129.148.226.11]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id lARDtPOr006517; Tue, 27 Nov 2007 08:55:26 -0500 (EST)
Message-ID: <474C21CD.7060408@sun.com>
Date: Tue, 27 Nov 2007 08:55:25 -0500
From: Brian Utterback <brian.utterback@sun.com>
User-Agent: Thunderbird 2.0.0.10pre (X11/20071125)
MIME-Version: 1.0
To: Brad Knowles <brad@shub-internet.org>
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> <p06240805c37176de00a4@[192.168.1.101]>
In-Reply-To: <p06240805c37176de00a4@[192.168.1.101]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Mark Stapp <mjs@cisco.com>
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


Brad Knowles wrote:

> Which implies that the NTP client now needs to become fully DHCP aware.
> 

Maybe. Maybe not. Simply make the requirement and let the
implementation decide how to fulfill it.

The reality is that the current reference implementation is
pretty robust around restarting the daemon. If the kernel
discipline is in use, the latest frequency correction will
continue to be in effect even during the downtime. Simply
have the DHCP subsystem create a new config file and restart.

Or use the ntpq/ntpdc facility to let the DHCP subsystem do
dynamic reconfiguration.

Or use another interface between the two that is more suitable
for the purpose (since the ntpq/ntpdc interface is somewhat
fragile as an internal interface).

Or make the ntpd daemon itself DHCP aware.

There lots of possibilities.

-- 
blu

"You've added a new disk. Do you want to replace your current
drive, protect your data from a drive failure or expand your
storage capacity?" - Disk management as it should be.
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

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