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

"Soliman, Hesham" <H.Soliman@flarion.com> Thu, 23 September 2004 19:11 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 PAA12272 for <ipv6-web-archive@ietf.org>; Thu, 23 Sep 2004 15:11:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAZ6o-0007OU-C9 for ipv6-web-archive@ietf.org; Thu, 23 Sep 2004 15:18:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAYpI-0008F9-Uu; Thu, 23 Sep 2004 15:00:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAYdW-0003QH-Ib for ipv6@megatron.ietf.org; Thu, 23 Sep 2004 14:48:10 -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 OAA09366 for <ipv6@ietf.org>; Thu, 23 Sep 2004 14:48:08 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23] helo=ftmailgfi.flariontech.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAYkL-0006kz-Hv for ipv6@ietf.org; Thu, 23 Sep 2004 14:55:14 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by ftmailgfi.flariontech.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Sep 2004 14:46:22 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Sep 2004 14:46:22 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD394B44@ftmailserver.flariontech.com>
Thread-Topic: IPv6 WG Last Call:draft-ietf-ipv6-optimistic-dad-02.txt
Thread-Index: AcShUTzZKvdT9wSMRW+BCM4fdj4scAATCqtg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: Pekka Savola <pekkas@netcore.fi>, Brian Haberman <brian@innovationslab.net>
X-OriginalArrivalTime: 23 Sep 2004 18:46:22.0394 (UTC) FILETIME=[9F1271A0:01C4A19D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 WG <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: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable


 > One major comment:
 >                                                              
 >                                                            
 > 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..

=> Actually, just another comment on the same line in the draft, 
what kind of work is needed to allow for SEND and optDAD to coexist?
SEND should make life easier for this proposal, what needs
to be done?

Hesham

 > 
 > .....
 > 
 > A couple of editorial nits/typos:
 > 
 >    There will be no response to its NS (sent from ::), and this NS 
 > will
 >  
 > ==> s/::/the unspecified address/ (clearer when used in braces)
 > 
 >    This version of Optimistic DAD is dependant on the details of the
 >  
 > ==> s/dependant/dependent/
 > 
 >    [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.
 > 
 > -- 
 > Pekka Savola                 "You each name yourselves king, yet the
 > Netcore Oy                    kingdom bleeds."
 > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
 > 
 > 
 > --------------------------------------------------------------------
 > IETF IPv6 working group mailing list
 > ipv6@ietf.org
 > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
 > --------------------------------------------------------------------
 > 

===========================================================
This email may contain confidential and privileged material for the sole use
 of the intended recipient.  Any review or distribution by others is strictly
 prohibited.  If you are not the intended recipient please contact the sender
 and delete all copies.
===========================================================


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