JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.

ORG

42

Serial Number based IPv6 Addressing Architecture in a Foreign IPv4 Network

Hamid Ali, Muhammad Arshad, Masood Habib and Rashid Naseem
AbstractMobility of a mobile node can be achieved by using two IP addresses. The home address, used for identification of the TCP connection, is static and the care-of-address (CoA) changes each time the point of attachment changes [1]. Therefore the CoA can be thought of as the mobile nodes topologically significant address. IPv4 and IPv6 will co-exist for a long time as it is impossible to switch over the entire Internet to IPv6 overnight. That is why transition mechanisms have been devised to make the transition to IPv6 smoothly [2]. This paper proposes a solution for an IPv6 node to get address in an IPv4 address family network, in perspective of IPv6 and IPv4 integrated networks, while not restricting an IPv6 configured node to roam only in IPv6 address family network hence the proposed technique makes it able to roam a MN also into IPv4 address family network [3]. In the new addressing mechanism the mobile node assigns the DHCPv6 allocated 28-bits Serial Number from 5th to 32nd bits position and the 32-bits IPv4 address of the default router is assigned from 33rd to 64th bits position of the network part of newly generated 128-bits IPv6 care-of-address, at foreign network. Using IPv4 address of the default router in the CoA of the mobile node (MN) helps other routers in the Internet to identify easily the current location of the MN and to establish communication link between the MN and CNs. The main focus of our proposed technique is to allow an IPv6 configured MN to roam also to an IPv4 configured network and thus getting services in that different address family network. Index TermsIPv6 address architecture, IPv6 care-of-address configuration, MIPv6 users, and Mobility management in Mobile environments.

1 INTRODUCTION
OBILITY support in IPv4 is quite different from that in IPv6, each has its own set of standards, and they continue to deviate more and more over time. Mobile IPv6 is much more proficient than Mobile IPv4, and due to the forthcoming exhaustion of the IPv4 address space, new research is being done on Mobile IPv6, not on Mobile IPv4 [4].

1.1 Mobile Internet Protocol version 4 (MIPv4) Mobile IP, an extension to IP, allows communication between mobile nodes without changing their IP addresses while roaming from one network to another [4]. The basic rules in MIPv4 for processing and mobility management are defined in specialized routers called Home Agent (HA) and Foreign Agent (FA) and in the node that have to roam about called MN. For the purpose of mobility to achieve the mobile IP supports two addresses one of which is permanent called Home Address (HoA) and another one temporary, just valid for roaming purpose, represent the nodes current point of attachment, called CoA [4]. Mobile IP provides mobility for MNs through binding

Hamid Ali is student of MS(CS) in Department of Computer Sciences, City University of Science & IT, Peshawar, Pakistan. Muhammad Arshad is working as Assistant Professor in Department of Computer Sciences, City University of Science & IT, Peshawar, Pakistan. Masood Habib is working as Lecturer in Department of Computer Sciences, City University of Science & IT, Peshawar, Pakistan. Rashid Naseem is working as Lecturer in Department of Computer Sciences, City University of Science & IT, Peshawar, Pakistan.

the HoA of the MN to its CoA. Mobility agents (HA and FA) keep records of this binding. If the correspondent node (CN) wants to communicate with the MN, all the packets will tunnel through the HA. The HA then forwards packets to the MNs CoA using binding table for mapping [4]. FA keeps records of the entire visiting nodes in the MNs visited/foreign network. FA and HA advertise messages, called agent advertisement messages, through which they show their presence. On roaming the MN requests the FA for its CoA, and after getting the CoA it registers the temporary CoA with the HA. The HA then forwards the packets encapsulating them with a new header having CoA as the destination address. When the FA receives the tunneled packets it de-encapsulates the header and forwards it to the MN [4]. Triangle routing is a major problem faced in the implementation of basic Mobile IP, where data communication between CN and MN takes place through HA and FA and it appears when the indirect path between CN and MN through the HA is longer than the direct path between them [1]. To solve the triangular routing problem Internet Engineering Task Force (IETF) introduced Mobile IP Rout Optimization, where communication takes place directly between communicating nodes. In this mechanism the CN sends binding request messages in order to know the current updates of the MN, and the MN send frequent binding update messages to the CNs. Once the MN is registered with the CN, the CN tunnels the datagram destined to the MN directly using its CoA and the MN also sent packets destined to CN using its HoA [1].

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

