NAME

MN-2-2-1-1-017 - Invalid Sequence Number (BA != BU)


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


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2      CN0
        |       |       |       |        |
        |       | <---- |       |        | 1.Router Advertisement
        |       |       |       |        |
        |      NUTY     |       |        |
        |       |       |       |        |
        |       | <------------ |        | 2.Router Advertisement
        |       |       |       |        |
        |       | ----> |       |        | 3.Neighbor Solicitations
        |       |       |       |        | 4.(no reply:3 seconds)
        |       |       |       |        |
        | <---- |       |       |        | 5.Binding Update
        | ----> |       |       |        | 6.Binding Acknowledgement(*1)
        |       |       |       |        |
        | <---- |       |       |        | 7.Binding Update
        |       |       |       |        |
                    
        1. Send Router Advertisement. (R1 -> R1_allnode_multi)
        2. Send Router Advertisement. (R2 -> R2_allnode_multi)
        3. Receive Neighbor Solicitations. (NUTX -> R1)
        4. (no reply)
            # Wait during a maximum of 3 seconds(RFC2461).
        5. Receive Binding Update. (NUTY -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTY)
            # The Sequence Number field does not match the Sequence Number sent by BU[5].
        7. Receive Binding Update. (NUTY -> HA0)
                    
        Packet Format is:
          6. Binding Acknowledgement
                    


JUDGEMENT

 (*1) PASS: HA0 receives the retransmission of Binding Update.
            Then, check whether this packet fills all of the following,
            - Sequence Number value greater than that used.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.7.3 Receiving Binding Acknowledgements
                    
   Upon receiving a packet carrying a Binding Acknowledgement, a mobile
   node MUST validate the packet according to the following tests:
                    
   o  The packet meets the authentication requirements for Binding
      Acknowledgements, defined in Section 6.1.8 and Section 5.  That
      is, if the Binding Update was sent to the home agent, underlying
      IPsec protection is used.  If the Binding Update was sent to the
      correspondent node, the Binding Authorization Data mobility option
      MUST be present and have a valid value.
                    
   o  The Binding Authorization Data mobility option, if present, MUST
      be the last option and MUST not have trailing padding.
                    
   o  The Sequence Number field matches the Sequence Number sent by the
      mobile node to this destination address in an outstanding Binding
      Update.
                    
   Any Binding Acknowledgement not satisfying all of these tests MUST be
   silently ignored.