MN-4-1-1-1-001 - Sending MPS (before the HoA becomes invalid)
Host
|
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 |
|
1. Selection Option
- none.
2. Position of Mobile Node
- none.
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.(wait)
| | | | |
| <---- | | | | 8.Mobile Prefix Solicitation (*1)
| | | | |
1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
# The Prefix Information option is included, and,
# - The Preferred Lifetime field is set to 120 seconds.
# - The Valid Lifetime field is set to 120 seconds.
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. (wait)
# Wait during a maximum of the remaining valid lifetime of the Home Address.
8. Receive Mobile Prefix Solicitation. (NUTX -> HA0)
Packet Format is:
8.Mobile Prefix Solicitation
(*1) PASS: HA0 receives Mobile Prefix Solicitation,
Then, check whether this packet fills all of the following,
- The lifetime of the Home Address does not expire.
- The Source Address is set to Care-of Address.
- The Destination Address is set to HA address.
- The Reserved field is cleared.
- The Home Address destination option is included, and,
- This option is placed as the right location.
(draft-ietf-mobileip-ipv6-24.txt)
11.4.2 Sending Mobile Prefix Solicitations
When a mobile node has a home address that is about to become
invalid, it SHOULD send a Mobile Prefix Solicitation to its home
agent in an attempt to acquire fresh routing prefix information. The
new information also enables the mobile node to participate in
renumbering operations affecting the home network, as described in
Section 10.6.
The mobile node MUST use the Home Address destination option to carry
its home address. The mobile node MUST support and SHOULD use IPsec
to protect the solicitation. The mobile node MUST set the Identifier
field in the ICMP header to a random value.
6.7 ICMP Mobile Prefix Solicitation Message Format
(snip)
Source Address
The mobile node's care-of address.
Destination Address
The address of the mobile node's home agent. This home agent must
be on the link which the mobile node wishes to learn prefix
information about.
(snip)
Destination Option:
A Home Address destination option MUST be included.
(snip)
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
(RFC2462 IPv6 Stateless Address Autoconfiguration)
5.5.3. Router Advertisement Processing
(snip)
d) If the prefix advertised does not match the prefix of an address
already in the list, and the Valid Lifetime is not 0, form an
address (and add it to the list) by combining the advertised
prefix with the link's interface identifier as follows:
| 128 - N bits | N bits |
+---------------------------------------+------------------------+
| link prefix | interface identifier |
+----------------------------------------------------------------+
If the sum of the prefix length and interface identifier length
does not equal 128 bits, the Prefix Information option MUST be
ignored. An implementation MAY wish to log a system management
error in this case. It is the responsibility of the system
administrator to insure that the lengths of prefixes contained in
Router Advertisements are consistent with the length of interface
identifiers for that link type. Note that interface identifiers
will typically be 64-bits long and based on EUI-64 identifiers as
described in [ADDR-ARCH].
If an address is formed successfully, the host adds it to the
list of addresses assigned to the interface, initializing its
preferred and valid lifetime values from the Prefix Information
option.