NAME

MN-2-1-2-2-017 - Sending CoTI (when the lifetime for a changed prefix decreases)


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


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2      CN0
        |       |       |       |        |
        | ====> | <--------------------- |  1.ICMP Echo Request
        |       |       |       |        |
        | <==== | ---------------------> |  2.Home Test Init
        |       | ---------------------> |  3.Care-of Test Init
        |       | <--------------------- |  4.Care-of Test
        | ====> | <--------------------- |  5.Home Test
        |       |       |       |        |
        | <==== | ---------------------> |  6.ICMP Echo Reply
        |       | ---------------------> |  7.Binding Update
        |       | ---------------------> |  8.ICMP Echo Reply
        |       |       |       |        |
        | ----> |       |       |        |  9.Mobile Prefix Advertisement
        | <---- |       |       |        | 10.Mobile Prefix Solicitations
        | ----> |       |       |        | 11.Mobile Prefix Advertisement
        |       |       |       |        |
        | <---- |       |       |        | 12.Binding Update
        | ----> |       |       |        | 13.Binding Acknowledgement
        |       |       |       |        |
        | <==== | ---------------------> | 14.Home Test Init
        |       | ---------------------> | 15.Care-of Test Init (*1)
        |       |       |       |        |
                    
        1. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        2. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
        3. Receive Care-of Test Init. (NUTX -> CN0)
        4. Send Care-of Test. (CN0 -> NUTX)
        5. Send Home Test. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        6. Receive ICMP Echo Reply or [8]. (out: NUTX -> HA0, in: NUT0 -> CN0)
        7. Receive Binding Update to CN0. (NUTX -> CN0)
        8. [6] or Receive ICMP Echo Reply. (NUTX -> CN0)
            # Home Address destination option is included.
        9. Send Mobile Prefix Advertisement. (HA0 -> NUTX)
            # Type2 routing header is included.
            # The Identifier is unsolicited.
       10. Receive Mobile Prefix Solicitations. (NUTX -> HA0)
            # Home Address destination option is included.
       11. Send Mobile Prefix Advertisement. (HA0 -> NUTX)
            # Type2 routing header is included.
            # The Identifier is set to the Identifier value from the Mobile Prefix Solicitation [10].
            # The Valid Lifetime and Preferred Lifetime is set to less than Binding Lifetime.
       12. Receive Binding Update to HA0. (NUTX -> HA0)
       13. Send Binding Acknowledgement. (HA0 -> NUTX)
       14. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
       15. Receive Care-of Test Init. (NUTX -> CN0)
                    
        Packet Format is:
          11. Mobile Prefix Advertisement
          15.Care-of Test Init
                    


JUDGEMENT

 (*1) PASS: CN0 receives 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)
                    
   After the mobile node has sent a Binding Update to its home agent to
   register a new primary care-of address (as described in Section
   11.7.1), the mobile node SHOULD initiate a correspondent registration
   for each node that already appears in the mobile node's Binding
   Update List.  The initiated procedures can be used to either update
   or delete binding information in the correspondent node.
                    
                    
11.4.2 Sending Mobile Prefix Solicitations
                    
   When the lifetime for a changed prefix decreases, and the change
   would cause cached bindings at correspondent nodes in the Binding
   Update List to be stored past the newly shortened lifetime, the
   mobile node MUST issue a Binding Update to all such correspondent
   nodes.