IETF Logo Mail Archive

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

"TS Glassey" <tglassey@earthlink.net> Mon, 26 November 2007 00:51 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 1IwSBm-0003kx-Lg; Sun, 25 Nov 2007 19:51:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwSBl-0003kQ-FR for dhcwg@ietf.org; Sun, 25 Nov 2007 19:51:05 -0500
Received: from elasmtp-masked.atl.sa.earthlink.net ([209.86.89.68]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwSBl-0007OS-4p for dhcwg@ietf.org; Sun, 25 Nov 2007 19:51:05 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=WWH4ac1y4SvjjMxIy8qHcgrVc4OYlaQzys3Kn4wchG6HH14XWwXDMnSPj3b8KqNo; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [24.23.176.93] (helo=tsg1) by elasmtp-masked.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IwSBi-0004lO-L0; Sun, 25 Nov 2007 19:51:02 -0500
Message-ID: <014d01c82fc6$6b1ecd70$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Ted Lemon <mellon@fugue.com>, Mark Andrews <Mark_Andrews@isc.org>
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Sun, 25 Nov 2007 16:50:59 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7939d48b7fb01b4ca082084746c2e1df83350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ntpwg@lists.ntp.org, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>, 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

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

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

v2.23.0 | Report a Bug | By Email