Re: IPv6 WG Last Call:draft-ietf-ipv6-optimistic-dad-02.txt

"Nick 'Sharkey' Moore" <sharkey@zoic.org> Thu, 23 September 2004 21:47 UTC

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 RAA26444 for <ipv6-web-archive@ietf.org>; Thu, 23 Sep 2004 17:47:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAbXx-000335-OP for ipv6-web-archive@ietf.org; Thu, 23 Sep 2004 17:54:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAbK1-0000cZ-UO; Thu, 23 Sep 2004 17:40:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAb80-0001z4-6y for ipv6@megatron.ietf.org; Thu, 23 Sep 2004 17:27:48 -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 RAA24965 for <ipv6@ietf.org>; Thu, 23 Sep 2004 17:27:45 -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 1CAbEq-0002es-7z for ipv6@ietf.org; Thu, 23 Sep 2004 17:34:54 -0400
Received: by anchovy.zoic.org (Postfix, from userid 1000) id 23FB37000A6; Fri, 24 Sep 2004 07:27:42 +1000 (EST)
Date: Fri, 24 Sep 2004 07:27:41 +1000
From: Nick 'Sharkey' Moore <sharkey@zoic.org>
To: Pekka Savola <pekkas@netcore.fi>
Message-ID: <20040923212741.GB15638@zoic.org>
Mail-Followup-To: Pekka Savola <pekkas@netcore.fi>, ipv6@ietf.org
References: <29AC4C04-0C9E-11D9-81FA-000D93330CAA@innovationslab.net> <Pine.LNX.4.44.0409231218330.2466-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0409231218330.2466-100000@netcore.fi>
User-Agent: Mutt/1.3.28i
X-URL: http://zoic.org/sharkey/
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ipv6@ietf.org
Subject: Re: IPv6 WG Last Call:draft-ietf-ipv6-optimistic-dad-02.txt
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

On 2004-09-23, Pekka Savola wrote:
> 
> 5. Security Considerations
> 
>    Further work will be required to integrate Optimistic DAD with Secure
>    Neighbor Discovery [SEND].
> 
> ==> sorry for not saying this earlier, but this seems unacceptable to
> me.  SEND specs are already in the RFC-ed queue, and the WG has been
> closed.  This IMHO needs to be analyzed here.  I.e., analyze and state
> how oDAD interacts (or not) with SEND.  AFAICS, there shouldn't be any
> showstoppers here..

Okay, I can see that.  I guess SEND ran past me while I wasn't
looking :-)  Would any of the ex-SEND-ites be able to help me 
out by reading the draft and suggesting a short bit of text --
as far as I can tell OptiDAD-02 and SEND-CGA "just works", because
version -02 no longer says anything about how addresses are
generated.

But are there any other SEND messages sent at address configuration
time which might cause harm in the case of an address collision?

> ==> s/::/the unspecified address/ (clearer when used in braces)
> ==> s/dependant/dependent/

No worries.

>    [MIPV6] D. Johnson, C. Perkins, J. Arkko. Mobility Support in IPv6,
>         revision 24 (draft-ietf-mobileip-ipv6-24).  June 2003 ...
>         Expired December 2003.
> 
> ==> now RFC.

Argh!  I was sure I'd fixed that one!  

Thanks,

-----Nick

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------