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

Brian Utterback <Brian.Utterback@Sun.COM> Mon, 26 November 2007 03:38 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 1IwUnh-0007K9-LM; Sun, 25 Nov 2007 22:38:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwUng-0007K3-Mn for dhcwg@ietf.org; Sun, 25 Nov 2007 22:38:24 -0500
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwUnd-00008R-D3 for dhcwg@ietf.org; Sun, 25 Nov 2007 22:38:24 -0500
Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id lAQ3cKUB004466 for <dhcwg@ietf.org>; Mon, 26 Nov 2007 03:38:21 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 <0JS300301GOAQJ00@mail-amer.sun.com> (original mail from Brian.Utterback@Sun.COM) for dhcwg@ietf.org; Sun, 25 Nov 2007 20:38:20 -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 <0JS3004XZGRTPN90@mail-amer.sun.com>; Sun, 25 Nov 2007 20:38:18 -0700 (MST)
Date: Sun, 25 Nov 2007 22:38:17 -0500
From: Brian Utterback <Brian.Utterback@Sun.COM>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
In-reply-to: <018501c82fd7$9ff707e0$6401a8c0@tsg1>
To: TS Glassey <tglassey@earthlink.net>
Message-id: <474A3FA9.5020303@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> <E0F01D6C-3FB6-4150-9722-32CFF3079327@fugue.com> <018501c82fd7$9ff707e0$6401a8c0@tsg1>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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:
>
> Sorry but reality is what it is, and adding this support to DHCP opens more 
> problems than it solves.
>
> Todd 
>   

Truly? In your audited world, can't you just preclude the use
of DHCP based server discovery if it poses such a problem?

blu

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