Study of packet level UDP performance of NAT44, NAT64 and IPv6 using iperf in the context of IPv6 migration

Vitruvius John D. Barayuga William Emmanuel S. Yu Institute of Computing Studies Department of Information Systems and Computer Science Ilocos Sur Polytechnic State College Ateneo de Manila Univeristy Santa Maria, Ilocos Sur, Philippines Quezon City [email protected] [email protected]

Abstract— The Internet Assigned Number Authority (IANA) The initial design specification did not take into account the allocated the last of the available /8's of the IPv4 address space to need for the protocol to handle video-on-demand services, or the Regional Internet Registries (RIR's) on February 2011. It other types of large scale data, also with the advent of mobile could not be denied that IPv6 is the Internet of the next communications, set top boxes that have internet access taking generation, however its utilization and implementation in a wide presence in the home, each device requires an IP address, each scale had brought hesitation to the users since it will take time device requires an IP address. and there are concerns that need to be explored in the future. However, the need for a new technology is not paramount; Hence, this paper will lead the way for the acceptance of Internet the current 30-year-old technology has been modified to Protocol version 6 (IPv6) migration in the Philippines using a coincide with new ideas and ways of working. For a similar Network Address Translation (NAT) that there is an sustainable network to be developed and evolve over the next apparent means to be taken into consideration and NAT IPv6 to IPv4 (NAT64) can be a good choice for computer networks with few years a seamless migration over to IPv6 needs to be made. the similar situation like the Philippines which is behind NAT44, It would be foolish to believe that this could be done overnight showing service providers and institutions in putting NAT64 as a in the infrastructure of the Internet along with the associated viable option to be used. Therefore it is concluded, where overall cost of upgrading hardware and software [2]. IPv6 was performance revealed that IPv6 and NAT64 network offered developed to solve the problem of IPv4 depletion. The question better performance against the NAT44 network in almost all of is, are we ready to replace the dotted decimal IP to a new the metrics in the iperf generic UDP mode test. For time transfer, address scheme? Aside from the evident change in addressing IPv6 had 19% less and NAT64 with 31% less where both scheme, the change will not be felt by normal user, this burden executed the transfer in a lesser time compared to NAT44 will fall upon network engineers and administrators. But the networks with 48% which is longer than the results of the change are even better, aside from limitless address space (32- aforementioned networks. In the bandwidth utilization, it is bit address to 128 bit address). presented that IPv6 network had 43% and NAT64 network with This paper aims to embolden NAT44 networks to take the 41% offered better bandwidth utilization as compared to NAT44 challenge or even taking the small step to prepare and switch to network with 15%. IPv6 network had 49% showed faster IPv6 by considering the idea of using NAT64 as a suitable transfer rate along with NAT64 network with 39% in transition mechanism to take the place of the current NAT44 comparison to the NAT44 network with only 10% transfer. For networks. The need of the hour has now come, it is to enable jitter, IPv6 network had lesser average with 28% and so with IPv6 capabilities on all existing networks. NAT64 network with 31% compared to NAT44 with 40% jitter which is a quite bigger than the other experimental networks. II. RELATED WORK For packet loss, IPv6 network had 26% and NAT64 network This section contains literature and studies, reviewed by the with 33% compared to NAT44 network that had 40% bigger than the other experimental networks. researcher, which have been found relevant to this paper. The discussion focuses on IPv4 Depletion, IPv6 Migration Keywords—IPv6 migration, NAT44, NAT64, IPv6 transition Techniques as well as pertinent information that could be mechanism useful in the experimental network environments.

