On Wed, 22 Sep 2004, Brian Haberman wrote:
>       This starts a 1 week IPv6 Working Group Last Call on advancing:
> 
>           Title           : Optimistic Duplicate Address Detection for IPv6
>           Author(s)  : N. Moore
>           Filename : draft-ietf-ipv6-optimistic-dad-02.txt
>           Pages       : 15
>           Date                 : 2004-9-9
> 
> as a Proposed Standard.  This last call is to ensure that all comments
> raised during the initial last call have been addressed.  Substantive
> comments should be addressed to the IPv6 mailing list.  The last call
> will end on Sept. 29, 2004.

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..

.....

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
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to