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

"David W. Hankins" <David_Hankins@isc.org> Tue, 27 November 2007 19:22 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 1Ix60e-00071P-IL; Tue, 27 Nov 2007 14:22:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix60d-000712-VR for dhcwg@ietf.org; Tue, 27 Nov 2007 14:22:15 -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 1Ix60d-0007ju-Hh for dhcwg@ietf.org; Tue, 27 Nov 2007 14:22:15 -0500
Received: by goliath.isc.org (Postfix, from userid 10200) id 6EA867E03; Tue, 27 Nov 2007 11:22:15 -0800 (PST)
Date: Tue, 27 Nov 2007 11:22:15 -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: <20071127192215.GC30466@isc.org>
References: <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> <20071126184216.GG24311@isc.org> <474C23F2.9060301@ntp.org>
Mime-Version: 1.0
In-Reply-To: <474C23F2.9060301@ntp.org>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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="===============1521792261=="
Errors-To: dhcwg-bounces@ietf.org

On Tue, Nov 27, 2007 at 09:04:34AM -0500, Danny Mayer wrote:
> If the address provided by DHCP is not providing NTP service ntpd will
> drop it. So in this case it has no recourse.

That's correct; there is no recourse and in DHCP's philosphy there
shouldn't be.

DHCP delivers a configuration state with an expiration time and
renewal time.  If that configuration is incorrect or flawed or
unusable at some point in its advertised lifetime (as set by the
operator of the DHCP server), it isn't a problem that can be solved
by going back to the well; the configuration is likely to have not
changed.  Going back to the well without some indication (the
reconfigure extensions) just creates useless traffic.

The theory is that DHCP server operators use lease lifetimes as a
tool for limiting stale configuration and for scheduling outages
and configuration changes (reducing the lease lifetimes as changeovers
approach).


I have a vague feeling that you've found the way to express a need for
this DHCP option to be configured via DNS names.  As I stated before,
I reserve any judgement until there's a draft.

-- 
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