MN-2-1-1-2-006 - Don't start the return routability procedure (when receiving the packet directly from known node)
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
- Route Optimization support: YES
2. Position of Mobile Node
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
| | | | |
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 to HA0. (NUTX -> HA0)
6. Send Binding Acknowledgement. (HA0 -> NUTX)
HA0 NUTX R1 R2 CN0
| | | | |
| ====> | <--------------------- | 1.ICMP Echo Request
| | | | |
| <==== | ---------------------> | 2.Home Test Init
| | ---------------------> | 3.Care-of Test Init
| | <--------------------- | 4.Care-of Test
| ====> | <--------------------- | 5.Home Test
| | | | |
| <==== | ---------------------> | 6.ICMP Echo Reply
| | ---------------------> | 7.Binding Update
| | ---------------------> | 8.ICMP Echo Reply
| | | | |
| | <--------------------- | 9.ICMP Echo Request
| | ---------------------> | 10.ICMP Echo Reply (*1)
| | | | |
1. Send ICMP Echo Request. (out: HA0 -> NUTX, in: CN0 -> NUT0)
2. Receive Home Test Init. (out: NUTX -> HA0, in: NUT0 -> CN0)
3. Receive Care-of Test Init. (NUTX -> CN0)
4. Send Care-of Test. (CN0 -> NUTX)
5. Send Home Test. (out: HA0 -> NUTX, in: CN0 -> NUT0)
6. Receive ICMP Echo Reply or [8]. (out: NUTX -> HA0, in: NUT0 -> CN0)
7. Receive Binding Update to CN0. (NUTX -> CN0)
8. [6] or Receive ICMP Echo Reply. (NUTX -> CN0)
# Home Address destination option is included.
9. Send ICMP Echo Request. (CN0 -> NUTX)
# Type 2 routing header is included.
10. Receive ICMP Echo Reply. (NUTX -> CN0).
# Home Address destination option is included.
Packet Format is:
9.ICMP Echo Request Data is:
IPv6 header (source = correspomdent node,
destination = care-of address)
Routing header (type 2)
home address
ICMPv6 Echo Request
10.ICMP Echo Reply Data is:
IPv6 header (source = care-of address,
destination = correspomdent node)
Destination Options header
Home Address option (home address)
ICMPv6 Echo Reply
(*1) PASS: CN0 receives the ICMP Echo Reply by Route Optimization.
(*1) PASS: HA0 does not receive the Home Test Init and CN0 does not receive the Care-of Test Init.
(draft-ietf-mobileip-ipv6-24.txt)
11.6 Return Routability Procedure
This section defines the rules that the mobile node must follow when
performing the return routability procedure. Section 11.7.2
describes the rules when the return routability procedure needs to be
initiated.
11.7.2 Correspondent Registration
(snip)
For nodes that do not appear in the mobile node's Binding Update
List, the mobile node MAY initiate a correspondent registration at
any time after sending the Binding Update to its home agent.
Considerations regarding when (and if) to initiate the procedure
depend on the specific movement and traffic patterns of the mobile
node and are outside the scope of this document.
In addition, the mobile node MAY initiate the procedure in response
to receiving a packet that meets all of the following tests:
o The packet was tunneled using IPv6 encapsulation.
11.3.1 Sending Packets While Away from Home
(snip)
Route Optimization
This manner of delivering packets does not require going through
the home network, and typically will enable faster and more
reliable transmission.
The mobile node needs to ensure that there exists a Binding Cache
entry for its home address so that the correspondent node can
process the packet (Section 9.3.1 specifies the rules for Home
Address Destination Option Processing at a correspondent node).
The mobile node SHOULD examine its Binding Update List for an
entry which fulfills the following conditions: