IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Tue, 27 November 2007 20:56 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 1Ix7UE-0005nn-Hv; Tue, 27 Nov 2007 15:56:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix7UC-0005li-Ts for dhcwg@ietf.org; Tue, 27 Nov 2007 15:56:53 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix7UC-0000uT-Dn for dhcwg@ietf.org; Tue, 27 Nov 2007 15:56:52 -0500
Received: from source ([81.200.64.181]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP; Tue, 27 Nov 2007 12:56:49 PST
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 302A05689A; Tue, 27 Nov 2007 12:21:22 -0800 (PST) (envelope-from mellon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4 tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level:
Received: from [10.71.0.243] ([12.4.29.2]) (authenticated user mellon@nominum.com) by mail.nominum.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 27 Nov 2007 12:21:21 -0800
Message-Id: <DE74EB27-71C0-4A45-A2E5-B9786C84E947@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "David W. Hankins" <David_Hankins@isc.org>
In-Reply-To: <20071127192215.GC30466@isc.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [dhcwg] Re: [ntpwg] Network Time Protocol (NTP) Options for DHCPv6
Date: Tue, 27 Nov 2007 15:21:20 -0500
References: <473D0C34.4030507@ntp.org> <1195185173.26090.4.camel@uma> <474114E3.9040309@ntp.org> <474198BA.3000109@sun.com> <1195484306.9159.13.camel@uma> <4741D057.4070703@ntp.org> <20071119232225.GJ14750@isc.org> <47479E84.8080309@ntp.org> <20071126184216.GG24311@isc.org> <474C23F2.9060301@ntp.org> <20071127192215.GC30466@isc.org>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: "ntpwg@lists.ntp.org" <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

On Nov 27, 2007, at 2:22 PM, David W. Hankins wrote:
>> If the address provided by DHCP is not providing NTP service ntpd  
>> will
>> drop it. So in this case it has no recourse.
>
> That's correct; there is no recourse and in DHCP's philosphy there
> shouldn't be.

Just to be clear, most DHCP options provide lists of IP addresses, not  
single IP addresses, so it amounts to the same thing.   Indeed, in  
every server of which I am aware, if you configure the DHCP server  
with a domain name that resolves to multiple IP addresses, and the  
option so configured supports multiple IP addresses, then the DHCP  
server sends each IP address.



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

v2.23.0 | Report a Bug | By Email