117

Chapter 5

Case Study Analysis and Comparison

This chapter will discuss the analysis of case study for implementing IPv6 in

Campus/Enterprise network in two different universities in Southampton and Malaysia.

Hopefully by analyze and compare the deployment of IPv6 in both universities can help

BiN us JWC determine the best solution for implementing IPv6 in term of time, cost, and

deployment strategies they want to choose.

5.1 Case Study Analysis to Compare the Deployment of IPv6 in Campus/Enterprise

Network

Before deploying IPv6 in BiN us JWC, it will be a good idea to look the analysis of IPv6

implementation in several universities around the world. By study the advantages and

disadvantages and also technical difficulties of the implementation, hopefully the

implementation of IPv6 in BiN us JWC will be well prepared.

5.1.1 Implementation of IPv6 in Large Academic Department (University of

Southampton)

University of Southampton using dual stack VLAN technique for implementing the IPv6.

Before talk much further about the technique, let’s see the list of system components that

are used in University of Southampton.

118

The system component in this university divided into five categories.

a) Network components

Ø Physical connectivity (Layer2), technologies used are: Switched Ethernet,

Gigabit Ethernet, Wireless Networking (802.11b)

Ø Routing and logical subnets, the equipment is composed of Alcatel OSR and

Omnicore L2/L3, with 15 internal IPv4 subnets

Ø Firewall, currently used CheckPoint Firewall-1 solution running on Nokia

IP740 hardware platform.

Ø Management, for the network management is performed by SNMP.

Ø Remote access, the component supporting remote access are: Livingston

Portmaster 56K/ISDN dialup, RADIUS server, Microsoft VPN Server.

Ø IPv6 access, for the IPv6 service is taken from regional network (LeNSE) to

the JANET (NREN) and facilitated by 6PE over MLPS

b) Address allocation components

Network devices will use a combination of address allocation mechanism:

Ø Manually configured addresses (in some servers)

Ø Stateful DHCPv6 (probably in fixed, wired devices and some servers)

Ø Stateless address autoconfiguration (probably in wireless and mobile devices)

Ø RFC 3041 privacy addresses (in some client devices)

c) Services

The components services hosted by the department of network are:

Ø Email, there are three MX host for inbound email, and two internal mail

servers. Sendmail is the MTA, POP and IMAP are used for mail access.

119

Ø Web Hosting, web content hosting is provided either with Apache 1.3x (open

source) or Microsoft IIS 5.0

Ø Directory services, directory server tool are in used: NIS (6 servers, all

Solaris), LDAP, Active Directory, RADIUS.

Ø Remote login is offer via ssh with sftp for file transfer. telnet and ftp is denied

by the firewall.

d) Host and devices platforms

List for host and device platform are:

Server platform:

Ø Windows 2003 server

Ø Windows 2000 server

Ø Windows NT

Ø Solaris 8

Ø Solaris 9

Ø Red Hat Linux

Ø SGI Origin 300 (Irix 6.5.x)

Host platform:

Ø Windows 98, 2000, ME, XP

Ø Linux

Ø MacOS/X

Ø BSD

PDA platform:

Ø Windows CE/.NET

120

Ø Palm OS

Ø Zaurus

e) User tools

Various user tools are:

Ø Hardware; networked printers and network webcams

Ø Mail client; Outlook, Eudora, mutt. and pine

Ø Web browser; Internet Explorer, Mozzilla, Safari, Opera

Ø Other collaboration tools; IRC, Jabber, MSN Messenger, and cvs.

5.1.1.1 Transition Status

The main focus for this implementation is to provide increasing functionality in a dual-

stack environment, with the goal of allowing IPv6-only devices to be introduced and to

operate successfully using only IPv6 transport.

Because the Alcatel switch/router equipment does not route IPv6, an alternative method

was required to deliver IPv6 on the wire to existing IPv4 subnets. To enable this, IPv6

router advertisements were delivered using a parallel IPv6 routing infrastructure. These

IPv6-only routers support IEEE 802.1q VLAN tagging; the BSD routers can inject a

different IPv6 prefix onto each IPv4 subnet, using congruent VLANs. The router tags the

packets travelling towards the internal network with a configured VLAN ID depending

on the destination IPv6 prefix/link. This VLAN method is described in Figure 5.1.

121

Figure 5.1 Use of IPv6 VLANs at Southampton [18]

As traffic in the site grows, multiple routers can be dedicated to this task for internal

routing, or a router with multiple interfaces. There currently four routers with quad Fast

Ethernet interfaces. BSD allows multiple-VLAN tagging per interface, so in light traffic

conditions the interface count can be collapsed. But problem occur when BSD begin to

handle more IPv6 traffic.

External IPv6 connectivity was configured using a Cisco 7206, for unicast and multicast

(SSM and PIM-SM), with IPv6 multicast routed internally onto the VLANs using the

BSD IPv6 multicast support. The connection to the JANET IPv6 service is delivered

natively through the LeNSE regional network.

The longer term plan is to use IPv6 firewalling on the Nokia IP740; until then the firewall

is an additional BSD system, on which ports are blocked by default. This is a partially

122

stateful firewall. Two IPv6-only DNS servers have been run in the past; now the main

servers network/subnet is IPv6- enabled the department’s three primary BIND9 DNS

servers have been IPv6-enabled.

The main Linux login server is IPv6-enabled, with ssh logins and sftp file transfer

available through the firewall. Once IPv6 is present on the wire, all that was needed was

the firewall hole to be opened up for the service, an IPv6 AAAA DNS entry added for the

login server, and the sshd daemon with IPv6 support turned on. Offering only secure

protocols (and not plain ftp or telnet) can be easier to do when starting afresh with a new

protocol.

NTP has been provisioned for IPv6 by use of both the RIPE TTM server as an NTP

server, and also a dedicated NTP server from Meinberg, that supports both IPv4 and

IPv6. Our SMTP and MX servers now exchange external email over IPv6. IPv6 DNS

records were added for the hosts that provide these services. If the sending or receiving

node we are communicating with supports IPv6, IPv6 transport for email is usually

preferred.

The department’s Wireless LAN (over 30 access points) is IPv6 enabled. Some Mobile

IPv6 has been deployed and tested between the WLAN and the local community wireless

network (SOWN), using the MIPL code (which lacks security elements, but is usable).

The more advanced WLAN network we deployed uses 802.1x based access control,

123

which is IP version neutral and thus can be used to secure the IPv4 and IPv6 WLAN

access.

5.1.1.2. Supporting Remote User

The researcher try to offer a tunnel broker and a 6to4 relay for remote users, e.g. students

in home networks or staff in wireless hotspots at conferences. At present tunnel broker

users connecting get either a single IPv6 address or a /64 prefix. To offer more, in

particular a /48 from our tunnel broker, we would need to use our RIPE membership to

obtain LIR status and get a larger ‘ISP’ prefix. The researcher are assisting UKERNA to

deploy a national academic IPv6 tunnel broker, using the Hexago broker which includes

TSP support.

5.1.1.3 Next Step for the Transition

For the next step of the transition several work had to be done:

Ø A DHCPv6 service is required; implementations will be tested in the near

future (from Cisco and Lucent). This will enable IPv6 DNS resolver discovery

for hosts, but also be used for address allocation.

Ø Work on modifications to Snort to allow IPv6 IDS functions to be used.

Ø A dynamic DNS service is required for statelessly configuring hosts.

124

5.1.1.4 IPv6 Transition Missing Components

In the study for transition, we have identified a number of missing (unavailable)

components for IPv6 transition, including:

Ø No IPv6 Layer 3 Functionality on the Alcatel OSR/Omnicore equipment.

Ø Lack of NFS/Samba IPv6 support,

Ø Lack of MS Exchange, Outlook, or Eudora IPv6 support,

Ø No IPv6 intrusion detection system,

Ø No IPv6 support for Active Directory,

Ø Lack of supported IPv6 for Windows 98/2000/ME,

Ø Lack of supported IPv6 for Irix,

Ø Lack of supported IPv6 for various PDA platforms

Ø No method available to offer reverse IPv6 DNS for sendmail to verify

autoconfiguration hosts.

Ø No available IPv6-enabled X11.

5.1.2 Migration from IPv4 to IPv6 in Universiti Sains Malaysia (USM)

The goal of migration process from IPv4 to IPv6 in Universiti Sains Malaysia (USM) is

to migrate to IPv6 network but consider being economical in term of the cost of

migration.

125

The discussion of this migration itself more focused on the cost of migration. Cost for

implementing IPv6 in USM network is divided into two main categories, Statistical

approach and Economic Assessment approach. Statistical approach discussing more

detail about IPv6 migration cost and also ISP transition cost in order to do that, the

analyst should collect data regarding the internet user and also the ISP itself. Whereas in

the other hand the Economical Assessment approach will discuss about direct cost that

will become an impact of the migration.

For the decision whether or not the migration in USM will take place or not, is based on

the analysis result of the Economical Assessment approach. Economical Assessment

approach predicts that the cost of migration will be high at the first time but the cost will

get lower eventually. The assumption itself is based on two reasons:

Ø Wide benefit that IPv6 offer

Ø Cost for hardware and software predict to be cheaper when everyone will

eventually move to IPv6 protocol.

Because USM consider being a non-profit organization (university) the cost model for

Economical Assessment is divided into four components:

Ø Network Hardware cost

The cost for network hardware can be seen based on the scope of the network

itself and how big the network is also the level of IPv6 that will be used in the

network. The type of network hardware is varying like router, switch, PC

Router, hosts, and Network Interface Card (NIC).

126

Ø Network Software and Operating System cost

This kind of upgrade usually will cost more than network hardware cost

depends on the number of software and operating system used. Operating

system cost considers being small cost compare to the large server application

like network monitoring software and ERP.

Ø Training cost

Training the network administrator to understand the migration process from

IPv4 to IPv6 becomes essential part of migrating system. The network

administrator is responsible to maintain the network and keep track for the

upgraded technology.

Ø Unpredictable cost

The unpredictable cost more likely the cost that the USM should prepare after

the migration process finished.

USM proposed cost model diagram to identify what kind of cost should be spend in the

migration process also the diagram make it USM easy to keep track the cost.

127

Figure 5.2 IPv6 Cost Model diagram [27]

Determining the four component of software, hardware, labor, and other cost from the

current network can predict the type of cost will be spend to upgrade to IPv6 network in

USM.

128

129

The estimated time of migration from IPv4 to IPv6 in USM using dual-stack mechanism

is more or less need about four months shows in Figure 5.3.

Figure 5.3 Estimated times for IPv6 deployment in USM [27]

For the conclusion, the migration process in the USM is based on the cost efficiency that

determine by four factors: hardware cost, software cost, labor cost, and other cost. By

looking to these key factors the university can determine the estimation cost that need to

be spend during migration. Because all the routers and switches in USM already

upgraded the estimation cost for the migration is low, the highest costs that will be spent

occurred on the labor and unpredictable cost. The estimation time for migrate itself will

take place around four months.

130

5.1.3 Study Case Comparison between University of Southampton and University

Sains Malaysia

The comparison of IPv6 implementation in both universities is on the final goal of

migration. For University of Southampton the goal is to allow IPv6-only devices to be

introduced and to operate successfully using IPv6 transport and for the future

implementation is providing IPv6 connectivity for remote user using tunnel broker and

6to4 relay. While in the University of Sains Malaysia (USM) the main goal is to migrate

to IPv6 successfully in the economical way in term of cost of migration.

In USM the migration is more focused in the cost they will spend. The cost is divided

into four part; hardware cost, software cost, labor cost, and other cost. The four factors is

the key factor that needs to be considering for USM in order to migrate successfully. In

the other hand University of Southampton is more focused to migrate to IPv6

successfully using dual stack mechanism without have to worry about the cost of

implementation they would have to spend.

The similarities for both universities are:

Ø Using dual-stack mechanism

Ø Lot of equipment (hardware & software) that doesn’t support IPv6

By looking at the similarities can be conclude that dual-stack mechanism is probably the

best strategy for deploying IPv6 in a campus network, but it not be 100% true because in

131

order to implement IPv6 the network topology is crucial to help determining the

deployment strategy. Second one is the number of equipment that doesn’t support IPv6. It

can be a major obstacle for most universities for deploying IPv6.

Because universities is consider to be a non-profit organization, to spend such a lot of

money to buy a new hardware and software that compatible to IPv6 is not easy it took a

lot of consideration. One thing to make them understand is to give information that all

organization around the world slowly will move toward IPv6 technology. That’s why the

migration of IPv6 has to be done as soon as possible.

5.1.4 Case Study IPv6 Implementation in BiNus JWC network

5.1.4.1 Goal and Objectives

For case study implementation IPv6 in BiN us JWC network, the goal to is determine

whether BiN us JWC network already suitable for deploying IPv6 or not. To reach the

goal there are several objectives that need to be fulfilled:

Ø Analyzing BiNus JWC Network Topology.

Ø Analyzing the internet connectivity in BiNus JWC (Internet Service Provider).

Ø Analyzing suitable time for implementing IPv6 in BiNus JWC.

Ø Analyzing estimation time and cost for migrating IPv4 to IPv6.

132

5.1.4.2 Background

BiNus JWC Network is consider to be a medium-to-small size department, it only a part

of the big BiNus Network that is centralized in BiNus Syahdan. There are several reasons

why BiN us Syahdan is chosen to be the central network that connected the entire BiN us

Network, one of the reasons is the location; BiNus Syahdan is located in the center of

four BiNus Institutions (BiNus Kijang, BiN us Anggrek, BiNus JWC, and BiNus High).

Most of the network services are centralized in BiN us Syahdan like Web Server and Mail

Server. BiN us JWC Network only run several network services that are needed for

maintain the network connection of this building only in other words only run for

maintain small scale of network. For much bigger purpose such as web server and mail

server were maintain in BiNus Syahdan.

133

5.1.4.3 BiNus JWC Network Specifications

5.1.4.3.1 Network Topology and Address Segmentation

Figure 5.4 BiNus JWC Network Diagram [BiNus JWC IT Support]

Main different in BiN us JWC network topology for each floor is located in 1st and 4th

floor meanwhile the network topology for the 2nd and 3rd floor is basically the same. The

similarity, for each floor network is connected to Cisco catalyst 2924. Cisco catalyst 2924

is responsible to maintain the connection for each floor. And the Cisco catalyst 2924 is

134

also connected to the main switch Cisco catalyst 3550. Besides each floor there is also

network topology for the Wi-Fi connection.

For the first floor network, the network topology is divided into four sub networks which

are:

a) Back Office

b) Lecturer Office

c) Marketing Office

d) Director

Each of the sub networks is divided into different segment of IP addressing.

For the second and third floor, the network topology is divided into floor and based on

the classes. Means that because the computer in second and third floor is only 10-12

computer in each floor so it the network segmentation is based only on floor 2nd & 3rd

floor not based by division like in the 1st floor.

The IP segmentation for second floor is set to 10.24.20.xxx the number 20 is used to

mark that the IP address is belong to the second floor network. And for the third floor the

IP segmentation is set to 10.24.30.xxx like the second floor, the number 30 is used to

mark that the IP address is belong to third floor network.

For the fourth floor, the network topology is divided into four parts. The first part is the

computer lab. In BiNus JWC there are three computer lab, so for each room is given one

135

different network to accommodate approximately 30 computer for each lab. The IP

address it self is set to 10.24.45.xxx, 10.25.44.xxx, and 10.25.43.xxx that is used to mark

lab 405 – lab 403.

The second part is the class room, for the IP segmentation is the same like in the second

and third floor. The third part is the library, library is considered to be different than

classroom but the IP segmentation is the same as classroom. The only thing differentiates

class with library is the main use of each room. The last part is the IT Support office

whereas the IP segmentation of this room is different than the other three rooms.

For the main switch that used in BiN us JWC Network is Cisco Catalyst 3550. Cisco

Catalyst 3550 is used to maintain the connectivity of network in BiN us JWC. This main

switch is connected to the BiNus Syahdan Network and also several network services in

the BiNus JWC Network such as File Server, DHCP Server, and RADIUS Server that are

located in the DMZ zone.

Besides connected to the BiNus Syahdan and network services in BiN us JWC the Cisco

Catalyst also connected to four switches in each floor in BiN us JWC. The four switch

using the same switch which is Cisco Catalyst 2924. Cisco Catalyst 2924 is responsible

to maintain the networking connectivity in each floor.

Devices Cisco Catalyst 3550 and Cisco Catalyst 2924 that used in BiN us JWC Network

are already compatible with IPv6. BiN us JWC Network do not use router in assumption

136

that switch already have the compatibility of router. Beside switches the other networking

tool used is computer in each room.

5.1.4.3.2 Network Services in Binus JWC Network

File Server

File Server in BiN us JWC is using two operating systems which are Microsoft Windows

Server 2003 and Novell Netware 5 (server).

DHCP Server

For the DHCP Server BiN us JWC is using Microsoft Windows Server 2003 for

maintaining the LAN connection and Mikrotik to maintain the Hotspot connection.

Microsoft SQL Server

For Microsoft SQL Server or Database Server BiN us JWC use Microsoft Windows

Server 2000.

RADIUS Server

For RADIUS or Authentication Server BiNus JWC use Linux Fedora Core. The

RADIUS Server is needed to authenticate the entire user that want to log in to the BiNus

JWC Hotspot connection.

137

To get to know more of the BiNus JWC Network please see the diagram below that

shows the rough picture of BiN us JWC Network.

5.1.4.4 Advance Planning & Deployment Scenario

5.1.4.4.1 Standard Operating Procedure

There is always standard operation procedure (SOP) for each project that everyone do, by

making SOP, people can get to know more how the process work.

Figure 5.5 explain about the first part of the SOP. First task that need to do is preparing

document for supported product and software, it means the network admin should gather

data about list of software and hardware in BiN us JWC.

Second step check whether the product/hardware support IPv6 or not, if the product is

supported, than continue with enabling the IPv6 in the operating system and checking the

software compatibility. After enabling IPv6 in the operating system, network

administrator can set up the IPv6 address. For the software compatibility if the software

is not support network administrator must patch the current software, but if the software

support just enable the IPv6.

138

Figure 5.5 Standard Operation Procedures 1.1

Third steps back to hardware compatibility checking, if the hardware is not compatible

jump to decision whether buying a new hardware or not. If BiN us JWC would not allow

the IT department to purchase new hardware, than leave the current hardware uses IPv4.

If BiN us JWC allow purchasing a new hardware, the marketing department must check

first if the hardware that want to purchase exceed budget or not.

139

If the hardware not exceed the budget than purchasing department create a purchase

request continue with purchase order to vendor and receive order back from the vendor.

If exceed the budget BiN us JWC will try to find an alternatives to solve the problem

either by using PC Router or other brand than continuing create a purchase request from

purchasing department continue with purchase order to vendor and receive order back

from the vendor. The detail process can be seen in Figure 5.6.

Figure 5.6 Standard Operation Procedures 1.2

140

Four steps is the final step which is implementation phase. Implementation phase is the

continuation process from the first, second, and third steps. After enabling and set up

IPv6 address and receive order from the vendor, the equipments in BiN us JWC network

are most likely support IPv6. After entering implementation phase administrator can

continue configuring IPv6 in Cisco or PC Router, configure network services to support

IPv6, and configure IPv6 address in workstation.

Figure 5.7 Standard Operation Procedures 1.2

141

5.1.4.4.2 Deployment Scenario

5.1.4.4.2.1 IPv6 Consideration in Indonesia

After planning the right strategy for implementing IPv6 in BiN us JWC in order to go

further with the deployment it will be a good idea to do some research first in the IPv6

infrastructure in Indonesia. Unlike other countries in Asia Pacific region, Australia, US,

and Europe that have its own IPv6 infrastructure that is support and provide IPv4/IPv6

[26] service, the development of IPv6 infrastructure in Indonesia has just begun in the

year of 2006. Figure 5.8 give an illustration IPv6 providers and infrastructure through out

the world.

Figure 5.8 IPv6 infrastructures in the world [26]

According to the Asia Pacific IPv6 Summit 2007 in Bali [26], the development of IPv6

infrastructure in Indonesia starts in 2006 and will be divided into three phases that will be

