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

Bud Millwood <budm@weird-solutions.com> Mon, 12 November 2007 14:31 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 1IraK8-0003f0-7E; Mon, 12 Nov 2007 09:31:36 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IraK6-0003ek-Lw for dhcwg@ietf.org; Mon, 12 Nov 2007 09:31:34 -0500
Received: from intermail.se.dataphone.net ([212.37.1.50]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IraK6-0001om-6H for dhcwg@ietf.org; Mon, 12 Nov 2007 09:31:34 -0500
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2) with ESMTP id 50761838 for dhcwg@ietf.org; Mon, 12 Nov 2007 15:31:32 +0100
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
Date: Mon, 12 Nov 2007 14:47:09 +0100
User-Agent: KMail/1.8
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <47385CDE.7010700@ntp.org>
In-Reply-To: <47385CDE.7010700@ntp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711121447.09978.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
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 Monday 12 November 2007 15:02, Danny Mayer wrote:
> [This is a resend since the dhcpwg SMTP list server rejected my email
> for no obvious reason]
>
> Benoit Lourdelet (blourdel) wrote:
> > Hello,
> >
> > We have just submitted a new draft proposing an NTP option for DHCPv6.
> >
> > The goal of this draft is to standardize automatic configuration of
> > NTPv4 (IPv6) clients over DHCPv6.
> > We think there is currently no satisfactory solution for configuring
> > NTPv4 clients from a centralized DHCPv6 server.
> >
> > We'd be very happy to hear feedback about the draft, and I'm planning to
> > ask that it becomes a WG draft eventually.
> >
> > Here's a url:
> >
> >
> > http://www.ietf.org/internet-drafts/draft-gayraud-dhcpv6-ntp-opt-00.txt
>
> 2) The server must never be specified as an IP address but always as a
> DNS name. If you wish to use only IPv6 there are options to do so. It is
> easy to configure a DNS server for the specific purpose if it is local
> to the site. We have had too many incidents of hardcoded addresses which
> cause major incorrect usage of ntp servers not to mention clients that
> continue to try and use the same server months and even years after it
> has stopped being an NTP server.

I suppose the argument here is not against provisioning services by IP 
address, but doing so across organizational lines, i.e. when you provide the 
service but don't provision the clients. In my experience NTP is one of those 
services, in which case I'd have to agree that it's a good idea to change 
this option from 'address' to 'DNS name'.

- Bud

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687

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