CN-3-1-1 - Registration - Alternate Care-of Address option
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(Src:Alternate CoA)
| | | | |
|-------------->|-------------->| 9.HoTI
| | | | |
|<------------------------------| 10.CoT
| | | | |
|<--------------|<--------------| 11.HoT
| | | | |
|------------------------------>| 12.BU(Alternate Care-of Address option)
| | | | |
|<------------------------------| 13.BA(Status=0) (*1)
| | | | |
|------------------------------>| 14.Echo Request(Home Address option)
| | | | |
|<------------------------------| 15.Echo Reply(Type2 Routing Header,Destination Address=altercnate care-of address) (*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(Alternate Care-of Address option). 13. Receive Binding Acknowledgement. 14. Send ICMP Echo Request(Home Address option). 15. Receive ICMP Echo Reply(Type2 Routing Header,Destination Address=altercnate care-of address).
Packet Format
12. Binding Update(Alternate Care-of Address option)
IPv6 header
Destination Options header
Home Address option
Mobility header
Binding Update
Alternate Care-of Address option
Nonce Indices option
Binding Authorization Data option
13. Binding Acknowledgement
14. ICMP_Echo Request(Home Address option)
15. 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). - Type 2 Routing Header is included. - The Home Address field of Type 2 Routing Header is set to MN home address.
(*2) MN receives ICMP Echo Reply. (Binding Cache entry is created.) - The Destination Address is set to the Alternate Care-of Address in the Binding Update. - Type 2 Routing Header is included. - The Home Address field of Type 2 Routing Header is set to MN home address.
(draft-ietf-mobileip-ipv6-24.txt)
9.5.1 Receiving Binding Updates
The specified care-of address MUST be determined as follows:
o If the Alternate Care-of Address option is present, the care-of
address is the address in that option.
9.5.1 Receiving Binding Updates
When the Home Registration (H) bit is not set, the following are also required:
(snip)
o The Binding Authorization Data mobility option MUST be present,
and its contents MUST satisfy rules presented in Section 5.2.6.
Note that a care-of address different from the Source Address MAY
have been specified by including an Alternate Care-of Address
mobility option in the Binding Update. When such a message is
received and the return routability procedure is used as an
authorization method, the correspondent node MUST verify the
authenticator by using the address within the Alternate Care-of
Address in the calculations.
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.