I. INTRODUCTION A. IPv4 Depletion IPv4 has been the networking protocol of the Internet since The IPv4 depletion is now at hand. IANA has just recently the 1970s. The 32-bit protocol which provides 4.3 billion allocated the last five /8 blocks of unassigned IPv4 addresses to the world’s five RIR’s [1]. Some networks are still hiding unique IP addresses for the Internet users for more than 30 inside NAT. It has been and still present in many networks in years is nearing its expiration date. Hidden from the view of the Philippines, though it has lengthened the life of IPv4 for typical users, every Internet communication relies on an several year, but is not actually the solution. This is where IPv6 underlying system of numbers to identify data sources and comes to action, the next generation to replace destinations. Users typically specify online destinations by IPv4. This research came about to show a clear path to IPv6 entering domain names (e.g. "congress.gov"). But the migration. The use of IPv4 has changed dramatically over the Internet's routers forward data according to numeric IP last 30 years, and the protocol was never designed to deal with addresses (e.g. 140.147.249.9). To date, the Internet has the stress and strains it has to endure over the last few years. enjoyed an ample supply of "IPv4" IP addresses, but demand Manuscript received July 15, 2014; acceptance August 27, 2014. This work was supported in part by the Commission on Higher Education of the Philippines and the University of the Cordilleras, Baguio City, Philippines.

