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

<anthony.flavin@bt.com> Tue, 27 November 2007 09:05 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 1IwwNV-0003gh-7i; Tue, 27 Nov 2007 04:05:13 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwwNU-0003g4-1I for dhcwg@ietf.org; Tue, 27 Nov 2007 04:05:12 -0500
Received: from smtp1.smtp.bt.com ([217.32.164.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwwNR-00008B-H6 for dhcwg@ietf.org; Tue, 27 Nov 2007 04:05:09 -0500
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.108]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Nov 2007 09:05:08 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Tue, 27 Nov 2007 09:05:05 -0000
Message-ID: <548EC156325C6340B2E85DF90CAE85860199F92F@E03MVB3-UKBR.domain1.systemhost.net>
In-Reply-To: <p06240802c37170b98ffe@[192.168.1.135]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Thread-Index: AcgwxlROjJgk+C+bSd6iFn+YYhixpwADeuzQ
From: <anthony.flavin@bt.com>
To: <brad@shub-internet.org>, <Mark_Andrews@isc.org>
X-OriginalArrivalTime: 27 Nov 2007 09:05:08.0044 (UTC) FILETIME=[9B84F0C0:01C830D4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

Completely wrong.

I can assure you that we do run our own NTP servers, and our customer
routers are pre-configured with a Name not an IP address to get to them.
We let our DNS servers sort out the load balancing issues (if we ever
get any).

It's working fine, and several hundred-thousand clients can't be wrong!
 
Tony Flavin

-----Original Message-----
From: Brad Knowles [mailto:brad@shub-internet.org] 
Sent: 27 November 2007 07:01
To: Mark Andrews; Flavin,AJ,Tony,DMJ R
Cc: mayer@ntp.isc.org; ntpwg@lists.ntp.org; mellon@fugue.com;
rgayraud@cisco.com; dhcwg@ietf.org
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP)
OptionsforDHCPv6

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