MN-2-2-1-1-010 - BU rejected (Status = 135)
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
- home registration Binding Update Retransmissions : YES
- home registration Binding Update Retransmissions(status=135) : YES/NO
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) (*1)
| | | | |
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)
# The Status field is set to 135(Sequence number out of window).
7. (wait)
# Wait during 32(MAX_BINDACK_TIMEOUT) seconds.
Packet Format is:
6. Binding Acknowledgement
The judgment changes by the following settings of "INITIALIZATION 1. Selection Option".
- home registration Binding Update Retransmissions(status=135) : YES
(*1) PASS: HA0 receives the retransmitting of Binding Update.
Then, check whether this packet fills all of the following,
- The Sequence Number field is set to the following value of
the Sequence Number field of Binding Acknowledgement.
- home registration Binding Update Retransmissions(status=135) : NO
(*1) PASS: HA0 does not receive the retransmitting of Binding Update.
(draft-ietf-mobileip-ipv6-24.txt)
11.7.3 Receiving Binding Acknowledgements
(snip)
When a mobile node receives a packet carrying a valid Binding
Acknowledgement, the mobile node MUST examine the Status field as
follows:
(snip)
o If the Status field indicates that the Binding Update was rejected
(the Status field is greater than or equal to 128), then the
mobile node can take steps to correct the cause of the error and
retransmit the Binding Update (with a new Sequence Number value),
subject to the rate limiting restriction specified in Section
11.8. If this is not done, or it fails, then the mobile node
SHOULD record in its Binding Update List that future Binding
Updates SHOULD NOT be sent to this destination.
11.7.1 Sending Binding Updates to the Home Agent
(snip)
The last Sequence Number value sent to the home agent in a Binding
Update is stored by the mobile node. If the sending mobile node has
no knowledge of the right Sequence Number value, it may start at any
value. If the home agent rejects the value, it sends back a Binding
Acknowledgement with status code 135, and the last accepted sequence
number in the Sequence Number field of the Binding Acknowledgement.
The mobile node MUST store this information and use the next Sequence
Number value for the next Binding Update it sends.