NAME

MN-4-2-1-1-012 - Receiving solicited MPA from unknown HA


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
    - Mobile Prefix Solicitation retransmit : YES
 2. Position of Mobile Node
    - none


TEST PROCEDURE

       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
        |       |       |       |        |
        | ----> |       |       |        | 7.Mobile Prefix Advertisement
        |       |       |       |        |
        | <---- |       |       |        | 8.Mobile Prefix Solicitetion
        | ----> |       |       |        | 9.Mobile Prefix Advertisement(*1)
        |       |       |       |        |
        | <---- |       |       |        | 10.Mobile Prefix Solicitetion
        |       |       |       |        |
                    
        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. (NUTX -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTX)
        7. Send unsolicited Mobile Prefix Advertisement. (HA0 -> NUTX)
            # The Identifier field is set to the random value.
        8. Receive Mobile Prefix Solicitation. (NUTX -> HA0)
        9. Send Mobile Prefix Advertisement. (HA0 -> NUTX)
            # The Source Address is not set to HA address.
       10. Receive Mobile Prefix Solicitation. (NUTX -> HA0)
                    
        Packet Format is:
          9.Mobile Prefix Advertisement
                    


JUDGEMENT

 (*1) PASS: HA0 receives the retransmitting of Mobile Prefix Solicitation message.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.4.3. Receiving Mobile Prefix Advertisements
                    
(snip)
                    
   When a mobile node receives a Mobile Prefix Advertisement, it MUST
   validate it according to the following test:
                    
   o  The Source Address of the IP packet carrying the Mobile Prefix
      Advertisement is the same as the home agent address to which the
      mobile node last sent an accepted home registration Binding Update
      to register its primary care-of address.  Otherwise, if no such
      registrations have been made, it SHOULD be the mobile node's
      stored home agent address, if one exists.  Otherwise, if the
      mobile node has not yet discovered its home agent's address, it
      MUST NOT accept Mobile Prefix Advertisements.
                    
   o  The packet MUST have a type 2 routing header and SHOULD be
      protected by an IPsec header as described in Section 5.4 and
      Section 6.8.
                    
   o  If the ICMP Identifier value matches the ICMP Identifier value of
      the most recently sent Mobile Prefix Solicitation and no other
      advertisement has yet been received for this value, then the
      advertisement is considered to be solicited and will be processed
      further.
                    
      Otherwise, the advertisement is unsolicited, and MUST be silently
      discarded.  In this case the mobile node SHOULD send a Mobile
      Prefix Solicitation.
                    
   Any received Mobile Prefix Advertisement not meeting these tests MUST
   be silently discarded.