NAME

MN-4-2-1-1-001 - Receiving solicited MPA


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
    - none
 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
        |       |       |       |        | 10.(wait) (*1)
        |       |       |       |        |
                    
        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 set to HA address.
            # The Destination Address matches Source Address 
            # in the Mobile Prefix Solicitation[8].
            # The type2 routing header is included.
            # The Identifier field matches the Identifier field 
            # in the Mobile Prefix Solicitation[8].
            # The Prefix Information option is included, and,
            #   - The Router Address(R) flag is set to ON.
            #   - The Valid Lifetime is not changed.
            #   - The Preferred Lifetime is not changed.
        10. (wait)
            # Wait during enough retransmission timer.
                    
        Packet Format is:
          9.Mobile Prefix Advertisement
                    


JUDGEMENT

 (*1) PASS: HA0 does not receive 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.
                    
                    
6.8 ICMP Mobile Prefix Advertisement Message Format
                    
(snip)
                    
   Source Address
                    
      The home agent's address as the mobile node would expect to see it
      (i.e., same network prefix).
                    
   Destination Address
                    
      If this message is a response to a Mobile Prefix Solicitation,
      this field contains the Source Address field from that packet.
      For unsolicited messages, the mobile node's care-of address SHOULD
      be used.  Note that unsolicited messages can only be sent if the
      mobile node is currently registered with the home agent.
                    
   Routing header:
                    
                    
                    
      A type 2 routing header MUST be included.
                    
(snip)
                    
   Identifier
                    
      An identifier to aid in matching this Mobile Prefix Advertisement
      to a previous Mobile Prefix Solicitation.
                    
(snip)
                    
   Reserved
                    
      This field is unused.  It MUST be initialized to zero by the
      sender and MUST be ignored by the receiver.
                    
(snip)
                    
   Prefix Information
                    
      Each message contains one or more Prefix Information options.
      Each option carries the prefix(es) that the mobile node should use
      to configure its home address(es).  Section 10.6 describes which
      prefixes should be advertised to the mobile node.