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

Brian Utterback <Brian.Utterback@Sun.COM> Mon, 26 November 2007 02:42 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 1IwTvn-0003BE-Mb; Sun, 25 Nov 2007 21:42:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwTvm-0003B3-GH for dhcwg@ietf.org; Sun, 25 Nov 2007 21:42:42 -0500
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwTvh-0007HB-TW for dhcwg@ietf.org; Sun, 25 Nov 2007 21:42:42 -0500
Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lAQ2gbcb009352 for <dhcwg@ietf.org>; Mon, 26 Nov 2007 02:42:37 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JS300A01E4H4S00@mail-amer.sun.com> (original mail from Brian.Utterback@Sun.COM) for dhcwg@ietf.org; Sun, 25 Nov 2007 19:42:37 -0700 (MST)
Received: from [192.168.1.5] ([71.168.64.220]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JS3004KAE6VPN20@mail-amer.sun.com>; Sun, 25 Nov 2007 19:42:37 -0700 (MST)
Date: Sun, 25 Nov 2007 21:42:31 -0500
From: Brian Utterback <Brian.Utterback@Sun.COM>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
In-reply-to: <017901c82fd4$9cad3b70$6401a8c0@tsg1>
To: TS Glassey <tglassey@earthlink.net>
Message-id: <474A3297.5040907@sun.com>
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
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> <017901c82fd4$9cad3b70$6401a8c0@tsg1>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Ted Lemon <mellon@fugue.com>, "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

TS Glassey wrote:
>
>> 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.
>
>   

Okay, Todd. The proposal is pretty much SOP right now, with some slight
refinements. If you deem that a show-stopper, I think the onus is on
you to suggest a reasonable alternative.

blu

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