[dhcwg] Minimum length for inbound DHCP packets

Greg Kilfoyle <gregk@redback.com> Mon, 04 March 2002 20: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 PAA21954 for <dhcwg-archive@odin.ietf.org>; Mon, 4 Mar 2002 15:47:54 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA00212 for dhcwg-archive@odin.ietf.org; Mon, 4 Mar 2002 15:47:58 -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 PAA00025; Mon, 4 Mar 2002 15:44:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA29483 for <dhcwg@ns.ietf.org>; Mon, 4 Mar 2002 15:31:58 -0500 (EST)
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.9.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20448 for <dhcwg@ietf.org>; Mon, 4 Mar 2002 15:31:54 -0500 (EST)
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9]) by mail.bucknell.edu (8.11.6/8.11.6) with ESMTP id g24KVr206719 for <dhcp-v4@bucknell.edu>; Mon, 4 Mar 2002 15:31:53 -0500 (EST)
Received: from wan-pppoe-1.lab.redback.com (wan-pppoe-1.lab.redback.com [10.13.48.37]) by prattle.redback.com (Postfix) with ESMTP id 9B11A262815 for <dhcp-v4@bucknell.edu>; Mon, 4 Mar 2002 12:31:51 -0800 (PST)
From: Greg Kilfoyle <gregk@redback.com>
To: dhcp-v4@bucknell.edu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0.2
Date: Mon, 04 Mar 2002 12:22:04 -0800
Message-Id: <1015273324.19876.61.camel@wan-pppoe-1.lab.redback.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Minimum length for inbound DHCP packets
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
Content-Transfer-Encoding: 7bit

Hi,

For a DHCP server or relay agent, I was wondering what is a reasonable
minimum length to check for on inbound packets. This is for DHCP support
only, no BOOTP support.

I was thinking an initial check should use the BOOTP minimum length and
check for a DHCP packet length of 300 bytes (which makes 328 bytes
including normal IP and UDP headers).

Using a test tool to test the DHCP server implementation showed that the
test tool was sending DHCP packets of less than 300 bytes (and the above
check was failing).

On one hand this is a problem with the test tool; on the other hand, how
many clients out there do not send the minimum BOOTP length? In other
words, if I don't allow less then the BOOTP minimum length, how many
clients will not work correctly?

Maybe a more forgiving approach would be a length that includes the
magic cookie and at least one option (an end option being 1 byte).

Any thoughts welcome.

Thanks, Greg.
-- 
Greg Kilfoyle (gregk@redback.com)



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