978-1-4799-6541-0/14/$31.00 ©2014 IEEE is substantial and growing. Current allocation rates suggest performance comparison regarding latency and packet loss, IPv4 exhaustion by approximately 2011 [3]. been discussed in [11]. IPv6 addresses inherent problems in the earlier version protocol and it provides new opportunities B. IPv6 Migration Techniques too. However, due to the increased overhead in IPv6 and its This section contains review of the papers and articles that interaction with the operating system that hosts this are relevant to IPv6. The following gave more than the basic communication protocol, there may be network performance information needed about the next generation protocol and the issues such as bandwidth and jitter performance comparison migration strategies currently available. A more detailed which was discussed in [12]. As discussed from the paper by account on what companies should do in preparation for IPv6 Llanto [13], the study was done through live laboratory migration was suggested in the article by Steve Harris [4]. network tests using NAT44, NAT64 and IPv6 technologies to These strategies are divided into three (3) types namely: 1) show that NAT64s performance is comparable to current Dual-stack mechanisms; 2) Tunneling techniques and 3) NAT44 networks with application testing on HTPP requests Translation techniques. scenario using apachebench which is a Hypertext Transfer The migration of IPv6 had not gone well as planned not Protocol (HTTP) server benchmarking tool. only within the Philippines but on several countries using On other hand, this study focused on the experimental NAT44 as well. There are lots of networks which are still network tests using NAT44, NAT64 and IPv6 technologies to using IPv4 and have not made any move to switch to IPv6. In show that NAT64 performance is comparable to current order to boost IPv6 adoption, NAT for IPv6 has been taken NAT44 networks through a load test scenario for the generic into consideration so that IPv4 and IPv6 networks can be UDP traffic by the use of iperf including factors on time connected. Several of these NAT solutions have been transfer, bandwidth, transfer rate, jitter and packet loss using proposed and these are discussed in [5]. different sets of payload size and concurrency level. Some of the most popular research topics over the past years was using NAT-PT for IPv6. An implementation of a III. METHODOLOGY NAT-PT gateway for IPv6 and IPv4 is discussed in [6] and a The purpose of this paper is to encourage other NAT44 research on how to design and realize the translation gateway networks to move to IPv6 using a possible option which is based on NAT-PT technology in detail, it compares various NAT64. In order to accomplish the paper, an experimental current transition technologies and points out that NAT-PT network had been done. Prior to the experimental networks technology is a more feasible project to carry out the transition using NAT44, NAT64 and native IPv6 had been configured to from IPv4 network to IPv6 network on the present stage [7]. test the viability of the research. Llano [13] mentioned in this paper that the Philippines and A. Procedures other market dependent and behind NAT would consider The following experimental network set-ups were created: NAT64 as a viable option to implement IPv6 within current NAT44, native IPv6 and NAT64. To evaluate the NAT44 networks as the start of the adjustment in accepting experimental networks iperf was used in the generic UDP the next generation of the internet protocol which is IPv6. mode. Each of the NAT44, NAT64 and IPV6 network was This paper used NAT64, which is another NAT translation executed in load test scenario with payload of 100 MB, 500 mechanism for IPv6 which allows IPv6 clients to get MB and 1000 MB sent to the server along concurrency levels connected to IPv4 servers. The NAT64 mechanism was based of 1, 10, 20 and 30 with sets of permutation. During this on the NAT-PT technology and it is discussed in [8]. An process the researchers noted the steps to configure and the example of a NAT64 implementation is TAYGA and Ecdysis. necessary data needed out form the experiment. The data Both are open source implementation of network address obtained during this phase can be useful considerations for translation 6 to 4 or NAT64. NAT64 technology is a other NAT44 networks with the intention of using IPv6 or mechanism that translates IPv6 packets to IPv4 packets and NAT64. This is the vital step that leads the way to IPv6 vice versa. An example of DNS64 implementation is BIND, migration in the Philippines. After completion of the IPv6 and DNS64 [9] performs synthesis of AAAA records from A NAT64 experimental network, data measurements were records. These two mechanisms work together to enable gathered from the networks. All of the data gathered from the client-server communication between an IPv6-only clients to IPv6 and NAT64 experimental networks was then compared an IPv4-only server, without requiring any modifications to to the data taken from the NAT44 experimental network. the nodes. For the research, we used Jool [10], another NAT64 implementation, it was selected over Ecdysis and TAYGA, it B. Software Tools and Daemons was chosen for its ease of configuration and implementation This section provides the software tools and daemons used over [10]. for the NAT44, NAT64 and IPv6 experimental networks. C. Network Performance Evaluation 1) IPtables - Iptables is a powerful firewall built into the Network performance had been a concern in migrating to Linux kernel and is part of the netfilter project. It can be the next generation protocol. In this section, various configured directly, or by using one of the many frontends and researches will be discussed regarding comparison on GUIs. IPtables is used for IPv4 and ip6tables is used for IPv6 performance on different networks. Comparison on the better [14]. performing path over IPv4 versus IPv6, they’ve done a 2) RADVD - The advertisement daemon (radvd) is run by Linux or BSD systems acting as IPv6 routers. It sends Router Advertisement messages, to a local LAN periodically and when requested by a node sending a Router Solicitation message. These messages are required for IPv6 stateless auto configuration [15]. 3) Jool NAT64 - Jool is an Open Source implementation of a stateful NAT64 on Linux. An implementation for Linux Fig. 4. Logical Diagram of the NAT64 experimental network of RFC6146 (stateful NAT64), developed by Monterrey D. NAT44 Network Institute of Technology (ITESM) and NIC Mexico. . It is intended to comply perfectly with the RFC. A stateful NAT64 In the experimental NAT44 network, IPtables were used to perform NAT and routing. BIND was used to perform the has a pool of IPv4 addresses to work with [16]. (DNS) service to provide access to the 4) Berkeley Internet Name Daemon (BIND) - It is the webserver. To test the experimental set-up, Iperf was used to most widely used Domain Name System (DNS) software on evaluate the performance of the network in terms of time the Internet. On Unix-like operating systems it is the de facto transfer, bandwidth, transfer rate, jitter and packet loss. Figure standard [17]. 2 shows the setup of the NAT44 experimental network. 5) Iperf - It is a tool used to measure maximum TCP bandwidth, allowing the tuning of various parameters and E. IPv6 Network UDP characteristics. Iperf metrics in TCP are namely: time Router Advertisement Daemon (RADVD), the main transfer and transfer rate while UDP metrics are namely: time requirement for the experimental native IPv6 network, was transfer, transfer rate, bandwidth, jitter and packet loss [18]. used to provide IPv6 addresses to the clients. Since all clients would fall under the same network by using RADVD, routing C. Experimental Networks was no longer needed. To test the experimental set-up, Iperf For the Experimental networks, iperf was used to send was used to evaluate the performance of the network in terms payload of 100, 500 and 1000 all in MB along 1, 10, 20 and 30 of time transfer, bandwidth, and transfer rate, jitter and packet concurrency levels. Figure 1 shows the general set-up for the loss. Figure 3 shows the setup of the IPv6 experimental experimental networks. network.

