MN-4-1-1-1-004 - Retransmissions (Use INITIAL_SOLICIT_TIMER as the initial retransmission timer)
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
- Mobile Prefix Solicitation retransmit : YES
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
| | | | | 9.(no reply)
| | | | |
| <---- | | | | 10.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)
9. (no reply)
# Wait during a maximum of the remaining valid lifetime of the Home Address.
10. Receive Mobile Prefix Solicitation. (NUTX -> HA0)
Packet Format is:
10.Mobile Prefix Solicitation
(*1) PASS: HA0 receives the retransmitted Mobile Prefix Solicitation.
Then, check whether this packet fills all of the following,
- The initial retransmission timer is set to INITIAL_SOLICIT_TIMER.
(draft-ietf-mobileip-ipv6-24.txt)
11.8 Retransmissions and Rate Limiting
The mobile node is responsible for retransmissions and rate limiting
in the return routability procedure, registrations, and in solicited
prefix discovery.
When the mobile node sends a Mobile Prefix Solicitation, Home Test
Init, Care-of Test Init or Binding Update for which it expects a
response, the mobile node has to determine a value for the initial
retransmission timer:
o If the mobile node is sending a Mobile Prefix Solicitation, it
SHOULD use an initial retransmission interval of
INITIAL_SOLICIT_TIMER (see Section 12).
o If the mobile node is sending a Binding Update and it does not
have an existing binding at the home agent, it SHOULD use
InitialBindackTimeoutFirstReg (see Section 13) as a value for the
initial retransmission timer. This long retransmission interval
will allow the home agent to complete the Duplicate Address
Detection procedure which is mandated in this case, as detailed in
Section 11.7.1.
o Otherwise, the mobile node should use the specified value of
INITIAL_BINDACK_TIMEOUT for the initial retransmission timer.
12. Protocol Constants
DHAAD_RETRIES 4 retransmissions
INITIAL_BINDACK_TIMEOUT 1 second
INITIAL_DHAAD_TIMEOUT 3 seconds
INITIAL_SOLICIT_TIMER 3 seconds
MAX_BINDACK_TIMEOUT 32 seconds
MAX_NONCE_LIFETIME 240 seconds
MAX_TOKEN_LIFETIME 210 seconds
MAX_RR_BINDING_LIFETIME 420 seconds
MAX_UPDATE_RATE 3 times
PREFIX_ADV_RETRIES 3 retransmissions
PREFIX_ADV_TIMEOUT 3 seconds
(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.