NAME

MN-3-3-1-2-007 - Receiving unexpected BE (Status = 2) from unknown node


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
 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. (NUTX -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTX)


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2      CN0
        |       |       |       |        |
        |       | <--------------------  | 1.Binding Error
        |       |       |       |        | 2.(no reply) (*1)
        |       |       |       |        |
        | ====> | <--------------------- | 3.ICMP Echo Request
        |       |       |       |        |
        | <==== | ---------------------> | 4.Home Test Init (*2)
        |       | ---------------------> | 5.Care-of Test Init (*2)
        |       |       |       |        |
                    
        1. Send Binding Error. (CN0 -> NUTX)
            # The Status field is set to 2(unrecognized MH Type value).
        2. (no reply)
        3. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        4. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
        5. Receive Care-of Test Init. (NUTX -> CN0)
                    
        Packet Format is:
          1.Binding Error
                    


JUDGEMENT

 (*1) PASS: CN0 does not receive the return routability procedure message.
 (*2) PASS: CN0 receives the return routability procedure message.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.3.6 Receiving Binding Error Messages
                    
   When a mobile node receives a packet containing a Binding Error
   message, it should first check if the mobile node has a Binding
   Update List entry for the source of the Binding Error message.  If
   the mobile node does not have such an entry, it MUST ignore the
   message.  This is necessary to prevent a waste of resources on e.g.
   return routability procedure due to spoofed Binding Error messages.