RE: [dhcwg] Comments on draft-ietf-dhc-3315id-for-v4-03
"Bernie Volz" <volz@cisco.com> Thu, 12 August 2004 16:38 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13622; Thu, 12 Aug 2004 12:38:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvIQT-0001xC-U9; Thu, 12 Aug 2004 12:27:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BvII2-0000EP-Du for dhcwg@megatron.ietf.org; Thu, 12 Aug 2004 12:18:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12019 for <dhcwg@ietf.org>; Thu, 12 Aug 2004 12:18:51 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvIN0-00070i-Op for dhcwg@ietf.org; Thu, 12 Aug 2004 12:24:04 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i7CGGtCN021593; Thu, 12 Aug 2004 09:17:01 -0700 (PDT)
Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AKU47393; Thu, 12 Aug 2004 12:16:59 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: "'David W. Hankins'" <David_Hankins@isc.org>, dhcwg@ietf.org
Subject: RE: [dhcwg] Comments on draft-ietf-dhc-3315id-for-v4-03
Date: Thu, 12 Aug 2004 12:16:59 -0400
Organization: Cisco
Message-ID: <002b01c48087$cba0f480$d0412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <20040812155100.GA38172@isc.org>
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: rbhibbs@pacbell.net
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit
> And I really doubt that > Microsoft will ever make something like a client identifier a > user-configurable option (like Apple does). Well, I don't know about Win XPe, but see http://support.microsoft.com/default.aspx?scid=kb;en-us;172408. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > On Behalf Of David W. Hankins > Sent: Thursday, August 12, 2004 11:51 AM > To: dhcwg@ietf.org > Cc: rbhibbs@pacbell.net > Subject: Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for-v4-03 > > > On Wed, Aug 11, 2004 at 06:34:13PM -0700, Ted Lemon wrote: > > different IP addresses. There is no harm in this, unless you are > > concerned about excessive IP address consumption. If you are > > I'm really confused by this statement, because I thought I > documented the harm. > > Go back and read what I said about Win XPe please? I never > answerd your other mail because your recommendations about > alternative actions equally surprised me...they won't work. > You also seem fixated upon having the PXE client send 'a > different client identifier' when in fact the problem is that > it doesn't send that option at all, and the problem would be > made worse if it ever did. > > So there's quite a lot of confusion floating around already. > > > To briefly restate, an undocumented behaviour which fixes > this problem without user intervention or new PXE clients has > arisen in the majority of DHCP servers. At least one client > has arisen (Win XPe) that relies upon this behaviour in order > to boot...at all. > > So it is no longer about over-consumption of addresses. That > issue, and the way that those servers choose to solve it for > their paying customers, is what has led us now to this impasse. > > > concerned about that, there are stopgap solutions to get > you over the > > hump until the last of those PXE cards dies a well-deserved death. > > That will not happen. > > I don't think that any iteration of 'dumb bootstrap device' > will ever learn anything more complicated than it absolutely > has to, for darn good reasons. And I really doubt that > Microsoft will ever make something like a client identifier a > user-configurable option (like Apple does). > > -- > David W. Hankins "If you don't do it right the > first time, > Operations Engineer you'll just have to do > it again." > Internet Systems Consortium, Inc. -- Jack T. Hankins > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Comments on draft-ietf-dhc-3315id-for-v4-… David W. Hankins
- RE: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Bernie Volz
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… David W. Hankins
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Ted Lemon
- RE: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Bernie Volz
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… David W. Hankins
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… David W. Hankins
- RE: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Bernie Volz
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… David W. Hankins
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Ted Lemon
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… David W. Hankins
- Re: [dhcwg] Comments on draft-ietf-dhc-3315id-for… Ted Lemon