F. NAT64 Network Setting-up IPv6 NAT64 requires IPtables, RADVD and Jool to be used. The IPtables were used to connect the IPv4 external network to the IP addresses to be used by Jool, the NAT64 daemon. RADVD was used to provide IPv6 addresses for the IPv6 clients. To test the experimental set-up, Iperf was used to evaluate the performance of the network in terms of time transfer, bandwidth, and transfer rate, jitter and packet Fig. 1. Experimental Set-up for NAT44, native IPv6 and NAT64 loss. Figure 4 shows the setup of the NAT64 experimental network. G. Materials and Instruments The setup of the NAT44, NAT64 and IPv6 was implemented using Linux based system. This was decided to be used to be economical in the setup. Iperf, was used to test the experimental network under different simulated network conditions through a generic UDP mode of test with payload Fig. 2. Logical Diagram of the NAT44 experimental network conditions of 100, 500 and 1000 sent to the server along concurrency levels of 1, 10, 20 and 30 with sets of permutations. The test was done in each of the NAT44, NAT64 and native IPv6 network. All of the data then were collected from the server and tabulated and analyzed after the experiments. The overall average and percentage was used to compare the data gathered from iperf on the NAT44, NAT64 and IPv6 network experiments. The experiment was done during the availability of the computer laboratory at Ilocos Sur

Fig. 3. Logical Diagram of the IPv6 experimental network Polytechnic State College due to the reason that summer classes were scheduled from months of March up to May where students use the computer laboratory often times. IV. RESULTS d) Jitter - The performance of NAT64 and IPv6 is shown in Figure 8. They are significant with each other. Jitter A. Summary of Iperf Generic UDP test results performance requires lesser rate. It was revealed that IPv6 is This section shows Iperf Generic UDP test results presented in 28% less compared to NAT64 which is 31%. graphs. e) Packet Loss - NAT64 and IPv6 packet loss is shown 1) NAT44 vs. NAT64 in Figure 9. Packet loss which requires lesser rate, IPv6 is 26% a) Time Transfer - For time transfer, the difference less compared to NAT64 which is 33%. between NAT44 and NAT64 is shown in Figure 5. NAT64 is 31% lesser in time transfer than NAT44 which had 48%. b) Bandwidth - NAT44 and NAT64 bandwidth utilization is shown in Figure 6, wherein NAT64 utilized 41% compared to NAT44 which utilized 15%. c) Transfer rate - NAT44 and NAT64 transfer rate shown in Figure 7, where NAT64 is faster in 39% than NAT44 which is 10%. d) Jitter - The performance of NAT64 and NAT44 shown in Figure 8 are significant with each other, which requires lesser jitter. Jitter performance of NAT64 is 31% less compared to NAT44 which is 40%.

