MN-2-1-1-2-002 - Receiving the packet (including home address destination) by tunneling
Host
|
HAcn CN0 NUTZ
| | |
-----+-------+--------+--------+------- LinkZ
|
R2 CN0Y NUTY
| | |
-----+-------+--------+--------+------- LinkY
|
R1 CN0X NUTX
| | |
-----+-------+-------+--------+--------+------- LinkX
| |
HA1 HA0 Node0 CN00 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 |
CN0 home link |
| HA0(Link0) |
3ffe:501:ffff:100:200:ff:fe00:a0a0 |
|
| HA1(Link0) |
3ffe:501:ffff:100:200:ff:fe00:a1a1 |
|
| 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 |
|
| HAcn(LinkZ) |
3ffe:501:ffff:104:200:ff:fe00:aaaa |
|
1. Selection Option
- Route Optimization support: YES
2. Position of Mobile Node
HA0 NUT0 R1 R2 CN0 HAcn
| | | | | |
| | | | | <---- | 1.Router Advertisement
| | | | | |
| | | | CN0Y |
| | | | | |
| | | | ----> | | 2.Router Advertisement
| | | | | |
| | | | | ----> | 3.Neighbor Solicitations
| | | | | | 4.(no reply:3 seconds)
| | | | | |
| | | | | ----> | 5.Binding Update
| | | | | <---- | 6.Binding Acknowledgement
| | | | | |
1. Send Router Advertisement. (HAcn -> HAcn_allnode_multi)
2. Send Router Advertisement. (R2 -> R2_allnode_multi)
3. Receive Neighbor Solicitations. (CN0 -> HAcn)
4. (no reply)
# Wait during a maximum of 3 seconds(RFC2461).
5. Receive Binding Update to HA0. (CN0Y -> HAcn)
6. Send Binding Acknowledgement. (HAcn -> CN0Y)
HA0 NUT0 R1 R2 CN0Y HAcn
| | | | | |
| ----> | | | | | 1.Router Advertisement
| | | | | |
| | <-------------------- | ====> | 2.Home Test Init
| | <-------------------- | | 3.Care-of Test Init
| | --------------------> | | 4.Care-of Test
| | --------------------> | <==== | 5.Home Test
| | | | | |
| | <-------------------- | | 6.Binding Update
| | --------------------> | | 7.Binding Acknowledgement
| | | | | |
| NUTX | | | |
| | | | | |
| | <---- | | | | 8.Router Advertisement
| | | | | |
| <---- | | | | | 9.Neighbor Solicitations
| | | | | | 10.(no reply:3 seconds)
| | | | | |
| <---- | | | | | 11.Binding Update
| ----> | | | | | 12.Binding Acknowledgement
| | | | | |
| ====> | <-------------------- | | 13.Echo Request
| | | | | |
| <==== | --------------------> | <==== | 14.Home Test Init (*1)
| | | | | |
1. Send Router Advertisement. (HA0 -> HA0_allnode_multi)
2. Send Home Test Init. (CN0 -> NUT0)
3. Send Care-of Test Init. (CN0Y -> NUT0)
4. Receive Care-of Test. (NUT0 -> CN0Y)
5. Receive Home Test. (NUT0 -> CN0)
6. Send Binding Update. (CN0Y -> NUT0)
7. Receive Binding Acknowledgement. (NUT0 -> CN0Y)
8. Send Router Advertisement. (R1 -> R1_allnode_multi)
9. Receive Neighbor Solicitations. (NUT0 -> HA0)
10. (no reply:3 seconds)
# Wait during a maximum of 3 seconds(RFC2461).
11. Receive Binding Update. (NUTX -> HA0)
12. Send Binding Acknowledgement. (HA0 -> NUTX)
13. Send Echo Request. (out: HA0 -> NUTX, in: CN0Y -> NUT0)
# Home Address destination option is included in inner packet.
14. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
Packet Format is:
13.ICMP Echo Request Data is:
IPv6 header (source = home agent,
destination = care-of address)
ESP header
IPv6 header (source = correspondent node(care-of address),
destination = home address)
Destination Options header
Home Address option (correspondent node(home address))
ICMPv6 Echo Request
14.Home Test Init
(*1) PASS: HA0 receives the Home Test Init.
- The Destination Address(inner) is set to the home address of ICMP Echo Request[12].
(draft-ietf-mobileip-ipv6-24.txt)
11.7.2 Correspondent Registration
(snip)
The peer address used in the procedure MUST be determined as follows:
o If a Home Address destination option is present in the original
(inner) packet, the address from this option is used.
o Otherwise, the Source Address in the original (inner) IPv6 header
of the packet is used.
9.3.1 Receiving Packets with Home Address Option
Packets containing a Home Address option MUST be dropped if the given
home address is not a unicast routable address.
Mobile nodes can include a Home Address destination option in a
packet if they believe the correspondent node has a Binding Cache
entry for the home address of a mobile node. Packets containing a
Home Address option MUST be dropped if there is no corresponding
Binding Cache entry. A corresponding Binding Cache entry MUST have
the same home address as appears in the Home Address destination
option, and the currently registered care-of address MUST be equal to
the source address of the packet. These tests MUST NOT be done for
packets that contain a Home Address option and a Binding Update.