Re: [dhcwg] DHCPv4 - definition of maximum message size.

"David W. Hankins" <David_Hankins@isc.org> Fri, 06 May 2005 18:52 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DU7wM-0003oM-Qu; Fri, 06 May 2005 14:52:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DU7wL-0003oH-Ce for dhcwg@megatron.ietf.org; Fri, 06 May 2005 14:52:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22789 for <dhcwg@ietf.org>; Fri, 6 May 2005 14:52:43 -0400 (EDT)
Received: from kaboom.isc.org ([204.152.187.72]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DU8As-0001LT-HB for dhcwg@ietf.org; Fri, 06 May 2005 15:07:47 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200) id A2D4EB240B; Fri, 6 May 2005 11:52:33 -0700 (PDT)
Date: Fri, 06 May 2005 11:52:33 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv4 - definition of maximum message size.
Message-ID: <20050506185233.GD826@isc.org>
References: <427B506B.1050005@thekelleys.org.uk>
Mime-Version: 1.0
In-Reply-To: <427B506B.1050005@thekelleys.org.uk>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0619771907=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

On Fri, May 06, 2005 at 12:09:31PM +0100, Simon Kelley wrote:
> Does the value in "maximum message size" option (option code 56) include 
> the IP and UDP headers?
> 
> Neither RFC2131 or RFC2132 ever state this explicitly, but they are 
> self-consistent if it's the case. RFC2132 states that the minimum legal 
> value is 576 octets, which equals IP header + UDP header + fixed DHCP 
> fields + the minimum 312 octet options field specified in RFC2131.

To add to your confusion, ISC DHCP calculates this as:

	'mms' - (ethernet + ip + udp + dhcp header sizes)

Should the 'mms' be less than 576, we use 576.

I suspect our inclusion of the ethernet header size in this calculation
is incorrect, since as you mention it doesn't add up if you use a 312 byte
options field.

> I ask because I've just come across a client which advertises a maximum 
> message size of 548. Presumably this is broken, and there's a chance 
> that the client is also misinterpreting a "576" maximum message size 
> option _from_ a DHCP server  and could potentially try and use 28 bytes 
> that the server cannot receive.

As I mentioned above, I believe our DHCP server would simply not observe
this mms, and pretend as though it was not supplied.

> If the wise ones here can confirm that this really is an RFC violation, 
> I'll submit a bug report to the vendor of the client.

I have no such wisdom.

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg