IETF Logo Mail Archive

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

Bud Millwood <budm@weird-solutions.com> Mon, 26 November 2007 08:34 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 1IwZQ1-0004cj-L9; Mon, 26 Nov 2007 03:34:17 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwZPy-0004ca-UP for dhcwg@ietf.org; Mon, 26 Nov 2007 03:34:14 -0500
Received: from intermail.se.dataphone.net ([212.37.1.50]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwZPy-0001oV-G3 for dhcwg@ietf.org; Mon, 26 Nov 2007 03:34:14 -0500
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2) with ESMTP id 51673984 for dhcwg@ietf.org; Mon, 26 Nov 2007 09:34:12 +0100
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Mon, 26 Nov 2007 08:48:23 +0100
User-Agent: KMail/1.8
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1>
In-Reply-To: <014d01c82fc6$6b1ecd70$6401a8c0@tsg1>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711260848.23497.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
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 Monday 26 November 2007 01:50, TS Glassey wrote:

> So Ted how does the DHCP server get refreshed to know that NTP Server "A"
> is dead now?

The server runs a keepalive for this service list (NTP). When an NTP server is 
down the list entry is marked as such and not given out until it's back 
online. No administrative intervention required unless all servers die.

- Bud

> Todd
>
> ----- Original Message -----
> From: "Ted Lemon" <mellon@fugue.com>
> To: "Mark Andrews" <Mark_Andrews@isc.org>
> Cc: <ntpwg@lists.ntp.org>; "Danny Mayer" <mayer@ntp.org>; "Richard Gayraud
> (rgayraud)" <rgayraud@cisco.com>; <dhcwg@ietf.org>
> Sent: Sunday, November 25, 2007 4:40 PM
> Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP)
> OptionsforDHCPv6
>
> > On Nov 25, 2007, at 6:09 PM, Mark Andrews wrote:
> >> I would think that this should be a push operation from the dhcp
> >> client rather than a pull operation.
> >
> > Sure, but it amounts to the same thing.   This is trivial to do with
> > the ISC DHCP client (which I presume is the one you use).   It's also
> > trivial to do on Linux with dbus.   Mac OS X and Windows handle it
> > differently still, but they already have mechanisms in place for doing
> > this.   So the point is that if the will exists to make it happen,
> > it's trivial to make it happen.
> >
> > _______________________________________________
> > ntpwg mailing list
> > ntpwg@lists.ntp.org
> > https://lists.ntp.org/mailman/listinfo/ntpwg
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

-- 
Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687

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

v2.23.0 | Report a Bug | By Email