Information AboutMobile Ip |
| CATEGORIES ABOUT MOBILE IP | |
| network protocols | |
|
INTRODUCTION Mobile IP provides an efficient, scalable mechanism for node mobility within the Internet. Using Mobile IP, nodes may change their point-of-attachment to the Internet without changing their IP address. This allows them to maintain transport and higher-layer connections while moving. Node mobility is realized without the need to propagate host-specific routes throughout the Internet routing fabric. Applications Mobile IP is most often found in wireless WAN environments where users need to carry their mobile devices across multiple LANs with different IP addresses. It may also be used in 3G networks to provide transparency when internet users migrate between cellular towers. In many applications, sudden changes in network and IP-address can cause problems. Examples of these applications include: HOW MOBILE IP WORKS In brief, Mobile IP works as follows. A mobile node can have two addresses - a permanent home address and a care-of address which is associated with the network the mobile node is visiting. There are two kinds of entities in Mobile IP -
A node wanting to communicate with the mobile node uses the home address of the mobile node to send packets. These packets are intercepted by the home agent which uses a table and tunnels the packets to the mobile's node care-of address with a new IP header, preserving the original IP header. The packets are decapsulated at the end of the tunnel to remove the added IP header, and delivered to the mobile node. The Mobile IP protocol defines the following:
Future Enhancements to the Mobile IP technique, such as Mobile IPv6 and Hierarchical Mobile IPv6 (HMIPv6), are being developed to improve mobile communications in certain circumstances by making the processes more secure and more efficient. NetBIOS similarity Readers may be intrigued to know that, aside from the authentication, Mobile IP is literally concept-for-concept identical to NetBIOS in combination with the Microsoft Network Neighborhood services. Readers may also be surprised to know that, despite the conceptual similarity, at the time that an analysis was done (January 2002) no reference to RFCs 1001 and 1002, nor to the Microsoft Network Neighborhood, could be found in any of the Mobile IP RFCs or Draft RFCs. EXTERNAL LINKS
|
|
|