43

1.2 Mobile Internet Protocol version 6 (MIPv6) As IPv4 is running out of address space, the ISPs are unable to allocate IPv4 addresses to the new connecting devices. Therefore the need for a new protocol version was unavoidable and that is why in early 90s the IETF has to design the next generation protocol called IPv6 [2]. The Internet connectivity through 4G cell phones has already fully deployed the IPv6 addressing structure. The whole of the Internet is going through transition phase, where IPv4 and IPv6 coexist in order to make the communication possible between the nodes having configured these two different kinds of address family protocols. Routers play the mediation roll between the hosts of these two types of protocols [2]. MIPv6 relies on IPv6 is currently the standard for the mobility problem, proposed by IETF, for nodes that have to have roaming capability from network to network. It enables the mobile devices to maintain its current addresses and transport layer connections while roaming between different networks [4]. Unlike MIPv4, Mobile IPv6 is a part of the IPv6 address family protocol. In IPv6, FA is not needed as the MN obtains new IPv6 address (CoA) either through Stateless or Stateful Address Auto Configuration. The uniqueness of Stateless Auto Configured address is verified through a mechanism called Duplicate Address Detection (DAD). The MN then sends the binding update (BU) to the HA to register CoA [5]. The HA plays a role of stationary proxy, when MN is away from its home network. The HA captures the packets destined to the MN. It checks its binding list with the packets destination address and tunnels the packets to the MNs CoA. The MN can communicate directly to the CN with binding update, binding acknowledgements, and the return routability mechanisms integrated in the IPv6 packet [6]. The structure of this paper is as follows. Chapter 2 reviews Problem Definition, Chapter 3 discusses the Related Work on addressing architecture of MN in visited network, Chapter 4 discusses the Proposed Solution of IPv4 addressing in IPv6 network and finally Chapter 5 Concludes the research developments.

less Address Auto-configuration and address configured from the DHCPv6 Server is called Stateful Address Autoconfiguration [8]. In the Stateless approach nodes select their addresses themselves and then through a mechanism known as DAD verify their uniqueness. The IETF Zero configuration protocol is an example of this approach [9]. In another scenario when an IPv4 node moves from its home network to a foreign/visited network then the node is assigned address through MIP, for IPv4 nodes, and MIPv6 in the case of IPv6 nodes. However a MN with IPv4 configuration cannot be restricted to roam only in IPv4 networks and similarly a MN having IPv6 configuration cannot be restricted to roam only in IPv6 networks i.e. IPv6 configured mobile users can visit IPv4 networks and IPv4 configured mobile users can visit IPv6 networks, but the major challenge is how the node will be configured for making it able to roam into a different address family network e.g. IPv4 addressing in IPv6 address family network and IPv6 addressing in IPv4 address family network [10]. Here we suggest a scenario in which an IPv6 configured node moves from its home IPv6 network and visits a foreign IPv4 network. According to Henderson [11], mobility causes some fundamental problems in the network layer. The first concern is IP Addressing, as for scalability purpose the IP routing and addressing are defined hierarchically; therefore the MNs usually have a topologically incorrect interface address when they attach to a new network, and especially the problem becomes more challenging when the home and foreign networks differ in address family as in our case [11]. The second problem is that of location management, when changing network the MN may become unreachable to the rest of the network unless the new address is somehow mediated to other nodes, the challenge is how to mediate the address between the nodes located at different address family networks. The third problem is about the session management i.e. the current transport protocols use the IP address as part of the connection identifier therefore the change of address causes breaks in active connections [11].

