NAME

MN-2-1-1-2-015 - Check not to support the Route Optimization


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: NO
                    
 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.ICMP Echo Reply (*1)
        |       |       |       |        |
                    
        1. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        2. Receive ICMP Echo Reply. (out: NUTX -> HA0 in: NUT0 -> CN0)
                    
        Packet Format is:
          1.ICMP Echo Request Data is:
            IPv6 header (source = home agent,
                         destination = care-of address)
            ESP header
            IPv6 header (source = correspondent node,
                         destination = home address)
            ICMPv6 Echo Request
                    
          2.ICMP Echo Reply Data is:
            IPv6 header (source = care-of address,
                         destination = home agent)
            ESP header
            IPv6 header (source = home address,
                         destination = correspondent node)
            ICMPv6 Echo Reply
                    


JUDGEMENT

 (*1) PASS: HA0 receives the ICMP Echo Reply by reverse tunneling.
 (*1) PASS: HA0 does not receive the Home Test Init and CN0 does not receive the Care-of Test Init.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.6 Return Routability Procedure
                    
   This section defines the rules that the mobile node must follow when
   performing the return routability procedure.  Section 11.7.2
   describes the rules when the return routability procedure needs to be
   initiated.
                    
                    
11.7.2 Correspondent Registration
                    
(snip)
                    
   A mobile node MAY also choose to keep its topological location
   private from certain correspondent nodes, and thus need not initiate
   the correspondent registration.
                    
                    
8.5 IPv6 Mobile Nodes
                    
(snip)
                    
   o  The node MUST allow route optimization to be administratively
      enabled or disabled.  The default SHOULD be enabled.