IETF Logo Mail Archive

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

"TS Glassey" <tglassey@earthlink.net> Mon, 26 November 2007 02:32 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 1IwTmC-0002Ry-9S; Sun, 25 Nov 2007 21:32:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwTmA-0002I1-Fq for dhcwg@ietf.org; Sun, 25 Nov 2007 21:32:46 -0500
Received: from elasmtp-scoter.atl.sa.earthlink.net ([209.86.89.67]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwTm7-00072H-2W for dhcwg@ietf.org; Sun, 25 Nov 2007 21:32:46 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=GriCHzH84gYZVULNA/q+FSUchlzhz5MnmHMITceKkJekresX6sP5WV11OyaYbZ8u; 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-scoter.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IwTm2-0004Qp-NE; Sun, 25 Nov 2007 21:32:39 -0500
Message-ID: <017901c82fd4$9cad3b70$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Ted Lemon <mellon@fugue.com>
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1> <5C093633-A256-4059-AA10-1800F62F522A@fugue.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Sun, 25 Nov 2007 18:32:34 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
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: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79f1280addc682424474bbbc67c241f07f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Mark Andrews <Mark_Andrews@isc.org>, "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

----- Original Message ----- 
From: "Ted Lemon" <mellon@fugue.com>
To: "TS Glassey" <tglassey@earthlink.net>
Cc: "Mark Andrews" <Mark_Andrews@isc.org>; <ntpwg@lists.ntp.org>; "Richard 
Gayraud (rgayraud)" <rgayraud@cisco.com>; <dhcwg@ietf.org>
Sent: Sunday, November 25, 2007 6:26 PM
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) 
OptionsforDHCPv6


> On Nov 25, 2007, at 6:50 PM, TS Glassey wrote:
>> So Ted how does the DHCP server get refreshed to know that NTP  Server 
>> "A" is
>> dead now?
>
> Like most DNS servers, most DHCP servers are operated by network 
> administrators.   So the network administrator goes in and updates one  or 
> the other, and the next time a request comes in, the DHCP server  gets the 
> new IP address and returns it, whether it gets it from the  DNS or from 
> its own configuration.
>

Which makes the Network Administrator liable for screw-up's and the damages 
therein... Sorry this one is a no-sale IMHO.

Todd 


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

v2.23.0 | Report a Bug | By Email