2 PROBLEM DEFINITION
IP addresses and addresses of key servers such like Domain Name Service (DNS) are the needed information that a node will be configured with, in order to establish and maintain IP-level connectivity [1]. The two types of IPv6 addresses are Link Local and Global IPv6 addresses, the former is used for communication to take place within LAN, while the latter is used for communication to take place between two hosts across a wide area network. Furthermore the Global IPv6 address is of two types, Static address and Dynamic address [7]. In Static address configuration, IPv6 address is assigned manually by the system administrator and in the case of Dynamic configuration the IPv6 address is configured automatically. The two types of Dynamic IPv6 addresses are Stateless and Stateful address. Address configured from the default router in the LAN is called State-

3 RELATED WORK
3.1 IPv4 Addressing in IPv4 Visited Network Mobil IP, an extension to IP, provides transparent mobility support to MNs within the Internet. Mobile IP uses two IP addresses HoA through which the MN is registered in HN and a CoA that changes each time the MN is attached to a different network. The CoA, usually provided by the FA, gives information of the current point of attachment of the MN. The FA is the default router of the MNs visited network. CoA must be informed to HA by sending a BU message from MN, a HA is Usually the default router at the home networks of the MN that tunnels datagrams for delivery to the MN when it is away from home, and maintains current location information for the MN [12]. Home agent is allowed to create a tunnel between the home network of the MN and the MNs current point of at-

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

44

tachment. The datagrams tunneled by the home agent are detunneled and delivered to the MN by the FA. Instead of relying on the home agent, binding updates allow the CN to tunnel datagrams directly to the MN's CoA. With route optimization techniques, FA can assist the MN to affect smooth handoffs, being careful not to drop any datagrams even when the MN has moved away from the care-of address receiving the datagrams [12].

3.3 IPv4 addressing architecture in IPv6 network This work designs an integrated system where Ipv6 network, provides services to both Ipv4 and Ipv6 mobile users. An Ipv4 node is allowed to roam also to an IPv6 network and there it gets configured with Ipv4 address without any DHCP server. In the proposed integrated system, an IPv4 user B from IPv4 HN is assumed to roam into IPv6 network. While being in the IPv6 network, B is referred as B. It obtains an IPv4 address from a special address range, 64.x.x.y/8 taken as an example, fixed for IPv4 addressing in IPv6 network [10]. Hexadecimal x, represents the first sixteen bits of the IPv6 router address, is converted to decimal and is assigned to the 9th to 24th bit position of the host part. Y is given a value from 0 to 254. This new 32 bit generated IPv4 address is the CoA of the MN B and is referred to as P46A. After successful return of DAD it is recorded into v4 enabled Gateway table and is forwarded to the HAv4 for registration. Hence the CNv4 and CNv6 can access the MN [10]. 3.2 IPv6 addressing architecture in IPv4 network It suggests a scenario in which IPv6 node while roaming from its home IPv6 network to a foreign IPv4 network gets IPv6 address using IPv4 router address in that visited network, IPv6 Cryptographically Generated Address (CGA), and with little modification in the IPv6 sitelocal address format. While roaming from its home IPv6 network, the mobile IPv6 node reaches an IPv4 network where it gets IPv4 router solicitation message and from this message it gets the router address [3]. It converts this decimal address to hexadecimal format and puts the address into 17th to 48th bit position of the network part of its new IPv6 address. The first 16 bits are assigned as Format Prefix (here 1001) and the 49th to 64th bit position is assigned 0s. For the least significant 64 bits, MAC address goes through Hash function. This newly generated address is called CoA for the MN and is referred as P46CGA.Whenever CN in IPv6 network (CNv6) wants to communicate with IPv6 configured MNv6 it request the HAv6 for the MNv6 address. The HAv6 sends it the CoA. From the information given in the CoA the CNv6 comes to know that the MNv6 is in an IPv4 network. So it extracts the 17th to 48th bit value and uses it in order to locate and route the MN [3]. To sum up, the proposed scenario in the current literature is scalable and yet relatively simple to track more than 268 million mobile nodes on the same or different topological locations. The mechanism in [10] and [12] do not consider an IPv6 mobile user roaming into IPv4 address family network, while the one studied in [3] is rela-

