MN-3-2-1-2-023 - Unrecognized mobility option (Binding Refresh Advice option)
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
- CN registration Acknowledge bit : ON
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. (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.Binding Acknowledgement
| | ---------------------> | 9.ICMP Echo Reply
| | | | |
| | <--------------------- | 10.ICMP Echo Request
| | ---------------------> | 11.ICMP Echo Reply
| | | | |
| | | | | 12.(wait) (*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 reverse tunneled ICMP Echo Reply or [9]. (out: NUTX -> HA0, in: NUT0 -> CN0)
7. Receive Binding Update to CN0. (NUTX -> CN0)
8. Send Binding Acknowledgement to NUTX. (CN0 -> NUTX)
# Binding Refresh Advice mobility option is included.
# The Refresh Interval field is set to the half of Lifetime field.
9. [6] or Receive ICMP Echo Reply. (NUTX -> CN0)
10. Send ICMP Echo Request. (CN0 -> NUTX)
11. Receive ICMP Echo Reply. (NUTX -> CN0)
12. (wait)
# Wait during the Refresh Interval of Binding Acknowledgement[9].
Packet Format is:
8. Binding Acknowledgement Data is:
IPv6 header (source = correspondent node,
destination = care-of address)
Routing header (type 2)
home address
Binding Acknowledgement
Binding Refresh Advice mobility option
Binding Authorization Data
(*1) PASS: CN0 does not receive Binding Update.
(draft-ietf-mobileip-ipv6-24.txt)
11.7.3 Receiving Binding Acknowledgements
(snip)
The treatment of a Binding Refresh Advice mobility option within the
Binding Acknowledgement depends on the where the acknowledgement came
from. This option MUST be ignored if the acknowledgement came from a
correspondent node. If it came from the home agent, the mobile node
uses Refresh Interval field in the option as a suggestion that it
SHOULD attempt to refresh its home registration at the indicated
shorter interval.
6.1.8 Binding Acknowledgement Message
(snip)
Mobility Options
Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. The encoding
and format of defined options are described in Section 6.2. The
receiver MUST ignore and skip any options which it does not
understand.
6.2.4 Binding Refresh Advice
(snip)
The Binding Refresh Advice option is only valid in the Binding
Acknowledgement, and only on Binding Acknowledgements sent from the
mobile node's home agent in reply to a home registration. The
Refresh Interval is measured in units of four seconds, and indicates
how long before the mobile node SHOULD send a new home registration
to the home agent. The Refresh Interval MUST be set to indicate a
smaller time interval than the Lifetime value of the Binding
Acknowledgement.