NAME

MoveDAD - MN does DAD after forming new CoA

TARGET

Host

SYNOPSIS

MoveDAD.seq [-tooloption ...] -pkt MN_Common.def

-tooloption: v6eval tool option

TOPOLOGY

                                      |
                                      R       TN
                                      |       |
                              --------+-------+--------------- LinkZ




                                      |
                                      R2             NUT2
                                      |               |
                              --------+---------------+------- LinkY




                                      |       |
                                      HA2     R1     NUT1
                                      |       |       |
                              --------+-------+-------+------- LinkX




                          |           |
             NUT0        HA1          HA0
              |           |           |
Link0 --------+-----------+-----------+-----------------------
Link0 3ffe:501:ffff:100::/64 home link
LinkX 3ffe:501:ffff:102::/64  
LinkY 3ffe:501:ffff:103::/64  
LinkZ 3ffe:501:ffff:104::/64  
HA0(Link0) 3ffe:501:ffff:100:200:ff:fe00:a1a1/64  
HA1(Link0) 3ffe:501:ffff:100:200:ff:fe00:a2a2/64  
HA2(LinkX) 3ffe:501:ffff:102:200:ff:fe00:a3a3  
R1(LinkX) 3ffe:501:ffff:102:200:ff:fe00:a4a4  
R2(LinkY) 3ffe:501:ffff:103:200:ff:fe00:a5a5  
TN(LinkZ) 3ffe:501:ffff:104:200:ff:fe00:a6a6  

TEST PROCEDURE

MN does DAD after forming new CoA


        HA     NUT     R1
        |       |       | 
        |       | <---- |  RA
        |       |       | 
        |       | ----> |  DAD NS
        |       |       |

JUDGEMENT

(*1) PASS: TN receives DAD NS

REFERENCE

draft-ietf-mobileip-ipv6-20.txt
11.5.2 Forming New Care-of Addresses 

   RFC 2462 [13] specifies that in normal processing for Duplicate
   Address Detection, the node SHOULD delay sending the initial Neighbor
   Solicitation message by a random delay between 0 and
   MAX_RTR_SOLICITATION_DELAY.  Since delaying DAD can result in
   significant delays in configuring a new care of address when the
   Mobile Node moves to a new link, the Mobile Node preferably SHOULD
   NOT delay DAD when configuring a new care of address.  The Mobile
   Node SHOULD delay according to the mechanisms specified in RFC 2462
   if the Mobile IP stack cannot distinguish between the normal process
   of moving to a new link and reinitializing the interface, or if the
   link layer does not include adequate local collision and congestion
   control mechanisms.