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

Ted Lemon <Ted.Lemon@nominum.com> Wed, 28 November 2007 22:35 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 1IxVVQ-0003l9-Ut; Wed, 28 Nov 2007 17:35:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxVVP-0003hg-O1 for dhcwg@ietf.org; Wed, 28 Nov 2007 17:35:43 -0500
Received: from exprod7og101.obsmtp.com ([64.18.2.155]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxVVP-0003XW-7T for dhcwg@ietf.org; Wed, 28 Nov 2007 17:35:43 -0500
Received: from source ([81.200.64.181]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP; Wed, 28 Nov 2007 14:35:40 PST
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 7666456840; Wed, 28 Nov 2007 14:35:40 -0800 (PST) (envelope-from mellon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4 tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level:
Received: from [10.0.1.6] ([66.108.142.160]) (authenticated user mellon@nominum.com) by mail.nominum.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Wed, 28 Nov 2007 14:35:39 -0800
Message-Id: <384B1789-85D1-43E5-BC6C-60CD877710F4@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Bud Millwood <budm@weird-solutions.com>
In-Reply-To: <200711282235.17331.budm@weird-solutions.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [dhcwg] Network Time Protocol (NTP) Options for DHCPv6
Date: Wed, 28 Nov 2007 17:35:38 -0500
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <200711282235.17331.budm@weird-solutions.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "dhcwg@ietf.org" <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 Nov 28, 2007, at 4:35 PM, Bud Millwood wrote:
> As a server writer I have a built-in aversion to changing the way we
> distribute location of services, but in this case it seems justified  
> to use a
> DNS name simply because the de-facto standard, as far as I can tell,  
> is to
> point clients outside the admin-controlled domain.

I don't know, this seems backwards to me.   I think that the point of  
typing a configuration into a DHCP server would be a great opportunity  
for a network administrator to stop and think, "do we really want to  
point people off our network?"   I think very few ISPs would  
deliberately make that choice - the reason they aren't currently  
providing NTP service is that they aren't telling people which NTP  
server to contact, and most users don't even know what NTP is.   It's  
not that they have made a decision to provide NTP service using some  
other site's NTP server.

This is a different situation from a router vendor putting a default  
value in, in the sense that an ISP providing configuration information  
is actively advising their customer to do something, whereas a router  
vendor is just doing it.



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