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

Danny Mayer <mayer@ntp.org> Tue, 27 November 2007 18:19 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 1Ix51n-0000Iq-4Q; Tue, 27 Nov 2007 13:19:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix51m-0000Ii-77 for dhcwg@ietf.org; Tue, 27 Nov 2007 13:19:22 -0500
Received: from exchdev.pega.com ([198.22.153.35] helo=exchdev.rpega.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix51j-0000Ty-7U for dhcwg@ietf.org; Tue, 27 Nov 2007 13:19:22 -0500
Received: from [10.60.98.36] ([10.60.98.36]) by exchdev.rpega.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Nov 2007 13:19:18 -0500
Message-ID: <474C5EFF.8050100@ntp.org>
Date: Tue, 27 Nov 2007 13:16:31 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Mark Stapp <mjs@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options for DHCPv6
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <4733482A.7020302@sun.com> <A05118C6DF9320488C77F3D5459B17B70634E4E5@xmb-ams-333.emea.cisco.com> <473D0C34.4030507@ntp.org> <1195185173.26090.4.camel@uma> <474114E3.9040309@ntp.org> <474198BA.3000109@sun.com><4743B902.3030406@udel.edu> <47445863.4000208@cisco.com> <A05118C6DF9320488C77F3D5459B17B706594DC6@xmb-ams-333.emea.cisco.com> <474B199E.3060700@cisco.com>
In-Reply-To: <474B199E.3060700@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Nov 2007 18:19:18.0598 (UTC) FILETIME=[0664D660:01C83122]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ntpwg@lists.ntp.org, 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

Mark Stapp wrote:
> making it possible to convey NTP servers in dhcpv6 doesn't seem to me to 
> be any different than conveying them in dhcpv4 was. that was done 
> something like ten years ago, and as far as I know that hasn't been a 
> problem.
> 
> I do wonder why some folks seem to think that using DNS names would 
> somehow be "safer" than using v6 addresses. if someone shipped a server 
> with a canned list of DNS names for NTP servers, there would be a 
> problem until the owners of the NTP servers named moved them. I don't 
> see how that'd be any better than the analogous mistake involving IP 
> addresses.
> 

Mark,

Slipping on my DNS hat for a moment, the whole point of DNS is that you
don't have to hardcode IP addresses in everything. You also benefit by
being able to put more than one IP address for the same name. It's safer
because the admin of the server doesn't have to worry when he moves a
service from on server to another. All he/she has to do is update the
DNS and not notify 1 million or so people that it's been moved. Can you
imagine moving a web server without it?

> shipping a DHCP server with a canned configuration would not be good, so 
> let's hope it doesn't happen. Mark Andrews's email seems to me to 
> summarize what happens: 'home' routers have a dhcp client face and a 
> dhcp server face, and use the client to populate the server.
> 
> aside from the catastrophe hypothetical, is there any really strong 
> reason - anything to do with the NTP protocol - that would prevent the 
> use of ipv6 addresses?
> 

It does use IPv6 addresses when it's presented with one. Now what
happens if that address is not running an NTP server? With DNS you can
get more than one address back and try another address or requery the
DNS to see if the address changed.

Danny

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