NAME

MoveFreq - CoA changes frequently

TARGET

Host

SYNOPSIS

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

CoA changes frequently


     Loop
        HA0    NUT1     R1      R2
        |       | <---- |       | RA
        | <---- |       |       | Binding Update (*1)
        | ----> |       |       | Binding Acknowledgement
        |      NUT2     |       | (Sleep 1 sec)
        |       | <------------ | RA
        | <---- |       |       | Binding Update (*2)
        | ----> |       |       | Binding Acknowledgement
        |       |       |       |
     Loop

JUDGEMENT

(*1) PASS: HA0 receives Binding Update

(*2) PASS: HA0 receives Binding Update

REFERENCE

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

   After detecting that it has moved from one link to another (i.e., its
   current default router has become unreachable and it has discovered a
   new default router), a mobile node SHOULD generate a new primary
   care-of address using normal IPv6 mechanisms.  A mobile node MAY form
   a new primary care-of address at any time, but a mobile node MUST NOT
   send a Binding Update about a new care-of address to its home agent
   more than MAX_UPDATE_RATE times within a second.