e) Packet Loss - Figure 9 shows that packet loss Fig. 5. Time transfer difference of the NAT44, NAT64 and IPv6 experimental requires lesser rate wherein NAT44 had bigger packet loss network compared to NAT64. NAT64 had 33% only compared to NAT44 which had 40%. 2) NAT44 vs. IPv6 a) Time Transfer - Figure 5 shows the difference between NAT44 and IPv6 in terms of time transfer. IPv6 is 19% less compared to NAT44 which had 48%. b) Bandwidth - The performance of IPv6 and NAT44 are significant with each other as shown in Figure 6 where bandwidth requires to be bigger. The bandwidth performance of IPv6 is 43% compared to NAT44 which is 15%. c) Transfer rate - Figure 7 shows the difference between NAT44 and IPv6 in terms of transfer rate. IPv6 is faster which had 29% than NAT44 which is 10%. Fig. 6. Bandwidth difference of the NAT44, NAT64 and IPv6 experimental d) Jitter - NAT44 vs. IPv6 jitter performance in Figure 8 network where jitter requires less, IPv6 is 28% less compared to NAT44 which is 40%. e) Packet Loss - Figure 9 shows the difference between NAT44 and IPv6 in terms of packet loss, wherein it requires lesser loss. IPv6 is 26% lesser in packet loss than NAT44 which is 40%. 3) NAT64 vs. IPv6 a) Time Transfer - For time transfer which requires lesser time, the difference in between NAT64 and IPv6 is shown in Figure 5. IPv6 is 19% lesser in time transfer than NAT64 which is 31%. b) Bandwidth - Figure 6 reveled that IPv6 utilized 43% compared to NAT64 which utilized 41%. This means that Fig. 7. Transfer rate difference of the NAT44, NAT64 and IPv6 experimental IPv6 is better than NAT64. network

c) Transfer rate - The difference between NAT64 and IPv6 in terms of transfer rate is shown in Figure 7. It was revealed that IPv6 is faster in 49% than NAT64 which is 39%. NAT44. Rather than waiting for the IPv6 adaptation to happen, this paper reveals the way for the acceptance of Internet Protocol version 6 (IPv6) migration in the Philippines using a similar Network Address Translation (NAT) that there is an apparent means to be taken into consideration and NAT IPv6 to IPv4 (NAT64) can be a good choice for computer networks with similar situation like the Philippines which is behind NAT44, showing service providers and institutions in putting NAT64 as a viable option to be used. In summary, in terms of iperf results in the generic UDP mode test on time transfer, bandwidth utilization and transfer rate, as a general result, NAT64 and IPv6 networks fared a lot better compared to NAT44 networks. It might be because IPv6

