NAME

MN-2-1-2-2-009 - Sending CoTI for each CN in BUL (after home re-registration)


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
        |       |       |       |        |
        | ====> | <--------------------- |  7.ICMP Echo Request
        |       |       |       |        |
        | <==== | ---------------------> |  8.Home Test Init
        |       | ---------------------> |  9.Care-of Test Init
        |       | <--------------------- | 10.Care-of Test
        | ====> | <--------------------- | 11.Home Test
        |       |       |       |        |
        | <==== | ---------------------> | 12.ICMP Echo Reply
        |       | ---------------------> | 13.Binding Update
        |       | ---------------------> | 14.ICMP Echo Reply
        |       |       |       |        |
                    
        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. (NUTX -> HA0)
        7. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
        8. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
        9. Receive Care-of Test Init. (NUTX -> CN0)
       10. Send Care-of Test. (CN0 -> NUTX)
       11. Send Home Test. (out: HA0 -> NUTX, in: CN0 -> NUT0)
       12. Receive ICMP Echo Reply or [14]. (out: NUTX -> HA0, in: NUT0 -> CN0)
       13. Receive Binding Update to CN0. (NUTX -> CN0)
       14. [12] or Receive ICMP Echo Reply. (NUTX -> CN0)
            # Home Address destination option is included.


TEST PROCEDURE

                    
       HA0     NUTX     R1      R2      CN0
        |       |       |       |        |
        |       | <---- |       |        |  1.Router Advertisement
        |       |       |       |        |
        |      NUTY     |       |        |
        |       |       |       |        |
        |       | <------------ |        |  2.Router Advertisement
        |       |       |       |        |
        |       | ----> |       |        |  3.Neighbor Solicitations
        |       |       |       |        |  4.(no reply)
        |       |       |       |        |
        | <---- |       |       |        |  5.Binding Update
        | ----> |       |       |        |  6.Binding Acknowledgement
        |       |       |       |        |
        | <==== | ---------------------> |  7.Home Test Init
        |       | ---------------------> |  8.Care-of Test Init (*1)
        |       |       |       |        |
                    
        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 to HA0. (NUTY -> HA0)
        6. Send Binding Acknowledgement. (HA0 -> NUTY)
        7. Receive Home Test Init. (out: NUTY -> HA0, in: NUT0 -> CN0)
        8. Receive Care-of Test Init. (NUTY -> CN0)
                    
        Packet Format is:
          8.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.
                    
                    
5.2.7 Updating Node Keys and Nonces
                    
(snip)
                    
   Given that the tokens are normally expected to be usable for
   MAX_TOKEN_LIFETIME seconds, the mobile node MAY use them beyond a
   single run of the return routability procedure until
   MAX_TOKEN_LIFETIME expires.  After this the mobile node SHOULD NOT
   use the tokens.  A fast moving mobile node MAY reuse a recent home
   keygen token from a correspondent node when moving to a new location,
   and just acquire a new care-of keygen token to show routability in
   the new location.