Re: DAD
"Nick 'Sharkey' Moore" <sharkey@zoic.org> Tue, 17 May 2005 22:17 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYANN-0001ww-24; Tue, 17 May 2005 18:17:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYANK-0001wm-Ix for ipv6@megatron.ietf.org; Tue, 17 May 2005 18:17:18 -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 SAA26696 for <ipv6@ietf.org>; Tue, 17 May 2005 18:17:15 -0400 (EDT)
Received: from static-2.241.240.220.dsl.comindico.com.au ([220.240.241.2] helo=anchovy.zoic.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DYAe8-0006iW-LM for ipv6@ietf.org; Tue, 17 May 2005 18:34:42 -0400
Received: by anchovy.zoic.org (Postfix, from userid 1000) id 965037000A8; Wed, 18 May 2005 08:17:11 +1000 (EST)
Date: Wed, 18 May 2005 08:17:09 +1000
From: Nick 'Sharkey' Moore <sharkey@zoic.org>
To: ipv6@ietf.org
Message-ID: <20050517221708.GA2640@zoic.org>
Mail-Followup-To: ipv6@ietf.org
References: <936A4045C332714F975800409DE092403F0A45@tayexc14.americas.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <936A4045C332714F975800409DE092403F0A45@tayexc14.americas.cpqcorp.net>
User-Agent: Mutt/1.3.28i
X-URL: http://zoic.org/sharkey/
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
On 2005-05-17, Bound, Jim wrote: > > There is also Optimistic DAD that can be used for commercial mobile > devices on wireless networks, one should review and check. But, today I > am aware of no implementations that do not implement DAD or have > implemented Optimistic DAD (but there are folks on this list that can > correct me if Optimistic DAD has been implemented???). Optimistic DAD is in the Standards Track queue now. We implemented it for Linux as part of the development process, and I'll make the patch available again soon ... I'm working on other things until the IESG/etc comments come back, then I'll update the patch and release. Some vendors have expressed their interest in implementing once it is nailed down in an RFC. Linux, at least, can be set up to not run DAD very simply by setting the DAD retransmits parameter to 0. Whether this is a good idea is another matter. There's some discussion of the original poster's question in the OptiDAD draft: see draft-ietf-ipv6-optimistic-dad-05.txt cheers, -----Nick -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------