serial number based ipv6 addressing architecture in a foreign ipv4 network

7/30/2019 Serial Number based IPv6 Addressing Architecture in a Foreign IPv4 Network

1/7

Serial Number based IPv6 AddressingArchitecture 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 fromthat in IPv6, each has its own set of standards, andthey 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 ad-dress 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 be-tween mobile nodes without changing their IP addresseswhile roaming from one network to another [4]. The basicrules in MIPv4 for processing and mobility managementare defined in specialized routers called Home Agent(HA) and Foreign Agent (FA) and in the node that haveto roam about called MN. For the purpose of mobility toachieve the mobile IP supports two addresses one ofwhich is permanent called Home Address (HoA) andanother 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

the HoA of the MN to its CoA. Mobility agents (HA andFA) keep records of this binding. If the correspondentnode (CN) wants to communicate with the MN, all thepackets will tunnel through the HA. The HA then for-wards packets to the MNs CoA using binding table formapping [4]. FA keeps records of the entire visiting nodesin the MNs visited/foreign network. FA and HA adver-

tise messages, called agent advertisement messages,through which they show their presence. On roaming theMN requests the FA for its CoA, and after getting theCoA it registers the temporary CoA with the HA. The HAthen forwards the packets encapsulating them with a newheader having CoA as the destination address. When theFA receives the tunneled packets it de-encapsulates theheader and forwards it to the MN [4].

Triangle routing is a major problem faced in the im-plementation of basic Mobile IP, where data communica-tion between CN and MN takes place through HA andFA and it appears when the indirect path between CNand MN through the HA is longer than the direct path

between them [1]. To solve the triangular routing prob-lem Internet Engineering Task Force (IETF) introducedMobile IP Rout Optimization, where communicationtakes place directly between communicating nodes.

In this mechanism the CN sends binding request mes-sages in order to know the current updates of the MN,and the MN send frequent binding update messages tothe CNs. Once the MN is registered with the CN, the CNtunnels the datagram destined to the MN directly usingits CoA and the MN also sent packets destined to CN us-ing its HoA [1].

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 oComputer 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 ComputerSciences, City University of Science & IT, Peshawar, Pakistan.

M

JOURNAL OF COMPUTING, VOLUME 4, ISSUE 10, OCTOBER 2012, ISSN (Online) 2151-9617

https://sites.google.com/site/journalofcomputing

WWW.JOURNALOFCOMPUTING.ORG 42


2/7

1.2 Mobile Internet Protocol version 6 (MIPv6)

As IPv4 is running out of address space, the ISPs are una-ble to allocate IPv4 addresses to the new connecting de-vices. Therefore the need for a new protocol version wasunavoidable and that is why in early 90s the IETF has todesign the next generation protocol called IPv6 [2]. TheInternet connectivity through 4G cell phones has already

fully deployed the IPv6 addressing structure. The wholeof the Internet is going through transition phase, whereIPv4 and IPv6 coexist in order to make the communica-tion possible between the nodes having configured thesetwo different kinds of address family protocols. Routersplay the mediation roll between the hosts of these twotypes of protocols [2].

MIPv6 relies on IPv6 is currently the standard for themobility problem, proposed by IETF, for nodes that haveto have roaming capability from network to network. Itenables the mobile devices to maintain its current ad-dresses and transport layer connections while roamingbetween different networks [4]. Unlike MIPv4, MobileIPv6 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 AutoConfiguration. The uniqueness of Stateless Auto Confi-gured address is verified through a mechanism calledDuplicate Address Detection (DAD). The MN then sendsthe binding update (BU) to the HA to register CoA [5].

The HA plays a role of stationary proxy, when MN isaway from its home network. The HA captures the pack-ets destined to the MN. It checks its binding list with thepackets destination address and tunnels the packets tothe MNs CoA. The MN can communicate directly to theCN 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 re-

views Problem Definition, Chapter 3 discusses the Re-lated Work on addressing architecture of MN in visitednetwork, Chapter 4 discusses the Proposed Solution ofIPv4 addressing in IPv6 network and finally Chapter 5Concludes the research developments.

2 PROBLEM DEFINITION

