NAME

MN-5-1-1-1-001 - Sending HAAD-Request at home-link


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
    - Sending HAAD : home link
 2. Position of Mobile Node
    - none.


TEST PROCEDURE

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


JUDGEMENT

 (*1) PASS: HA0 receives Home Agent Address Discovery Request.
            Then, check whether this packet fills all of the following.
             - The destination address is set to a home Agents anycast address.
             - The reserved field is cleared.
 (*2) PASS: HA0 receives Binding Update.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.4.1 Dynamic Home Agent Address Discovery
                    
   Sometimes, when the mobile node needs to send a Binding Update to its
   home agent to register its new primary care-of address, as described
   in Section 11.7.1, the mobile node may not know the address of any
   router on its home link that can serve as a home agent for it.  For
   example, some nodes on its home link may have been reconfigured while
   the mobile node has been away from home, such that the router that
   was operating as the mobile node's home agent has been replaced by a
   different router serving this role.
                    
   In this case, the mobile node MAY attempt to discover the address of
   a suitable home agent on its home link.  To do so, the mobile node
   sends an ICMP Home Agent Address Discovery Request message to the
   Mobile IPv6 Home-Agents anycast address [16] for its home subnet
   prefix.  As described in Section 10.5, the home agent on its home
   link that receives this Request message will return an ICMP Home
   Agent Address Discovery Reply message.  This message gives the
   addresses for the home agents operating on the home link.
                    
   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.