NAME

MN-3-1-2-2-002 - Valid BU of re-registration (src address == CoA or Alternate CoA option == CoA)


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.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
        |       | <--------------------- | 16.Care-of Test
        | ====> | <--------------------- | 17.Home Test
        |       |       |       |        |
        |       | ---------------------> | 18.Binding Update (*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 reverse tunneled 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)
        9. Send unsolicited Mobile Prefix Advertisement. (HA0 -> NUTX)
       10. Receive Mobile Prefix Solicitations. (NUTX -> HA0)
       11. Send solicited Mobile Prefix Advertisement. (HA0 -> NUTX)
       12. Receive Binding Update. (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)
       16. Send Care-of Test. (CN0 -> NUTX)
       17. Send Home Test. (out: HA0 -> NUTX, in: CN0 -> NUT0)
       18. Receive Binding Update to CN0. (NUTX -> CN0)
                    
        Packet Format is:
          11. Mobile Prefix Advertisement
          18.Binding Update
                    


JUDGEMENT

 (*1) PASS: CN0 receives Binding Update.
            Then, check whether this packet fills all of the following.
             - Either the Source Address or the Alternate Care-of Address 
               mobility option is set to the care-of address.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.7.2 Correspondent Registration
                    
(snip)
                    
   In any Binding Update sent by a mobile node, the care-of address
   (either the Source Address in the packet's IPv6 header or the Care-of
   Address in the Alternate Care-of Address mobility option of the
   Binding Update) MUST be set to one of the care-of addresses currently
   in use by the mobile node or to the mobile node's home address.  A
   mobile node MAY set the care-of address differently for sending
   Binding Updates to different correspondent nodes.
                    
(snip)
                    
   A Binding Update is created as follows:
                    
   o  The current care-of address of the mobile node MUST be sent either
      in the Source Address of the IPv6 header or in the Alternate
      Care-of Address mobility option.
                    
                    
5.2.6 Authorizing Binding Management Messages
                    
(snip)
                    
   The value in the Source Address field in the IPv6 header carrying the
   Binding Update is normally also the care-of address which is used in
   the binding.  However, a different care-of address MAY be specified
   by including an Alternate Care-of Address mobility option in the
   Binding Update (see Section 6.2.5).  When such a message is sent to
   the correspondent node and the return routability procedure is used
   as the authorization method, the Care-of Test Init and Care-of Test
   messages MUST have been performed for the address in the Alternate
   Care-of Address option (not the Source Address).  The nonce indices
   and MAC value MUST be based on information gained in this test.