IP addresses and addresses of key servers such like Do-main Name Service (DNS) are the needed informationthat a node will be configured with, in order to establish

and maintain IP-level connectivity [1]. The two types ofIPv6 addresses are Link Local and Global IPv6 addresses,the former is used for communication to take place withinLAN, while the latter is used for communication to takeplace between two hosts across a wide area network. Fur-thermore the Global IPv6 address is of two types, Staticaddress and Dynamic address [7].

In Static address configuration, IPv6 address is as-signed manually by the system administrator and in thecase of Dynamic configuration the IPv6 address is confi-gured automatically. The two types of Dynamic IPv6 ad-dresses are Stateless and Stateful address. Address confi-gured from the default router in the LAN is called State-

less Address Auto-configuration and address configuredfrom the DHCPv6 Server is called Stateful Address Auto-configuration [8]. In the Stateless approach nodes selecttheir addresses themselves and then through a mechan-ism known as DAD verify their uniqueness. The IETFZero configuration protocol is an example of this ap-proach [9].

In another scenario when an IPv4 node moves from itshome network to a foreign/visited network then the nodeis assigned address through MIP, for IPv4 nodes, andMIPv6 in the case of IPv6 nodes. However a MN withIPv4 configuration cannot be restricted to roam only inIPv4 networks and similarly a MN having IPv6 configura-tion cannot be restricted to roam only in IPv6 networksi.e. IPv6 configured mobile users can visit IPv4 networksand IPv4 configured mobile users can visit IPv6 net-works, but the major challenge is how the node will beconfigured for making it able to roam into a different ad-dress family network e.g. IPv4 addressing in IPv6 addressfamily network and IPv6 addressing in IPv4 address fam-ily network [10].

Here we suggest a scenario in which an IPv6 confi-gured node moves from its home IPv6 network and visitsa foreign IPv4 network. According to Henderson [11],mobility causes some fundamental problems in the net-work layer. The first concern is IP Addressing,as for sca-lability purpose the IP routing and addressing are definedhierarchically; therefore the MNs usually have a topologi-cally incorrect interface address when they attach to anew network, and especially the problem becomes morechallenging when the home and foreign networks differin address family as in our case [11].

The second problem is that of location management,when changing network the MN may become unreacha-

ble to the rest of the network unless the new address issomehow mediated to other nodes, the challenge is howto mediate the address between the nodes located at dif-ferent address family networks. The third problem isabout the session management i.e. the current transportprotocols use the IP address as part of the connectionidentifier therefore the change of address causes breaks inactive connections [11].

3 RELATED WORK

3.1 IPv4 Addressing in IPv4 Visited Network

Mobil IP, an extension to IP, provides transparent mobilitysupport to MNs within the Internet. Mobile IP uses two IPaddresses HoA through which the MN is registered in HNand a CoA that changes each time the MN is attached to adifferent network. The CoA, usually provided by the FA,gives information of the current point of attachment of theMN. The FA is the default router of the MNs visited network.CoA must be informed to HA by sending a BU message fromMN, a HA is Usually the default router at the home networksof the MN that tunnels datagrams for delivery to the MNwhen it is away from home, and maintains current locationinformation for the MN [12].

Home agent is allowed to create a tunnel between thehome network of the MN and the MNs current point of at-





3/7

tachment. The datagrams tunneled by the home agent are de-tunneled and delivered to the MN by the FA. Instead of rely-ing on the home agent, binding updates allow the CN to tun-nel datagrams directly to the MN's CoA. With route optimiza-tion techniques, FA can assist the MN to affect smooth han-doffs, being careful not to drop any datagrams even when theMN has moved away from the care-of address receiving thedatagrams [12].

3.3 IPv4 addressing architecture in IPv6 network

This work designs an integrated system where Ipv6 net-work, provides services to both Ipv4 and Ipv6 mobileusers. An Ipv4 node is allowed to roam also to an IPv6network and there it gets configured with Ipv4 addresswithout any DHCP server. In the proposed integratedsystem, an IPv4 user B from IPv4 HN is assumed to roaminto IPv6 network. While being in the IPv6 network, B isreferred as B. It obtains an IPv4 address from a specialaddress range, 64.x.x.y/8 taken as an example, fixed forIPv4 addressing in IPv6 network [10].

