IETF Logo Mail Archive

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

"David W. Hankins" <David_Hankins@isc.org> Wed, 21 November 2007 16:58 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 1IusuC-0000Wb-DB; Wed, 21 Nov 2007 11:58:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IusuA-0000WV-Qe for dhcwg@ietf.org; Wed, 21 Nov 2007 11:58:26 -0500
Received: from [2001:4f8:3:bb:20c:76ff:fe16:4040] (helo=goliath.isc.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IusuA-0003Vm-HF for dhcwg@ietf.org; Wed, 21 Nov 2007 11:58:26 -0500
Received: by goliath.isc.org (Postfix, from userid 10200) id 7D5F07E03; Wed, 21 Nov 2007 08:58:26 -0800 (PST)
Date: Wed, 21 Nov 2007 08:58:26 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor DHCPv6
Message-ID: <20071121165826.GD3291@isc.org>
References: <47442EB4.1010100@sun.com> <009201c82c54$11cd6e90$6401a8c0@tsg1>
Mime-Version: 1.0
In-Reply-To: <009201c82c54$11cd6e90$6401a8c0@tsg1>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ntpwg@lists.ntp.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>
Content-Type: multipart/mixed; boundary="===============1910107037=="
Errors-To: dhcwg-bounces@ietf.org

On Wed, Nov 21, 2007 at 07:34:49AM -0800, TS Glassey wrote:
> Seems like there are two ways to deal with this, either define a set of 
> pre-existing names and services ala RFC1918 type thingee or through some 
> lookup process in DHCP. Either way it seems that this also plugs into the 
> NEA functionality as well.

Isn't there already an 'all ntp servers' multicast address allocated?

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

v2.23.0 | Report a Bug | By Email