Re: [dhcwg] DHCPv4 - definition of maximum message size.
"David W. Hankins" <David_Hankins@isc.org> Mon, 09 May 2005 17:20 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVBvU-0005OR-Vp; Mon, 09 May 2005 13:20:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVBvT-0005OM-HX for dhcwg@megatron.ietf.org; Mon, 09 May 2005 13:20:15 -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 NAA08501 for <dhcwg@ietf.org>; Mon, 9 May 2005 13:20:12 -0400 (EDT)
Received: from kaboom.isc.org ([204.152.187.72]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVCAc-00016O-0T for dhcwg@ietf.org; Mon, 09 May 2005 13:35:55 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200) id 9FA82B240B; Mon, 9 May 2005 10:20:00 -0700 (PDT)
Date: Mon, 09 May 2005 10:20:00 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv4 - definition of maximum message size.
Message-ID: <20050509172000.GA17500@isc.org>
References: <427B506B.1050005@thekelleys.org.uk> <200505071335.26787.budm@weird-solutions.com>
Mime-Version: 1.0
In-Reply-To: <200505071335.26787.budm@weird-solutions.com>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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="===============1833381190=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
On Sat, May 07, 2005 at 01:35:26PM +0200, Bud Millwood wrote: > And for David: I seem to recall that the ISC DHCP server uses some type > of raw > interface to the network layer; might the ethernet header size be included > for that reason? Yes, this was probably done to ensure that the output packet would never exceed 1500 bytes (due to some platform limitation in passing data in sizes larger than that, even though through raw sockets, I am imagining). But this is calculating the maximum size of the "options" space from the client-supplied mms, and consequently the maximum size of the output packet since that's the only variable, rather than directly calculating output packet space. It doesn't matter if the client (or server) is not ethernet, and it doesn't matter if the server is using Berkeley sockets. It's applied in every case. I think this is pretty clearly a bug on our part, but the fact that this is in all released versions of the software of which I am aware (this calculation of "udp overhead" is in RCS version 1.1 of the header, so it appeared in all version-2 releases), I think muddies the 'what does MMS mean' question that's being asked here. -- 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
- [dhcwg] DHCPv4 - definition of maximum message si… Simon Kelley
- Re: [dhcwg] DHCPv4 - definition of maximum messag… David W. Hankins
- RE: [dhcwg] DHCPv4 - definition of maximum messag… Bernie Volz (volz)
- Re: [dhcwg] DHCPv4 - definition of maximum messag… Bud Millwood
- Re: [dhcwg] DHCPv4 - definition of maximum messag… Simon Kelley
- RE: [dhcwg] DHCPv4 - definition of maximum messag… Barr Hibbs
- RE: [dhcwg] DHCPv4 - definition of maximum messag… Barr Hibbs
- RE: [dhcwg] DHCPv4 - definition of maximum messag… Bernie Volz (volz)
- Re: [dhcwg] DHCPv4 - definition of maximum messag… David W. Hankins