Hexadecimal x, represents the first sixteen bits of the

IPv6 router address, is converted to decimal and is as-signed to the 9th to 24th bit position of the host part. Y isgiven a value from 0 to 254. This new 32 bit generatedIPv4 address is the CoA of the MN B and is referred to asP46A. After successful return of DAD it is recorded intov4 enabled Gateway table and is forwarded to the HAv4for registration. Hence the CNv4 and CNv6 can access theMN [10].

3.2 IPv6 addressing architecture in IPv4 network

It suggests a scenario in which IPv6 node while roamingfrom its home IPv6 network to a foreign IPv4 networkgets IPv6 address using IPv4 router address in that vi-

sited network, IPv6 Cryptographically Generated Ad-dress (CGA), and with little modification in the IPv6 site-local address format. While roaming from its home IPv6network, the mobile IPv6 node reaches an IPv4 networkwhere it gets IPv4 router solicitation message and fromthis message it gets the router address [3].

It converts this decimal address to hexadecimal formatand puts the address into 17th to 48th bit position of thenetwork part of its new IPv6 address. The first 16 bits areassigned as Format Prefix (here 1001) and the 49th to 64thbit position is assigned 0s. For the least significant 64 bits,MAC address goes through Hash function. This newlygenerated address is called CoA for the MN and is re-ferred as P46CGA.Whenever CN in IPv6 network (CNv6)

wants to communicate with IPv6 configured MNv6 itrequest the HAv6 for the MNv6 address. The HAv6 sendsit the CoA. From the information given in the CoA theCNv6 comes to know that the MNv6 is in an IPv4 net-work. So it extracts the 17th to 48th bit value and uses it inorder to locate and route the MN [3].

To sum up, the proposed scenario in the current litera-ture is scalable and yet relatively simple to track morethan 268 million mobile nodes on the same or differenttopological locations. The mechanism in [10] and [12] donot consider an IPv6 mobile user roaming into IPv4 ad-dress family network, while the one studied in [3] is rela-

tively closer to our proposed mechanism. But the ap-proach of getting IP address and especially integrating anoval approach of tracking the mobile nodes through the28-bits serial number embedded in the IPv6 care-of address is the major difference between the two proposedmechanisms. The current literature has a new, SerialNumber based IP address configuration mechanism fornetwork management, therefore makes decision regard-ing resource utilization/allocation tremendously easy ascontrary to [3].

4 PROPOSED SOLUTION

Currently IPv4 is the standard for communications overthe Internet. However, with the tremendous expansion ofthe Internet, IPv4 is proving to be incapable of handlingthe growth of the Internet expected in future [13]. IPv6 isthe emerging Internet Protocol for next generation net-working. It is not backward compatible with IPv4 andtherefore both of them have their own users and serviceproviders. In order to make communication possible be-

