Re: [dhcwg] ARP reply vs. ARP request to announce address acquired from DHCP

Thamer Al-Harbash <tmh@whitefang.com> Tue, 14 January 2003 00:36 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29661; Mon, 13 Jan 2003 19:36:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E0nZJ03690; Mon, 13 Jan 2003 19:49:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0E0cSJ03290 for <dhcwg@optimus.ietf.org>; Mon, 13 Jan 2003 19:38:28 -0500
Received: from helena.whitefang.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29318 for <dhcwg@ietf.org>; Mon, 13 Jan 2003 19:24:03 -0500 (EST)
Received: (qmail 91784 invoked from network); 14 Jan 2003 00:27:43 -0000
Received: from helena.whitefang.com (216.254.175.50) by 0 with SMTP; 14 Jan 2003 00:27:43 -0000
Date: Mon, 13 Jan 2003 19:27:43 -0500
From: Thamer Al-Harbash <tmh@whitefang.com>
X-X-Sender: shadows@helena.whitefang.com
To: Ted Lemon <Ted.Lemon@nominum.com>
cc: Erik Nordmark <Erik.Nordmark@sun.com>, Thomas Narten <narten@us.ibm.com>, zeroconf@merit.edu, Stuart Cheshire <cheshire@apple.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] ARP reply vs. ARP request to announce address acquired from DHCP
In-Reply-To: <BC338052-2730-11D7-A7EA-00039367340A@nominum.com>
Message-ID: <Pine.BSF.4.51.0301131922010.85425@helena.whitefang.com>
References: <BC338052-2730-11D7-A7EA-00039367340A@nominum.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>

On Mon, 13 Jan 2003, Ted Lemon wrote:

> This is what is recommended in the Stevens TCP/IP book.   I think the
> reason this is so common is that the ARP announcement is part of the
> interface configuration process, and is not done by the DHCP client, so
> the people that read the DHCP spec aren't the ones that write the code
> that does the announcement.   This is certainly the case with the ISC
> DHCP client.   On Unix systems of which I am aware, it's not possible
> to do ARP processing outside the kernel.   Since the ISC DHCP client
> runs on Unix, it's pretty much stuck with whatever the operating system
> provides.

The dhcpcd package specifically fires off an ARP reply after
setting its interface up last I checked. My own code, dhcp-agent,
has this feature in the old release and in its -current.

> So in fact all the DHCP clients of which I am aware are technically out
> of spec with RFC2131.

I'm surprised you haven't implemented this in the ISC dhcp suite
or think others havent for any technical reason. It's actually
pretty straight forward under UNIX since with a DHCP program you
generally talk to the network rawly and it's literally just a
matter of writing the packet to the raw network device and going
on with business as usual.

It's an entirely different matter if the other operating systems
on the LAN will take note of it.

-- 
Thamer Al-Harbash            http://www.whitefang.com/
          team dresch made me do it
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg