enterprise optimal transition plan from ipv4 to ipv6 ... · enterprise optimal transition plan from...
TRANSCRIPT
Enterprise Optimal Transition Plan from
IPv4 to IPv6.
Municipality of Gaza as a Case Study.
روتوكول اإلصدار الرابع لبالحل األمثل للمؤسسات لالنتقال من اإلنترنت لإلصدار السادس
: بلدية غزةدراسة حالة
By
AbedElkareem Omar Hassouna
Supervised by
Prof. Aiman Abu Samra
Prof. of Computer Engineering
A thesis submitted in partial fulfillment of the requirements for the degree of
Master of Computer Engineering
December/2018
The Islamic University of Gaza
Deanship of Research and Graduate Studies
Faculty of Engineering
Master of Computer Engineering
زةــــــغب ةــالميــــــة اإلســـــــــامعـالج
البحث العلمي والدراسات العليا عمادة
ــــــةالهندسة ــــــــــــــــــــــــــــــــليـك
ماجســـــــــــــــتير هندسة الحاسوب
I
إقرار
العنوان:أنا الموقع أدناه مقدم الرسالة التي تحمل
Enterprise Optimal Transition Plan from IPv4 to IPv6.
Municipality of Gaza as a Case Study.
نت األمثل للمؤسسات لالنتقال من اإلصدار الرابع لبروتوكول االنترالحل
.لإلصدار السادس
: بلدية غزةدراسة حالة
أقر بأن ما اشتملت عليه هذه الرسالة إنما هو نتاج جهدي الخاص، باستثناء ما تمت اإلشارة إليه
حثي باآلخرين لنيل درجة أو لقب علمي أو حيثما ورد، وأن هذه الرسالة ككل أو أي جزء منيا لم يقدم من قبل
لدى أي مؤسسة تعليمية أو بحثية أخرى.
Declaration
I understand the nature of plagiarism, and I am aware of the University’s
policy on this. The work provided in this thesis, unless otherwise referenced, is the
researcher's own work, and has not been submitted by others elsewhere for any other
degree or qualification.
:Student's name عبد الكريم عمر على حسونة اسم الطالب:
:Signature التوقيع:
:Date التاريخ:
III
Abstract
Nowadays, Internet access is not limited to computers, there are many devices
that need access to the Internet. Moreover, networking requirements which aren’t
exclusive just for web browsing and send emails, so that the number of IPv4 addresses
available can’t fit this amount of devices. Therefore, IPv4 addresses become an
impediment to developing internet. IPv4 addresses shortage is the main reason for
prevent the concept of the Internet of Things from spreading widely in the world. IoT
is a system of interrelated computing devices, which provide transfer data over a
network without requiring human-to-human or human-to-computer interaction.
Although the IPv4 addresses shortage the main reason for inventing IPv6, they are also
several reasons for the appearance of IPv6, such as simply header to optimize routing,
the consequent speed, reduce delay, increase security and enhancement in quality of
service.
IPv6 is not compatible with IPv4, so to transit from IPv4 to IPv6 is not an easy
job. In contrast transition process need a lot of hard work to avoid any problems, it is
not a single step, but a careful, prepared, pre-planned and anticipated study of any
technical emergency that may be rise during the transition process.
A lot of enterprises avoid talking about IPv6, they do not have the minimum
knowledge and this is what we derived before starting this study. Therefore, in this
study, we will provide a specific transition plan including an appropriate model for the
Municipality of Gaza to transit from IPv4 to IPv6. This transition plan could be a
guideline for many enterprises with similar size and technology maturity.
This study provides a transition plan from IPv4 to IPv6 in two main stages:
before administrative approval and after administrative approval. Before
administrative approval contains three steps: estimate the cost step, justifications step
and preparation plan step. After administrative approval which contains two steps:
proposed migration plan and implementation. The proposed enterprise transition plan
is built according to the analysis of the Municipality of Gaza network.
IV
الملخص
ئل الهاوذلك بسبب العدد اإلنترنت،لم يعد اإلصدار الرابع من بروتوكول اإلنترنت مناسب لتطور
جهزة من األجهزة التي تحتاج الولوج إلى اإلنترنت وقرب نفاذ العناوين التي يوفرها اإلصدار القديم لأل
وين . لذلك كانت الحاجة لظهور اإلصدار السادس الذي يوفر العديد من العناتاإلنترن تخداماسلتتمكن من
ين وكان الظهور للبروتوكول الجديد فرصة لتحس الرابع،يصل إلى أربع أضعاف العدد الذي يوفره اإلصدار
.االتصالسرعة وأداء
بل ،بينهما وهذه العملية ليست عشوائية لالنتقاللذا هناك إمكانية ،غير متوافقين اإلصدارين كال
.االتصالعملية مرتبة ومخطط لها مسبق لتفادي األخطاء ومشاكل
الكثير من المؤسسات التي تعد شبكات الحواسيب رأس مالها تركن إلى اإلصدار القديم وتتجنب
يه المؤسسات ليس لدهذا التفادي يجعل الكثير من ،اإلصدار السادس لقلة الخبرة المطلوبة والمعرفة به
.االنتقالللبروتوكول الجديد وليس لديه أي مخطط لعملية االنتقالأي فكرة عن طريقة
إلى لالنتقالنكون قد تمكنا من إعداد خطة تناسب شبكة بلدية غزة ،لذلك ومن خالل هذا البحث
ن المؤسسات الذي من الممكن أن يكون مرجع للكثير م ،اإلصدار السادس من بروتوكول اإلنترنت
التغيير.المشابهة التي تنوي
قبل ،ةقبل الموافقة اإلدارية وبعد الموافقة اإلداري رئيسيتين،وقسم هذا البحث الخطة إلى مرحلتين
مل أما بعد فتش المخطط،إعداد مرحلة و ثالث مراحل هي مرحلة تقدير التكلفة ومرحلة التبريريحتوي على
يلهاسوف يجري تحل التيلطبيعة شبكة البلدية ةوعملية التطبيق المناسب االنتقالخطة مرحلتين وهما على
.خالل هذا البحث
V
Dedication
To the spirit of my father.
To great mother.
To my sisters and my brothers.
To my Dear wife.
To my daughter “Aisha”.
And to my beautiful country “Palestine”.
VI
Acknowledgment
First of all, all praises to Allah for helping me to complete this work.
I would like to thank my thesis advisor Prof. Aiman Abu Samra, he consistently
allowed this thesis to be my own work, and he oriented me in the right direction
whenever he thought I needed it.
Finally, All the love and gratitude of my family members who give me all the
support to accomplish this message, especially my mother who has the greatest credit
in my life.
VII
Table of Contents
I ............................................................................................................................ إقرار
Judgment ................................................................................................................ II
Abstract ................................................................................................................. III
IV ..................................................................................................................... الملخص
Dedication ............................................................................................................... V
Acknowledgment .................................................................................................. VI
Table of Contents ............................................................................................... VII
List of Tables ........................................................................................................ IX
List of Figures ......................................................................................................... X
List of Acronyms ................................................................................................ XII
Chapter 1: Introduction ........................................................................................ 1
1.1 Content. .............................................................................................................. 2
1.2 Thesis Motivation............................................................................................... 3
1.3 Thesis Significance. ........................................................................................... 4
1.4 Research Questions. ........................................................................................... 4
1.5 Thesis Goals. ...................................................................................................... 5
1.6 Thesis Limitations. ............................................................................................. 5
1.7 Thesis Layout. .................................................................................................... 6
Chapter 2: Related Works..................................................................................... 7
2.1 Theoretical Category. ......................................................................................... 9
2.2 Scientific and Applied Manner Category. ........................................................ 11
Chapter 3: Theoretical Overview ....................................................................... 19
3.1 Network: ........................................................................................................... 20
3.1.1 Components of Networks. ............................................................................. 20
3.2 OSI Model. ....................................................................................................... 21
3.3 IPv4. ................................................................................................................. 22
3.3.1 IPv4 Features. ................................................................................................ 22
3.3.2 IPv4 Header. .................................................................................................. 23
3.4 IPv6. ................................................................................................................. 24
3.4.1 IPv6 Header. .................................................................................................. 24
3.4.2 IPv6 Features. ................................................................................................ 25
3.4.3 IPv6 Addressing Modes. ............................................................................... 26
VIII
3.4.4 IPv6 Addressing Structure. ........................................................................... 28
3.5 Transition Methods from IPv4 to IPv6. ........................................................... 30
Chapter 4: MOG Network Analysis ................................................................... 33
4.1 Introduction. ..................................................................................................... 34
4.2 Survey of MOG Network. ................................................................................ 36
4.3 Infrastructure. ................................................................................................... 36
4.3.1 Media............................................................................................................. 36
4.3.2 End Devices. ................................................................................................. 36
4.3.3 Intermediary Devices. ................................................................................... 38
4.4 Services. ........................................................................................................... 39
4.5 IP Addressing and VLAN Design. ................................................................... 40
4.6 Conclusion........................................................................................................ 41
Chapter 5: Transition Analysis and Proposed Plan.......................................... 43
5.1 First Stage: Before Administrative Approval. ................................................. 45
5.1.1 Estimate the Migration Cost. ......................................................................... 45
5.1.2 Justifications Step.......................................................................................... 46
5.1.3 Planning Preparation Step. ............................................................................ 47
5.2 Second Stage: After Administrative Approval: ............................................... 47
5.2.1 Proposed Migration Plan. .............................................................................. 47
5.2.2 Implementation. ............................................................................................ 56
5.3 Conclusion and Validation. .............................................................................. 57
Chapter 6: Experimental Validation .................................................................. 59
6.1 Windows Platform. .......................................................................................... 60
6.1.1 Methodology. ................................................................................................ 61
6.1.2 Results. .......................................................................................................... 61
6.2 Networking. ...................................................................................................... 63
6.2.1 IPv4/IPv6 Design and Implementation. ........................................................ 63
6.2.2 Methodology. ................................................................................................ 63
6.2.3 Components................................................................................................... 67
6.2.4 Results. .......................................................................................................... 67
6.3 Conclusion and Validation ............................................................................... 70
The References ..................................................................................................... 71
Appendix 1 ............................................................................................................ 76
IX
List of Tables
Table (2.1): Scenarios for Service Provider's Migration. ......................................... 14
Table (3.1): OSI Model. ............................................................................................ 21
Table (4.1): Affected Components By Migration Process........................................ 34
Table (4.2): Types of MOG Cameras. ...................................................................... 37
Table (5.1): Calculated Cost for IPv6 Deployment in MOG. ................................... 46
Table (5.2): VLAN in IPv6 for MOG Network. ....................................................... 53
X
List of Figures
Figure (2.1): Generic Migration Guidelines. ............................................................ 13
Figure (3.1): IPv4 Header. ........................................................................................ 23
Figure (3.2): IPv6 Header. ........................................................................................ 25
Figure (3.3): Unicast Addressing Mode. .................................................................. 27
Figure (3.4): Any-cast Addressing Mode. ................................................................ 27
Figure (3.5): Multicast Addressing Mode. ............................................................... 28
Figure (3.6): Global Unicast Address. ...................................................................... 29
Figure (3.7): Link-Local Address. ............................................................................ 29
Figure (3.8): Unique-Local Address. ........................................................................ 30
Figure (3.9): Different Transition Technologies. ..................................................... 30
Figure (3.10): Dual Stack Works in Network Layer in OSI Model. ........................ 31
Figure (4.1): General Topology for MOG Network. ................................................ 35
Figure (4.2): Dealing with Devices Doesn’t Support IPv6 Procedure. .................... 42
Figure (5.1): Generic Transition Plan. ...................................................................... 44
Figure (5.2): Affected Components by IPv6 Deployment. ....................................... 45
Figure (5.3): Connection Types Between MOG Buildings. ..................................... 48
Figure (5.4): IP Equipment Connected to MOG Network. ...................................... 49
Figure (5.5): Proposed Transition Plan for MOG Network. ..................................... 50
Figure (5.6): Suggested IPv6 Address Plan for MOG Network. .............................. 52
Figure (5.7): DNS64/NAT64 Mechanism. ............................................................... 55
Figure (6.1): DHCPv6 in PDC.................................................................................. 62
Figure (6.2): DNS in PDC. ....................................................................................... 62
Figure (6.3): IPv4 Architecture. ................................................................................ 64
Figure (6.4): IPv6 Architecture. ................................................................................ 64
XI
Figure (6.5): VLAN in IPv4 Architecture. ............................................................... 65
Figure (6.6): VLAN in IPv6 Architecture. ............................................................... 66
Figure (6.7): Creating VLANs in Switches. ............................................................. 66
Figure (6.8): Comparing Delay Between IPv4 and IPv6. ......................................... 68
Figure (6.9): Comparing Delay Between IPv4 and VLAN in IPv6. ........................ 68
Figure (6.10): Comparing Delay Between IPv6 and VLAN in IPv6. ...................... 69
Figure (6.11): Comparing Response Time Between IPv4 and IPv6. ....................... 70
XII
List of Acronyms
IP Internet Protocol.
IPv4 Internet Protocol version 4.
IPv6 Internet Protocol version 6.
MOG Municipality of Gaza.
IETF Internet Engineering Task Force.
IoT Internet of Things.
RFC Request for Comments.
DNS Domain Name System.
DHCP Dynamic Host Configuration Protocol.
OPNET Optimized Network Engineering Tool.
NAT Network Address Translation.
CIDR Classless Inter-Domain Routing.
VLSM Variable Length Subnet Mask.
GNS3 Graphical Network Simulator-3.
CPU Central Processing Unit.
MTU Maximum Transmission Unit.
NAT-PT Network Address Translation - Protocol Translation.
CPE Customer Premises Equipment.
VOIP Voice Over Internet Protocol.
FTP File Transfer Protocol.
SNMP Simple Network Management Protocol.
SMTP Simple Mail Transmission Protocol.
TCP Transmission Control Protocol.
UDP User Datagram Protocol.
XIII
Heln Header Length.
TOS Type of Service.
IPSec Internet Protocol Security.
RTT Round Time Trip.
SLAAC Stateless Address Auto-configuration.
LAN Local Area Network.
OSI Open Systems Interconnection.
SIIT Stateless IP/ICMP Translation Algorithm.
BIS Bump in the Stack.
ISATAP Intra Site Automatic Tunneling Address Protocol.
NAS Network Attached Storage.
VPN Virtual Private Network.
QNAP Quality Network Appliance Provider.
PBX Private Branch Exchange.
ADSL Asymmetric Digital Subscriber Line.
ISA Internet Security and Acceleration.
TMG Threat Management Gateway.
AD Active Directory.
VPN Virtual Private Network.
VLAN Virtual Local Area Network.
LIR Local Internet Registry.
PDC Primary Domain Controller.
1
Chapter 1: Introduction
Chapter 1
Introduction
2
Chapter 1
Introduction
Due to the tremendous technological development in many fields such as social
media, e-marketing, Iot, e-learning and web browsing available on the Internet. A lot
of requirements have been emerged to provide the functions and features for each of
the mentioned fields. IPv4 will not be able to meet these requirements, not only due to
IPv4 addresses shortage but also in the need to enhance real-time applications, increase
Quality of services, security, and mobility (V. Limkar, R. K. Jha, and S. Pimpalkar,
2013). IPv6 was founded to meet these requirements. In addition to the auto-
configuration and multicasting (A.Dutta et al., 2006). To gain these improvements and
enhancements, and to benefit from IPv6 features, we should prepare a suitable plan to
implement IPv6 in our networks.
This plan should be prepared carefully. Plans are needed to assess network
readiness for IPv6 implementation to discover which devices support IPv6 and which
does not, in order to calculate the cost for this process. Besides that, the suitable
address plan for the network should be prepared and choosing the correct method to
do that. After these initial steps to get a successful migration plan, a test bed should be
established to assure the effectiveness of IPv6 deployment and his effects to reduce
delay and response time to increase network performance. We choose OPNET modeler
and VMWARE workstations simulation tools to do similar experiments.
Implementing IPv6 in near future for enterprises, should not be limited only to
the gain of its advantages, but not to be isolated from the rest of the world. Because by
2020 most giant IT enterprises will provide their services in IPv6 only, so preparing
migration plan is a critical decision to be alive.
1.1 Content.
IPv6 was initiated in 1994 by Internet Engineering Task Force (IETF) as a
worthy tool to supplant IPv4 over the coming years (D Kaushik, 2008). The main
reason for inventing IPv6 is the explosion of sorts of the numbers and ranges of IP
capable devices that are being released in the market which lead to exhaustion for IPv4
addresses. IPv6 aims to support effectively the ever-expanding Internet usage and
3
functionality. Also, it addresses security concerns. Although there are many short-term
solutions to overcome IPv4 limitations in lack in addresses such as network address
translation (NAT) which allows multiple private IP's to share the same unique public
IP and Classless Inter-Domain Routing (CIDR) which introduce mechanisms to reduce
wasted IP’s, these solutions solve IPv4 exhaustion in the near term, but have dark side
for these solutions related to security concerns, router overhead and prevent End to
End communication (FJ Molina Robles, 2010).
IPv6 will be the future of the internet, and to ensure internet growth all of
organizations and enterprises should migrate to IPv6 in imminent style. Although
many new features were introduced by IPv6, many enterprises are reluctant to embrace
IPv6, considering that it as an additional cost and risk with no direct use for their daily
business. These enterprises were left to use IPv4 right now without preparing a
transition plan to migrate to IPv6 take into account all aspects related to network
structure to avoid any disruption in enterprise work. In order to change such these
fears, migration mechanisms must be studied and analyzed by organizations in order
to find the best mechanism to meet their requirements.
Sooner IPv6 will be presented in every network, so in order to achieve IPv6
enabled network and minimize costs.
This thesis provides full specific plan for transit MOG network from IPv4 to
IPv6 that can be used by network administrators not just in MOG but also can be useful
for similar enterprises as guideline to deploy IPv6 in the networks.
1.2 Thesis Motivation.
IPv6 was invented to compensate IPv4shortage in address space. In addition,
(ITEF) took advantage of the opportunity to develop new protocol not just to achieve
IPv6 address adequacy, but also to enhance security, support to better quality of
service, improve efficiency and optimization for the network and create a better
environment to move into next-generation networking infrastructure.
There is no doubt, IPv6 will be applied by 2020 especially giant corporations
like Facebook, Microsoft and Google provide them services through IPv6, although
that a lot of organizations are lacking behind the migration due to the lack in
4
awareness, training, and fear from high cost. So, preparing the IPv6 transition gradual
plan is crucial for any enterprise to refute these illusions, which could be an obstacle
to technological development. MOG network is a good example to be a case study for
our proposed plan, the choice was not for nothing but for many reasons, because it has
a large network that is extensive, sensitive to the data that is the capital of this
enterprise, its support for many forms of communication. MOG network has multiple
technologies and characterized by diversity in equipment. So setup plan for such kind
of organizations considered a big challenge and need extraordinary effort to implement
IPv6 without disruption.
1.3 Thesis Significance.
This thesis is considered, as far as I know, the first kind in Gaza strip that
preparing a plan related to transit from IPv4 to IPv6. Besides that, after asking a
number of related questions in a brief interview was held with the head of systems and
networks department in MOG, it turned out that MOG has no idea about IPv6, IT staff
hasn’t any prior knowledge about IPv6 transition process. In addition, MOG does not
have attention for purchasing equipment that supports IPv6. all of these obstacles for
migration process will be fading away after our thesis because our thesis outputs will
work to remove such these obstacles from developing an appropriate transition plan
and training the IT staff and alert them to the purchase of new devices which support
IPv6.
Note that, questions in the interview will be appended in appendix 1.
1.4 Research Questions.
In this thesis, many questions related to this subject are answered such as:
1. Does MOG network infrastructure applicable for IPv6 deployment?
2. What is a transition method should be selected to migrate MOG network and why?
3. What is the anticipated cost of this job?
4. What are the requirements of this process?
5. What are the suitable phases and arrangement of the transition process of the MOG
network?
5
6. How to set up a suitable address plan for the MOG network and in which
mechanism?
7. What are the steps of implementing the new protocol and what improvements the
MOG will gain from this transition process?
1.5 Thesis Goals.
Introduce proposed plan for transition process from IPv4 to IPv6 for MOG
network Characterized by the following:
1. An IPv6 enabled network: the main objective.
2. As much as possible reduce the cost required for this process.
3. This plan should be well structured and covered all aspects of MOG network.
4. End users should touch change in network performance.
5. They should be test bed before real implementation to assure they will be no failures
in MOG network.
1.6 Thesis Limitations.
One of the most important challenges we faced in this thesis was the inability to
implement the migration plan in a real environment. To compensate for this, we choose
simulation programs such as VMware workstation and OPNET modeler to ensure
network connectivity without any problems when deploy IPv6. Moreover, these
simulation programs, make us able to make comparisons between IPv4 and IPv6
related to different factors such as delay and response time.
There are also other challenges related to the municipality of Gaza itself such as:
1. The size and dimensions of this network make it impossible to produce migration
process in a short time.
2. For security reasons, we are not authorized to present a full image.
Therefore, the migration plan can’t be tested for all network peripherals, so IPv6
deployment will run on topologies characterized by diversity which contain several
types from IP devices.
6
1.7 Thesis Layout.
The work in this thesis organized and grouped in the main five chapters as
follows:
Chapter2: In this chapter, we embark on related work and discuss what such this
thesis suggest and prove and how these write help us to achieve our goal. We classify
this references in two axes: first class we group similar references which detail the
subject clearly technically and compare between several transition methods according
to several factors, and the second proceed the subject in an applied manner.
Chapter3: We make some reviews for readers about IPv4 and IPv6, what are the main
differences between them in header format, what are the main IPv4 short comes, what
are the new IPv6 features, address notations for both and what are the main methods
for a transition from IPv4 to IPv6.
Chapter4: In this chapter, a full analysis for MOG network infrastructure and
applications to help us to determine which IP devices support IPv6 and which does
not. Besides that, we will clarify the reasons for choosing the MOG network as a case
study.
Chapter5: This chapter provides proposed transition plan in a subset of MOG
network, this plan provides full steps to transit to IPv6 distributed over two main
stages: firstly “before administrative approval” and secondly “after administrative
approval”. These steps will be discussed in details in chapter 5, and every discussion
was made related to choose the best method either for IPv6 addressing or choose the
best method for a transition.
Chapter6: This chapter is presented simulation results, to persuade network
administrators in MOG enterprise to take our plan seriously to deploy it on the ground.
This simulation will illustrate the advantage of IPv6 after comparing its performance
with IPv4 related to delay and response time factors.
7
Chapter 2: Related Works
Chapter2
Related Works
8
Chapter2
Related Works
There is a number of scientific papers that reviewed the advantages offered by
the IPv6 protocol and compare it with the IPv4. IPv6 is more sufficient than IPv4 in
terms of more address space, management and administration, routing performance,
better multicasting/Media, efficient mobility and security (B Vachon, R Graziani and
JM Díaz, 2009).
Some of these papers make a study in a technical way, they explain the transition
methods and illustrate the appropriate environment and the factors that characterize
using one of them. Also measuring the performance for each transition method, and
doing comparisons between them in terms of hardware, software, complexity,
performance, security, and cost (S Zeadally, L Raicu, 2003).
But despite a large number of these research papers, a few of them have
discussed the process of transition in practice, deploying the system on a medium-
sized enterprise. In order to help the owners of such enterprises, to get a model and
transition plan that stimulates both the executive managers and the relevant technicians
to implement IPv6.
The migration process should not be random, neither a short-term process. If you
do not have a complete plan that takes into account everything such as time, cost and
expects the errors resulting from the upgrade process, IPv6 migration will not be
applicable. Transition to IPv6 should be done under the perfect conditions in order to
avoid false judgment.
The relevant papers for our topic were found include several important
information that helps us to build our transition plan. These papers were divided into
two main categories.
Firstly: a category that presented the subject in a purely scientific way. These
papers are reviewing the most important differences between the two versions, and
mentioned all the transition methods that can be used in the process of promotion, and
measured the performance of each of them with different simulation tools. Without
taking into account other factors such as the size and nature of the work of the
9
enterprise. These factors can affect many things such as the cost of the transition,
whether by buying new devices, or the cost of training people who will deal with the
IPv6.
Secondly: a category that presented the subject in a scientific and applied
technical manner, suitable for large enterprises. This category has mentioned
everything about the nature of these enterprises in terms of the size, choice of the best
transition method and anticipated cost for the transition to IPv6.
In addition to the advances in the most important differences between the two
versions IPv4 and IPv6 and how to transit between them. This thesis will provide a
proposed transition plan from IPv4 to IPv6, for medium-sized enterprises. In chapter
5, this transition plan will be discussed in details consistent with MOG network status.
2.1 Theoretical Category.
(Lefty Valle et al., 2012), this paper addressed the design and implementation of
IPv6 by using two simulators packet tracer and GNS3, and designed topology was
tested with two transition mechanisms: dual-stack and tunneling. This paper only
mentioned the importance of IPv6 from many respective such as extended IP address,
the simplified header, enhanced mobility, and security compared with IPv4 (B Vachon,
R Graziani, JM Díaz – 2009). But unfortunately did not mention why it favored the
transition and did not offer any plan that allows enterprises of all sizes to benefit from
the simulation conducted by them. In the practical aspect of this paper, they explained
and showed some commands that configure IPv6 in some devices. Finally, they
presented as a conclusion to them work the reasons for their selection packet tracer
and GNS3 as simulators. This paper is provided why we should use these transition
methods, dual stack when we have IPv4 and IPv6 nodes and tunneling when we do not
have IPv6 nods to encapsulate IPv6 packets over IPv4 networks. Also, they said, the
dual stack has a dilemma in performance due to increase routing tables for both
versions which cause CPU overhead. And tunneling main disadvantage is that the
MTU increases in 20 bytes the header of each IPv4 packet, besides troubleshooting
becomes more complicated (Lefty Valle-Rosado1, Lizzie Narváez-Díaz1 and Cinhtia
González-Segura1, 2012)
10
(IoanRaicu and SheraliZeadally,2003), this paper like its counterpart in this
section, evaluate two types of transition: 6-over-4 and IPv6 in IPv4 tunneling impact
of these approaches on end-to-end application performance. They evaluate the
performance impact of these mechanisms in a real-world setting, which includes hosts
and routers supporting dual IPv4/IPv6 stacks (R Gilligan and E Nordmark, 2000).
They provide test results for these transition methods under three classifications, IPv6
only, IPv6 with IPv4 by 6-over-4(B Carpenter, C Jung – 1999) transition methods and
IPv6 with IPv4 IPv6 in IPv4 tunneling (A Conta, S Deering, 1998). They use several
factors to comparing these transition methods such as latency, Throughput, latency,
CPU utilization, TCP connection time and Web Client/Server Simulation. After doing
their comparisons and getting the desired results, this study recommended the
encapsulation transition mechanism performed slightly better than the native IPv6
protocol stack or IPv6 in IPv4 tunneling. Such these papers which contain such these
results and recommendation, be inspiring and shorten a lot of time in a specific stage
of the IPv6 transition plan. But the successful transition plan has many stages and a lot
of hard work, our proposed plan will discuss these stages in details in the rest of this
thesis.
(GYAY Al-Gadi, A Amin Babiker, N Mustafa and MA Hamied, 2014), like the
previous papers, this paper provided a comparison between the three main transition
methods dual stack, tunneling and translation (NAT-PT) (P Loshin, 2004). This
comparison was done by using GNS3(JC Neumann, 2015) simulator to build three
topologies, every topology expresses one way for every transition method. Beside
GNS3 they use Solar winds software for analysis the traffic between multiple
destinations, to measure the performance of the network at every one of the transition
methods according to three parameters (Latency, Packet loss, response time). They
found that the tunneling is the best in terms of latency, technique packet loss and
response time.
(L Valle-Rosado and L Narváez-Díaz, 2012), this paper reviewed the IPv6 in
technical terms only, without mentioning any actions or plans. This paper was
mentioned what distinguishes the IPv6 about its predecessor, related for addressing,
simplified header, enhanced mobility, and security. In order to demonstrate IPv6
preference, they have published this paper that shows the knowledge and skill required
11
in IPv6 eventual implementation. a tested network was implemented using two
simulators, Packet Tracer and Graphical Network Simulator (GNS3), this network will
support IPv6 as addressing protocol, the routing protocol RIPng was implemented and
finally, the network was tested with two transition mechanisms, dual-stack, and
tunneling. During working, they displayed the most important commands used to
activate IPv6 and its routing in both simulators.
Finally, they concluded that a dual stack mechanism is easier to implement but
devices must support it. The main disadvantage for dual stack that makes routing tables
to increase considerably and this creates processes and longer times. Also they
conclude, a tunneling is a good choice when devices do not support IPv6, but this
mechanism has this problem that the MTU increases IPv4 header packet about 20
bytes.
Authors (G Al-Gadi and AA Babiker, N Mustafa, A Al-Gadi, 2014), do evaluate
between IP4 and IPv6 in related to different factors such as Ethernet delay and
response time under different circumstances: a low, medium and heavy load. The
results obtained by using OPNET simulation tool after built project which contained
several scenarios, tell us that the performance of IPv6 is much better than IPv4. IPv6
performs better under specific circumstances. Finally, this paper recommended us to
deploy IPv6 as early as possible to avoid future drops on the internet. This paper
provides us a good simulation tool to test both protocols performance related to several
factors. Although the valuable information was included, this paper is free from any
steps to form specific or generic plan to deploy IPv6, it just shows us simulation results
to measure IPv4 and IPv6 performance.
2.2 Scientific and Applied Manner Category.
There are still few or nearly no papers for applying the transition from IPv4 to
IPv6 in a medium-sized enterprise, but authors (N Quynh Anh, M Nguyen and N Phu,
2012) try to find out best transition method for large enterprise networks. This thesis
does not only focus on the technical aspects but also the management aspect and this
is the most important feature. This thesis includes eight chapters, half of them show
the theoretical aspect of the topic and the rest for the practical aspect.
12
In the theoretical aspect, the writers, show overview of IPv4, IPv6, and
differences between them.
Design science method was introduced to assist and evaluate the current network
infrastructure to know the effectiveness and risks from IPv6 implementation.
In this paper, the research question “Transition from IPv4 to IPv6: What is the
best method for large enterprise networks?” Was Consider the seed and the real
starting point toward finding the suitable transition method for IPv6. This is not just a
question, because that, to find right answer you should do hard work to collect real
data from Specialists and workers in the field across different ways. Based on this
paper submissions and conclusion, you will find the main objectives for a thesis, which
is what is the best transition method that suitable for large enterprises.
Other papers like (X Che andD Lewis, 2010) consider a good example for this
category, is a research based on the mention of percentages of IPv6 deployment in the
continents in the world. Also, this paper was mentioned the most important differences
between IPv4 and IPv6 in terms of address, components, and services provided by
both.
One of the distinguishing features of this paper is that they make a comparison
between IPv6 and NAT (G Goth, 2005). This comparison shows us that NAT, besides
more solutions such as VLSM are considered short-term solutions to extend IPv4 life.
This is a smart comparison because it works to convince enterprises interested in the
transition process, because of the NAT consider a single point of failure, Short-term,
pragmatic, and incremental approach of increasing the number of network connections
via NAT over IPv4(G Goth, 2005).
This paper presented some incentives and also some obstacles that would be
inhibited in the development process. Unfortunately, some of these obstacles were
related to the proper planning of such transition process and the additional potential
cost that could affect the achievement, in addition to the human element that does not
favor development for fear of learning and training (C Popoviciu, 2006). Such as
mentioned obstacles will be dealt with it in our thesis and try to find the right solutions
to overcome them.
13
At the end of this paper, they submitted generic migration guidelines irrelevant
to the size or nature of enterprises. The enterprises may be private or state-owned.
These migration guidelines contain eight stages. Figure (2.1) clarify these guidelines
(X Che and D Lewis, 2010).
Figure (2.1): Generic Migration Guidelines.
Authors (BR Dawadi, SR Joshi and AR Khanal, 2015) adopted the reasons for a
transition from three different perspectives. the first one is a technical reason because
IPv6 helps to avoid address lack, enhance security, better quality of service, improve
efficiency and optimization of the network. The second is business and e-commerce
reason because network infrastructure with IPv6 provides perfect e-commerce
implementation, secure online transaction, and reliable email service. In additions
business that does not think in IPv6 deployment will risk accessibility problems of
their websites and other internet-connected locations and services (BR Dawadi, SR
Joshi and AR Khanal, 2015). The third perspective is that with IPv6 better public
service delivery and create a global competitive and legitimate environment from
government reason (BR Dawadi, S Shakya and AR Khanal, 2015). Besides that, the
authors suggest three strategies to deal with the current situation of the service
14
provider's network migration. The first strategy is doing nothing, and therefore you
will not find a place. The second strategy is to work on finding short-term solutions
such as NAT and VLSM to extend IPv4 lifespan. The third strategy is deploying IPv6
by choosing and compare transition methods like a dual stack, translation, and
tunneling. One of the highlights of this paper is that it presented in its content five
scenarios to choose which way to migrate to IPv6, depending on the nature of the
network built in the service provider compared to the surrounding networks. Table
(2.1) shows the summary of these scenarios.
Table (2.1): Scenarios for Service Provider's Migration.
No. Service provider
network
Customers
network Notes
First scenario IPv4 only IPv6
Service provider may provide Tunnel
Broker service, without the need to replace
CPE equipment.
Second scenario IPv4 only IPv6
Replace the customer premise devices with
dual -stack capable and follow 6 Rapid
Deployment (6RD) approaches.
Third scenario Both IPv4 and IPv6 IPv6
Service provider will enable its network
infrastructure into dual stack mode by either
migrating the software or replacing the
hardware equipment.
Fourth scenario Few IPv4 servers IPv6
(NAT64) can be used to translate the IPv6
header to IPv4 and vice versa. DNS64 server
is required for domain name resolution
together with NAT64 for large family of
address translation.
Fifth scenario IPv4 IPv4 through
IPv6 network. 464XLAT.
These scenarios can be useful for different service providers at different stages
of their network migration. In the end of the paper, authors provide an advice for a
15
service provider to the development of strategic planning. This plan can be providing
and summarized in these points:
1- Identification of customer requirements.
2- IPv6 address reservation.
3- Staff training.
4- Testing
5- Hardware/software compatibility.
6- Budget.
7- Risk management
8- Security
9- Interconnection with other service providers.
Migration to IPv6 is not a sudden task, because a huge number of IPv4 users, in
order to avoid interrupts and problems. The migration should be a pre-planned process
and we should do organization evaluation model for assessing the organization’s
readiness towards IPv6 migration. To be able to prepare such these models, you need
to know the factors that affect this process. (A Main, NA Zakaria, R Yusof, 2015) are
work on these factors. In this paper, the researchers found that many enterprises do not
have at least minimum desire to transit to IPv6. For that, they conducted to several IT
experts in several organizations in Malaysia.
These interviews were about the factors that affect the organization's readiness
to migrate to IPv6, and these factors were identified through previous studies and
classified into two categories (MM Yousafzai, NE Othman and R Hassan, 2015):
1. Physical factors; IPv6 deployment (planning), equipment and cost.
2. Human factors; involve knowledge, training, and motivation.
The questions for each factor were as follow:
Deployment: Does the organization need to start/show any effort to show that they
are aware of this migration process?
Equipment: The nature of the equipment in the organization and what should be
changed from it?
Cost: Is this an expensive process?
16
Knowledge: what about the nature of this knowledge which will be provided for the
staff?
Training: What type/form of training needed by the organizations to train their
technical?
Motivation: why we should do that?
Authors, through this qualitative research method, which is empirical data
collection. They conclude that… related to technical factors, organizations should
have prepared their networking equipment and end-user devices before initiate the
IPv6 project. Human factors such as knowledge, training, and motivations are high
priority factors which influence organization readiness for migration IPv6.
Authors (SV Limkar, RK Jha, T Patil and M Kalbande, 2010) discussed where
the deployment of the IPv6 arrived in India. The authors reviewed the most important
features of the new protocol and what are the motivations behind implementing it.
These motivations were as follows: ease for administration, an end to end network
model for better video and VOIP, scalability and more address space (D Lowe, 2003).
The main point that was introduced by this paper is standing behind the reasons for
poor planning for migration to IPv6 in India and try to find solutions that will reduce
these problems. These problems in general talk about the fear of failure by applying
this transition due to knowledge lacking. In addition to not know the additions and
benefits that IPv6 offers, and there no any applications which need the new protocol.
The author suggests different solutions to overcome these fears through Workshops
and scientific seminars and the role of academic institutions in clarifying the
importance and necessity of the IPv6. At the end of this paper, the author identifies a
roadmap for IPv6 in his country, by combining all efforts at all levels by the
government, universities, research centers, and service providers to be more
responsible for implementing and work in IPv6. Moreover, to mentioned problems,
the absence of a successful model for the deployment of IPv6 in order to use it as a
reference by specialists, consider the main obstacle for IPv6 deployment.
Authors (MM Yousafzai, NE Othman and R Hassan, 2015) them focus was on
two main objectives, firstly: how to prepare, Implement, test, and analyze an IPv6 test-
bed. Secondly: how to do a smooth transition from IPv4 to IPv6 by seven steps. The
17
authors for the first goal consider all devices in the network support IPv6 and their
methodology consist of four phases as follow (GB Shelly and ME Vermaat, 2011):
1. Preparation- In this phase, a survey was performed to check existing network
devices for IPv6 test-bed support.
2. Implementation: assigning every device in network IPv6address.
3. Testing: for three things connectivity, bandwidth speed and IPv6 websites
browsing.
4. Analysis: All the tests were successful, and the test-bed was functioning properly.
Due to the second goal, this paper provides seven steps for a smooth transition for
IPv6, these steps as follow:
1. Determine which devices support IPv6 or not, if not upgrade it to support the new
version.
2. Determine application and services, to look for ones that do not support IPv6, and
try to upgrade it.
3. Develop IPv6 strategic development plan which includes IPv6 address allocation,
pure IPv6 test-bed design and implementation, IPv4 to IPv6migration, hardware
and software upgrades, change management, risk management, equipment budget,
manpower resources, IPv6 audit, and IPv6 effective implementation.
4. IPv6 Address Allocation Policy, to conserve IPv6 addresses.
5. IT Staff training.
6. Implement a Pure IPv6 Test-bed Network, to avoid dis-connectivity in network
applications.
7. Choose the suitable transition method.
(PFM de Castro, 2013) proposed a generic plan for any large enterprise want to
deploy IPv6. It is considered as a guideline in this field, it consists of nine steps to
follow it to prepare successfully IPv6 deployment plan. This plan compromises the
following steps to achieve IPv6 upgrading:
1. Analysis of the current situation.
2. Present a study focused on the migration impact for the company.
3. Survey of the enterprise’s network.
4. Analyze IPv6 support from ISPs.
18
5. Estimate the costs of migrating the company’s network.
6. Migration plan.
7. Test-bed.
8. Identify problems.
9. Final implementation.
19
Chapter 3: Theoretical Overview
Chapter 3
Theoretical Overview
20
Chapter 3
Theoretical Overview
In this chapter, we will talk about internet protocols, its versions, and the main
features for each of them, the differences between both IPv4 and IPv6, what is new in
IPv6 and what the main methods for a transition from IPv4 to IPv6. All of these
subtitles will be presented in details, but before starting, let’s present some
terminologies which contribute to understanding the subject clearly.
3.1 Network:
A group of computers which connected with each other through switches to
benefit from services that are provided by huge computers which called servers, even
to benefit from shared storage and hardware (D Lowe, 2003).
3.1.1 Components of Networks.
1. Servers: is a dedicated computer system, which is used as the central repository of
data and various programs that are shared by users in a network. There are many
types of network servers for example, file print, database, and active directory
servers. Every network server has its own services to provide it for clients if we
take AD server as an example, its bundled DNS and DHCP services to provide IP's
and hostnames to client computers.
2. Client computers: is an individual computer that accesses the information and
programs stored on a server as part of a network environment.
3. Transmission media: This Describes the type of physical system used to carry a
communication signal from one system to another. Examples of transmission
media include twisted-pair cable, coaxial cable, and fiber optic cable.
4. Communication devices: is a hardware device capable of transmitting an analog or
digital signal over the telephone, other communication wire, or wirelessly.
Examples of such these devices include modems, routers, and switches.
5. Network software: Network software is an extremely broad term for a range of
software aimed at the design and implementation of modern networks.
21
Presently, the world’s largest computer network is the Internet. “The Internet is
a worldwide collection of networks that connects millions of businesses, governments,
agencies, educational institutions and individuals” (S Boss, J Krauss – 2014).
For that, every node connected to the network should have a unique address, to
enable other nodes to communicate with it (send and receive packets). This address is
the IP address, which stands for Internet Protocol which manages all communication
activities through defining the order, size, and format of messages sent through
networks.
3.2 OSI Model.
Open System Interconnections: It is a standard for communication between
different nodes which running different hardware and software with different
underlying architectures. It contains seven abstract layers, every layer deals with under
layer and prepare a packet for above layer (K Downset al., 1998). Every layer has its
own main objective in communication process see table (3.1), we can show the seven
layers and the main function for each one, in addition, the protocols that can work in
every layer (N Briscoe - PC Network Advisor, 2000). As we see the Internet Protocol
(IP) works in the network layer.
Table (3.1): OSI Model.
Layer Objective Protocols
Application (7) This layer contains web browsers and email
clients. This layer is an interface between
the network layer and user applications.
FTP,SNMP,SMTP
and Telnet
Presentation(6) This layer is responsible for the formats of
transmit data, also for encryption and
compression of data.
Session(5) This layer is responsible for set up, manage
and end sessions between client computers.
22
Layer Objective Protocols
Transport(4) This layer controls data flow and provide
error checking before and after the
transition.
TCP, UDP
Network(3) This layer is responsible for IP addressing
and routing
IPv4, IPv6
Data(2) This layer defines the format in which data
will be transmitted such as data fragment
and encapsulation
NOT Specified
Physical(1) This layer defines the network transition
components which is responsible for
transferring data across networks such as
cables and, NICs.
3.3 IPv4.
IP is stands for Internet protocol that is documented in RFC 971, this protocol
works in layer 3 from OSI model. IPv4 responsibility to delivering data packets
between network devices (K Downset al., 1998). In the rest of this section, we will
present IPv4 header, features and address notation in details.
3.3.1 IPv4 Features.
IPv4 is the most widely used version of the Internet Protocol. it defines an IP
address for every attached device to the network, the IP address contains four octets
separated by a dot(.). 32 bit is the length of IP, which mean IPv4 provides 2^32
addresses, which consider a small number of addresses compared with the number of
devices connected to the internet. IP is responsible for delivering packets, by unreliable
connectionless communication in packet switching network, each packet has header
contain mandatory and optional information about the source and destination nodes (K
Downset al., 1998).
23
IPv4 addresses created in classes clearly defines the bits used for network
prefixes and the bits used for hosts on that network. To have more addresses in IPv4
we do subnet to get fewer hosts per more several networks, through manipulating the
default classful netmask that allows us to borrow host bits to be used as subnet bits.
3.3.2 IPv4 Header.
Figure (3.1): IPv4 Header.
In figure (3.1) we can show IPv4 header and its fields (K Downset al., 1998):
1. Version: the value for this field is 4 as the name for IPv4.
2. Hlen: is the header length value, and point to the beginning of data.
3. Type of Service (TOS): it is an indicator for the upper layer to deal with a packet.
4. Length: total length of data plus header.
5. Identifier: is a ticket for reordering segments in a packet.
6. Protocol: is used to define which upper layer protocol will be used after IP
protocol processing is finished.
7. Checksum: is used for verification from that, the packet which sends is received.
8. Source address: the IP address of the sender.
9. Destination address: the IP address of the receiver.
10. Options: implement some features like security.
24
11. Data: data to process by an upper layer.
3.4 IPv6.
IPng (the next generation) or IPv6, it is an Internet Protocol Similar to IPv4. IPv6
is an Internet Layer protocol for packet-switched internetworking and provides end-
to-end datagram transmission across multiple IP networks (S Deering, R Hinden,
2017). This protocol is overcome IPv4 limitations especially in lack of IP addresses
and built-in security. In the next sections we will provide a simple overview about
different things related to IPv6 such as header structure, extension headers, addressing
and IPv6 features.
3.4.1 IPv6 Header.
The movement of unimportant fields from the new protocol header aims to
reduce IPv6 header overhead, which causes IPv6 packets to be processed more
efficiently in intermediate routers, so the delay for transmitting packets will be reduced
and performance will be enhanced. In chapter 6, after use OPNET modeler we will see
the vast difference between IPv6 and IPv4 delays.
In figure (3.2), we can show the simplified header for IPv6, which contains these
fields:
1. Version: version number=6.
2. Traffic class: 8-bit traffic class, such as TOS in IPv4.
3. Flow label: 20-bit flow label, allow labeling sequences of packets.
4. Payload length: length of next header plus length of extension header
5. Next header: It uses the same values as the IPv4 Protocol field, there is three
possible values TCP header, UDP header or extension header.
6. Hop limit: the packet is discarded if the hop limit is decremented to zero.
7. Source address: 128-bit address of packet sender.
8. Destination address: 128-bit address of packet receiver
25
Figure (3.2): IPv6 Header.
3.4.2 IPv6 Features.
The IPv6 header becomes more flexible and simple processed producing less
overhead in intermediate routers. Because of the new IPv6 header format, that was
relocating unimportant and options fields in IPv4 in extensions headers. Extensions
header have come after IPv6 header; besides this flexibility, they are some new
features which make IPv6 implementation more motivating.
In order to improve routing efficiency by using IPv6, the new version introduces
a new mechanism which called extensions header that makes routers less overhead and
the analyzes become in destination nodes.
Extensions header can be one or more of the following fields:
1. Destination header: additional information about destinations.
2. Authentication header: for authentication and integrity.
3. Encapsulating security payload header: provides message integrity and
confidentially.
4. Fragment header: in contrast with IPv4, fragmentation happens in source address
not in routers, when the packet size bigger than maximum MTU.
5. Routing nodes: the header must be used to specify predetermined nodes to visit.
26
6. Hop by hop: the only header should be analyzed in every node in the path.
Beside to extensions header, there are a lot of advantages were introduced in IPv6, the
following list illustrates the new features of IPv6:
1. More address space from 32 bit in IPv4 for 128 bit in IPv6.
2. No broadcast and the alternative are multicasting to reduce network overhead.
3. Anycast: routes packet to the nearest group of nodes have the same destination
address.
4. Improved quality of service because traffic class and flow label fields.
5. Improved performance, because fragmentation will not be processed by routers but
in source nodes, which decrease workload in routers.
6. Mobility.
7. Built-in security. Through using IPsec protocol which located in IPv6 extension
header, that produce additional security level to ensure all data encapsulated in
packets to travel safely.
8. End to End communication: no NAT.
9. Throughput: IPv6 can reach higher throughputs and a Round Trip Time (RTT) than
IPv4 under the same conditions.
10. Auto-configuration: IPV6 introduce Stateless Address Auto-configuration
(SLAAC), which mean host can have IP when attached to the network, which called
link-local address to communicate in the same LAN.
3.4.3 IPv6 Addressing Modes.
Address mode is the mechanism of how we address a host on the network. In
IPv6 there are three main types of address mode.
1- Unicast Mode.
Every device in a segment has a unique IPv6 address, in IPv6 header, there are
a source and destination addresses. A host interface is equipped with an IP address
which is unique in that network segment (A Shiranzaei, RZ Khan, 2015). Figure (3.3)
clarify the meaning of unicast mode addressing.
27
Figure (3.3): Unicast Addressing Mode.
2- Anycast Mode.
This is a new mode was provided by IPv6, in which multiple interfaces are
assigned a same anycast IP address. when host wants to communicate with a device
equipped with anycast IP address, sends a unicast message and according to complex
routing mechanism, in term of routing cost that unicast message is delivered to the host
closest to the Sender (A Shiranzaei, RZ Khan, 2015). Figure (3.4) shows the anycast
address mode process.
Figure (3.4): Any-cast Addressing Mode.
28
3- Multicast Mode.
The IPv6 multicast mode is the same as that of IPv4. The packet destined to
multiple hosts is sent on a special multicast address (A Shiranzaei, RZ Khan, 2015).
Figure (3.5) shows the mechanism of multicast mode, which is a group of end devices
have a same IPv6 address.
Figure (3.5): Multicast Addressing Mode.
3.4.4 IPv6 Addressing Structure.
IPv6 address is made of 128 bit divided into 16-bit block, each block is converted
into four hexadecimal numbers. Blocks are separated by colons, for example:
0010000000000001 0000000000000000 0011001000111000 1101111111100001
0000000001100011 0000000000000000 0000000000000000 1111111011111011.
These 128 bit long can be converted to:
2001:0000:3238:DFE1:0063:0000:0000: FEFB.
Although the address was converted to hexadecimal, the IPv6 remain long. ITEF
provide some rules to simplify IPv6 address.
1. Leading zeros in address will be discarded, as shown next
2001:0000:3238:DFE1:63:0000:0000:FEFB.
2. Contiguous zeroes blocks will be omitted and replaced by double colons.
29
2001:0000:3238:DFE1:63::FEFB.
3. The previous rule can be done once in IPv6address, but the 2nd block will be having
special treatment by a shrunk number of zeroes.
2001:0:3238:DFE1:63::FEFB.
There are three types of IPv6 unicast scheme which are Global Unicast Address,
Unique-Local Address, and Link-Local Address. Each of these types has several
characteristics, in addition for that, every type has its scope.
1. Global Unicast Address. This type like IPv4 public address, globally
identifiable, uniquely addressable and three most significant bits set as 001. See
Figure (3.6).
Figure (3.6): Global Unicast Address.
2. Link-Local Addresses. Auto-configured IPv6, the first 16 bits are equal to (FE80)
and these addresses are non-routable. Figure (3.7), present for us link local address
format.
Figure (3.7): Link-Local Address.
3. Unique-Local Address. This type of IPv6 address is globally unique, but it should
be used in local communication, always starts with ‘FD’. Figure (3.8), shows what
the components of this addressing mode are.
30
Figure (3.8): Unique-Local Address.
3.5 Transition Methods from IPv4 to IPv6.
Figure (3.9): Different Transition Technologies.
According to figure (3.9), there are many transition methods between IPv4 and
IPv6, such as dual-stack, translation and tunneling (S Subramanian, 2003). choose the
best method that suitable for network infrastructure is an important decision to save
cost and to stay your network work probably. Therefore, before making decision
related for choosing the best method you should analyze your network, as we done in
chapter 4. Understanding the current situation, also is an important task in order to be
able to analyze your network functionalities, needs scalability and security. In this
section, we will present a major overview of basic transition technologies.
31
1. Dual Stack.
This method is a simple and flexible way to transit to IPv6 because enterprise
doesn’t have to replace all existing IP nodes or upgrade all of them at the same time.
In this method, both protocol versions will harmonize for some time. According to the
figure (3.10), the dual stack is implemented in the network layer for both IPv4 and
IPv6 (Mukti, aan and Negara, 2016). Choosing the suitable protocol will depend on
information in the data link layer. DNS is responsible for management in this method,
because when stacked device queries the name of a destination, one of IP versions will
reply depending on the type of DNS record. For example, when DNS resolve the name
with A record IPv4 packet will be sent, or when reply with (AAAA) record IPv6 packet
will be sent.
Despite the simplicity and flexibility related to this way, they are some
concerned issues with this method such as every dual stack device will require two
routing tables, additional resources to stacked devices and more security consideration.
Figure (3.10): Dual Stack Works in Network Layer in OSI Model.
2. Translation.
The meaning of this method is to convert directly protocols from IPv4 to IPv6
or vice versa, Look Figure (3.9). Translation method is results in transforming those
two protocols headers and payload. This method works in three OSI model layers
32
which are network, transport and application. Translation methods have several
mechanisms which can be either stateful or stateless depending on do conversion
related to the previous packets or not. Translation method mechanisms, for instance,
NAT-PT and BIS, apply an algorithm known as Stateless IP/ICMP Translator(SIIT).
The function of this algorithm is to translate packet-by-packet the headers in the IP
packet between IPv4 and IPv6, and also addresses in the headers among IPv4, IPv4-
translated or IPv4-mapped IPv6 addresses. However, this does not mean IPv6 hosts
can get an IPv4 address or route packets, but this assumes that each IPv6 host can have
a temporary assigned IPv4 address (Nakajima, Masaki, and Nobumasu Kobayashi,
2004).
NAT-PT is considered as a stateful translator mechanism which provides the
IPv4 address for IPv6 nodes, NAT-PT may be server or router to can do this role. BIS
is another example for translation mechanism that stands for Bump in the stack that
based on inserting their additional fields into the structure of TCP/IP stack. BIS
mechanism is used especially for communication between IPv4 applications on an
IPv4-only host and IPv6-only hosts.
Although the translation method has several advantages especially you don’t
need any application to implement it nor modification to nodes but some modification
for boundary routers. Translation method has many drawbacks, which hinder their
implementation. For instance, NAT technique prevents an end to end security, increase
complexity in IP addresses and routers become a single point of failure.
3. Tunneling.
It provides a better solution where user’s data can pass through a non-supported
IP version. for example, when two different locations with IPv6 addresses want to talk
over IPv4 network or vice versa. To accomplish these routers/hosts that will send the
datagram should be able to encapsulate the IPv6 datagram in an IPv4 datagram. The
tunneling can be done in two ways, manually and automatically which includes several
mechanisms such as 6to4, Toredo, ISATAP, Tunnel Brokers and 6rd mechanisms (J
Bi, J Wu and X Leng, 2007). The red arrow in Figure (3.9), represent tunneling method
after using IPv4 internet as transmission media between two distant IPv6 islands.
33
Chapter 4: MOG Network Analysis
Chapter 4
MOG Network Analysis
34
Chapter 4
MOG network analysis
4.1 Introduction.
This chapter will provide details about Municipality of Gaza network and
clarifies how buildings and departments connected to Datacenter and list devices
connected to the network. This list is mentioned to obtain which one support IPv6 and
which does not. The reason behind choosing the MOG network as a case study for a
suggested plan, because MOG network use several technologies, multiple techniques
to connect several locations.
The main objective of this analysis is to identify which components must be
upgraded or replaced in order to enable IPv6 in the MOG network. The analyzing of
dependencies between every attached component to avoid any collapse in the network.
The components that could be affected by the migration process from IPv4 to IPv6 are
listed in table (4.1).
Table (4.1): Affected Components by Migration Process.
Components Description
Hardware Every IP based device does not support
IPv6 should be replaced
IP addressing Tough the large IP address space,
manage IP distribution as in IPv4 is a
necessity. Routing Every dynamic routing protocol has its
support to IPv6, but with few changes.
Services and application All application and services must
support IPv6.
Security Intrusion detection systems must support
IPv6.
But before talking about the MOG network, a short introduction about the
Municipality of Gaza nature work will be introduced. The MOG is a service
organization for the residents of Gaza City, which provides various services to citizens
of water and sanitation, building management services and licenses of crafts. All of
these services are linked to one bill for each citizen. In order to facilitate the provision
of such services and the collection of funds. In order to achieve that, it was necessary
35
to provide computerized databases, to be amended and added and even deleted by the
municipal staff deployed in ten departments and various places linked to a single
network each according to his specialty. Connect different places by Internet or by
fiber optics, see figure (4.1).
Figure (4.1): General Topology for MOG Network.
Therefore, the Gaza Municipality Network is considered to be the most
important property for the completion of its various activities. Hence, this thesis gains
value because it contains proposed plan to transit from IPv4 to IPv6, which is of great
importance and necessity to meet the needs and aspirations of Municipality of Gaza in
the near future.
With more than 500 computers, more than 40 servers, printers, cameras and
fingerprints that organize employee entry and exit movements, all of these mentioned
types connected to one network, making it easy to access any information that anyone
needs with different restrictions.
Most organizations believe that the transition process takes only a single day,
which causes a lot of problems from network downtime, security gaps and financial
costs. All of these problems can be avoided by arranging a good transition plan which
consists of multiple phases will be mentioned to suit the MOG network in the next
36
chapter. This transition plan could be a generic plan for other organizations that have
the desire and technological maturity.
4.2 Survey of MOG Network.
In this section, we will present a survey of the existing devices and equipment
regarding their IPv6 support. The reason for this survey is to find and identify which
devices must be upgraded or replaced in order to enable IPv6 in the MOG network.
According to the next classification, we will make our survey:
1. Infrastructure.
End devices
Intermediary devices.
Media.
2. Services.
3. IP scope and VLAN design.
4.3 Infrastructure.
In this section, three types of components will be mentioned in details,
these types formed the MOG network. This illustration is contributing to
understand the current situation and facilitate transition processes analysis.
4.3.1 Media.
As mentioned above, fiber optics, Ethernet cables and internet are the main
transmission medium used to connect MOG network. Fiber Optics was used to
interconnect distant places to a data center, Ethernet cables for internal extension and
internet was used to provide both VPN connections of both, site to site connection and
client to site connection. The tradeoff process between the fiber optics and internet due
to distances and the size of transferred data.
4.3.2 End Devices.
Regarding end devices, we should be grouping them according to their
networking task, and mention them in details to know which of them support IPv6 and
which not. In addition, mention the number of devices didn’t support IPv6, in order to
calculate the cost of upgrading or replacing them.
37
1. Backup and Storage
MOG network has three major solutions for this part, HP 3Par is used to make
schedule backup, it supports the IPv6 protocol. Regarding for network attached storage
NAS, two types of equipment was provided for this objective. The first type is QNAP
for recording cameras and the second type is WD my cloud for store files and data.
Both of these types support IPv6 protocol without the need to replace any of them.
2. Virtualization and Monitoring
Virtualization is one of the most important components of an organization,
because it provides plenty of space, less consumption of power and it easier in remote
management. VMware Sphere is basic virtualization tool in MOG, which consist of a
bundle of virtualization software. ESXi is the hypervisor and it creates and runs virtual
machines in a shared storage, its utilize IP protocol to communicate and it supports
IPv6. Regarding monitoring, we want to classify monitoring tools on two groups: the
first group for IP cameras which exceeds fifty cameras, from DLINK corporation, see
table (4.2). The second group for fingerprint devices, there are more than twenty
devices from CHIYU corporation support IPv6.
Table (4.2): Types of MOG Cameras.
Camera Model Number Status
DCS-6010 3 Support
DCS-7010 22 Support
DCS-5222 3 Support
DCS-910 19 Doesn’t support
DCS-3411 7 Doesn’t support
38
3. Desktop and Laptops.
There are more than 500 PC’s and laptops, all of them used widely Microsoft
solutions as operating systems such as windows 7 and windows 10 and both editions
support the IPv6 protocol.
4. Printers and scanners.
There is more than a type of printer attached to MOG network which supports
IPv6, therefore there isn’t any fear towards these devices to make any problem. In
addition, the scanners are built in these printers.
5. Servers.
There are more than 40 servers in a data center, every server provides specific
services for clients, all of them run Microsoft windows server 2008 and later, all of
these editions support IPv6. For example, Domain Controller, File server, exchange
server and print server, besides those database servers which run windows server2008.
6. IP PBX and IP telephones.
In the MOG network we have main PBX and many sub PBX in different
buildings to make phone calls between employers to facilitate work. The PBX were in
two models Hiipath 3800 and Hiipath 3550, and both of them support IPv6.
There are several IP telephones which connect to MOG network and run over
TCP/IP protocol, there are many types of IP telephony vendors such as Openscape
Desk Phone IP 35G which support IPv6.
4.3.3 Intermediary Devices.
We mean in this portion every equipment responsible for connection and data
flow such as:
1. Routers.
There is one router used in MOG network, 1941 CISCO router with 15.2(4)
M3IOS, which support different feature to implement IPv6 routing. Beside this router,
there are several numbers of ADSL routers located in different external sites to make
a site to site VPN connection with Data Center. DGN2200v4 Netgear router hasn’t any
problem to support IPv6. Moreover, there is 750gr2 Mikrotik router to distribute
39
internet to users, this type from routers can support IPv6 after download IPv6 package
and enable it.
2. Switches.
They are many L2 CISCO switches, all of these switches support IPv6 for the
management interface, and therefore there is no problem for these switches to work in
dual-stack mode. MOG network included SG200 8, 20 and 26 ports, SG300 28 and 10
ports and SF500-48 port. In addition, for these L2 switches, there is one backbone
switch which is CISCO catalyst 4750, this switch is L3 used to make routing between
different VLANs in MOG network, and interconnect all different building. This switch
support IPv6 interface management and IPv6 routing protocols. Beside these… there
are one more GSM7212 NETGEAR switch, which does not support IPv6 management
interface in currently installed firmware.
3. Firewalls
Firewall is a fundamental aspect in any internal network to keep it secure from
external attacks, the MOG network has different types of firewall, these types can be
categorized as next:
Software Firewall: which found in ISA, TMG and PFSENSE servers, which
are support IPv6 without any problems.
Hardware Firewall: which represented in CISCO ASA firewall and
NETGEAR ProSafe Gigabit Dual-WAN SSL VPN Firewall FVS336Gv2, both
of these firewalls support IPv6.
4.4 Services.
Services are important things that affected by migration process, therefore we
should take care about them and try to find every service provided through MOG
network to avoid any mistake and network collapse, after enumeration we found these
services:
1. Active directory.
Represent repository for windows users, works with DNS and DHCP as a
domain controller. AD in MOG network runs on Microsoft server 2012, and there is
no problem to configure IPv6.
40
2. DNS.
The DNS service is essential for any IP network, to resolve the domain name
into a corresponding IP address. MOG network has two distinct DNS servers, enabling
IPv6 in both is easy.
3. DHCP.
Dynamic Host Configuration Protocol is responsible for distributing IP’s,
Gateways, DNS, and subnet mask for every attached device to the network. DNS and
DHCP are installed in the domain controller, which run over windows server 2012.
4. E-Mail
Microsoft Exchange Server is the largest and the most popular communication,
collaboration and emails messaging application today. Microsoft Exchange serves as
the hub of all email communications in most corporate environments that use the
Active Directory technology. The exchange server 2010 was deployed in the MOG
network and there no problem to support IPv6.
5. File Share.
We use in MOG network file server to facilitate access for data and file sharing,
this File server runs on Microsoft windows server 2008.
6. Print server.
To connect printers to client computers over IP networks and to ease printer’s
management. Printer drivers for more than fifty printers were installed on windows
server 2008, therefore no disquiet from this to support IPv6.
7. Oracle Database.
These Databases were installed in windows server 2008 and later, and all of these
editions support IPv6. This database represents the value of the MOG network because
it enables employees in different general administrations to make changes on it.
4.5 IP Addressing and VLAN Design.
In this section, we will present how the entire topology for the MOG network,
which has a main data center and contains more than forty servers and different devices
like UPS, storage, backbone switch and firewall. several L2 managed switches located
41
in different departments connected to a backbone switch, either by Ethernet cables or
Fiber optics to access servers and database to provide necessary services to citizens.
Many external locations connected to data center either by internet making VPN
connection or by Fiber Optics. The Municipality of Gaza has ten public
administrations located in different places, to facilitate manage and troubleshoot MOG
network, VLANs was implemented. Every VLAN has its own addresses scope
distributed by DHCP like this 172.17.x.y with subnet mask 24, x number represents
VLAN ID, all of these VLANs have routed in Backbone switch. There are more than
18 VLANs due to Administrative considerations and nature of work. Native VLAN
has its own private scope which is 172.16.0.0/16, every client connected to native
VLAN has IP ranged from 172.16.0.1-172.16.2.254.
Range 172.16.3.0-172.16.3.254 was reserved for servers and equipment in data
Center. The range 172.17.50.1-172.17.50.254 for CAMS VLAN. In a similar way
VLAN ID equals 100 reserved for printers and VLAN ID equal 60 reserved for finger-
printers. For security, we will not expand in enumerate MOG network elements and
obtain how MOG network connected to each other. MOG LAN is connected to the
WAN through CISCO ASA 5525 firewall, all of the external sites which connect to
MOG network through internet were connected through ASA firewall.
4.6 Conclusion.
After inventorying all the equipment connected to the network as we note in previous
sections and indicating which equipment does support IPv6 and which does not
support, we will display the mechanism that will be used to deal with these devices
which doesn't support IPv6 by the following procedure in figure (4.2), to minimize
costs as much as possible, to motivate the administration to adopt migration plan.
According to the next figure and after analysis for all mentioned devices, there
is equipment which needs a firmware upgrade, after doing a firmware upgrade for this
equipment, there is no necessity to replace it, these devices include finger-printers and
NETGEAR switch.
42
Figure (4.2): Dealing with Devices Doesn’t Support IPv6 Procedure.
After using the procedure in figure (4.2) in order to minimize the cost for
migration process, the only devices that need to be replaced to newer versions, just
twenty-six cameras form DLINK corporation.
43
Chapter 5: Transition Analysis and
Proposed Plan
Chapter 5
Transition Analysis and
Proposed Plan
44
Chapter 5
Transition analysis and proposed plan
In this chapter a prepared plan for MOG network to migrate from IPv4 to IPv6
will be introduced, it will be based on RFC 7381(Chittimaneni et al., 2014) and RFC
6180 (Arkko, J., & Baker, F., 2011) but in a suitable manner with MOG infrastructure
and IT staff experience. Therefore, the process will be defined in two consecutive
stages: the first will be before administrative approval, and the second will be
afterward, see figure (5.1). The adoption of these two stages is to emphasize that the
transition process consists of two aspects of administrative and technical sides. The
administrative aspect to ensure that the cost cannot be compared with the additions
that can be gained from improved network performance, increased security and to
ensure that the work in the enterprise will continue without interruption. The technical
aspect is the choice of the best transition method to migrate to IPv6 in addition to
prepare the address plan and put several alternatives for any arise problem during a
migration process. The proposed migration plan and its details will be discussed in the
rest of this chapter.
Figure (5.1): Generic Transition Plan.
45
5.1 First Stage: Before Administrative Approval.
This stage contains mainly three steps which estimate the cost, justifications and plan
preparation. They consider the initial stage to spread the idea of transition from IPv4
to IPv6 and make it acceptable at the administrative and technical level. These steps
will be containing several actions to complete them in order to achieve the first stage.
5.1.1 Estimate the Migration Cost.
The migration process is critical and is not as simple as it seems because they
are several components will be affected. Therefore, analyzing the network should be
done carefully, to know dependencies elements well. In order to have the ability to
calculate the estimated cost correctly, figure (5.2) illustrates the affected components.
Figure (5.2): Affected Components by IPv6 Deployment.
1. IT Staff Training: Every employee works in systems and networks department in
MOG should have 100 hours course that contains three main axes: CISCO, windows
and networking. This training in order to have the ability to deal with IPv6, also to
provide employees with the abilities and skills to follow – up work, provide quick
solutions for any problems and provide troubleshooting.
2. IP addressing: The cost of Acquiring an IPv6 address block from PALTEL, to
make address Plan for whole MOG network to reserve addresses and make network
management easy.
3. Hardware: Every IP capable device should be considered to estimate the right
cost for migration process and according to previous chapter, every device was
presented to show which of these doesn't support IPv6. Only twenty-six cameras don't
46
support IPv6. The next table will illustrate the total cost required in Municipality of
Gaza to IPv6 deployment.
Table (5.1): Calculated Cost for IPv6 Deployment in MOG.
Type Description Total Cost
IT staff training 100hours * 18$ 1800 $
DLINK cameras 26 * 200$ 5200 $
Acquiring IPv6 prefix Not Clear by PALTEL Do not exceed 300 $
Total 7300 $
The total cost was founded isn't comparable to what will benefit the MOG of a
marked improvement in the performance of the network. Moreover, to be proactive,
not reactive in the transition to IPv6. In addition, the cost will be much higher if the
process of deployment was sudden.
5.1.2 Justifications Step.
In addition to the expected cost of the replacement process, which is simple
compared to the improvements that will be gained by the Municipality of Gaza at the
network related to high performance and high security. There are many justifications
that will help the administration make the decision to adopt the transition plan.
1. The Municipality of Gaza is characterized by its possession of modern equipment
in the field of information technology.
2. The work of MOG is based mainly on its network compared to other institutions,
so the IPv6 should be considered.
3. The preparation plan, will avoid bad investment in equipment, due to take enough
time to make the right decisions related to IPv6 deployment model.
4. There is no need to replace existing equipment and devices, as more than 90%
support IPv6.
5. Present a Study Focused on the Migration Impact for the MOG, the new protocol
contains features and advantages in improving performance and increasing speed.
47
6. The team of engineers responsible for this task must pay special attention to security
and connection problems that may arise. So before implementation, they will make
a test-bed for assuring there will not be unexpected problems raised.
5.1.3 Planning Preparation Step.
As the idea gets an approval MOG administration, they will be several actions
should be done to lay the foundation stone for this process:
1. Inform every department about the migration process.
2. IT staff should have IPv6 training.
3. All software developed inside MOG, should take IPv6 into consideration.
4. From now, every requested hardware or software should support IPv6, and suppliers
should be asked for their roadmap to IPv6.
5. Acquire an IPv6 address block from its LIR.
6. IT staff should make some experiences with IPv6 through the LAB environment,
and try to find similar cases with other institutions to avoid mistakes and network
collapse.
5.2 Second Stage: After Administrative Approval:
This stage considers the actual beginning to implement IPv6, it contains two
steps. Every mentioned step in this section will have several actions and components
to achieve transition plan from IPv4 to IPv6. in the rest of this section, all these steps
will be discussed in details.
5.2.1 Proposed Migration Plan.
In this section, a prototype of the MOG network will be chosen to make a
transition plan, this subset of MOG network is comprehensive because it contains from
every mentioned device in previous chapter one, such as client PC, windows server,
Cisco router, Cisco firewall, camera, telephone, Cisco switch and fingerprint device.
For the reasons mentioned in thesis limitations, the whole MOG network will not be
subject for our proposed transition plan.
Let explain the current situation in details, our scope will have three different
locations, headquarter building, IT building and external collection center.
48
As we shown in Figure (5.3), three building summarizes the current situation in
MOG, IT building contain Data center connected with headquarter building through
Fiber Optics and VPN connection with external collection building through the
internet.
Figure (5.3): Connection Types Between MOG Buildings.
In figure (5.4) illustrates what is every site contain from IP devices to introduce
our steps in the transition process, taking this topology as an example to provide
optimal transition process to IPv6 and provide several solutions to every problem
anticipated to arise.
The next steps describe figure (5.4) that will help us to understand the migration
steps will be followed:
1. All servers have static IP from local native subnet such that 172.16.3.x
255.255.0.0.
2. All switches have static IP for management interfaces such that 172.16.90.x
255.255.0.0.
3. All printers have static IP such that 172.17.110.x 255.255.255.0.
4. All cameras have static IP such that 172.17.50.x 255.255.255.0.
5. All fingerprint devices have static IP such that 172.17.60.x 255.255.255.0.
6. All phones have static IP such that 172.16.110.x 255.255.0.0.
7. All end devices such as computers and laptops get their IP from DHCP server
according to the superior VLAN.
49
8. There are more than twenty VLANs with twenty different scopes in the DHCP
server.
9. Primary DNS used by clients to resolve a hostname to IP addresses.
10. Routing between different VLANs to reach each other is performed in L3 Cisco
switch.
Figure (5.4): IP Equipment Connected to MOG Network.
Therefore, to achieve our goal and make successful IPv6 migration, we will
consider every device attached to MOG network and observe every scenario, we cannot
turn the shelf away from any part, so as not to deceive ourselves. Our methodology
based fully on dual-stack and partially on tunneling mechanisms, we will provide our
reasons for our choice in section 5.2.3.
50
The proposed migration plan should have five major phases, to get in final a full
IPv6 transition, see figure (5.5):
1. Replacing equipment does not support IPv6.
2. Addressing plan.
3. Arrangement IPv6 deployment in the network.
4. Translation IPv4 network devices.
5. Disposal of IPv4.
Figure (5.5): Proposed Transition Plan for MOG Network.
51
1. Replacing Equipment does not support IPv6.
After analyzing MOG network and consider every attached device to the
network, 90% of these devices support both protocols which facilitate our approach to
implement dual-stack. Regarding the rest of devices which doesn't support the IPv6
such as cameras and fingerprint devices and based on figure 4.2, we found that twenty-
two fingerprint device from chiyu CO., for both versions BF630, BF670, after upgrade
firmware can support IPv6 protocol. Netgear switch can be upgraded to the latest
firmware to support IPv6 according to Netgear documentation.
In contrast, for some DLINK cameras such as DCS-930, DCS-910 and DCS-2103
which their number does not exceed twenty-six should be replaced for newer cameras
to support IPv6.
2. Addressing plan.
This section is very important and critical, there are several choices, but we
should choose what suit the current status in MOG.
Refer to "Preparing an IPv6 Address Plan Manual", it discussed a lot of methods,
and you as network administrator should pick one method for addressing to implement
it. There are three main methods:
A. No addressing plan.
This is for small networks, if you use this method, you should reserve every
distributed IP in excel sheet to be able to manage your network. This is not a practical
solution and cause overhead in network engineers and does not suitable for MOG
network.
B. Direct Addressing Map between IPv4 and IPv6.
For example, if you have the network with subnet mask /24, to facilitate it you
put the penultimate number of the IPv4 address (60 172.17.60.24/24, for example) in
the IPv6 subnet. The IPv6 address will then be 2001:db8:1234:60: :/64. This solution
is poor and doesn’t solve all problems occur from the previous method from MOG
perspective, for different reasons. One of these reasons, MOG subnet is not /24 and
our MOG LAN is big, in order to have the ability to save these addresses in Excel
sheets.
52
C. Prepare Addressing Plan.
This method is the best one, and make our choice for several reasons:
Easier to address trace and troubleshoot.
Scalability.
Implement security policies.
Effective way for management.
The first step to implement this method, is acquiring IPv6 prefix from PALTEL,
and we do that in October 2018 and they told us, there aren’t any blocks available right
now. PALTEL will start in June 2019 to distribute IPv6 blocks depends on the request.
For prepare address plan there are multiple choices available discussed in "IPv6
Addressing Plan Manual", we pick one suite for MOG management hierarchy which
based on use type primary subnet.
In the next example, we will discuss this method and clarify everything refers to
it, see figure (5.6)
Figure (5.6): Suggested IPv6 Address Plan for MOG Network.
Let’s say our IPv6 prefix is 2001: ad12: 1234/48, to calculate our subnets, the
following steps should be done:
a. Number of subnets based on use type equal to five subnets (IT, planning, finance,
projects, VPN)
53
b. One subnet for backbone.
c. Future use type is four. “constant”
d. Total equal to ten.
If we round this up to the first power of 2, this results in 16 subnets. Incorporating
these subnets into the IPv6 address requires 4 bits (G) (24 = 16). This leaves 12
available bits (B).
200
1
ad1
2
123
4
G G G G B B B B B B B B B B B B ::/6
4
Using type as primary subnet in order to facilitate implement a security policy,
and our sub-networks in MOG was distributed according to the type of use. Therefore,
our subnets become, see table (5.2).
Table (5.2): VLAN in IPv6 for MOG Network.
Subnet Address Prefix
IT subnet 2001:ad12:1234:1000:://64
Finance subnet 2001:ad12:1234:2000:://64
Planning subnet 2001:ad12:1234:3000:://64
Projects subnet 2001:ad12:1234:4000:://64
VPN 2001:ad12:1234:5000:://64
After the address plan become ready and include all sub-networks in MOG, the
next step is to configure hosts addresses. To manage hosts with IPv6 there are three
main methods to implement that, two of configuring hosts methods fall under
automatic configuration, and the third method is static configuration.
A. Automatic Configuration.
Stateless Address Auto-configuration. Or SLAAC which use information in router
advertisement (RA) information, to combine with interface MAC address to assign
an IPv6 address. This in short, but this method not suitable for MOG network
54
because there aren’t any router assigns IP addresses (Thomson, S., Narten, T., &
Jinmei, T., 2007).
Dynamic Host Configuration Protocol for IPv6 (DHCPv6).
DHCPv6 can be used as a substitute for SLAAC. In this case, the IPv6 addresses
are explicitly distributed by the DHCPv6 service. DHCPv6 service is bundled with
DNS service and Active Directory in the same server, for every subnet, we create scope
from IPv6 address and exclude from every scope definite number of IPs reserved for
some equipment related to this subnet.
B. Manual Address Configuration.
We recommend manual assigning IPv6 addresses for devices such as L2
switches, L3 switch, servers and firewalls. In order to ease management for this
devices and to avoid misconfiguration. For example, if these devices configured
through automatic ways and one of the interfaces was replaced without modifying their
DNS AAAA record, will cause a lot of problems in tracing and troubleshooting.
3. Arrangement of IPv6 Network Deployment
To implement IPv6 in the MOG network, there will be ordering to this process
to ensure there will not be any problem and avoid the MOG network to be down. This
order should be followed to facilitate the migration process and control it.
A. Firewalls and Switches.
Switches are layer 2, and the only thing we can do to it, configure their IPv6
management interface. L3 4507 switch has a static routing table between VLANs, this
routing table should be upgraded to include IPv6 routing between different subnets.
Due to the policies of security related to the firewall, it should be upgraded to have the
ability to deal with IPv6 packets with extension header to protect it from dropping.
B. Basic Network Services.
After the previous step, all of the services should be upgraded to support IPv6
such as DNS and DHCP. Because when upgrading internal devices and request
hostname, DNS can have the ability to respond to these requests according to AAAA
record. Beside that when attached devices request an IPv6 address from their scope
through L3 switch through IP helper, they get the reply.
55
C. End Devices.
End devices such as PC’s, Laptops, workstations and printers. As it is clear the
order of the deployment process from boundary devises to internal passing through
services.
4. Translation IPv4 Network Devices.
A10networks fabricated devices overcome the problem of IPv4 network devices
which are vital in organization functions, and in the same time they couldn’t be
upgraded into IPv6 by NAT64/DNS64. which uses a protocol translation approach,
versus an encapsulation approach, to connect IPv6 users to IPv4 services. This allows
data only available via IPv4 to be retrieved and returned to an IPv6 client. See the
below figure, which explains in several steps, the process for NAT64/DNS64 solution.
Figure (5.7): DNS64/NAT64 Mechanism.
56
5. Disposal of IPv4.
Step by step and as time passes on, depending on IPv4 become less, and every
device in the MOG network should support IPv6. In this level we should do that to
reduce overhead and complexity from boundary devices:
A. IPv4 should be removed from the firewall and the router.
B. IPv4 addresses should be returned to the respective LIR.
C. Every device attached to the network to facilitate IPv6 only devices to connect
IPv4 devices or Vice versa, should be removed.
After complete these steps, we found us make complete IPv6 migration.
5.2.2 Implementation.
The primary goal for our IPv6 deployment is to facilitate the continued growth
of the MOG network and deployment of internet technology without confusion and
assure for network connectivity in low capital. This cannot be done by IPv4, because
it is stressed, so it becomes expensive either in real cost or complexity in technology.
To achieve success IPv6 deployment, there are several features should be taking
into account such as:
The deployment process should be in incremental fashion. MOG network should
be divided into several parts, and the transition process shouldn’t be switched
suddenly.
Lack of dependencies between components to avoid a user become not able to
retrieve any service.
Allow the network to be maintained, serviced, diagnosed and measured.
Simple, operate under any circumstances.
The design should be support robust interoperability.
To implement success design characterized by previous features, several factors
such as IT staff experience and reduce cost, should define the suitable transition
method from IPv4 to IPv6. There are several models were discussed in RFC 6180, but
the most relevant models for MOG status and fit MOG network specifications are two,
dual stack and tunneling.
57
1. Dual stack:
The simplest model and recommended approach by IETF standards such as
[RFC4213], it is applicable to most networks such as home, enterprises and service
provider (E Nordmark and R Gilligan, 2005). It is avoiding problems associated with
the configuration of tunnels and MTU. These networks are robust and reliable.
2. Tunneling:
This model is recommended when native IPv6 connectivity is not always
available. Tunneling is used if it is necessary to cross a segment of IP version X when
communicating from IP version Y to Y. The IPv6 Rapid Deployment (6RD) (Despres,
R., (2010) approach is a newer version of the 6to4 tunneling solution, it offers
systematic IPv6 tunneling over IPv4 across an ISP, correspondence between IPv4 and
IPv6 routing, and can be deployed within an ISP without the need to rely on other
parties.
5.3 Conclusion and Validation.
In this chapter a full specific transition plan was put down for deployment IPv6
in MOG network, see figure (5.5). This model meets the requirements of MOG
network infrastructure and the experience of IT staff in MOG. This model after has the
administrative agreement for such process, should start with analyzing the current
situation in the MOG network, because by this action we have the ability to estimate
the correct cost. after complete the first step, the IT staff should be ready to replace
every device would hinder the IPv6 deployment by found suitable alternative that
supports IPv6.
and the next step after all of the devices in the network support IPv6 is to prepare
address plan fit the MOG network and its characteristics, in beside that choose the
correct method to configure the hosts. The next step is to choose the order of deploy
IPv6 among devices, taking into consideration what the provided solutions to deal with
vital components that don't support IPv6, and there is no way to replace them. Finally
choose suitable transition methods to implement IPv6 such as dual stack and 6RD
tunneling.
58
After this plan was submitted to the “Systems and network” department in MOG,
they were astonished by this plan and provided me this certification as approval.
59
Chapter 6: Experimental Validation
Chapter 6
Experimental Validation
60
Chapter 6
Experimental Validation
After proposed transition plan becomes ready for implementation, the simulation
environment is a critical issue to assure IPv6 efficiency and MOG network is out of
any problems. In order to build our virtual Lab and topologies to compare between
IPv4 and IPv6 performances related to several parameters such as delay and response
time. This is not the only reason for using such simulations but also to test the validity
of the proposed transition plan, including different methods, if it will be suitable for
the nature of the MOG network?
In this chapter we carried out our simulations using two tools: the first one is
VMWARE workstation for testing windows virtual LAB to verify the services built in
windows is free from any errors or be stopped. The second tool is OPNET simulation
for testing some scenarios (J Theunis and P Leys, J Potemans, 2003), that reflect the
MOG network, to show IPv6 performance, these scenarios and their results will be
discussed in details in next two sections.
6.1 Windows Platform.
The MOG network contains more than 500 computers, in addition, more than 40
servers, all of them run Microsoft Windows platforms variance between Windows 7
and Windows 10 for client computers. All of the servers are used windows server
operating system 2008 and later, as we discussed previously in chapter 4, all of these
operating systems are supporting IPv6.
These windows products in documentation support IPv6, but we should check if
these products support all windows services after using IPv6 as internet protocol and
to assure that these services are operating without any errors or need anything to run
normally. Remote desktop is famous remote service provided by windows, which
allow help desk group members to access any remote desktop to provide quick
problem-solving. Also, there is another third party application which has the same
objective broadly used in the MOG network which called DamWare mini remote
control. Not just these services there are several important services for any network
such as active directory (AD), DHCP and DNS.
61
6.1.1 Methodology.
After establishing virtual LAB, which consists of three machines by VMWARE
workstation tool, this LAB contains a domain controller machine, windows 7 and
windows 8 machines. The domain controller is very important, it contains three of the
network services AD, DHCP and DNS. Active directory to authorize and authenticate
users and computers and to assign and enforce security policies for all computers and
installing or updating software. DHCP to distribute four main components to attached
equipment in the network, which are IP address, subnet mask, default gateway and
DNS. DNS to resolve names from IP addresses.
This scenario was built after installing windows server 2012 and assign it both
static IP4 and IPv6 addresses, and change the name of this computer as "PDC”. In
addition, run “dcpromo” command to convert this machine as a primary domain
controller. Besides that, we set up additional two services DHCP and DNS and
configure them.
Two client computers with two operating systems 7 and 10 were established, and
join them for the “MOG” domain after obtaining IPv4 and IPv6 addresses from DHCP
and DHCPv6 services configured in PDC.
After these two client machines joined the domain, automatically A and (AAAA)
records were created in DNS.
6.1.2 Results.
As we show in figure (6.1), DHCP service works well and assign every joined
machine dynamic IP for both: IPv4 and IPv6. Pc1 and Pc2 have obtained the IP
addresses, and both will be founded in address lease in DHCP service.
62
Figure (6.1): DHCPv6 in PDC.
DNS service works well in IPv6, two records created for every PC, one for IPv4
and the other for IPv6 as we notice in figure 6.2.
Figure (6.2): DNS in PDC.
63
6.2 Networking.
The aim of this section is to find out what the advantages gained from using IPv6
under particular applications run in MOG network. The simulation has been carried
out using optimized network Engineering Tool (OPNET).
OPNET Network simulator is a tool to simulate the behavior and performance
of any type of network, we choose this tool because of its power and versatility
compared to other tools, besides that it is open free software and there is a large number
of project scenarios that are offered information on OPNET (Clore, B., Dunlop, M.,
Marchany, R., & Tront, J., 2012).
6.2.1 IPv4/IPv6 Design and Implementation.
The objective of this simulation is to compare between IPv4 and IPv6
performance according to different parameters which are delay and response time. This
comparison carried out using two projects: “final” and “vlancompare” projects. Each
project has two scenarios close enough to the real state of MOG network and similar
to figure (5.4). The final project has two scenarios, flat IPv4 topology as the figure
(6.3) and flat IPv6 topology as the figure (6.4). The second project vlancompare has
two scenarios for both IP protocol versions with VLAN, see figure (6.6) and (6.7).
6.2.2 Methodology.
The method for the first project consists of selection two Ethernet switches
located in different locations, ten Ethernet workstations attached for every switch via
100baseT. Three different servers each one provides different application, these
applications are a database, print and file server. These applications which consider
the most three important applications in the MOG network, we recognized applications
in project. If we compare figure (6.4) and figure (6.5) with each other’s, we will find
both have similar components which we mentioned above, but the main variance
between them is the used protocol for every scenario.
64
Figure (6.3): IPv4 Architecture.
This figure (6.3) represents flat IPv4, its contain the same components and
application configuration in figure (6.4), except IP version used to transmit the packet.
This topology is exclusive for IPv4 testing.
Figure (6.4): IPv6 Architecture.
After creating another scenario in the final project exclusive for IPv6, we get the
topology obtained by a figure (6.4). This topology to test IPv6 performance related to
delay and response time parameters.
65
Due to the vlancompare project, we define three different VLANs which are IT,
planning and financial in the switches, but in less number of Ethernet workstations.
The figure (6.5) and (6.6) related to this project. In both projects we define IP versions
used in the network by using the protocols>IPv6>Auto-Assign IPv6 addresses for
IPv6 network, related to both IPv6 scenarios. Due to IPv4 network, we choose
protocols>IPv4>Auto-Assign IPv4 addresses, for both IPv4 scenarios in both
projects. On free space, press down right click and choose individual DES statistics
and choose which parameter do your analysis in your scenario, for our measurements
we select Ethernet delay and response time.
Figure (6.5): VLAN in IPv4 Architecture.
The creation of VLAN was done by configuring both switches in figure (6.5)
and figure (6.6), every VLAN contain a different number of PCs. VLAN members
request them services from a dedicate server. Three servers which are planning, IT and
financial handle member’s requests.
66
Figure (6.6): VLAN in IPv6 Architecture.
This topology in figure (6.6), designed for test IPv6 performance related to delay
and response time, after establishing VLAN in it.
VLAN in OPNET can be created after configuring switches ports to be a member
of one VLAN. Figure (6.7), illustrate for us how to create VLAN in switches by
OPNET tool.
Figure (6.7): Creating VLANs in Switches.
67
6.2.3 Components
This section discusses the general components used in suggested network
models formed in OPNET:
1- The "Profile Config" node: Can be used to create profiles for users, which can be
applied to different nodes in the network, that is used to generate layer 7 (application
layer) traffic. In the “ApplicationConfig” you must create an application to be used by
this profile.
2- Using the “Application Config”: You can specify the traffic patterns followed by
the applications as well as the configured profiles of this object.
3- The Ethernet server model represents a server node with server application run
over TCP and UDP.
4- The Ethernet workstation represents client computer which runs client-server
applications.
5- The 100BaseT link: links between several switches, servers and workstations.
6.2.4 Results.
In figure (6.8) the comparison happened between two protocols in flat topology
without VLANs configuration, the mentioned figure shows us the delay of IPv6 is less
than the delay in IPv4. This simulation is done in 0.2 hours for twenty workstations,
three servers and two switches, for IPv4 it exceeds 37 ms in contrast with IPv6, the
delay reaches approximately 26ms.
We suggest that if we increase the number of devices, the difference between
two protocols will be more noticeable and this result rationality due to the simplicity
of IPv6 header, in addition to the fragmentation in packets does not happen in
intermediary nodes but in end devices in contrast with IPv4.
68
Figure (6.8): Comparing Delay Between IPv4 and IPv6.
With reference to figure (6.9) the comparison happened between the results of
two scenarios. One for native IPv4 topology and VLAN in IPv6 topology, the
difference in delay for these scenarios approve the advantage for VLAN
implementation in IPv6. The delay for the last one not exceed 5 ms, because just
routing tables will be implemented in switches, without more processes happening for
packets in switches, in contrast with native IPv4 scenario, the fragmentation of packets
and broadcast will happen in switches, besides that the IPv4 header complexity which
will increase time to handle packets.
Figure (6.9): Comparing Delay Between IPv4 and VLAN in IPv6.
69
According to figure (6.10), shows us the benefits of implementing VLAN in
IPv6 over native IPv6 topology. The difference between delay in both scenarios was
clear, with VLANs not exceed 5 ms, without VLAN reaches approximately 26ms.
Figure (6.10): Comparing Delay Between IPv6 and VLAN in IPv6.
Related to figure (6.11), the output diagram shows us the difference between
response time relevant to each protocol, with regard to IPv4 response time exceed 55
ms which is higher than IPv6 response time that reach approximately 50 ms. This
useful for MOG network users because a lot of interactions have been done in the
database which accelerates database response. The reason for this difference in
response time between two protocols because of simple header for IPv6 and disposal
from unimportant fields and convert it to optional fields. In addition to fragmentation
for packets happened in end devices, not in switches which reduce processing for these
intermediary devices.
70
Figure (6.11): Comparing Response Time Between IPv4 and IPv6.
6.3 Conclusion and Validation
IPv6 will be a predominant internet protocol and this issue is inevitable in the
near future, because IPv4 is not compatible with the huge technological development,
in terms of providing sufficient number of addresses for IP equipment. In addition, this
main drawback, IPv4 header complexity affect real-time application by degrade
performance of such application, moreover security gaps and prevent an end to end
communication through implement short-term solutions like NAT.
IPv6 come to solve IPv4 drawbacks especially in abundance of it addresses,
enhance routing, have attention for the quality of service and built-in security and more
as discussed in chapter 3. And regardless of these valuables features, unless the
enterprises pay attention to IPv6 migration, it will face the danger of death, because it
will become completely isolated from the other world. For this reason, every enterprise
should have a complete transition plan, complete answer “know how” to succeed when
they decide to migrate to IPv6.
In this thesis we worked hard to suggest the proposed plan for an enterprise
migration to IPv6, we took MOG network as a case study, because it has a huge
network that includes many different technologies that are characterized by
technological advances, this institution makes this research a valuable resource for
many institutions that aspire to do so.
71
The References
The References
72
The References
A10, Website: http://www.a10networks.com/products/axseries-NAT64_DNS64.php.
Al-Gadi, G. Y. A. Y., Amin Babiker, A., Mustafa, N., & Hamied, M. A. (2014).
Evaluation and Comparisons of Migration Techniques From IPv4 To IPv6 Using
GNS3 Simulator. Evaluation, 4(08).
Arkko, J., & Baker, F. (2011). Guidelines for Using IPv6 Transition Mechanisms
during IPv6 Deployment (No. RFC 6180).
Bi, J., Wu, J., & Leng, X. (2007). IPv4/IPv6 transition technologies and univer6
architecture. International Journal of Computer Science and Network
Security, 7(1), 232-243.
Boss, S., & Krauss, J. (2014). Reinventing project-based learning: Your field guide to
real-world projects in the digital age. International Society for Technology in
Education.
Briscoe, N. (2000). Understanding the OSI 7-layer model. PC Network
Advisor, 120(2).
Carpenter, B., & Jung, C. (1999). Transmission of IPv6 over IPv4 domains without
explicit tunnels (No. RFC 2529).
Che, X., & Lewis, D. (2010). Ipv6: current deployment and migration
status. International journal of research and reviews in computer science, 1(2), 22.
Chittimaneni, K. K., Chown, T., Howard, L., Kuarsingh, V., Pouffary, Y., & Vyncke,
E. (2014). RFC 7381: Enterprise IPv6 Deployment Guidelines (No. RFC 7381).
IETF.
Clore, B., Dunlop, M., Marchany, R., & Tront, J. (2012, May). An evaluation of IPv6
in simulation using OPNET modeler. InProc. of the 8th Advanced International
Conference on Telecommunications (pp. 111-115).
Conta, A., & Deering, S. (1998). Generic packet tunneling in IPv6 specification (No.
RFC 2473).
73
Dawadi, B. R., Joshi, S. R., & Khanal, A. R. (2015). Service Provider IPv4 to IPv6
Network Migration Strategies. Journal of Emerging Trends in Computing and
Information Sciences, 6(10).
Dawadi, B. R., Shakya, S., & Khanal, A. R. (2015). Government Roadmap for IPv4 to
IPv6 Network Migration: A Case of Nepal. Journal of the Institute of
Engineering, 11(1), 67-78.
de Castro, P. F. M. (2013). Process for IPv6 Migration in Large Organizations.
Deering, S., & Hinden, R. (2017). Internet protocol, version 6 (IPv6)
specification (No. RFC 8200).
Despres, R. (2010). IPv6 rapid deployment on IPv4 infrastructures (6rd).
Downs, K., Spanier, S., Ford, M., Stevenson, T., & Lew, H. K.
(1998). Internetworking technologies handbook. Cisco Press.
Dutta, A., Alberi, J., Cheng, A., Horgan, B., McAuley, T., Chee, D., & Lyles, B. (2006,
October). IPv6 transition techniques for legacy application. In Military
Communications Conference, 2006. MILCOM 2006. IEEE (pp. 1-9). IEEE.
Francisco, M. (2010). Planificación y Administración de Redes.
Gilligan, R., & Nordmark, E. (2000). Transition mechanisms for IPv6 hosts and
routers (No. RFC 2893).
Goth, G. (2005). Close to the edge: NAT vs. IPv6 just the tip of a larger problem. IEEE
Internet Computing, 9(2), 6-9.
Kaushik, D. (2008). IPv6–The History and Timeline.
Kobayashi, V. M. N. V. N. (2004). IPv4/IPv6 translation technology. FUJITSU Sci.
Tech. J, 40(1), 159-169.
Limkar, S. V., Jha, R. K., Patil, T., & Kalbande, M. (2010). IPv6: Features, Current
Deployment Scenario, Issues and Migration Status in India. In Proceeding of the
International Conference on Software and Computing Technology, ICSCT(pp.
V2-149).
Loshin, P. (2004). IPv6: Theory, protocol, and practice. Elsevier.
74
Lowe, D. (2003). Networking for dummies. John Wiley & Sons.
Main, A., Zakaria, N. A., & Yusof, R. (2015). Organisation Readiness Factors
Towards IPv6 Migration: Expert Review. Procedia-Social and Behavioral
Sciences, 195, 1882-1889.
Negara, E. S. Performance Analysis for Migration Method IPv4 to IPv6 Using Dual-
Stack Technique.
Neumann, J. C. (2015). The Book of GNS3: Build Virtual Network Labs Using Cisco,
Juniper, and More. No Starch Press.
Nordmark, E., & Gilligan, R. (2005). Basic IPv6 Transition Mechanisms (RFC4213).
Popoviciu, C. (2006). Deploying ipv6 networks. Pearson Education India.
Preparing an IPV6 Address Plan, (2013), Manual, Website:
https://www.ripe.net/support/training/material/IPv6-for-LIRs-Training-
Course/Preparing-an-IPv6-Addressing-Plan.pdf
Quynh Anh, N., Nguyen, M., & Phu, N. (2012). Transition from IPv4 to IPv6: Best
transition method for large enterprise networks.
Raicu, I., & Zeadally, S. (2003, February). Evaluating IPv4 to IPv6 transition
mechanisms. In Telecommunications, 2003. ICT 2003. 10th International
Conference on (Vol. 2, pp. 1091-1098). IEEE.
Shelly, G. B., & Vermaat, M. E. (2011). Discovering Computers, Complete: Your
Interactive Guide to the Digital World. Cengage Learning.
Shiranzaei, A., & Khan, R. Z. (2015, March). Internet protocol versions—a review.
In Computing for Sustainable Global Development (INDIACom), 2015 2nd
International Conference on (pp. 397-401). IEEE.
Subramanian, S. (2003). Ipv6 transition strategies. White Paper, 4, 5.
Theunis, J., Leys, P., Potemans, J., Van den Broeck, B., Van Lil, E., & Van de Capelle,
A. (2003). Advanced Networking Training for Master Students Through OPNET
Projects. In Proceedings of the 2003 OPNETWORK Conference.
Thomson, S., Narten, T., & Jinmei, T. (2007). IPv6 stateless address
autoconfiguration (No. RFC 4862).
75
Vachon, B., Graziani, R., & Díaz, J. M. (2009). Acceso a la WAN: guía de estudio de
CCNA Exploration. Cisco.
Valle-Rosado, L., Narváez-Díaz, L., González-Segura, C., & Chi-Pech, V. (2012).
Design and Simulation of an IPv6 Network Using Two Transition
Mechanisms. International Journal of Computer Science Issues (IJCSI), 9(6), 60.
Yousafzai, M. M., Othman, N. E., & Hassan, R. (2015). TOWARD IPV4 TO IPV6
MIGRATION WITHIN A CAMPUS NETWORK. Journal of Theoretical &
Applied Information Technology, 77(2).
Zeadally, S., & Raicu, L. (2003). Evaluating IPv6 on windows and solaris. IEEE
Internet Computing, 7(3), 51-57.
76
Appendix 1
An interview with the head of systems and networks department in the
municipality of Gaza.
1. Is there any prior knowledge of IPv6?
Yes, there is
2) If the answer to the first question is yes, how did you gain this
knowledge?
I gained this knowledge through IPv6 course had done at IUGAZA and
donated by PALTL. This course aimed to guide network engineer to merge to
IPv6.
3) Through your studies of the new protocol, did you feel it could be
applied to your organization?
Sure, the trend now mandatory to change to IPv6
4) Which vendors do you have for laptops, servers, switches and
routers?
For laptops, PCs, Servers are HP and DELL.
For switches and routers are Cisco.
5) What do you think about the advantages of the new protocol? Do you feel
that your organization needs to apply it?
Sure. Because of all new hardware and software should work with a latest and
updated protocol. So, we Know that in short period of time.
6) If there is a desire to apply the new protocol, is there a plan for this
implementation?
Sure, there is. But no plan till now.
7) What concerns do you have if the new protocol is implemented, given the cost
of training, the replacement of the equipment to support, and the time
required for the transition?
77
A. We need a capacity building for the technical stuff.
B. We do need to update all OS to support IPv6.
C. We need to update all intermediary devices to support IPv6. Also we should
replace old devices gradually.
D. The time is very important.
E. Cost of the whole component of an immigration plan.
8) What is the expected cost and time required to complete it?
We haven’t any plan till now,
9) If the new protocol is approved, what is the most important thing to
determine the best type of transition, is it cost or performance?
Sure the performance
10) How large is your current computer network? (Number of
computers/users/servers)?
Computers are 550 and users the same number, servers more than 40.
11) What is the expected budget that your organization would be willing to
spend for the transmission from IPv4 to IPv6?
This is varying and depend in many factors.
12) What do you expect from this solution?
This solution will open closed doors in all IT Fields.