tween the two address family Protocols transition me-chanisms have been devised [14].This paper suggests a scenario in which a mobile node Bmoves from its home IPv6 network and visits a foreignIPv4 network, in the foreign network mobile node B isreferred as B`. While roaming B` gets IPv4 address fromthe default Gateway of the IPv4 network. In the followingsub-sections we describe the mechanism of configuring aserial number based IPv6 address from the IPv4 addressat the foreign network. Here we assume that B`, the HA athome IPv6 network and the default Gateway at the IPv4network are IPv4- and IPv6-enabled. Also we assume thatonly Mobile IPv4 is used between the mobile node,

V6/V4 Gateway and the HA at home IPv6 network, thescenario of proposed IPv6 Addressing Architecture(IP64S) in IPv4 Network is shown in Fig. 5.The proposed mechanism is able to be implemented im-mediately as the main components needed are; IPv6 Rou-ter which is already available in the IPv6 network, a newDHCPv6 server to be installed in IPv6 network andV6/V4 Gateway which is to be installed newly within thedefault Router of the IPv4 network, without the need ofadditional devices to be included with the existing infra-structure either into IPv6 or in IPv4 address family net-work.Though the addressing mechanism in our proposed sys-

tem slightly differs from that of the existing standard ad-dressing architecture, rest of the procedures remains thesame as existing standards. . Whole of the scenario in sig-naling form is depicted in the Fig. 1.The advantage of the proposed mechanism of using the28-bits serial number with combination of Gateways IPv4address in generating IPv6 CoA, is that it is easy to trackthe number of mobile nodes down at the home network,either they are located at the same foreign network ortopologically at different foreign networks. As a result:

As we have information of Serial number and in-formation of IPv4 topological address in hand,we get topology based information of the mobile





4/7

nodes Decision of resource allocation to all the mobile

nodes going out of a network, as a whole as wellas per topology based becomes possible

It is possible to track the number of active mobilenodes down, went out of a network as a whole aswell as per topology based with respect to com-munication

4.1 Agent Discovery and IPv6 Addressing in IPv4Network

Whenever B moves to the IPv4 network, using agentdiscovery protocol, it attempts to discover IPv4 Gatewayin the IPv4 network [15]. In the foreign IPv4 network theMN B is referred as B`. B` discovers the IPv4 default Ga-teway from the foreign agents periodically advertisedmessages on the network or it may also broadcast anagent solicitation message onto the visiting network toask the agent for advertisement [16][17].

The default Gateway responds by sending its IPv4 ad-dress (here 123.55.77.69) in the agent advertisement mes-sage to the requesting MN. When B` gets the agent adver-

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

4.2 Discovering the Care-of Address

When the MN moves to the foreign IPv4 network, itneeds to get a CoA. The CoA first needs a Serial numberin our proposed mechanism. In order to get a 28-bits Seri-al number from the DHCPv6 server the MN provides itsHAs IP address (2001:d02:0:0::95) to the V6/V4 gateway.The V6/V4 gateway forwards the query to the HA whichin turn gets it from the DHCPv6 at home network andforwards it to the V6/V4 gateway. The 28 bits serialnumber in hexadecimal format (000 000B) is assignedfrom 5th to 32nd bit position of the new IPv6 address. Inorder to get gateways IPv4 address, once a second or

Fig. 1. Signaling diagram for Proposed System.





5/7

once every few seconds, is the regular interval of time, themobility agents broadcast their agent advertisement mes-sages, or in an alternate mechanism MN can broadcast a

solicitation request message that will be answered by thedefault Gateway and thus it gets the gateways address[17][19] ], the format of the address scheme in IPv4 net-work is shown in Fig. 3.

The 32-bits IPv4 router address (123.55.77.69) that is indecimal format is first converted into hexadecimal format(7B37 4D45) and then it is assigned from 33rd to 64th bitsposition of the network part of the IPv6 address. The first4-bit is assigned as Format Prefix (FP) that has not beenreserved by other types of IPv6 address and we considerthe format prefix as 0100/4 or 4 in hexadecimal, here werefer 4 as MNs IPv6 CoA generated from an IPv4 addressin an IPv4 network. Through agent solicitation messagesthe 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` be-gins to hunt for new CoA using again either of the follow-ing two methods, it may choose to wait for another agentadvertisement or it may send an agent solicitation mes-sage to the network [17][20].

IPv6 node B` reuses the 64-bits interface identifier(0123 4567 89AB CDEF) that was assigned by DHCPv6

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

MAC address and HA address is recorded into V6/V4Gateway Table shown in Fig. 4, while B` sends a BUmessage to its HA.

The reason why we select IPv4 router address is thatwhenever a packet is transmitted to this IPv6 MN, look-ing into the 33rd to 64th bit value and by converting thisinto IPv4 decimal notation, the location of the mobilenode can easily be identified and routed to the correctlocation in order to minimize the routing and packetprocessing delay.

4.3 Registration and Redirection of Packets

On moving the MN from home IPv6 network to theforeign IPv4 network, the newly generated IP64S address(i.e. 4000:000B:7B37:4D45:0123:4567:89AB:CDEF) is firstregistered with the HA at the home IPv6 network. In or-der to register with the V6/V4 Gateway at foreign net-

work, B` provides its HAs IP address to the V6/V4 Ga-teway. The Gateway forwards the request for registrationto the HA. When the HA accepts the request, it begins to

