IETF Logo Mail Archive

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

Brian Utterback <Brian.Utterback@Sun.COM> Mon, 26 November 2007 03:23 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 1IwUZK-0004Sv-C3; Sun, 25 Nov 2007 22:23:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwUZJ-0004Sq-DI for dhcwg@ietf.org; Sun, 25 Nov 2007 22:23:33 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwUZI-0002qP-Lv for dhcwg@ietf.org; Sun, 25 Nov 2007 22:23:32 -0500
Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lAQ3NVUN003201 for <dhcwg@ietf.org>; Mon, 26 Nov 2007 03:23:31 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JS300L01FUWVW00@mail-amer.sun.com> (original mail from Brian.Utterback@Sun.COM) for dhcwg@ietf.org; Sun, 25 Nov 2007 20:23:31 -0700 (MST)
Received: from [192.168.1.5] ([71.168.64.220]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JS30044QG36PN80@mail-amer.sun.com>; Sun, 25 Nov 2007 20:23:31 -0700 (MST)
Date: Sun, 25 Nov 2007 22:23:30 -0500
From: Brian Utterback <Brian.Utterback@Sun.COM>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
In-reply-to: <018401c82fd7$9f632c50$6401a8c0@tsg1>
To: TS Glassey <tglassey@earthlink.net>
Message-id: <474A3C32.1020006@sun.com>
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
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> <474A3297.5040907@sun.com> <018401c82fd7$9f632c50$6401a8c0@tsg1>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Ted Lemon <mellon@fugue.com>, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
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

TS Glassey wrote:
>
> I still don't know that the service is needed I have heard a couple of 
> people mandate that they think this is necessary but in actuality I 
> still haven't heard anything that makes this mandatory. Especially 
> since without any pain at all its pretty easy to create a set of known 
> NTP servers and just use the local DNS service to propagate these. WKS 
> inside of DNS is a simple method that is time tested.
>
> Todd

Okay, so your suggestion is to not have a DHCP NTP field at all, but to have
the clients use WKS and DNS resolution to find servers. Fair enough.

blu


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

v2.23.0 | Report a Bug | By Email