Fig. 8. Jitter difference of the NAT44, NAT64 and IPv6 experimental network is simpler in packet structure compared to the IPv4 packet and this might be due to the bigger overhead constraints of IPv6. In terms of time transfer difference, IPv6 network together with NAT64 network had better performance against NAT44 network. Time transfer requires lesser time which is understood to be faster wherein IPv6 network is 19% less and NAT64 network is 31% less than NAT44 network with 48%. Bandwidth utilization result of IPv6 network is about 43% and NAT64 network is 41% which is a lot better despite of higher bandwidth utilization compared to NAT44 network which is 15% in bandwidth utilization. For transfer rate which requires substantial rate, IPv6 network with NAT64 network fared well against the NAT44 network. Since a bigger time is required for time transfer wherein IPv6 network is 49% and NAT64 network is 39% compared to NAT44 network with only 10% of transfer rate. Fig. 9. Packet Loss difference of the NAT44, NAT64 and IPv6 experimental network The difference in jitter performance where bigger results means poor performance wherein IPv6 is 28% and NAT64 is Table I shows the summary of the UDP test results 31% compared to a bigger result on NAT44 network with between NAT44, NAT64 and IPv6 experimental networks. It 40%. can be seen that IPv6 and NAT64 performed well compared to In terms of packet loss performance difference where NAT44. bigger results means poor performance where IPv6 network had 26% less and NAT64 network had 33% less compared to TABLE I the NAT44 network with 40% loss. SUMMARY OF THE IPERF UDP TEST RESULTS OF NAT44, NAT64 Overall performance is then been perceived that IPv6 AND NATIVE IPv6 network and NAT64 network offered better performance against the NAT44 network in almost all of the metric results NAT44 NAT64 IPv6 in the iperf generic UDP mode test. Metric Unit Average Average Average B. Conclusion Time 1420.148 910.4224 580.9093 seconds Based from the findings of this study, it is therefore Bandwidth 24.12628 63.36266 66.87149 mbits/sec concluded that IPv6 network and NAT64 network offered Transfer 5.569533 20.19766 25.16149 Mbytes better performance against the NAT44 network in almost all Jitter 1.634948 1.26528 1.178391 ms of the metrics in the iperf generic UDP mode test. For time Packet loss 0.0001322 0.000109 8.51556E-05 percent transfer, IPv6 had 19% less and NAT64 with 31% less where both executed the transfer in a lesser time compared to NAT44 V. CONCLUSION networks with 48% which is longer than the results of the aforementioned networks. In the bandwidth utilization, it is A. Summary presented that IPv6 network had 43% and NAT64 network Since there are still certain concerns in the implementation with 41% offered better bandwidth utilization as compared to of IPv6 in wider scale which are yet to be explored in the NAT44 network with 15%. IPv6 network had 49% showed future. Everyone knows that IPv6 is the Internet of the next faster transfer rate along with NAT64 network with 39% in generation where it is advisable to prepare for it. The benefits comparison to the NAT44 network with only 10% transfer. of IPv6 overshadow the loss that hinder us from using any of For jitter, IPv6 network had lesser average with 28% so with the translation techniques in replacement to the current NAT64 network with 31% compared to NAT44 with 40% jitter which is a quite bigger than the results other [9] M. Bagnulo, A. Sullivan, P. Matthews and I. van Beijnum, "DNS64: experimental networks. For packet loss, IPv6 network had DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers". April 2011. [Online]. Available: 26% and NAT64 network with 33% compared to NAT44 http://tools.ietf.org/html/rfc6147. Accessed January 10, 2014 network that had 40% bigger than the other experimental [10] Monterrey Institute of Technology (ITESM) and NIC Mexico, "Jool is a networks. stateful NAT64 for Linux". 2012. [Online]. Available: The full IPv6 implementation is still in its early step and http://jool.mx/index.html. Accessed January 10, 2014 more research will be beneficial to the future Internet and this [11] Arthur Berger and Akamai Technologies, "Working Paper on Comparison of Performance over IPv6 versus IPv4 ". March 29, 2011. makes perpetuation strategy more essential. NAT64 and other [Online] Available: IPv6 transition mechanism is a very prevailing topic that could http://www.caida.org/workshops/isma/1202/slides/aims1202_acox_supp be an important part of the next generation of the internet yet lement.pdf. Accessed January 10, 2014 to come. To the future researchers who might be interested to [12] Savita Shiwani, G.N. Purohit and Naveen Hemrajani, Performance undertake a study on NAT64 as a transition mechanism, Analysis of IPv4 v/s IPv6 in Virtual Environment using UBUNTU, IJCA Proceedings on International Conference on Computer following recommendations are proposed: Communication and Networks CSI-COMNET-2011 , vol comnet - 1 , 1) To perform and learn more about the limitations on a no 1, p.86 – 91 larger size of network which could show an improved [13] Kenneth Joachim O. Llanto and William Emmanuel S. Yu, Performance comparison on NAT44 and NAT64 networks, it might show a of NAT64 versus NAT44 in the context of IPv6 Migration , Proceedings of the International Multi-Conference of Engineers and Computer more detailed comparison in a larger network traffic. Scientist 2012, vol I 2) To test in the use of many IP Address along with quite [14] Iptables, “Linux Networking Iptables” .[Online]. Available: larger payload and concurrency for the experimental network, https://wiki.archlinux.org/index.php/iptables. Accessed December 27, in order to come up with different behavior of scenarios in the 2013 [15] Pekka Savola, “Router Advertisement Daemon” .[Online]. Available: experiments of the NAT44, NAT64 and IPv6. http://www.litech.org/radvd/. Accessed December 28, 2013 3) Ongoing and future research area that we will embark [16] Jool NIC Mexico – “Jool NAT64 Impementation” .[Online]. Available: on a test scenario which involves a test-bed with a multi https://www.jool.mx/. Accessed December 29, 2013 service router and live experiment of NAT44, NAT64 and [17] BIND, “BIND DNS” .[Online]. http://en.wikipedia.org/wiki/BIND. IPv6 in virtual clouds for network performance test. .[Online]. Available:Accessed December 29, 2013 [18] IPERF, “Networking with iperf” .[Online]. Available: http://openmaniak.com/iperf.php. Accessed December 29, 2013 ACKNOWLEDGMENT