associate the HoA of the B` with its newly generatedIP64S, and maintains this association until the registrationlifetime expires [17].

The HA then replies to the V6/V4 Gateway, who inturn forwards the reply to B`. During the registrationlifetime B` must refresh its registration to continue to re-ceive service. B` deregisters with the HA on returningback to its home network. To get a packet from IPv6 net-work to the B`, the CN first delivers the packet to B` using

Fig. 4. V6/V4 Gateway table.

Fig. 3. IP64S Address Scheme in IPv4 Network.

Fig. 2. IPv6 and IPv4 Integrated Network.





6/7

its HoA, the HA gets the packet as it act a role of proxyfor mobile node B` [17][21]. From the first 4-bits formatprefix number (0100/4), the HA comes to know that theMN is in IPv4 network, thus it extracts 33 rd to 64th bitsposition value of the IP64S, converts it into decimal nota-tion, the scenario is depicted in Fig. 5 below.

The HA redirect packets, using this 32-bits addressfrom the home IPv6 network to B` by constructing a newIP header. This new IP header contains the 32-bits adressas the destination address shielding or encapsulating theoriginal packet having B` HoA as the destination address.

It causes home address of B` to have no effect on therouting of the encapsulated packet until it arrives at theV6/V4 Gateway. Such encapsulation/tunneling causesfor efficient and hierarchical delivery of packets to B`. The32-bits address extracted from IP64S is used as the desti-nation IP address in the new tunnel header and HAs IPaddress is used as the tunnel source IP address. In orderto recover the original packet the V6/V4 Gateway neededonly to eliminate the tunnel header and then it deliversthe rest to B` [17].

5 CONCLUSION

Since IPv6 is not extensively deployed, it is unlikely thatmobile nodes (MNs) will primarily use only IPv6 ad-dresses for the means of their communication [22]. It isreasonable to assume that MNs will, for a long time, needan IPv4 HoA that can be used by upper layers of the pro-tocol stack [23].It is also reasonable to assume that MNs will roam aboutto networks that might not support IPv6 protocol stack

and would therefore need the capability to support anIPv4 address family protocol [23]. The paper is about aMobility Management Solution for an IPv6 Node in aForeign IPv4 Network. It proposes a new technique toconfigure an IPv6 MN roaming in IPv4 network with aSerial Number based IPv6 address obtained from theV6/V4 Gateways IPv4 address and adding a SerialNumber to generate the 128-bits CoA.When the MN gets the agent advertisement message itregisters with the HA and uses the 128-bits newly gener-ated address based on V6/V4 Gateways IPv4 address asits CoA. We select the IPv4 address of the V6/V4 Gate-way to generate the CoA because MNs location can easi-

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





7/7

ly be identified whenever a packet is transmitted to it.Also the routing and packet processing delay can be re-duced whenever the CN sends packets to the MN. Fur-thermore the proposed mechanism is able to be imple-mented immediately, as only V6 enabled IPv4 router isthe new deployment which is to be installed within theIPv4 default Router at the IPv4 network. As a futurework, the performance of the proposed mechanism willbe evaluated using NS-2 [24] simulator.

REFERENCES

[1] N. Jaggi, Koushik, "Distributed authentication mechanism for

mobile IP route optimization," presented at the IEEE Interna-

tional Conference on Wireless Networks, Communications and Mo-

bile Computing, Maui, Hawaii, USA, pp. 1271-1276 (June 2005).

[2] G. Jivika, J. Govil, Navkeerat Kaur, Harkeerat Kaur, "An ex-

amination of IPv4 and IPv6 networks: constraints and various

transition mechanisms," presented at the IEEE Region 3 Hunts-

ville Section (IEEE SoutheastCon 2008), Huntsville, Alabama,

USA, pp. 178-185, (April 2008).

[3] Rabara S.A., Jayanthi J.G., "IPv6 addressing architecture in IPv4network," presented at the Second International Conference on

Communication Software and Networks, Singapore, Singapore, pp.

461-465, (Feb. 2010).

[4] T. M. Mahmoud, M. R. Girgis, Youssef S. T., H. S. Hassan, "Per-

