NAME

MN-2-1-1-1-008 - Sending BU (after the expiration of home registration)


TARGET

Host


TOPOLOGY

                    
                                  |
                                  R       CN0
                                  |        |
                     -----+-------+--------+---------------- LinkZ
                          |
                          R2                      NUTY
                          |                         |
                     -----+-------+-----------------+------- LinkY
                                  |
                                  R1              NUTX
                                  |                 |
                     -----+-------+-----------------+------- LinkX
                          |
                         HA0             Node0    NUT0
                          |               |         |
    ----------------------+---------------+---------+------- 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:a0a0  
Node0(Link0) 3ffe:501:ffff:100:200:ff:fe00:a3a3  
R1(LinkX) 3ffe:501:ffff:102:200:ff:fe00:a4a4  
R2(LinkY) 3ffe:501:ffff:103:200:ff:fe00:a6a6  
CN0(LinkZ) 3ffe:501:ffff:104:200:ff:fe00:a8a8  


INITIALIZATION

 1. Selection Option
    - none
 2. Position of Mobile Node
    - none


TEST PROCEDURE

                    
       HA0     NUT0     R1      R2      CN0
        |       |       |       |        |
        | ----> |       |       |        |  1.Router Advertisement
        |       |       |       |        |
        |      NUTX     |       |        |
        |       |       |       |        |
        |       | <---- |       |        |  2.Router Advertisement
        |       |       |       |        |
        | <---- |       |       |        |  3.Neighbor Solicitations(NUD)
        |       |       |       |        |  4.(no reply)
        |       |       |       |        |
        | <---- |       |       |        |  5.Binding Update
        | ----> |       |       |        |  6.Binding Acknowledgement
        |       |       |       |        |
        |       |       |       |        |  7.(wait)
        |       |       |       |        |
        |       | <---- |       |        |  8.Router Advertisement
        |       |       |       |        |
        | <---- |       |       |        |  9.Binding Update (*1)
        |       |       |       |        | 10.(no reply)
        |       |       |       |        |
        | <---- |       |       |        | 11.Binding Update (*2)
        |       |       |       |        |
                    
        1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
        2. Send Router Advertisement. (R1 -> R1_allnode_multi)
        3. Receive Neighbor Solicitations(NUD). (NUT0 -> HA0)
        4. (no reply)
            # Wait during a maximum of 3 seconds(RFC2461).
        5. Receive Binding Update. (NUTX -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTX)
        7. (wait)
            # Wait during a maximum of the lifetime value in the Binding Update[5].
        8. Send Router Advertisement. (R1 -> R1_allnode_multi)
        9. Receive Binding Update. (NUTX -> HA0)
       10. (no reply)
       11. Receive Binding Update. (NUTX -> HA0)
                    
        Packet Format is:
          9. Binding Update
                    


JUDGEMENT

 (*1) PASS: HA0 receives Binding Update.
 (*2) PASS: HA0 receives the retransmission of Binding Update.
            Then, check whether this packet fills all of the following,
            - The initial retransmission timer is set to InitialBindackTimeoutFirstReg.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.7.1 Sending Binding Updates to the Home Agent
                    
(snip)
                    
   The home agent will only perform DAD for the mobile node's home
   address when the mobile node has supplied a valid binding between its
   home address and a care-of address.  If some time elapses during
   which the mobile node has no binding at the home agent, it might be
   possible for another node to autoconfigure the mobile node's home
   address.  Therefore, the mobile node MUST treat creation of a new
   binding with the home agent using an existing home address the same
   as creation of a new home address.  In the unlikely event that the
   mobile node's home address is autoconfigured as the IPv6 address of
   another network node on the home network, the home agent will reply
   to the mobile node's subsequent Binding Update with a Binding
   Acknowledgement containing a Status of 134 (Duplicate Address
   Detection failed).  In this case, the mobile node MUST NOT attempt to
   re-use the same home address.  It SHOULD continue to register care-of
   addresses for its other home addresses, if any.  (Mechanisms outlined
   in Appendix B.5 may in the future allow mobile nodes to acquire new
   home addresses to replace the one for which Status 134 was received.)