IETF Logo Mail Archive

Re: [dhcwg] DHCP server supports BOOTP client

Ralph Droms <rdroms@cisco.com> Mon, 03 May 2004 19:41 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24801; Mon, 3 May 2004 15:41:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKjCV-0006Wj-1H; Mon, 03 May 2004 15:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKiyt-0003W9-Pl for dhcwg@optimus.ietf.org; Mon, 03 May 2004 15:19:59 -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 PAA23405 for <dhcwg@ietf.org>; Mon, 3 May 2004 15:19:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKiys-0001Sc-Ib for dhcwg@ietf.org; Mon, 03 May 2004 15:19:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKiy7-0001M1-00 for dhcwg@ietf.org; Mon, 03 May 2004 15:19:12 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BKixR-0001Bx-00 for dhcwg@ietf.org; Mon, 03 May 2004 15:18:29 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i43JHtWB000774; Mon, 3 May 2004 12:17:57 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.168]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AIC68309; Mon, 3 May 2004 15:17:54 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040503151126.02b61840@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 03 May 2004 15:17:50 -0400
To: Shirley Ma <mashirle@us.ibm.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHCP server supports BOOTP client
Cc: dhcwg@ietf.org
In-Reply-To: <200405031108.44346.mashirle@us.ibm.com>
References: <DD24B3AA7EFE0D47BD09F5809C0D5D8A03DFDC25@merkur.hirschmann.de> <DD24B3AA7EFE0D47BD09F5809C0D5D8A03DFDC25@merkur.hirschmann.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
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>

The two statements are subtly different.  The design goal from RFC 2131
(which is not particularly well-worded) is aimed at compatibility of the
DHCP specification with BOOTP clients.  The statement from RFC 1534 is
intended to allow but not require that any specific DHCP server provide
BOOTP service.

A DHCP server can be compliant with RFC 2131 without providing service
to BOOTP clients...

- Ralph


At 11:08 AM 5/3/2004 -0700, Shirley Ma wrote:
>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

v2.23.0 | Report a Bug | By Email