CN-4-12-1 - Indices not recent but valid - Registration from the foreign link
Host
HA----------R2----------R1----------R0
| | | |
| | | |
|---- |---- |----MN |----CN(NUT)
| | | |
| | | |
Home Link Link2 Link1 Link0
(Foreign) (Foreign)
Link0 3ffe:501:ffff:100::/64 Link1 3ffe:501:ffff:101::/64 Foreign Link Link2 3ffe:501:ffff:102::/64 Foreign Link 2 Home Link 3ffe:501:ffff:104::/64 Home Link CN(NUT) 3ffe:501:ffff:100::X
Auto Configuration (InterfaceID)MN(in Link1) 3ffe:501:ffff:101::Y
Increased in each test (InterfaceID)MN care-of address MN(in Home Link) 3ffe:501:ffff:104::Y
Increased in each test (InterfaceID)MN home address R0(Link0) 3ffe:501:ffff:100::1 R1(Link1) 3ffe:501:ffff:101::1 R2(Link2) 3ffe:501:ffff:102::1 HA(Home Link) 3ffe:501:ffff:104::1
Reboot NUT (reboot.rmt)
MN R1 HA R0 CN(NUT)
| | | | |
| | | |------>| 1.RA
| | | | |
| | | |------>| 2.NS
| | | | |
| | | |<------| 3.NA
| | | | |
|-------------->|-------------->| 4.Echo Request
| | | | |
|<--------------|<--------------| 5.Echo Reply
| | | | |
|------------------------------>| 6.Echo Request(Home Address option)
| | | | |
|<------------------------------| 7.BE(Status=1)
| | | | |
|-------------->|-------------->| 8.HoTI
| | | | |
|<--------------|<--------------| 9.HoT
| | | | |
|------------------------------>| 10.CoTI
| | | | |
|<------------------------------| 11.CoT
| | | | |
|-------------->|-------------->| 12.HoTI
| | | | |
|<--------------|<--------------| 13.HoT
| | | | |
| | | | | Repeat 12. and 13. until receiving different index (Max 210sec)
| | | | |
|------------------------------>| 14.CoTI
| | | | |
|<------------------------------| 15.CoT
| | | | |
| | | | | Repeat 14. and 15. until receiving different index (Max 210sec)
| | | | |
|------------------------------>| 16.BU(Indices=received value in 9. and 11., Authenticator=Calculated from tokens received in 9 and 11.)
| | | | |
|<------------------------------| 17.BA(Status=0) (*1)
| | | | |
|------------------------------>| 18.Echo Request(Home Address option)
| | | | |
|<------------------------------| 19.Echo Reply(Type2 Routing Header) (*2)
| | | | |
1. Send Router Advertisement. 2. Send Neighbor Solicitation. 3. Receive Neighbor Advertisement. 4. Send ICMP Echo Request. 5. Receive ICMP Echo Reply. 6. Send ICMP Echo Request(Home Address option). 7. Receive Binding Error(Status=1). 8. Send Home Test Init. 9. Receive Home Test. 10. Send Care-of Test Init. 11. Receive Care-of Test. 12. Send Home Test Init. 13. Receive Home Test. *Repeat 12. and 13. until receiving different index (Max 210sec). 14. Send Care-of Test Init. 15. Receive Care-of Test. *Repeat 14. and 15. until receiving different index (Max 210sec). 16. Send Binding Update (Indices=received value in 9. and 11., Authenticator=Calculated from tokens received in 9 and 11). 17. Receive Binding Acknowledgement(Status=0). 18. Send ICMP Echo Request(Home Address option). 19. Receive ICMP Echo Reply(Type2 Routing Header).
Packet Format 16. Binding Update 17. Binding Acknowledgement 18. ICMP_Echo Request(Home Address option) 19. ICMP Echo Reply(Type2 Routing Header)
(*1) MN receives Binding Acknowledgement. - The Destination Address is set to the Source Address of the Binding Update (MN care-of address). - The Status field is set to 0. - Binding Authorization Data option is included. - Authenticator field of Binding Authorization Data option has the valid value.
(*2) MN receives ICMP Echo Reply. (Binding Cache entry is created.) - The Destination Address is set to MN care-of address. - Type 2 Routing Header is included.
(draft-ietf-mobileip-ipv6-24.txt)
5.2.7 Updating Node Keys and Nonces
Correspondent nodes generate nonces at regular intervals. It is recommended to keep each nonce (identified by a nonce index) acceptable for at least MAX_TOKEN_LIFETIME seconds (see Section 12) after it has been first used in constructing a return routability message response. However, the correspondent node MUST NOT accept nonces beyond MAX_NONCE_LIFETIME seconds (see Section 12) after the first use. As the difference between these two constants is 30 seconds, a convenient way to enforce the above lifetimes is to generate a new nonce every 30 seconds. The node can then continue to accept tokens that have been based on the last 8 (MAX_NONCE_LIFETIME / 30) nonces. This results in tokens being acceptable MAX_TOKEN_LIFETIME to MAX_NONCE_LIFETIME seconds after they have been sent to the mobile node, depending on whether the token was sent at the beginning or end of the first 30 second period. Note that the correspondent node may also attempt to generate new nonces on demand, or only if the old nonces have been used. This is possible, as long as the correspondent node keeps track of how long a time ago the nonces were used for the first time, and does not generate new nonces on every return routability request.