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

Danny Mayer <mayer@ntp.org> Wed, 28 November 2007 03:03 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 1IxDD1-0004MT-CM; Tue, 27 Nov 2007 22:03:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxDD0-0004Ka-08 for dhcwg@ietf.org; Tue, 27 Nov 2007 22:03:30 -0500
Received: from mx04.gis.net ([208.218.130.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxDCz-0006pl-LX for dhcwg@ietf.org; Tue, 27 Nov 2007 22:03:29 -0500
Received: from [10.10.10.101] ([63.209.224.211]) by mx04.gis.net; Tue, 27 Nov 2007 22:03:24 -0500
Message-ID: <474CD9D2.3050405@ntp.org>
Date: Tue, 27 Nov 2007 22:00:34 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
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> <E0F01D6C-3FB6-4150-9722-32CFF3079327@fugue.com> <018501c82fd7$9ff707e0$6401a8c0@tsg1> <A6BDB3D6-4CDA-4BC1-ADF0-1845E539DD4C@fugue.com> <474A521A.2090905@ntp.org> <EB79E4A4-9DC7-4C86-8CB7-96920EAD579A@fugue.com> <p06240803c37171dcd41c@[192.168.1.135]> <474C855F.6080609@udel.edu> <BFF6FCB9-231F-4EB8-B4CB-3FCD1F673FFA@nominum.com>
In-Reply-To: <BFF6FCB9-231F-4EB8-B4CB-3FCD1F673FFA@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "David L. Mills" <mills@udel.edu>
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

Ted Lemon wrote:
> On Nov 27, 2007, at 4:00 PM, David L. Mills wrote:
>> If the DHCP server followed that advice, it would
>> occasionally re-resolve the name and pass the new IP address to its
>> clients.  It is not at all clear that this advice is followed in the real
>> world.
> 
> It is followed, actually.   E.g., the Nominum DHCP server (DCS) just
> looks the name up every time, under the assumption that the caching name
> server is going to perform better than any ad hoc resolver we might
> stuff into the DHCP server.   The ISC DHCP server caches names for an
> hour - a decision I made when caching name servers weren't as good as
> they are now, and when I was a lot more naive about DNS than I am now. 
> I can't speak for the other vendors, so you'd have to ask them, but I'd
> be really surprised if they didn't do the same thing - if you cache the
> value, you have to cache it some/where/ - it's not quite the same as
> when a server looks up an address in the DNS so that it can connect to
> that address.
> 

This was the next question to ask of course. How many of the addresses
in the reply are cached for distribution as appropriate? With the pool
config option we use as many as 10 returned from the DNS query. How many
of these would we expect to get if we relied on DHCP to supply those IP
addresses.

> I don't know what SOHO routers do, in general - it would be interesting
> to investigate.

Volunteers?

Danny

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