IETF Logo Mail Archive

Re: [dhcwg] Am I missing something?

dworley@globespanvirata.com Mon, 21 January 2002 15:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13079 for <dhcwg-archive@odin.ietf.org>; Mon, 21 Jan 2002 10:47:09 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA13473 for dhcwg-archive@odin.ietf.org; Mon, 21 Jan 2002 10:47:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13339; Mon, 21 Jan 2002 10:39:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13317 for <dhcwg@optimus.ietf.org>; Mon, 21 Jan 2002 10:39:57 -0500 (EST)
Received: from firewall.agranat.com (agranat.com [198.113.147.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12813 for <dhcwg@ietf.org>; Mon, 21 Jan 2002 10:39:54 -0500 (EST)
From: dworley@globespanvirata.com
Received: from agranat.com (alice.agranat.com [10.21.0.130]) by firewall.agranat.com (8.9.0/8.9.0) with ESMTP id KAA00981 for <dhcwg@ietf.org>; Mon, 21 Jan 2002 10:39:27 -0500
Received: from dhcp75.ma.virata.com (dhcp75.ma.virata.com [10.21.0.75]) by agranat.com (8.11.6/8.11.6) with ESMTP id g0LFdQQ07512 for <dhcwg@ietf.org>; Mon, 21 Jan 2002 10:39:26 -0500
Received: (from worley@localhost) by dhcp75.ma.virata.com (8.11.0/8.11.0) id g0LFdQU10176; Mon, 21 Jan 2002 10:39:26 -0500
Date: Mon, 21 Jan 2002 10:39:26 -0500
Message-Id: <200201211539.g0LFdQU10176@dhcp75.ma.virata.com>
X-Authentication-Warning: dhcp75.ma.virata.com: worley set sender to dworley@globespanvirata.com using -f
To: dhcwg@ietf.org
In-reply-to: <4.3.2.7.2.20020121094439.01942580@goblet.cisco.com> (message from Mark Stapp on Mon, 21 Jan 2002 09:48:09 -0500)
Subject: Re: [dhcwg] Am I missing something?
References: <20020121002231.17648.qmail@quiet-like-a-panther.org> <4.3.2.7.2.20020121094439.01942580@goblet.cisco.com>
X-Scanned-By: MIMEDefang 2.2 (www dot roaringpenguin dot com slash mimedefang)
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

   From: Mark Stapp <mjs@cisco.com>

   I agree with you. I don't think that we should force our users to deploy 
   and configure any additional protocols in order to locate their ftp 
   servers. Those servers are a fundamental part of the boot process in some 
   environments, and that's what DHCP is for, right? FTP and TFTP server 
   options should be part of the base option set.

I'm not that familiar with DHCP usage, but my belief is that the most
common use for DHCP is distributing IPv4 addresses, and the
second-most-common use is for distributing TFTP addresses and file
names for fetching boot images.  If so, we would need a very strong
reason for eliminating the FTP server options.

Also, if the DHCP FTP server information is to be distributed by
another mechanism, we must ensure that existing boot ROMs will be able
to hold the code for the additional mechanism.  If not, a vendor will
recreate the FTP server options as a vendor-specific option, and 1,000
other vendors will copy it.

Dale
-- 
Dale R. WORLEY    Director, ABU Engineering     <dworley@globespanvirata.com>
GlobespanVirata	  Applications Infrastructure   http://emweb.com

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

v2.23.0 | Report a Bug | By Email