| 1: | You would use a Mobile IP solution, rather than DHCP or a simple WLAN, when you are interested in which of the following? Nomadic mobility Intrasubnet mobility Always-on IP mobility Stationary IP communication Link-layer mobility
|
| A1: | Answer: c. Mobile IP allows the user to remain in active communication as the user moves. Thus, the user can maintain TCP/UDP connections while moving, because the home IP address of the Mobile Node does not change. DHCP, on the other hand, is a nomadic solution. The user obtains a new address in the foreign/new network and must close all communication before moving again. WLAN provides mobility within one IP subnet. |
| 2: | What is the difference between nomadicity and mobility in the context of Mobile IP? |
| A2: | Answer: Nomadicity refers to the ability to move from one location to another and start communications. The user must terminate and restart sessions and applications as a result of the move. By contrast, mobility refers to the ability to move and maintain communication in the process. |
| 3: | What are the four requirements that a mobility solution must address? |
| A3: | Answer: A mobility solution must address four requirements: location discovery, move detection, update signaling, and path (re)establishment. |
| 4: | Link-layer mobility protocols by themselves are capable of handling interaccess technology handovers. True False
|
| A4: | Answer: False. By definition, link-layer mobility is associated only with a specific access link technology. |
| 5: | IP layer mobility allows all IP-enabled applications, whether they use TCP, UDP, or another transport protocol, to seamlessly inherit full mobility across a diverse range of access link types. True False
|
| A5: | Answer: True. |