HA_2_1_3 - Decrease Lifetime
Router
NUT
|
--------+-------+-------+------- Link0
| |
R0 MN0
|
--------+-------+------- Link0X
|
MN0X
Link0 global 3ffe:501:ffff:100::/64 home link Link0X global 3ffe:501:ffff:1100::/64 foreign link R0 (Link0) global 3ffe:501:ffff:100::a0a0 ether 00:00:00:00:a0:a0 MN0 global 3ffe:501:ffff:100:200:ff:fe00:a2a2 home address MN0X global 3ffe:501:ffff:1100:200:ff:fe00:a2a2 care-of address
Check Link0 routing tableNUT (Link0) MN0X | | | <---- | Echo Request | ----> | Echo Reply | |
1. MN0X sends Echo Request 2. MN0X receives Echo Reply
home registrationNUT (Link0) MN0X | | | <---- | BU (SN=1, A=1, lifetime=0x0010) (SPI=0x101) | ----> | BA (SN=1, lifetime=X) (SPI=0x102) | | | <---- | Echo Request w/ HaO | ----> | Echo Reply w/ RH | |
1. MN0X sends BU 2. MN0X receives BA 3. MN0X sends Echo Request w/ HaO 4. MN0X receives Echo Reply w/ RH
BU Lifetime vs. BA LifetimeNUT (Link0) MN0X | | | <---- | BU (SN=2, A=1, lifetime=X/2) (SPI=0x101) | ----> | BA (SN=2, lifetime=Y) (SPI=0x102) (*1) | |
1. MN0X sends BU packet format is: Binding_Update_message_format_from_MN_to_HA_ESP.gif 2. MN0X receives BA (*1) packet format is: Binding_Acknowledgement_message_format_from_HA_toMN_ESP.gifCheck BCENUT (Link0) MN0X | | | <---- | Echo Request w/ HaO | ----> | Echo Reply w/ RH (*2) | |
1. MN0X sends Echo Request w/ HaO 2. MN0X receives Echo Reply w/ RH (*2)
BU Lifetime vs. BA Refresh IntervalNUT (Link0) MN0X | | | <---- | BU (SN=3, A=1, lifetime=Y/2) (SPI=0x101) | ----> | BA (SN=3) (SPI=0x102) (*3) | |
1. MN0X sends BU packet format is: Binding_Update_message_format_from_MN_to_HA_ESP.gif 2. MN0X receives BA (*3) packet format is: Binding_Acknowledgement_message_format_from_HA_toMN_ESP.gifCheck BCENUT (Link0) MN0X | | | <---- | Echo Request w/ HaO | ----> | Echo Reply w/ RH (*4) | |
1. MN0X sends Echo Request w/ HaO 2. MN0X receives Echo Reply w/ RH (*4)
(*1) PASS: MN0X receives BA (*2) PASS: MN0X receives Echo Reply w/ RH (*3) PASS: MN0X receives BA (*4) PASS: MN0X receives Echo Reply w/ RH
The lifetime of the Binding Cache entry depends on a number of factors:o The lifetime for the Binding Cache entry MUST NOT be greater than the Lifetime value specified in the Binding Update.o The lifetime for the Binding Cache entry MUST NOT be greater than the remaining valid lifetime for the subnet prefix in the mobile node's home address specified with the Binding Update. The remaining valid lifetime for this prefix is determined by the home agent based on its own Prefix List entry for this prefix [12].The remaining preferred lifetime SHOULD NOT have any impact on the lifetime for the binding cache entry.The home agent MUST remove a binding when the valid lifetime of the prefix associated with it expires.o The home agent MAY further decrease the specified lifetime for the binding, for example based on a local policy. The resulting lifetime is stored by the home agent in the Binding Cache entry, and this Binding Cache entry MUST be deleted by the home agent after the expiration of this lifetime.(snip)If the Binding Refresh Advice mobility option is present, the Refresh Interval field in the option MUST be set to a value less than the Lifetime value being returned in the Binding Acknowledgement. This indicates that the mobile node SHOULD attempt to refresh its home registration at the indicated shorter interval. The home agent MUST still retain the registration for the Lifetime period, even if the mobile node does not refresh its registration within the Refresh period.