completed in year 2008. The major projects itself involving the government (Depkominfo

RI, stakeholders (ISP), and universities. Three phase that mentioned before are:

Ø Phase I – Socialization, Reset, and Development of IPv6 technician (2006)

Ø Phase II – Development of IPv6 Infrastructure and Content (2007)

NSPIXP6 PAIX AMS-IX LINX UK6X JPNAP6 EQUI6IX

Japan

Korea

Taiwan

Hong Kong

Malaysia Australia

U.S.

Europe

DE-CIX PARIX EQUI6IX ESPANIX HK6IX IPv6 IX

142

Ø Phase III – Application Development and Transition Process (2008)

If the project successful there will be no doubt that the deployment of IPv6 in Indonesia

will begin in year 2008.

5.1.4.4.2.2 Suitable Time for Deploying IPv6

Based on the prediction by IPv6 Task Force Nasional that IPv6 infrastructure will be

finished in the year 2008, the author suggest the appropriate time for BiN us JWC to

migrate it network form IPv4 to IPv6 in mid 2008 or in semester break period. At

semester break period the time will be perfect for deploying IPv6 because the activities in

BiN us JWC will not be as crowded as usual that can make the IT support work better.

5.1.4.4.2.3 Implementation Strategy

The most suitable method to deploy IPv6 in Enterprise or Campus network is Dual-Stack

mechanism to enable two different IP in one network. To enable communication between

IPv4 and IPv6 6over4 or 6to4 tunneling mechanism can be used with router-to-router

tunneling method. Tunneling can be used to communicate between BiN us Syahdan and

ISP that support IPv6. Tunneling is choosing to accommodate the connection with IPv4

network. Until all networks already support IPv6 the Tunneling method can still be used.

For end-to-end connectivity translation method is needed. Application Layer Gateway

(ALG) is the most suitable translation method to be implemented because it is possible

143

for ALG to establish proxy servers, mail gateways, or web gateways to translate between

IPv4 and IPv6 protocol packet.

5.1.4.4.3 Cost Analysis

Cost analysis is needed to predict how much the cost that will be spending when we want

to deploy IPv6 in BiN us JWC Network. The cost itself will be vary, so the first step that

needed to do is to determine if all the networking tool that used in BiN us JWC Network

already IPv6 compatible or not. Figure 5.8 help to determine the product that used inside

Binus JWC Network.

144

If the networking tool is not IPv6 compatible it will be a problem because we have to

purchase new tool that compatible to IPv6 and for school institution like BiN us, it might

been a problem because school institution will prefer to spend money to purchase

something that more beneficial than networking tools.

From the Figure 5.8 some of the Operating System in BiN us JWC is not supported IPv6

in this case Novell Netware 5 and Microsoft Windows 2000. For the last Operating

System mentioned Microsoft Windows 2000, actually it can be supported IPv6 but need

to download a program first from Microsoft in order to support IPv6. Microsoft it self do

not recommend Microsoft Windows 2000 for implementation IPv6.

Other problem concerning hardware and software occur in BiN us JWC Network is the

main router. Cisco 3550 unfortunately doesn’t support IPv6 technology. In other word,

BiN us JWC need to purchase new switch that can accommodate IPv6 technology. The

new type of Cisco 3550 is already support IPv6 which is Cisco 3560 & Cisco 3750.

Upgrading Software and Hardware will cost a lot of money. Figure 5.9 will give an

estimation cost for upgrading the network element.

145

The total estimation price if BiN us JWC wants to upgrade their hardware and software

around $19,466.65 or Rp.180.000.000,00 if using Cisco Catalyst 3560 and around

$21,466.65 or Rp.200.000.000,00 if using Cisco Catalyst 3750. The details of hardware

and software pricing can be seen below:

146

Other aspects that need to be considered are the human resource. In order to migrate fully

to IPv6 either using standalone or alongside (dual – stack) BiN us as the institution that

implement it have to train the IT staff or recruit an expertise for maintain the network

with IPv6 capability. Recruiting an expertise will cost more money, so it will be better to

train all the IT staff about the IPv6 technology and how to run and maintain a network

that runs under IPv6.

For the total cost to migrate from IPv4 to IPv6 the author estimate around $24,000.00 or

Rp.220.000.000,00. The breakdown can be seen in table 5.6.

147

The estimation is taken by assuming that BiN us JWC will choose to use Cisco Catalyst

3750 in its network. For labor cost or IT training the author allocate $1,000.00 for one

week divided into three person which is the amount of people that works as IT support in

BiN us JWC. Other cost is used to anticipate the “unpredictable” cost that could come up

during the implementation.

5.1.4.4 Estimated Time Deployment

As already explain above that the most appropriate time to deploy IPv6 in BiN us JWC is

during mid 2008 between June - September. Task that need to be done during the

implementation are:

Ø Hardware & Software Support

148

Ø IT Support Training

Ø Router Configuration

Ø Switch Configuration

Ø Setting PC and Server

Ø Testing and Implementation

Figure 5.9 shows the Gantt chart that will show the breakdown time for each process.

From the chart can be seen that Hardware & Software support need longer time to

accomplish the task approximately 13 weeks. The other tasks only need one until two

week for completion.

Figure 5.9 Estimated timeframe to deploy IPv6 in Binus JWC

149

Testing and implementation is very crucial to determine that the system that already been

prepared can be run effectively in BiN us JWC Network. Hopefully within the timeframe

that already been planned the IPv6 implementation in BiN us JWC can be finished on

time.

At last, in order to make implementation plan to be implement successfully support from

BiN us JWC along with all the staff and student are needed. The author personally hopes

the planning that already purpose can be useable.