tively closer to our proposed mechanism. But the approach of getting IP address and especially integrating a noval approach of tracking the mobile nodes through the 28-bits serial number embedded in the IPv6 care-of address is the major difference between the two proposed mechanisms. The current literature has a new, Serial Number based IP address configuration mechanism for network management, therefore makes decision regarding resource utilization/allocation tremendously easy as contrary to [3].

4 PROPOSED SOLUTION
Currently IPv4 is the standard for communications over the Internet. However, with the tremendous expansion of the Internet, IPv4 is proving to be incapable of handling the growth of the Internet expected in future [13]. IPv6 is the emerging Internet Protocol for next generation networking. It is not backward compatible with IPv4 and therefore both of them have their own users and service providers. In order to make communication possible between the two address family Protocols transition mechanisms have been devised [14]. This paper suggests a scenario in which a mobile node B moves from its home IPv6 network and visits a foreign IPv4 network, in the foreign network mobile node B is referred as B`. While roaming B` gets IPv4 address from the default Gateway of the IPv4 network. In the following sub-sections we describe the mechanism of configuring a serial number based IPv6 address from the IPv4 address at the foreign network. Here we assume that B`, the HA at home IPv6 network and the default Gateway at the IPv4 network are IPv4- and IPv6-enabled. Also we assume that only Mobile IPv4 is used between the mobile node, V6/V4 Gateway and the HA at home IPv6 network, the scenario of proposed IPv6 Addressing Architecture (IP64S) in IPv4 Network is shown in Fig. 5. The proposed mechanism is able to be implemented immediately as the main components needed are; IPv6 Router which is already available in the IPv6 network, a new DHCPv6 server to be installed in IPv6 network and V6/V4 Gateway which is to be installed newly within the default Router of the IPv4 network, without the need of additional devices to be included with the existing infrastructure either into IPv6 or in IPv4 address family network. Though the addressing mechanism in our proposed system slightly differs from that of the existing standard addressing architecture, rest of the procedures remains the same as existing standards. . Whole of the scenario in signaling form is depicted in the Fig. 1. The advantage of the proposed mechanism of using the 28-bits serial number with combination of Gateways IPv4 address in generating IPv6 CoA, is that it is easy to track the number of mobile nodes down at the home network, either they are located at the same foreign network or topologically at different foreign networks. As a result: As we have information of Serial number and information of IPv4 topological address in hand, we get topology based information of the mobile

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

45

Fig. 1. Signaling diagram for Proposed System.

nodes Decision of resource allocation to all the mobile nodes going out of a network, as a whole as well as per topology based becomes possible It is possible to track the number of active mobile nodes down, went out of a network as a whole as well as per topology based with respect to communication

4.1 Agent Discovery and IPv6 Addressing in IPv4 Network Whenever B moves to the IPv4 network, using agent discovery protocol, it attempts to discover IPv4 Gateway in the IPv4 network [15]. In the foreign IPv4 network the MN B is referred as B`. B` discovers the IPv4 default Gateway from the foreign agents periodically advertised messages on the network or it may also broadcast an agent solicitation message onto the visiting network to ask the agent for advertisement [16][17]. The default Gateway responds by sending its IPv4 address (here 123.55.77.69) in the agent advertisement message to the requesting MN. When B` gets the agent adver-

tisement message it registers with the Gateway and uses the Gateways IPv4 address to generate its 128 bits CoA. We select the Gateways IPv4 address for generating the CoA because the location of the MN can easily be identified whenever a packet is transmitted to it either from the Home Agent or directly from a CN. As a result the routing and packet processing delay can be minimized [18], the scenario of the proposed model of integrated networks is depicted in Fig. 2.