formance evaluation of a new route optimization technique for

mobile IP," International Journal of Network Security & Its Applica-

tions, vol. 1 ( 3), pp. 6373, (October 2009).

[5] P. Shalini, K.Sankaranarayanan, B. Sakthi "Comparative study

of secured optimized route in MIPv6," Proceedings of the Inter-

national Journal of Computer Science and Network Security, vol. 8,

pp. 377 382, (November 2008).

[6] APNIC, Geoff Huston, "IPv4 address depletion and transition

to IPv6," Internet Protocol Journal, vol. 10 ( 3), pp. 18-28 (Septem-

ber 2007).

[7] Jivesh Govil, Jivika Govil, On the Investigation of Transaction-

al and Interoperability Issues between IPv4 and IPv6, pre-

sented at the IEEE Electro/Information Technology Conference,

Chicago, USA, pp. 604-609, (17-20 May 2007).

[8] Dongkeun Lee, Jaepil Yoo, Keecheon Kim, Kyunglim Kang,

IPv6 Stateless Address Auto-configuration in Mobile Ad-hoc

Network (TDAD) and Performance Evaluation, ACM Proceed-

ings of the 2nd ACM international workshop on Performance evalua-

tion of wireless ad hoc, sensor, and ubiquitous networks, Montreal,

Quebec, Canada, pp. 271-272, (October 2005).

[9] Mesut Gunes, Jorg Reibel, An IP Address Configuration Algo-

rithm for Zeroconf. Mobile Multi-hop Ad-Hoc Networks, Pro-

ceedings of the International workshop on Broadband wireless Ad-hoc networks and services, Sophia Antipolis, France, (Sept 2002).

[10] 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, Chi-

na, pp. 282-287, (March 2010).

[11] Henderson, Ahrenholz, Kim, J., Experience with the Host

Identity Protocol for Secure Host Mobility and Multihoming,

Proceedings of the IEEE Wireless Communications and Network-

ing, pp. 2120-2125, (March 2003).

[12] Perkins, C., "IP Mobility Support", RFC 2002, October 1996.

[13] Yong Feng, Zhongfu Wu, Jiang Zhong, Chunxiao Ye, Kaigui

Wu, Novel Authentication Mechanism Based on CGA for BU

Message Disposal in Mobile IPv6, Proceedings of the Interna-

tional Conference on Networking, Architecture, and Storage, pp.

137-143, (June 2008).

[14] E. Karpilovsky, Gerber, A., Pei, D., Rexford, J., Shaikh, A.,

"Quantifying the extent of IPv6 deployment," in Passive and Ac-

tive Measurement, PAM 2009, Springer Berlin/ Heidelberg, isbn:

978-3-642-00974-7 (March 2009).

[15] 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.

[16] 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).

[17]Johnson, D., Perkins, C., and Arkko J. Mobility Support in

IPv6, http://tools.ietf.org/rfc/rfc3775.txt, (Accessed: 2012).

[18] K. Ren, W. Lou, K. Zeng, F. Bao, J. Zhou, and R. H. Deng,

Routing optimization security in mobile IPv6, Computer Net-

works, vol. 50, pp. 24012419, (2006).

[19] Davies, J., Understanding IPv6, Microsoft Press, Redmond,

WA, (2003).

[20] D. Malone, "Observations of IPv6 addresses," Proceedings of

the Passive and Active Network Measurement Conference, Vol.

4979, pp. 2130, (2008).

[21]Jong-Hyouk Lee and Tai-Myoung Chung, A Traffic Analysis

of Authentication Methods for Proxy Mobile IPv6, Proceed-

ings of the International Conference on Information Security and

Assurance 2008, Busan, pp. 512-517, (April 2008).

[22] Geoff Huston, Telstra, IPv4: How long do we have?... Internet

Protocol Journal, Vol. 6 (4), pp. 2-15,( 2003).

[23] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and

Routers", http://tools.ietf.org/rfc/rfc5555.txt (Accessed: 2012).

[24] NS-2 homepage, http://www.isi.edu/nsnam/ns , (Accessed: 2012)




serial number based ipv6 addressing architecture in a foreign ipv4 network

Documents