CN-3-3-2 - De-Registration - From the foreign link, without the return routability procedure
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.CoTI
| | | | |
|-------------->|-------------->| 9.HoTI
| | | | |
|<------------------------------| 10.CoT
| | | | |
|<--------------|<--------------| 11.HoT
| | | | |
|------------------------------>| 12.BU
| | | | |
|<------------------------------| 13.BA
| | | | |
|------------------------------>| 14.Echo Request(Home Address option)
| | | | |
|<------------------------------| 15.Echo Reply(Type2 Routing Header)
| | | | |
|------------------------------>| 16.BU(Lifetime=0, reused Home Nonce index and token)
| | | | |
|<------------------------------| 17.BA(Status=0) (*1)
| | | | |
|------------------------------>| 18.Echo Request(Home Address option)
| | | | |
|<------------------------------| 19.BE(Status=1) (*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 Care-of Test Init. 9. Send Home Test Init. 10. Receive Care-of Test. 11. Receive Home Test. 12. Send Binding Update. 13. Receive Binding Acknowledgement. 14. Send ICMP Echo Request(Home Address option). 15. Receive ICMP Echo Reply(Type2 Routing Header). *Expire De-Registration Start Time. 16. Send Binding Update(Lifetime=0, reused Home Nonce index and token). 17. Receive Binding Acknowledgement(Status=0). 18. Send ICMP Echo Request(Home Address option). 19. Receive Binding Error(Status=1).
Packet Format 16. Binding Update 17. Binding Acknowledgement 18. ICMP_Echo Request(Home Address option) 19. Binding Error
(*1) MN receives Binding Acknowledgement. - The Destination Address is set to the Source Address of the Binding Update (MN care-of address). - Type 2 Routing Header is included. - The Home Address field of Type 2 Routing Header is set to MN home address.
(*2) MN receives Binding Error. (Binding Cache entry is deleted.) - The Destination Address is set to the Source Address of ICMP Echo Request (MN care-of address). - The Status field is set to 1. - The Home Address field is set to the value in the Home Address option in the ICMP Echo Request (MN home address).
(draft-ietf-mobileip-ipv6-24.txt)
9.5.1 Receiving Binding Updates
o If the Lifetime specified in the Binding Update is zero or the
specified care-of address matches the home address for the
binding, then this is a request to delete the cached binding for
the home address. In this case, the Binding Update MUST include a
valid home nonce index, and the care-of nonce index MUST be
ignored by the correspondent node. The generation of the binding
management key depends then exclusively on the home keygen token
(Section 5.2.5). If the Home Registration (H) bit is set in the
Binding Update, the Binding Update is processed according to the
procedure specified in Section 10.3.2; otherwise, it is processed
according to the procedure specified in Section 9.5.3.
9.5.3 Requests to Delete a Binding
Any existing binding for the given home address MUST be deleted. A Binding Cache entry for the home address MUST NOT be created in response to receiving the Binding Update.
9.5.4 Sending Binding Acknowledgements
If the Source Address field of the IPv6 header that carried the Binding Update does not contain a unicast address, the Binding Acknowledgement MUST NOT be sent, and the Binding Update packet MUST be silently discarded. Otherwise, the acknowledgement MUST be sent to the Source Address. Unlike the treatment of regular packets, this addressing procedure does not use information from the Binding Cache. However, a routing header is needed in some cases. If the Source Address is the home address of the mobile node, i.e., the Binding Update did not contain a Home Address destination option, then the Binding Acknowledgement MUST be sent to that address, and the routing header MUST NOT be used. Otherwise, the Binding Acknowledgement MUST be sent using a type 2 routing header which contains the mobile node's home address.