SendingBUtoHA - MN sends Binding Update when changing primary CoA
Host
SendingBUtoHA.seq [-tooloption ...] -pkt MN_Common.def
-tooloption: v6eval tool option
|
R TN
| |
--------+-------+--------------- LinkZ
|
R2 NUT2
| |
--------+---------------+------- LinkY
| |
HA2 R1 NUT1
| | |
--------+-------+-------+------- LinkX
| |
NUT0 HA1 HA0
| | |
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:a1a1/64 HA1(Link0) 3ffe:501:ffff:100:200:ff:fe00:a2a2/64 HA2(LinkX) 3ffe:501:ffff:102:200:ff:fe00:a3a3 R1(LinkX) 3ffe:501:ffff:102:200:ff:fe00:a4a4 R2(LinkY) 3ffe:501:ffff:103:200:ff:fe00:a5a5 TN(LinkZ) 3ffe:501:ffff:104:200:ff:fe00:a6a6
MN sends Binding Update when changing primary CoA
HA0 NUT1 R1 R2 TN
| | | | |
| | <---- | | | RA
| | | | |
| <---- | | | | Binding Update (*1)
| ----> | | | | Binding Acknowledgement
| | | | |
| | <-------------------- | Echo Request
| | --------------------> | Echo Reply (*2)
| | | | |
| NUT2 | | |
| | | | |
| | <------------ | | RA
| | | | |
| <---- | | | | Binding Update (*3)
| ----> | | | | Binding Acknowledgement
| | | | |
| | <-------------------- | Echo Request
| | --------------------> | Echo Reply (*4)
| | | | |
(*1) PASS: TN receives Binding Update
(*2) PASS: TN receives Echo Reply
(*3) PASS: TN receives Binding Update
(*4) PASS: TN receives Echo Reply
draft-ietf-mobileip-ipv6-20.txt
11.5.4 Returning Home
After deciding to change its primary care-of address as described in Section 11.5.1 and Section 11.5.2, a mobile node MUST register this care-of address with its home agent in order to make this its primary care-of address. Also, if the mobile node wants the services of the home agent beyond the current registration period, the mobile node MUST send a new Binding Update to it well before the expiration of this period, even if it is not changing its primary care-of address.
In both of these situations, the mobile node sends a packet to its home agent containing a Binding Update, with the packet constructed as follows:
o The Home Registration (H) bit MUST be set in the Binding Update.
o The Acknowledge (A) bit MUST be set in the Binding Update.
o The packet MUST contain a Home Address destination option, giving
the mobile node's home address for the binding.
o The care-of address for the binding MUST be used as the Source
Address in the packet's IPv6 header, unless an Alternate Care-of
Address mobility option is included in the Binding Update. This
option SHOULD be included in all home registrations, as the ESP
protocol will not be able to protect care-of addresses in the IPv6
header. (Mobile IPv6 implementations that know they are using
IPsec AH to protect a particular message might avoid this option.
For brevity the usage of AH is not discussed in this document.)
o If the mobile node's link-local address has the same interface
identifier as the home address for which it is supplying a new
care-of address, then the mobile node SHOULD set the Link-Local
Address Compatibility (L) bit.
o If the home address was generated using RFC 3041 [18], then the
link local address is unlikely to have a compatible interface
identifier. In this case, the mobile node MUST clear the
Link-Local Address Compatibility (L) bit.
o If the IPsec security associations between the mobile node and the
home agent have been established dynamically, and the mobile node
has the capability to update its endpoint in the used key
management protocol to the new care-of address every time it
moves, the mobile node SHOULD set the Key Management Mobility
Capability (K) bit in the Binding Update. Otherwise, the mobile
node MUST clear the bit.
o The value specified in the Lifetime field SHOULD be less than or
equal to the remaining lifetime of the home address and the
care-of address specified for the binding.