Re: [dhcwg] Re: [mobile-ip] IPv4 Address Conflict Detection

dworley@globespanvirata.com Tue, 05 February 2002 15:13 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 KAA02942 for <dhcwg-archive@odin.ietf.org>; Tue, 5 Feb 2002 10:13:57 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA05471 for dhcwg-archive@odin.ietf.org; Tue, 5 Feb 2002 10:13:59 -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 JAA03946; Tue, 5 Feb 2002 09:55:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03925 for <dhcwg@optimus.ietf.org>; Tue, 5 Feb 2002 09:55:36 -0500 (EST)
Received: from firewall.agranat.com (agranat.com [198.113.147.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02185 for <dhcwg@ietf.org>; Tue, 5 Feb 2002 09:55:34 -0500 (EST)
From: dworley@globespanvirata.com
Received: from agranat.com (alice.agranat.com [10.21.0.130]) by firewall.agranat.com (8.9.0/8.9.0) with ESMTP id JAA22180; Tue, 5 Feb 2002 09:54:47 -0500
Received: from dhcp75.ma.virata.com (dhcp75.ma.virata.com [10.21.0.75]) by agranat.com (8.11.6/8.11.6) with ESMTP id g15EskQ30825; Tue, 5 Feb 2002 09:54:46 -0500
Received: (from worley@localhost) by dhcp75.ma.virata.com (8.11.0/8.11.0) id g15Eskg12995; Tue, 5 Feb 2002 09:54:46 -0500
Date: Tue, 5 Feb 2002 09:54:46 -0500
Message-Id: <200202051454.g15Eskg12995@dhcp75.ma.virata.com>
X-Authentication-Warning: dhcp75.ma.virata.com: worley set sender to dworley@globespanvirata.com using -f
To: mobile-ip@sunroof.eng.sun.com, dhcwg@ietf.org
In-reply-to: <200202050532.GAA08761@dumburken.it.kth.se> (message from Gerald Maguire on Tue, 5 Feb 2002 06:32:14 +0100 (MET))
Subject: Re: [dhcwg] Re: [mobile-ip] IPv4 Address Conflict Detection
References: <200202041944.g14JiY026372@scv2.apple.com> <200202050532.GAA08761@dumburken.it.kth.se>
X-Scanned-By: MIMEDefang 2.2 (www dot roaringpenguin dot com slash mimedefang)
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

   From: Gerald Maguire <maguire@it.kth.se>

   I think the idea of probing and waiting _before_ using an address is
   completely wrong. Since it involves waiting for something _not_ to
   happen. The better approach is to detect the conflict -- if there is
   one.

IMHO, detecting address conflicts is not a matter of a single
strategy.  For instance, if there aren't resource limitations, DHCP
clients should check for address conflicts, but DHCP servers should
also.  Hosts should also continuously monitor their interfaces for
evidence of duplicate addresses (e.g., ARPs from other hosts holding
the same address).

Especially because this is the first attempt to formalize address
conflict detection, we should be documenting all methods that are
known to be useful, preferably with notes on their costs and benefits,
and circumstances in which they are known to be particularly useful.

Dale

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