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

"David W. Hankins" <David_Hankins@isc.org> Mon, 26 November 2007 18:42 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 1IwiuQ-0004Bq-Q0; Mon, 26 Nov 2007 13:42:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwiuP-00049j-BL for dhcwg@ietf.org; Mon, 26 Nov 2007 13:42:17 -0500
Received: from [2001:4f8:3:bb:20c:76ff:fe16:4040] (helo=goliath.isc.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwiuO-0008AK-DU for dhcwg@ietf.org; Mon, 26 Nov 2007 13:42:17 -0500
Received: by goliath.isc.org (Postfix, from userid 10200) id 945C25A6ED; Mon, 26 Nov 2007 10:42:16 -0800 (PST)
Date: Mon, 26 Nov 2007 10:42:16 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
Message-ID: <20071126184216.GG24311@isc.org>
References: <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> <1195484306.9159.13.camel@uma> <4741D057.4070703@ntp.org> <20071119232225.GJ14750@isc.org> <47479E84.8080309@ntp.org>
Mime-Version: 1.0
In-Reply-To: <47479E84.8080309@ntp.org>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.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>
Content-Type: multipart/mixed; boundary="===============1093283977=="
Errors-To: dhcwg-bounces@ietf.org

On Fri, Nov 23, 2007 at 10:46:12PM -0500, Danny Mayer wrote:
> That's currently the situation with the reference implementation of
> ntpd. It gets its configuration information and doesn't go back. You can

You can classify this as an ntpd problem, or a system integration
problem.

In the former, you might want to accept a HUP sometimes.  In the
latter, all the tools to restart the daemon are already available.

Whichever one you choose, you'll still get the job done.  If ntpd
accepts HUPs, maybe you can optimize 'keeping your clock synched'
across reconfiguration events.

> now. So for the DHCP client to have an influence on what it uses for
> servers it either needs to use ntpdc, send private mode 7 NTP packets,
> restart ntpd, or have some sort of interface for ntpd to get updated
> values from the DHCP client.

The client itself has no need to do this.  The operating system's
configuration management system which accepts DHCP input needs to
solve this problem.

For ISC, we call this "dhclient-script", and although we package
several examples with our software I know of no actual operating
systems that use them...they all cook their own scripts that
integrate with their configuration management.

Still, it is trivial;

	if [ x$new_ntp_servers != x$old_ntp_servers ] ; then
		rewrite_ntp_conf()
		rcntp force-reload
	fi

> Well, if ntpd can poke the DHCP client for new values, presumably it can
> request new values from the DHCP server to pass back to ntpd. That's not
> even defined.

Presently, all the poking is in the opposite direction.  What I was
referring to here is that there are Server->Client messages that can
suggest the client needs to update its config, rather than wait for
the usual lease renewal timer to expire.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg