NAME

MN-2-1-4-2-004 - Invalid inner src address


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
    - Route Optimization support: YES
    - Care-of Test Init Retransmissions: YES
                    
 2. Position of Mobile Node
                    
       HA0     NUT0     R1      R2      CN0
        |       |       |       |        |
        | ----> |       |       |        |  1.Router Advertisement
        |       |       |       |        |
        |      NUTX     |       |        |
        |       |       |       |        |
        |       | <---- |       |        |  2.Router Advertisement
        |       |       |       |        |
        | <---- |       |       |        |  3.Neighbor Solicitations
        |       |       |       |        |  4.(no reply:3 seconds)
        |       |       |       |        |
        | <---- |       |       |        |  5.Binding Update
        | ----> |       |       |        |  6.Binding Acknowledgement
        |       |       |       |        |
                    
        1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
        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 Binding Update to HA0. (NUTX -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTX)


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2      CN0
        |       |       |       |        |
        | ====> | <--------------------- |  1.ICMP Echo Request
        |       |       |       |        |
        | <==== | ---------------------> |  2.Home Test Init
        |       | ---------------------> |  3.Care-of Test Init
        |       | <--------------------- |  4.Care-of Test
        | ====> | <--------------------- |  5.Home Test
        |       |       |       |        |
        | <==== | ---------------------> |  6.ICMP Echo Reply
        |       |       |       |        |
        |       | ---------------------> |  7.Care-of Test Init (*1)
        |       | <--------------------- |  8.Care-of Test
        |       |       |       |        |
        |       | ---------------------> |  9.Binding Update (*2)
        |       | ---------------------> | 10.ICMP Echo Reply
        |       |       |       |        |
                    
        1. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        2. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
        3. Receive Care-of Test Init. (NUTX -> CN0)
        4. Send Care-of Test. (CN0 -> NUTX)
            # CN0 source address is wrong.
        5. Send Home Test. (out: HA0 -> NUTX, in: CN1 -> NUT0)
        6. Receive ICMP Echo Reply or [10]. (out: NUTX -> HA0, in: NUT0 -> CN0)
        7. Receive Care-of Test Init. (NUTX -> CN0)
        8. Send Care-of Test. (CN0 -> NUTX)
        9. Receive Binding Update to CN0. (NUTX -> CN0)
       10. [6] or Receive ICMP Echo Reply. (NUTX -> CN0)
            # Home Address destination option is included.
                    
        Packet Format is:
          4.Care-of Test
          9.Binding Update
                    


JUDGEMENT

 (*1) PASS: CN0 receives the retransmisson of Care-of Test Init.
 (*2) PASS: CN0 receives the Binding Upadate.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.6.2 Receiving Test Messages
                    
(snip)
                    
   Upon receiving a packet carrying a Care-of Test message, a mobile
   node MUST validate the packet according to the following tests:
                    
   o  The Source Address of the packet belongs to a correspondent node
      for which the mobile node has a Binding Update List entry with a
      state indicating that return routability procedure is in progress.
      Note that there may be multiple such entries.
                    
   o  The Binding Update List indicates that no care-of keygen token has
      been received yet.
                    
   o  The Destination Address of the packet is the current care-of
      address of the mobile node.
                    
   o  The Care-of Init Cookie field in the message matches the value
      stored in the Binding Update List.
                    
   Any Care-of Test message not satisfying all of these tests MUST be
   silently ignored.  Otherwise, the mobile node MUST record the Care-of
   Nonce Index and care-of keygen token in the Binding Update List.  If
   the Binding Update List entry does not have a home keygen token, the
   mobile node SHOULD continue waiting for the Home Test message.
                    
                    
11.8 Retransmissions and Rate Limiting
                    
(snip)
                    
   If the mobile node fails to receive a valid, matching response within
   the selected initial retransmission interval, the mobile node SHOULD
   retransmit the message, until a response is received.