RE: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
<anthony.flavin@bt.com> Wed, 28 November 2007 09:13 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 1IxIys-00061O-IG; Wed, 28 Nov 2007 04:13:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxIyq-00061D-QK for dhcwg@ietf.org; Wed, 28 Nov 2007 04:13:16 -0500
Received: from smtp1.smtp.bt.com ([217.32.164.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxIyo-0000ZP-OS for dhcwg@ietf.org; Wed, 28 Nov 2007 04:13:16 -0500
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.108]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Nov 2007 09:13:13 +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: Wed, 28 Nov 2007 09:13:12 -0000
Message-ID: <548EC156325C6340B2E85DF90CAE8586019A0008@E03MVB3-UKBR.domain1.systemhost.net>
In-Reply-To: <p06240800c37214d60719@[192.168.1.101]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Thread-Index: AcgxJtt/HXk4zluxSFOu9g5fEnM/EQAd8H0g
From: anthony.flavin@bt.com
To: brad@shub-internet.org, Mark_Andrews@isc.org
X-OriginalArrivalTime: 28 Nov 2007 09:13:13.0563 (UTC) FILETIME=[E75302B0:01C8319E]
X-Spam-Score: -0.7 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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
Perhaps some other ISP's involved with the NTPWG would care to comment on whether or not the poor practice of the past is still in place, or being replaced with best practice (which is to install their own servers, or reach an agreement for the use of somebody else's). -----Original Message----- From: Brad Knowles [mailto:brad@shub-internet.org] Sent: 27 November 2007 18:42 To: Flavin,AJ,Tony,DMJ R; brad@shub-internet.org; Mark_Andrews@isc.org 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/27/07, <anthony.flavin@bt.com> wrote: > Completely wrong. My statement was with regards to most ISPs that I have experience with or or where we have had reports from others. Your specific ISP was not necessarily included in that statement. Therefore, your single solitary counter-example does not necessarily disprove anything. > 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). You're just one ISP. You do not comprise the whole of all ISPs on the planet. > It's working fine, and several hundred-thousand clients can't be wrong! And I personally worked at AOL (tens of millions of customers) and the largest ISP in Belgium (over a million customers), and I've consulted at other ISPs around the world. We've also had reports regarding a number of other ISPs around the world. Your one counter example does not disprove our experience. -- 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
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Harlan Stenn
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Mark Andrews
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… TS Glassey
- RE: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… anthony.flavin
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Hui Deng
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Brian Utterback
- RE: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… anthony.flavin
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Mark Andrews
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Brad Knowles
- RE: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Brad Knowles
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Brad Knowles
- Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NT… Danny Mayer