Version 4.1 - 1.11 Mobile IP Part 2
This section will wrap up Mobile IP (and Section 1) with a discussion of Mobile IPv6. Note that the Cisco Exam Guide (Pocket Guide) does not even cover IPv6.
The Cisco Doc on Implementing Mobile IPv6 is very long. But if there's going to be a mobile question, it would come from here.
The first thing we would start with is to be aware of the IPv4 and IPv6 address differences. The whole point of mobile is to deal with the address issues imposed by roaming (versus stationary hosts). In IPv4 you get an address which has a network where the traffic is routed. In IPv6, you have more "relative" addressing (think of link-local addresses). The other thing about IPv6 is that it has Extended Headers. Remember Bull Hockey DR FAE DM? The "M" stands for Mobility. "Mobile IPv6 uses IPv6 option headers (routing, destination, and mobility) and benefits from the use of neighbor discovery." So with all that, it's obvious that the most obvious difference between the two is that IPv6 doesn't need a Foreign Agent.
To implement Mobile IPv6, you need a home agent on the home subnet on which the mobile node's home address resides. The IPv6 home address (HA) is assigned to the mobile node. The mobile node obtains a new IPv6 address (the CoA) on networks to which it connects. The home agent accepts BUs from the mobile node informing the agent of the mobile node's location. The home agent then acts as proxy for the mobile node, intercepting traffic to the mobile node's home address and tunneling it to the mobile node.
An interesting point is that the node can actually optimize the route and bypass the HA in IPv6. In may not be used in all implementations, but it is possible. They also use "NEMO" in this document. It's the Network Mobility Protocol feature. IPv6 Mobility also uses a binding cache and a Binding Update (BU) list to work this mobility magic. Another new term is DHAAD - Dynamic Home Agent Address Discovery. It's a feature that allows a mobile node to discover the address of the home agent on its home link.
Like I said, it's a long read (the Cisco Doc), but you really should read it. That way you're at least familiar with the processes and see the configuration examples. Another important note is the table for Feature Information. You probably will NOT see a question that would ask when a specific feature was implemented, but you should at least know that these features exist.
And now I am putting all of Section 1 "to bed." I really feel confident now about all these topics. Those 14 questions are now toast! Hopefully I have helped someone with these notes and links. But the biggest help you can get is to do this for yourself. It's a lot of work, but the journey is worth it.
What I am doing to create these posts is similar to a research paper. I'm using the blueprint to guide the topics and then going to my notes, books and looking on the Cisco Documentation for other relevant material. Where I can, I cite sources - and provide links instead of a bibliography. And I am reading the documents that I am linking. So I have seen this material on one or more videos. Then I read about the topic in a book. Then I looked it up on the Cisco site and read the Cisco Documentation. At that point, it should be ingrained in your memory and you don't have to rely on any memorization. You KNOW the material. And any "over studying" that you do will make the lab section that much easier. No learning is ever wasted.