Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6

Danny Mayer <mayer@ntp.org> Tue, 27 November 2007 14:14 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 1Ix1CM-00083q-9K; Tue, 27 Nov 2007 09:14:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix1CL-00083j-RE for dhcwg@ietf.org; Tue, 27 Nov 2007 09:14:01 -0500
Received: from exchdev.pega.com ([198.22.153.35] helo=exchdev.rpega.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ix1CL-0002eD-I9 for dhcwg@ietf.org; Tue, 27 Nov 2007 09:14:01 -0500
Received: from [10.60.98.36] ([10.60.98.36]) by exchdev.rpega.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Nov 2007 09:14:01 -0500
Message-ID: <474C2582.8090804@ntp.org>
Date: Tue, 27 Nov 2007 09:11:14 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1> <5C093633-A256-4059-AA10-1800F62F522A@fugue.com> <017901c82fd4$9cad3b70$6401a8c0@tsg1> <E0F01D6C-3FB6-4150-9722-32CFF3079327@fugue.com> <018501c82fd7$9ff707e0$6401a8c0@tsg1> <A6BDB3D6-4CDA-4BC1-ADF0-1845E539DD4C@fugue.com> <474A521A.2090905@ntp.org> <20071126190312.GI24311@isc.org>
In-Reply-To: <20071126190312.GI24311@isc.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Nov 2007 14:14:01.0058 (UTC) FILETIME=[C20E7420:01C830FF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: ntpwg@lists.ntp.org, DHC WG <dhcwg@ietf.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>
Errors-To: dhcwg-bounces@ietf.org

David W. Hankins wrote:
> I do not believe there is any reasonable way we can provide this
> with complete assuredness.
> 
> It may appear that if you gave the DNS name via DHCP that the clock's
> administrator can now do clever things with DNS replies to ease the
> pain on the individual clocks.  So mitigation tools may exist.
> 
> However it also opens the doorway for a clock manufacturer to set
> the static value to a domain name they control - and deliver A records
> for other folks' clocks.
> 

With the pool config option you can now point to the pool (pool.ntp.org)
and each time you make a query you will get a different list of
addresses to use. The pool also is grouped into areas and countries and
provides a much better loading on the NTP servers in the list. ntpd will
configure up to 10 of these addresses to use.

> You're screwed either way...in this case, you have some control over
> firmware that has not been upgraded.
> 

We prefer the pool.

Danny

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