IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Fri, 16 November 2007 03:52 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 1IssGF-0001Kf-CU; Thu, 15 Nov 2007 22:52:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IssGD-0001Gf-BL for dhcwg@ietf.org; Thu, 15 Nov 2007 22:52:53 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IssGA-0004az-Sq for dhcwg@ietf.org; Thu, 15 Nov 2007 22:52:53 -0500
Received: from [10.6.126.250] (unknown [206.128.65.108]) by toccata.fugue.com (Postfix) with ESMTP id 65D4CBC43CB; Thu, 15 Nov 2007 20:52:49 -0700 (MST)
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
From: Ted Lemon <mellon@fugue.com>
To: Danny Mayer <mayer@ntp.org>
In-Reply-To: <473D0C34.4030507@ntp.org>
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <4733482A.7020302@sun.com> <A05118C6DF9320488C77F3D5459B17B70634E4E5@xmb-ams-333.emea.cisco.com> <473D0C34.4030507@ntp.org>
Content-Type: text/plain
Date: Thu, 15 Nov 2007 20:52:53 -0700
Message-Id: <1195185173.26090.4.camel@uma>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.0
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Utterback <brian.utterback@sun.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

On Thu, 2007-11-15 at 19:19 -0800, Danny Mayer wrote:
> No you should be using a DNS name and not IP addresses. The client
> then can use the DNS to lookup the name and get a bunch of IP
> addresses. The new pool option will then configure all of them
> (up to 10) for NTP servers.
 
True, but not really important, since the DHCP server is normally
configured with a domain name, not an IP address.   So it can do the
lookup and return those ten IP addresses to the client.   So you get the
same effect whether you send the FQDN to the client and make it do the
lookup, or do the lookup on the server.   The advantage of doing it on
the server is (1) you don't have to send an FQDN, and (2) the client
doesn't need to have a resolver.



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

v2.23.0 | Report a Bug | By Email