NAME

MN-3-2-1-1-001 - Generate CoA using RFC2462 at foreign-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
    - care-of address create mode : RFC2462
 2. Position of Mobile Node
    - none.


TEST PROCEDURE

                    
       HA0     NUT0     R1      R2      CN0
        |       |       |       |        |
        | ----> |       |       |        | 1.Router Advertisement
        |       |       |       |        | 
        |      NUTX     |       |        |
        |       |       |       |        |
        |       | <---- |       |        | 2.Router Advertisement
        |       |       |       |        |
        |       | ----> |       |        | 3.Neighbor Solicitation(DAD) (*1)
        |       |       |       |        | 4.(no reply)
        |       |       |       |        |
        | <---- |       |       |        | 5.Neighbor Solicitations(NUD)
        |       |       |       |        | 6.(no reply)
        |       |       |       |        |
        | <---- |       |       |        | 7.Binding Update (*2)
        | ----> |       |       |        | 8.Binding Acknowledgement
        |       |       |       |        | 
                    
        1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
        2. Send Router Advertisement. (R1 -> R1_allnode_multi)
        4. Receive Neighbor Solicitation(DAD). (NUTX(Unspecified) -> R1_solinode_multi)
        5. (no reply)
            # Wait during 3 seconds.
        6. Receive Neighbor Solicitations(NUD). (NUT0 -> HA0)
        7. (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:
          5.Neighbor Solicitation(DAD) Data is:
            IPv6 header (source = unspecified address,
                         destination = solicited-node multicast)
            ICMP Neighbor Solicitation
                Type       = 135
                Code       = 0
                Checksum   = (auto)
                Reserved   = 0
                Target Address = link local address
                    
          7.Binding Update
                    


JUDGEMENT

 (*1) PASS: R1 receives Neighbor Solicitation(DAD).
            Then, check whether this packet fills all of the following.
             - The target address is a link local address.
 (*2) PASS: HA0 receives Binding Update.
            Then, check whether this packet fills all of the following.
             - Alternate Care-of Address option is set to a care-of address.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.5.2 Forming New Care-of Addresses
                    
   After detecting that it has moved a mobile node SHOULD generate a new
   primary care-of address using normal IPv6 mechanisms.  This SHOULD
   also be done when the current primary care-of address becomes
   deprecated.  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.
                    
(snip)
                    
   As described in Section 4, in order to form a new care-of address, a
   mobile node MAY use either stateless [13] or stateful (e.g., DHCPv6
   [29]) Address Autoconfiguration.  If a mobile node needs to use a
   source address (other than the unspecified address) in packets sent
   as a part of address autoconfiguration, it MUST use an IPv6
   link-local address rather than its own IPv6 home address.