4.2 Discovering the Care-of Address When the MN moves to the foreign IPv4 network, it needs to get a CoA. The CoA first needs a Serial number in our proposed mechanism. In order to get a 28-bits Serial number from the DHCPv6 server the MN provides its HAs IP address (2001:d02:0:0::95) to the V6/V4 gateway. The V6/V4 gateway forwards the query to the HA which in turn gets it from the DHCPv6 at home network and forwards it to the V6/V4 gateway. The 28 bits serial number in hexadecimal format (000 000B) is assigned from 5th to 32nd bit position of the new IPv6 address. In order to get gateways IPv4 address, once a second or

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

46

Fig. 2. IPv6 and IPv4 Integrated Network.

once every few seconds, is the regular interval of time, the mobility agents broadcast their agent advertisement messages, or in an alternate mechanism MN can broadcast a solicitation request message that will be answered by the default Gateway and thus it gets the gateways address [17][19] ], the format of the address scheme in IPv4 network is shown in Fig. 3. The 32-bits IPv4 router address (123.55.77.69) that is in decimal format is first converted into hexadecimal format (7B37 4D45) and then it is assigned from 33rd to 64th bits position of the network part of the IPv6 address. The first 4-bit is assigned as Format Prefix (FP) that has not been reserved by other types of IPv6 address and we consider the format prefix as 0100/4 or 4 in hexadecimal, here we refer 4 as MNs IPv6 CoA generated from an IPv4 address in an IPv4 network. Through agent solicitation messages the B` will keep itself updated and will detect the changes in the current point of attachment of the mobility agents. If the V6/V4 Gateway fails to deliver services then B` begins to hunt for new CoA using again either of the following two methods, it may choose to wait for another agent advertisement or it may send an agent solicitation message to the network [17][20]. IPv6 node B` reuses the 64-bits interface identifier (0123 4567 89AB CDEF) that was assigned by DHCPv6

MAC address and HA address is recorded into V6/V4 Gateway Table shown in Fig. 4, while B` sends a BU message to its HA. The reason why we select IPv4 router address is that whenever a packet is transmitted to this IPv6 MN, looking into the 33rd to 64th bit value and by converting this into IPv4 decimal notation, the location of the mobile node can easily be identified and routed to the correct location in order to minimize the routing and packet processing delay.

