RE: [dhcwg] DHCP server supports BOOTP client

"Kevin A. Noll" <kevin.noll@perfectorder.com> Mon, 03 May 2004 19:18 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23157; Mon, 3 May 2004 15:18:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKilR-0007k4-Fp; Mon, 03 May 2004 15:06:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKifT-0000gl-Bl for dhcwg@optimus.ietf.org; Mon, 03 May 2004 14:59:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20536 for <dhcwg@ietf.org>; Mon, 3 May 2004 14:59:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKifQ-0006Xx-Ca for dhcwg@ietf.org; Mon, 03 May 2004 14:59:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKiei-0006RM-00 for dhcwg@ietf.org; Mon, 03 May 2004 14:59:08 -0400
Received: from endeavor.poss.com ([198.70.184.137] helo=smtp.poss.com) by ietf-mx with esmtp (Exim 4.12) id 1BKidb-0006E4-00 for dhcwg@ietf.org; Mon, 03 May 2004 14:57:59 -0400
Received: from conversion-daemon.endeavor.poss.com by endeavor.poss.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) id <0HX500101J0E8R@endeavor.poss.com> for dhcwg@ietf.org; Mon, 03 May 2004 14:57:28 -0400 (EDT)
Received: from kan1 (user213.net456.oh.sprint-hsd.net [65.40.141.213]) by endeavor.poss.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0HX500MSLJBQC4@endeavor.poss.com>; Mon, 03 May 2004 14:57:27 -0400 (EDT)
Date: Mon, 03 May 2004 14:57:26 -0400
From: "Kevin A. Noll" <kevin.noll@perfectorder.com>
Subject: RE: [dhcwg] DHCP server supports BOOTP client
In-reply-to: <200405031108.44346.mashirle@us.ibm.com>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: dhcwg@ietf.org
Message-id: <PPEKLDPHBHOIHMHKFGLLEEIBDAAA.kevin.noll@perfectorder.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
Content-Transfer-Encoding: 7BIT


I think the correct interpretation would be that the server MUST
be able to support BOOTP clients, but the system administrator
MUST be able to determine how BOOTP requests are handled.

If you re-read Section 2, Paragraph 1 of RFC 1534, I think you'll
see that this interpretation is implied.

There appears to be a consensus on this because most DHCP servers
do it this way.

--kan--



> -----Original Message-----
> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of
> Shirley Ma
> Sent: Monday, 03 May, 2004 2:09 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] DHCP server supports BOOTP client
> 
> 
> In RFC 1534, Section 2. BOOTP clients and DHCP servers
> 	In summary, a DHCP server:
> 	. May suppport BOOTP client
> 
> In RFC 2131, section 1.6 Design goals
> 	. DHCP must provide service to existing BOOTP clients.
> 
> It's confused, which one we need to follow?
> 
> -- 
> Thanks
> Shirley Ma
> IBM Linux Technology Center
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 

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