NAME

MN-5-1-2-1-027 - Sending BU to the 2nd HA of HAAD-Reply(1st=HA1 & 2nd = HA0)


TARGET

Host


TOPOLOGY

                    
                                  |
                                 HAcn     CN0     NUTZ
                                  |        |        |
                     -----+-------+--------+--------+------- LinkZ
                          |
                          R2              CN0Y    NUTY
                          |                |        |
                     -----+-------+--------+--------+------- LinkY
                                  |
                                  R1      CN0X    NUTX
                                  |        |        |
             -----+-------+-------+--------+--------+------- LinkX
                  |       |
                 HA1     HA0    Node0     CN00    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 CN0 home link
HA0(Link0) 3ffe:501:ffff:100:200:ff:fe00:a0a0  
HA1(Link0) 3ffe:501:ffff:100:200:ff:fe00:a1a1  
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  
HAcn(LinkZ) 3ffe:501:ffff:104:200:ff:fe00:aaaa  


INITIALIZATION

 1. Selection Option
    - Sending HAAD : foreign link
 2. Position of Mobile Node
    - none.


TEST PROCEDURE

                    
      HA1      HA0     NUT0     R1      CN0
       |        |       |       |        |
       |        | ----> |       |        | 1.Router Advertisement
       |        |       |       |        |
       |        |      NUTX     |        |
       |        |       |       |        |
       |        |       | <---- |        | 2.Router Advertisement
       |        |       |       |        |
       |        | <---- |       |        | 3.Neighbor Solicitations
       |        |       |       |        | 4.(no reply:3 seconds)
       |        |       |       |        |
       |        | <---- |       |        | 5.Home Agent Address Discovery Request
       |        | ----> |       |        | 6.Home Agent Address Discovery Reply
       |        |       |       |        |
       | <------------- |       |        | 7.Binding Update (*1)
       | -------------> |       |        | 8.Binding Acknowledgement
       |        |       |       |        |
                    
        1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
            # The Home Agent (H) bit is clear.
        2. Send Router Advertisement. (R1 -> R1_allnode_multi)
        3. Receive Neighbor Solicitations. (NUT0 -> HA0)
        4. (no reply)
            # Wait during a maximum of 3 seconds(RFC2461).
        5. Receive Home Agent Address Discovery Request. (NUTX -> NUT0_ha_any)
        6. Send Home Agent Address Discovery Reply. (HA0 -> NUTX)
            # The Home Agent Addresses field contains global IP address for HA1.
            # The Home Agent Addresses field contains global IP address for HA0.
        7. Receive Binding Update. (NUTX -> HA1)
        8. Send Binding Acknowledgement. (HA1 -> NUTX)
                    
        Packet Format is:
          6. Home Agent Address Discovery Reply
          7. Binding Update
                    


JUDGEMENT

 (*1) PASS: HA1 receives Binding Update.
            Then, check whether this packet fills all of the following.
             - The destination address is set to HA1 address of Home Agent Address Discovery Reply[6].


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.4.1 Dynamic Home Agent Address Discovery
                    
(snip)
                    
   The mobile node, upon receiving this Home Agent Address Discovery
   Reply message, MAY then send its home registration Binding Update to
   any of the unicast IP addresses listed in the Home Agent Addresses
   field in the Reply.  For example, the mobile node MAY attempt its
   home registration to each of these addresses, in turn, until its
   registration is accepted.  The mobile node sends a Binding Update to
   an address and waits for the matching Binding Acknowledgement, moving
   on to the next address if there is no response.  The mobile node
   MUST, however, wait at least InitialBindackTimeoutFirstReg seconds
   (see Section 13) before sending a Binding Update to the next home
   agent.  In trying each of the returned home agent addresses, the
   mobile node SHOULD try each in the order listed in the Home Agent
   Addresses field in the received Home Agent Address Discovery Reply
   message.