4.3 Registration and Redirection of Packets On moving the MN from home IPv6 network to the foreign IPv4 network, the newly generated IP64S address (i.e. 4000:000B:7B37:4D45:0123:4567:89AB:CDEF) is first registered with the HA at the home IPv6 network. In order to register with the V6/V4 Gateway at foreign network, B` provides its HAs IP address to the V6/V4 Gateway. The Gateway forwards the request for registration to the HA. When the HA accepts the request, it begins to

Fig. 4. V6/V4 Gateway table.

Fig. 3. IP64S Address Scheme in IPv4 Network.

server at home network. It uses the same 64-bits number and assigns it to the least significant 64-bits part of newly generated CoA. The 128-bits address generated for the IPv6 MN in IPv4 network is the CoA and we refer it as IP64S. This IP64S is the MNs CoA which along with its

associate the HoA of the B` with its newly generated IP64S, and maintains this association until the registration lifetime expires [17]. The HA then replies to the V6/V4 Gateway, who in turn forwards the reply to B`. During the registration lifetime B` must refresh its registration to continue to receive service. B` deregisters with the HA on returning back to its home network. To get a packet from IPv6 network to the B`, the CN first delivers the packet to B` using

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

47

Fig. 5. Proposed IPv6 Addressing Architecture (IP64S) in IPv4 Network.

its HoA, the HA gets the packet as it act a role of proxy for mobile node B` [17][21]. From the first 4-bits format prefix number (0100/4), the HA comes to know that the MN is in IPv4 network, thus it extracts 33rd to 64th bits position value of the IP64S, converts it into decimal notation, the scenario is depicted in Fig. 5 below. The HA redirect packets, using this 32-bits address from the home IPv6 network to B` by constructing a new IP header. This new IP header contains the 32-bits adress as the destination address shielding or encapsulating the original packet having B` HoA as the destination address. It causes home address of B` to have no effect on the routing of the encapsulated packet until it arrives at the V6/V4 Gateway. Such encapsulation/tunneling causes for efficient and hierarchical delivery of packets to B`. The 32-bits address extracted from IP64S is used as the destination IP address in the new tunnel header and HAs IP address is used as the tunnel source IP address. In order to recover the original packet the V6/V4 Gateway needed only to eliminate the tunnel header and then it delivers the rest to B` [17].

5 CONCLUSION
Since IPv6 is not extensively deployed, it is unlikely that mobile nodes (MNs) will primarily use only IPv6 addresses for the means of their communication [22]. It is reasonable to assume that MNs will, for a long time, need an IPv4 HoA that can be used by upper layers of the protocol stack [23]. It is also reasonable to assume that MNs will roam about to networks that might not support IPv6 protocol stack and would therefore need the capability to support an IPv4 address family protocol [23]. The paper is about a Mobility Management Solution for an IPv6 Node in a Foreign IPv4 Network. It proposes a new technique to configure an IPv6 MN roaming in IPv4 network with a Serial Number based IPv6 address obtained from the V6/V4 Gateways IPv4 address and adding a Serial Number to generate the 128-bits CoA. When the MN gets the agent advertisement message it registers with the HA and uses the 128-bits newly generated address based on V6/V4 Gateways IPv4 address as its CoA. We select the IPv4 address of the V6/V4 Gateway to generate the CoA because MNs location can easi-

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617 https://sites.google.com/site/journalofcomputing WWW.JOURNALOFCOMPUTING.ORG

48

ly be identified whenever a packet is transmitted to it. Also the routing and packet processing delay can be reduced whenever the CN sends packets to the MN. Furthermore the proposed mechanism is able to be implemented immediately, as only V6 enabled IPv4 router is the new deployment which is to be installed within the IPv4 default Router at the IPv4 network. As a future work, the performance of the proposed mechanism will be evaluated using NS-2 [24] simulator.

[14]

[15]

REFERENCES
[1] N. Jaggi, Koushik, "Distributed authentication mechanism for mobile IP route optimization," presented at the IEEE International Conference on Wireless Networks, Communications and Mobile Computing, Maui, Hawaii, USA, pp. 1271-1276 (June 2005). G. Jivika, J. Govil, Navkeerat Kaur, Harkeerat Kaur, "An examination of IPv4 and IPv6 networks: constraints and various transition mechanisms," presented at the IEEE Region 3 Huntsville Section (IEEE SoutheastCon 2008), Huntsville, Alabama, USA, pp. 178-185, (April 2008). Rabara S.A., Jayanthi J.G., "IPv6 addressing architecture in IPv4 network," presented at the Second International Conference on Communication Software and Networks, Singapore, Singapore, pp. 461-465, (Feb. 2010). T. M. Mahmoud, M. R. Girgis, Youssef S. T., H. S. Hassan, "Performance evaluation of a new route optimization technique for mobile IP," International Journal of Network Security & Its Applications, vol. 1 ( 3), pp. 6373, (October 2009). P. Shalini, K.Sankaranarayanan, B. Sakthi "Comparative study of secured optimized route in MIPv6," Proceedings of the International Journal of Computer Science and Network Security, vol. 8, pp. 377 382, (November 2008). APNIC, Geoff Huston, "IPv4 address depletion and transition to IPv6," Internet Protocol Journal, vol. 10 ( 3), pp. 18-28 (September 2007). Jivesh Govil, Jivika Govil, On the Investigation of Transactional and Interoperability Issues between IPv4 and IPv6, presented at the IEEE Electro/Information Technology Conference, Chicago, USA, pp. 604-609, (17-20 May 2007). Dongkeun Lee, Jaepil Yoo, Keecheon Kim, Kyunglim Kang, IPv6 Stateless Address Auto-configuration in Mobile Ad-hoc Network (TDAD) and Performance Evaluation, ACM Proceedings of the 2nd ACM international workshop on Performance evaluation of wireless ad hoc, sensor, and ubiquitous networks, Montreal, Quebec, Canada, pp. 271-272, (October 2005). Mesut Gunes, Jorg Reibel, An IP Address Configuration Algorithm for Zeroconf. Mobile Multi-hop Ad-Hoc Networks, Proceedings of the International workshop on Broadband wireless Adhoc networks and services, Sophia Antipolis, France, (Sept 2002). Rabara S.A., Jayanthi J.G., "IPv4 addressing architecture in IPv6 network," presented at the Second International Conference on Advanced Computer Control (ICACC), Shenyang, Liaoning, China, pp. 282-287, (March 2010). Henderson, Ahrenholz, Kim, J., Experience with the Host Identity Protocol for Secure Host Mobility and Multihoming, Proceedings of the IEEE Wireless Communications and Networking, pp. 2120-2125, (March 2003). Perkins, C., "IP Mobility Support", RFC 2002, October 1996. Yong Feng, Zhongfu Wu, Jiang Zhong, Chunxiao Ye, Kaigui Wu, Novel Authentication Mechanism Based on CGA for BU [16]

[2]

[17] [18]

[3]

[19] [20]

[4]

[21]

[5]

[22] [23] [24]

[6]

Message Disposal in Mobile IPv6, Proceedings of the International Conference on Networking, Architecture, and Storage, pp. 137-143, (June 2008). E. Karpilovsky, Gerber, A., Pei, D., Rexford, J., Shaikh, A., "Quantifying the extent of IPv6 deployment," in Passive and Active Measurement, PAM 2009, Springer Berlin/ Heidelberg, isbn: 978-3-642-00974-7 (March 2009). Sajal Saha, Asish K Mukhopadhyay and Suranjan Ghose, "Fast handoff mobile IP protocol using a novel route optimization technique," International Journal of Recent Trends in Engineering, vol. 2 (1), pp. 207 211, November 2009. Sajal Saha et al. A comparative Study of Route Optimization Protocols in Mobile IP, Proceedings of the National Conference on Computing and Communication System (CoCoSys-2009), pp. 105-109, (January 2009). Johnson, D., Perkins, C., and Arkko J. Mobility Support in IPv6, http://tools.ietf.org/rfc/rfc3775.txt, (Accessed: 2012). K. Ren, W. Lou, K. Zeng, F. Bao, J. Zhou, and R. H. Deng, Routing optimization security in mobile IPv6, Computer Networks, vol. 50, pp. 24012419, (2006). Davies, J., Understanding IPv6, Microsoft Press, Redmond, WA, (2003). D. Malone, "Observations of IPv6 addresses," Proceedings of the Passive and Active Network Measurement Conference, Vol. 4979, pp. 2130, (2008). Jong-Hyouk Lee and Tai-Myoung Chung, A Traffic Analysis of Authentication Methods for Proxy Mobile IPv6, Proceedings of the International Conference on Information Security and Assurance 2008, Busan, pp. 512-517, (April 2008) . Geoff Huston, Telstra, IPv4: How long do we have?... Internet Protocol Journal, Vol. 6 (4), pp. 2-15,( 2003). Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Routers", http://tools.ietf.org/rfc/rfc5555.txt (Accessed: 2012). NS-2 homepage, http://www.isi.edu/nsnam/ns, (Accessed: 2012)

[7]

[8]

[9]

[10]

[11]

[12] [13]