NAME

MN-2-1-2-1-005 - Sending BU (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
    - none
 2. Position of Mobile Node
    - none


TEST PROCEDURE

                    
       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.Mobile Prefix Advertisement
        | <---- |       |       |        | 8.Mobile Prefix Solicitation
        | ----> |       |       |        | 9.Mobile Prefix Advertisement
        |       |       |       |        |
        | <---- |       |       |        | 10.Binding Update(*1)
        |       |       |       |        |
                    
        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)
        7. Send unsolicited Mobile Prefix Advertisement. (HA0 -> NUTX)
            # - The Valid Lifetime is set less than the remaining lifetime of 
            #   the home registration.
            # - The Preferred Lifetime is set less than the remaining lifetime of 
            #   the home registration.
        8. Receive Mobile Prefix Solicitation. (NUTX -> HA0)
        9. Send Mobile Prefix Advertisement. (HA0 -> NUTX)
            # - The Valid Lifetime is set less than the remaining lifetime of 
            #   the home registration.
            # - The Preferred Lifetime is set less than the remaining lifetime of 
            #   the home registration.
       10. Receive Binding Update. (NUTX -> HA0)
                    
        Packet Format is:
          9. Mobile Prefix Advertisement
          10. Binding Update
                    
                    


JUDGEMENT

 (*1) PASS: HA0 receives Binding Update message,
            Then, check whether this packet fills all of the following,
             - The Sequence Number field is set more than the Sequence Number 
               in the previous Binding Update[5].
             - The Lifetime field is set less than Valid Lifetime 
               in Mobile Prefix Advertisement[9].
             - The Alternate Care-of Address mobility option is included, and,
                - The Care-of Aaddress fiels is set to the care-of address.


REFERENCE

                    
(draft-ietf-mobileip-ipv6-24.txt)
                    
11.7.1 Sending Binding Updates to the Home Agent
                    
(snip)
                    
   o  The value specified in the Lifetime field SHOULD be less than or
      equal to the remaining valid lifetime of the home address and the
      care-of address specified for the binding.
                    
                    
11.4.2 Sending Mobile Prefix Solicitations
                    
(snip)
                    
   As described in Section 11.7.2, Binding Updates sent by the mobile
   node to other nodes MUST use a lifetime no greater than the remaining
   lifetime of its home registration of its primary care-of address.
   The mobile node SHOULD further limit the lifetimes that it sends on
   any Binding Updates to be within the remaining valid lifetime (see
   Section 10.6.2) for the prefix in its home address.
                    
   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.
                    
   These limits on the binding lifetime serve to prohibit use of a
   mobile node's home address after it becomes invalid.