The authors wish to express their gratitude to Dr. Rafael B. Vitruvius John D. Barayuga The author received B.S. Querubin, the SUC President of Ilocos Sur Polytechnic State degree in Information Technology from Ilocos Sur College, Santa Maria, Ilocos Sur, Philippines, together with Polytechnic State College, Santa Maria, Ilocos Sur Philippines in 2005 and M.S. degree in Information his administrative staff and the research head of ICS Technology from Don Mariano Marcos Memorial State department for their collaboration in this research. University, San Fernando City, La Union Philippines in 2010, respectively; He takes interest in computer programming and computer networking. REFERENCES He has worked in the academe for over 10 years. He is currently an [1] Potaro Website, “IPv4 Address Report”. [Online]. Available: Instructor and Executive Assistant of the President for ICT of Ilocos Sur http://www.potaroo.net/tools/ipv4/. Accessed July 5, 2014 Polytechnic State College, Philippines. Current research interests include [2] S. H. Gunderson, “Global IPv6 statistics - Measuring the Current State Computer Networking and Software Development. of IPv6 for Ordinary Users”, Google White Paper, 2008 William Emmanuel S. Yu The author received B.S. [3] Benjamin Edelman, Running out of numbers: Scarcity of IP addresses degree in computer engineering and B.S. degree in and what to do about it. Springer Berlin Heidelberg; ed, Vol . 14.2009. Physics, M.S. and Ph.D. degrees in Computer Science [4] Steve Harris, "IPv6: Coming Soon to a Network Near You", January 31, from the Ateneo de Manila University, Quezon City, 2011. [Online]. Available: Philippines; respectively. He currently serves as a http://www.cedmagazine.com/articles/2011/01/ipv6%3A-coming-soon- faculty member at the Ateneo de Manila University's to-a-network-near-you. Accessed January 10, 2014 Computer Science department and the Asian Institute of [5] David Geer, "Technology News," Computer, vol.41, no.10, pp.16,19, Management. At present he is a Senior Vice President Oct. 2008 for Technology and Chief Technology Officer at Novare Technologies, [6] Xiaoyu Zhao; Yan Ma, "Linux based NAT-PT gateway responsible for global technology service fulfilment at Novare Technologies, a implementation," Info-tech and Info-net, 2001. Proceedings. ICII 2001 - technology consulting firm, working on projects involving Enterprise Beijing. 2001 International Conferences on , vol.5, no., pp.258,263 Mobility, Next Generation Networks and Web-Telco convergence in diverse vol.5, 2001 CCa industries from Telecommunications, Banking and Finance, Software, and Sales and Distribution. Prior to joining Novare, he is also s Systems and [7] Yang Ying; Lan Hai-tao; Liu Ping, "Research on IPV4/IPV6 translation gateway based on NAT-PT technology," Future Computer and Network Consultant at Ateneo de Manila University. A founding member of Communication (ICFCC), 2010 2nd International Conference on , vol.3, the Internet Society-Philippines. Member of the Philippine Linux Users no., pp.V3-419,V3-422, 21-24 May 2010 DDa Groups. [8] M. Bagnulo, P. Matthews and I. Van Beijnum, "Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers draft-ietf-behave-v6v4-xlate-stateful-12", July 10, 2010. [Online]. Available: http://tools.ietf.org/html/draft-ietf-behave-v6v4- xlate-stateful-12. [Accessed January 10, 2014]