NAME

MN-2-1-1-2-003 - Don't start the return routability procedure (when receiving the tunneled CoTI)


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
    - Route Optimization support: YES
                    
 2. Position of Mobile Node
                    
       HA0     NUT0     R1      R2     CN0     HAcn0
        |       |       |       |       |       |
        |       |       |       |       | <---- |  1.Router Advertisement
        |       |       |       |       |       |
        |       |       |       |      CN0Y     |
        |       |       |       |       |       |
        |       |       |       | ----> |       |  2.Router Advertisement
        |       |       |       |       |       |
        |       |       |       |       | ----> |  3.Neighbor Solicitations
        |       |       |       |       |       |  4.(no reply:3 seconds)
        |       |       |       |       |       |
        |       |       |       |       | ----> |  5.Binding Update
        |       |       |       |       | <---- |  6.Binding Acknowledgement
        |       |       |       |       |       |
        |       |       |       |       |       |
        | ----> |       |       |       |       |  7.Router Advertisement
        |       |       |       |       |       |
        |      NUTX     |       |       |       |
        |       |       |       |       |       |
        |       | <---- |       |       |       |  8.Router Advertisement
        |       |       |       |       |       |
        | <---- |       |       |       |       |  9.Neighbor Solicitations
        |       |       |       |       |       | 10.(no reply:3 seconds)
        |       |       |       |       |       |
        | <---- |       |       |       |       | 11.Binding Update
        | ----> |       |       |       |       | 12.Binding Acknowledgement
        |       |       |       |       |       |
                    
        1. Send Router Advertisement. (HAcn -> HAcn_allnode_multi)
        2. Send Router Advertisement. (R2 -> R2_allnode_multi)
        3. Receive Neighbor Solicitations. (CN0 -> HAcn)
        4. (no reply)
            # Wait during a maximum of 3 seconds(RFC2461).
        5. Receive Binding Update to HA0. (CN0Y -> HAcn)
        6. Send Binding Acknowledgement. (HAcn -> CN0Y)
        7. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
        8. Send Router Advertisement. (R1 -> R1_allnode_multi)
        9. Receive Neighbor Solicitations. (NUT0 -> HA0)
       10. (no reply)
            # Wait during a maximum of 3 seconds(RFC2461).
       11. Receive Binding Update to HA0. (NUTX -> HA0)
       12. Send Binding Acknowledgement. (HA0 -> NUTX)


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2     CN0Y    HAcn
        |       |       |       |       |       |
        | ====> | <-------------------- |       |  1.Care-of Test Init
        | <==== | --------------------> |       |  2.Care-of Test
        |       |       |       |       |       |  3.(wait) (*1)
        |       |       |       |       |       |
                    
        1. Send Care-of Test Init. (out: HA0 -> NUTX, in: CN0Y -> NUT0)
        2. Receive Care-of Test. (out: NUTX -> HA0, in: NUT0 -> CN0Y)
        3. (wait)
            # Wait during a maximum of 3 seconds(RFC2461).
                    
        Packet Format is:
                    
          1.Care-of Test Init Data is:
            IPv6 header (source = home agent,
                         destination = care-of address)
            ESP header
            IPv6 header (source = correspondent node(care-of address),
                         destination = home address)
            Mobility header
              Care-of Test Init
                    
          2.Care-of Test Data is:
            IPv6 header (source = care-of address,
                         destination = home agent)
            ESP header
            IPv6 header (source = home address,
                         destination = correspondent node(care-of address))
            Mobility header
              Care-of Test
                    


JUDGEMENT

 (*1) PASS: CN0Y does not receive the Home Test Init and the Care-of Test Init.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.7.2 Correspondent Registration
                    
   (snip)
                    
   In addition, the mobile node MAY initiate the procedure in response
   to receiving a packet that meets all of the following tests:
                    
   o  The packet was tunneled using IPv6 encapsulation.
                    
   o  The Destination Address in the tunnel (outer) IPv6 header is equal
      to any of the mobile node's care-of addresses.
                    
   o  The Destination Address in the original (inner) IPv6 header is
      equal to one of the mobile node's home addresses.
                    
   o  The Source Address in the tunnel (outer) IPv6 header differs from
      the Source Address in the original (inner) IPv6 header.
                    
   o  The packet does not contain a Home Test, Home Test Init, Care-of
      Test, or Care-of Test Init message.