Re: [dhcwg] Network Time Protocol (NTP) Options for DHCPv6

Danny Mayer <mayer@ntp.org> Thu, 29 November 2007 06:40 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 1Ixd4L-00078X-PV; Thu, 29 Nov 2007 01:40:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ixd4J-00078C-Ex for dhcwg@ietf.org; Thu, 29 Nov 2007 01:40:15 -0500
Received: from mx05.gis.net ([208.218.130.13]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ixd4J-0007cG-4r for dhcwg@ietf.org; Thu, 29 Nov 2007 01:40:15 -0500
Received: from [10.10.10.101] ([63.209.224.211]) by mx05.gis.net; Thu, 29 Nov 2007 01:40:01 -0500
Message-ID: <474E5E16.5060003@ntp.org>
Date: Thu, 29 Nov 2007 01:37:10 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Network Time Protocol (NTP) Options for DHCPv6
References: <A05118C6DF9320488C77F3D5459B17B7062ED3C6@xmb-ams-333.emea.cisco.com> <200711282235.17331.budm@weird-solutions.com> <384B1789-85D1-43E5-BC6C-60CD877710F4@nominum.com>
In-Reply-To: <384B1789-85D1-43E5-BC6C-60CD877710F4@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, NTP Working Group <ntpwg@lists.ntp.isc.org>, Bud Millwood <budm@weird-solutions.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

Ted Lemon wrote:
> This is a different situation from a router vendor putting a default
> value in, in the sense that an ISP providing configuration information
> is actively advising their customer to do something, whereas a router
> vendor is just doing it.

Unfortunately it looks like yet another router vendor is doing this.
Information about this showed up in my email this afternoon. It's the
reason that I'm so leary of just having IP addresses. It's virtually
impossible to get the firmware updated in already shipped routers.

Danny


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