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

Danny Mayer <mayer@ntp.org> Wed, 21 November 2007 19:37 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 1IuvO5-0002Sf-12; Wed, 21 Nov 2007 14:37:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuvO3-0002LW-5X for dhcwg@ietf.org; Wed, 21 Nov 2007 14:37:27 -0500
Received: from exchdev.pega.com ([198.22.153.35] helo=exchdev.rpega.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuvO2-0005Eo-SL for dhcwg@ietf.org; Wed, 21 Nov 2007 14:37:27 -0500
Received: from [10.60.98.36] ([10.60.98.36]) by exchdev.rpega.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Nov 2007 14:37:20 -0500
Message-ID: <4744884F.70200@ntp.org>
Date: Wed, 21 Nov 2007 14:34:39 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Optionsfor DHCPv6
References: <47442EB4.1010100@sun.com> <009201c82c54$11cd6e90$6401a8c0@tsg1> <20071121165826.GD3291@isc.org>
In-Reply-To: <20071121165826.GD3291@isc.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Nov 2007 19:37:20.0980 (UTC) FILETIME=[EED52140:01C82C75]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: ntpwg@lists.ntp.org, DHC WG <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

David W. Hankins wrote:
> 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?

FF02::101 and FF05::101 are reserved for link-local and site-local.
Actually the whole FFxx::101 space is reserved for NTP.

Danny

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