Re: Minimum length of DHCP packet ?

Shawn Mamros <mamros@ftp.com> Fri, 08 March 1996 17:47 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15599; 8 Mar 96 12:47 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15595; 8 Mar 96 12:47 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa10297; 8 Mar 96 12:47 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu; (5.65v3.0/1.1.8.2/29Aug94-0956AM) id AA27602; Fri, 8 Mar 1996 12:37:43 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4) id AA05031; Fri, 8 Mar 1996 12:30:01 -0500
Received: from ftp.com by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA18232; Fri, 8 Mar 1996 12:29:59 -0500
Received: from ftp.com by ftp.com ; Fri, 8 Mar 1996 12:29:36 -0500
Received: from mailserv-C.ftp.com by ftp.com ; Fri, 8 Mar 1996 12:29:36 -0500
Received: from mamros.cavedog.ftp.com by mailserv-C.ftp.com (5.0/SMI-SVR4) id AA21644; Fri, 8 Mar 96 12:27:49 EST
Date: Fri, 8 Mar 96 12:27:49 EST
Message-Id: <9603081727.AA21644@mailserv-C.ftp.com>
To: tomy@sfc.wide.ad.jp
Subject: Re: Minimum length of DHCP packet ?
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Shawn Mamros <mamros@ftp.com>
Reply-To: mamros@ftp.com
Cc: Mike.Carney@east.sun.com, weber@tungsten.seattle.geoworks.com, dhcp-v4@bucknell.edu
X-Orig-Sender: mamros@mailserv-c.ftp.com
Repository: mailserv-C.ftp.com, [message accepted at Fri Mar 8 12:27:46 1996]
Originating-Client: cavedog.ftp.com

If you are *generating* a DHCP message, it should be no smaller than
300 bytes, in order to avoid being discarded by some relay agents.

If you are *receiving* a DHCP message...  IMO, as an absolute minimum, you
should insist on the full BOOTP header, plus five bytes of options field
(enough to contain the four byte RFC 1497 "magic cookie" plus one byte
to denote end of options field (0xFF)).  That works out to 241 bytes.

(Note that such a message would be an absolute minimalist BOOTP message,
but cannot be a DHCP message - that would require at least one additional
option, for either the DHCP message type or option overload - either way,
that would be an additional three bytes.)

-Shawn Mamros
E-mail to: mamros@ftp.com