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

Brad Knowles <brad@shub-internet.org> Wed, 28 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 1IxNNh-0006T5-5w; Wed, 28 Nov 2007 08:55:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwumX-0001Jj-Ew for dhcwg@ietf.org; Tue, 27 Nov 2007 02:22:57 -0500
Received: from smtp102.his.com ([216.194.225.125]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwumU-0004YJ-6T for dhcwg@ietf.org; Tue, 27 Nov 2007 02:22:57 -0500
Received: from localhost (localhost [127.0.0.1]) by smtp102.his.com (Postfix) with ESMTP id F02E513E4292; Tue, 27 Nov 2007 02:22:53 -0500 (EST)
Received: from smtp102.his.com ([216.194.225.125]) by localhost (smtp102.his.com [216.194.225.125]) (amavisd-new, port 10024) with ESMTP id 19868-09; Tue, 27 Nov 2007 02:22:51 -0500 (EST)
Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by smtp102.his.com (Postfix) with ESMTP id 4607113E41D1; Tue, 27 Nov 2007 02:22:51 -0500 (EST)
Received: from [192.168.1.101] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.13.1/8.12.3) with ESMTP id lAR7MjBe091113; Tue, 27 Nov 2007 02:22:49 -0500 (EST) (envelope-from brad@shub-internet.org)
Mime-Version: 1.0
Message-Id: <p06240802c37170b98ffe@[192.168.1.135]>
In-Reply-To: <200711261201.lAQC1NS8060633@drugs.dv.isc.org>
References: <200711261201.lAQC1NS8060633@drugs.dv.isc.org>
Date: Tue, 27 Nov 2007 01:01:04 -0600
To: Mark Andrews <Mark_Andrews@isc.org>, anthony.flavin@bt.com
From: Brad Knowles <brad@shub-internet.org>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Virus-Scanned: Debian amavisd-new at smtp502.his.com
X-Spam-Status: No, score=-4.342 tagged_above=-99 required=5 tests=[ALL_TRUSTED=-1.8, AWL=0.057, BAYES_00=-2.599]
X-Spam-Score: -4.342
X-Spam-Level:
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Wed, 28 Nov 2007 08:55:11 -0500
Cc: mayer@ntp.isc.org, ntpwg@lists.ntp.org, mellon@fugue.com, 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

On 11/26/07, Mark Andrews wrote:

>	ISP's will do similar things with NTP servers.  They will point
>	the DHCP clients to their NTP servers.  SOHO routeres will just
>	re advertise what they learnt.

No, the ISPs don't work this way.  I have yet to see many ISPs that 
have demonstrated any capacity or interest in setting up their own 
NTP server.  If they use NTP at all, in almost all cases they rely on 
external NTP servers.  It is these same external servers that they 
would plug into their DHCP servers (because they can't be bothered to 
run their own NTP servers), and which would then be passed on to the 
clients.

Which leads us to the mess that Danny is trying to help prevent.

>	This is a non-issue.

I'm not convinced of that.

-- 
Brad Knowles <brad@shub-internet.org>
LinkedIn Profile: <http://tinyurl.com/y8kpxu>

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