Re: [dhcwg] Maximum message size interpretation

Tobin Coziahr <tobin.coziahr@sun.com> Tue, 19 February 2002 09:31 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 EAA13038 for <dhcwg-archive@odin.ietf.org>; Tue, 19 Feb 2002 04:31:28 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA23024 for dhcwg-archive@odin.ietf.org; Tue, 19 Feb 2002 04:31:29 -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 EAA22331; Tue, 19 Feb 2002 04:22:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA22304 for <dhcwg@ns.ietf.org>; Tue, 19 Feb 2002 04:21:54 -0500 (EST)
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12955 for <dhcwg@ietf.org>; Tue, 19 Feb 2002 04:21:52 -0500 (EST)
Received: from sunmail1.Sun.COM ([129.145.1.2]) by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA05266; Tue, 19 Feb 2002 02:21:48 -0700 (MST)
Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.84.45]) by sunmail1.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1-Sun.COM.mod.2) with ESMTP id BAA21079; Tue, 19 Feb 2002 01:23:38 -0800 (PST)
Received: from sun.com (raistlin.Eng.Sun.COM [129.146.86.244]) by jurassic.eng.sun.com (8.12.2+Sun/8.12.2) with ESMTP id g1J9LlrU359410; Tue, 19 Feb 2002 01:21:48 -0800 (PST)
Message-ID: <3C721940.3D1D0D80@sun.com>
Date: Tue, 19 Feb 2002 01:22:08 -0800
From: Tobin Coziahr <tobin.coziahr@sun.com>
Organization: Sun Microsystems
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.9 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Bud Millwood <budm@weird-solutions.com>
CC: DHCP discussion list <dhcwg@ietf.org>
Subject: Re: [dhcwg] Maximum message size interpretation
References: <20020215102055.NDNZ23536.fep01-svc.swip.net@there>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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

Bud-

The Maximum Message Size option is also known as the "maximum DHCP
message size" option (See RFC 2131, page 9-10).  This ONLY refers to the
size of the DHCP packet itself, without the IP and UDP headers.  The
point of the option is to let servers use messages larger than 548
bytes, which is the default max.

So no, don't subtract the header size.

-Tobin 


Bud Millwood wrote:
> 
> When a client gives my server the maximum message size it can receive, should
> I interpret that as the total IP packet size the client can receive or just
> the size of the DHCP portion?
> 
> >From the description of this option, it appears that I should interpret the
> value as the size of the entire IP packet the client can receive.
> 
> In other words, should I subtract IP and UDP header sizes from a client's
> Maximum Message Size value?
> 
> - Bud
> 
> Bud Millwood
> Weird Solutions, Inc.
> http://www.weird-solutions.com
> tel: +46 70 566 7803
> fax: +46 8 758 3687
> mailto:budm@weird-solutions.com
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

-- 
Tobin Coziahr			650-786-7118 (x87118)
Solaris Networking		tobin.coziahr@sun.com
Sun Microsystems

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