Response to UKF Trading Company-

Invitation to Tender

6/21/2018

Proposal With a copy of this document, we (herein referred to as "the consultant" or "the company")

respond to UKF's (the client) Invitation to Tender (ITT) for a network design, installation and

operation for a trading floor. The proposed network design promises high network

performance, availability, throughput, and scalability that would meet the clients current and

future networking needs and lowest total cost of ownership(TCO) in the market. The

company’s chosen TCO model promises faster deployment and productivity, highly

streamlined use and management as well as increased flexibility.

As can see from our website, our team is comprised of professionals with both the academic

qualification and excellent track records. Some of our clients include Coca-Cola Company,

Barclays Bank, New York stock exchange and London stock exchange for whom we have

either designed and installed the whole network or have been subcontracted. Our equipment

vendors include the world-leading networking solutions providers that deal in a wide range of

wired and wireless routers, Ethernet switches, VOIP equipment and, domain security.

The company will draw from its experience in handling similar high demand network

systems for major corporations to deliver and exceed the client's expectation. We are glad to

offer our network design, quotation, and TCO model, we would be glad if our application

shall meet your kindest consideration in your organization's pursuit of its bottom-line.

Below is an outline of the contents of this document:

Table of ContentsProposal.................................................................................................................................................2

1.1 Our understanding of your current enterprise network design.....................................................4

1.2 Proposed Logical Design and Topology......................................................................................5

1.3 Associated Design documents.....................................................................................................6

1.4 The IPv6 addressing scheme........................................................................................................6

1.5 Defining the site ID and sub-netting............................................................................................7

1.6Allocations....................................................................................................................................7

Part 2: the proposed Next-Gen infrastructure for the client’s trading floor............................................9

2.1 Key assumptions about the trading floor.....................................................................................9

2.2 Networking protocols................................................................................................................10

2.3 WLAN/VLAN outlay................................................................................................................11

Part 3: Estimated Cost of Service.........................................................................................................11

3.1 Required Equipment, Vendors and Bill of Quantities................................................................12

3.2 Cost Estimation, and Depreciation.............................................................................................15

3.3 Support's priority and guaranteed response times......................................................................15

3.4 Vendor profiles..........................................................................................................................16

Part 1: Background

1.1 Our understanding of your current enterprise network designThe client “UKF” is a trading company that occupies 2 trading floors in Manchester ‘city.

The company’s networks are limiting the company’s performance in terms of availability,

performance, and capability. For one, the company needs a scalable network to

accommodate for future changes in the scope of operation as well as meet the current

enterprise network needs. The company/s network requires a complete overhaul and redesign.

Design for future means that the enterprise network design must be flexible to accommodate

for future networking needs including designing for simplicity, manageability, scalability,

and flexibility. The IPv6 subnets adopt the one size fits all with its simplicity by mapping the

working bits and grouping by 4 bits per the hex digits to operate the network using a logical

topology and the defined meanings allocated in multiples of 24n such as 16, 256, 4096, and

more. The network would need only 3 layers of address hierarchy for simplicity. The

following are the key business systems taken into considerations in the design of the network

enterprise:

Email

Trading floor systems: 2

Financial systems: 1

Payroll: 1

Purchasing: 1

Office applications: 1

1.2 Proposed Logical Design and Topology

In case the PI space is chosen by the firm and has received 2001:0DB8:1: /48 for its location

registry, the prefix can be divided as shown below:

The above scheme comprises 16 regions each with 16 sites. Of the 16 sites can identify 16

other functional prefixes that support the 16 subnets. For the sake of the company, the

functional prefix would include workstations, servers, wireless connection and voice subnets

(VOIP). The address would communicate ghee location as well as the function of the specific

address thereby helping in streamlining the operational processes

1.3 Associated Design documents

Internet Protocol version 6 (IPv6) is the current version of the internet protocol

providing the identification and location mechanism for the computers on any network and

can router traffic across the internet. Ipv6 is an upgrade over ipv4 that was characterized by

address exhaustion (ipv4 addresses are limited to only 4.3bilion addresses which also limited

growth). In the networks, each of the devices on the internet has their unique addresses that

are assigned to it by default to help in the identification and definition of the location. For

example, devices in Omaha and Chicago are each assigned a unique IP address. Other

technical benefits provided by the IPv6 include its ability to provide the users with

hierarchical address allocation that allows route aggregation across the internet. Hierarchical

address allocation also limits the expansion of the available routing tables in addition to

expanding and simplifying the optimization of the delivery services. At the design phase of

the IPv6, device mobility, device security as well as device configuration are some of the key

factors that are given primacy. The most important fact to note about the IPv6 addresses is

that they are represented at eight groups composed of four hexadecimal digits each with each

group being separated by a colon but the full notation can be abbreviated.

1.4 The IPv6 addressing scheme

The IPv6 address scheme is a new addressing scheme whereby the /48adress is broken up

across an enterprise network. For enterprises such as the company, the address is broken

down across location to give each device a unique IP address for easier identification and

location. To subnet the IPv6, each character in the IPv6 is initially represented by the 4 bits

notation with each IPv6 representing the 16bits made up of 4 characters of 4 bits. Each of the

subnets bits has one fewer host and each host has one more bit making a subnet. It is

important to note that the ISP must provide the /48 prefix meaning that the enterprises have

2^80 bits that they can manipulate (out of the 128 bits the, 8 bits remaining after the 48 prefix

is used). The RFC4291 recommends that /64 should be the smallest prefix because there is no

need to conserve address in IPv6. Therefore, /64 would be assigned to a point to point; link

but the /128 would be used on the network's loopback address.

1.5 Defining the site ID and sub-netting

Defining the site ID would allow for optimal route aggregation and route summarization.

The site ID would be used in each location and in this case, the trading floor or office, data

centre or the other geographical regions). In this case, if the ISP would assign the company:

2001:0DB8:0002:/48, the company would have ‘0002" to manipulate for the whole site as

well as the sub-suites and the subnet IDs. The address would be broken down depending on

the business needs for each site. In this case, the consultant would recommend breaking the

address along with the nibble boundary.

The company would deploy the following networking and sub-netting scheme: 4 sites with 4

subside on each of the four sites. This would also provide 4096 sub-networks at each of the

sub-sites. For this, the first 2 bits would be preserved for the suites, the subsequent two bits

would be for the sub-sites also referred to as the first nibble site while the subsequent three

nibbles are left for the subnets (being (2^12).

1.6AllocationsThe first layer allocation would be done by the application. As the company uses its

IPv6 addresses for various functions, the first layer would be allocated by an application such

as video, VoIP, data and wireless connection. Allocation by application allows the consultant

to define a routing policy that would be used across all the company's routers for each of the

application used by the company as appropriate. There are only 16 allocations, therefore; the

first nibble would be 49-52 bits as shown below based on the sparse allocation technique. It is

immigrant to note that sparse allocation technical is referred for companies that intend to

scale up or scale down their operations in future because it allows for growth optimization

–        Data: 2001:0DB8:1a:0000: /48

–        Voice: 2001:0DB8:1a:8000: /48

–        Video: 2001:0DB8:1a:4000: /48

–        Wireless: 2001:0DB8:1a:c000: /48

–        Financial systems: 2001:0DB8:1a:2000: /48

The video and data routing policies would be configured in all the routers and the application

would be enumerated to a packet of which the source IPv6 would be an address within the

established address within 2001:0DB8:1a:4000: /52 blocks.

Second layer

The second layer ID would be allocated by region. For example, the second later would take

a nibble or four bits in the ID. Each of the application blocks would be allocated by region.

For example, the voice block would be allocated as shown below:

–        Voice –trading floor:    2001:0DB8:1a:8000: /48

Third layer

The third layer would be defined by the business unit to the next nibble or the bits between 57

and 60 would be used. For example, in this case, each of the business units would need

representation in each of the regions and this is the same case for each of the application.

Each of the business units would be added to the existing 10 allocations this means that if the

company has five business units, it would have 100 allocations. For example, in case of

voice- in the southern region branch, the company would add its business units

monotonically:

– Email– Corporate: 2001:0DB8:1a:8c00: /48

–     Voice – Trading floor systems: 2001:0DB8:1a:8c10: 48

–     Voice –– Financial systems: 2001:0DB8:1a:8c20: /48

– Voice –- Purchasing: 2001:0DB8:1a:8c30: /48

Part 2: the proposed Next-Gen infrastructure for the client’s trading floorIn part 2, the proposed network design for the trading floor and outline include the

infrastructures that would be used as well as the alternative vendors to choose from. It is

important to note that the consultant focused on quality and not costs when selecting vendees

because cheaper equipment could be costly to the company in the long run.

2.1 Key assumptions about the trading floor Secondly, there were many assumptions that were made in the design phase including the

assumption that the trading floor had no IT equipment as the current systems would be

completely overhauled. For example, the company would use to ISP links that are mainly

MPLS connection to one router to ensure that the DMZ servers can only be accessed from the

company’s remote client (Guo & Chang, 2010).

The first ISP (ISP1) will be connected to defined clients and servers in the first

trading floor and servers. However, the complete 10.10.10.0 network would be made

accessible to both the first and the second trading floor. Network address translation (NAT)

would also be enabled for both trading floors and be connected to the second ISP. New

subinterfaces for both ISPs would be created and the Network address translation (NAT)

would be performed for both (Achar, & Mei, 2014). A single network would be translated for

two ISP as opposed to the default route. The static route of the subnet would be configured to

the two ISP routers. The LAN connectivity would be replaced to improve the quality of

connection and enhance scalability. The company’s current main distribution frame (MIDF)

would also be replaced in addition to the peripheral. It is also assumed that the company

would be joining that 24 hours economy so there would be 24 hours operations with people

working round the clock.

For flexibility, all major equipment and networking infrastructures would be located at one

corner including MDF, and IDF. The assumption is that each trading floor would have the

specific room for MDF and IDF. It is in those partitioned rooms that routes, hedge switches,

and other connectors would be located (Zhang, 2016). Each of the three LAN port would also

need connection and the three wires to those ports would be bundled into a single wire to

reduce the number of wires in the room floor. For optimal output, each of the LAN ports

would have an additional for optimal uptimes as a failover port (Sendra, Fernández, Quilez &

Lloret, 2011). For mobility, the company would propose a wireless connection with the

controllers stored in the MDF/IDF rooms (Grewal and Dangi, 2012). The floor plan for the

first trading floor would as indicated in the appendix.

2.2 Networking protocols Some of the key criteria for the proposed network include high availability, capacity,

capability, performance and costs. Therefore, the following protocols would be adopted as

the meet the criteria above and can manage the current and future traffics of both VOIP,

data and network capacities such as Busy Hour Call Attempts (BHCA), Busy Hour Call

Completions (BHCC) and Calls per Second (CPS)

1. Power Link™ Failover, Load Balancing and WAN Optimization – the power links

would be used as a border gateway protocols because it can aggregate the WAN links

from many separate ISP and allow the users to muse the working connection. The

system can enable multi-homing without the BGP as it uses the network address

translation (NAT) and the latest dynamic domain names services (DDNS) to redirect

all the new TCP session. The system would also enable the company to achieve load

balancing for the outbound traffic and inbound traffic to achieve optimal application

prefaces. Other important features include firewall, site-to-site VPN and SIP traffic

load balancing.

2. CISCO- Enhanced Interior Gateway Routing Protocol (EIGRP)/SPF. The EIGRP/

SPF would be used because the gateways would independently help in solving the

optimization problems. The SPF is referred because its main advantage is that it can

respond to changes in the network faster thereby preventing routing loops and can

also deal with more data that the IGRP

2.3 WLAN/VLAN outlay 3. The VLAN 64 would be used for the management, VLAN - /64, VLAN 10 – printer,

102 VoIP, and 104 for security while VLAN 102 is for Wireless

Part 3: Estimated Cost of Service

3.1 Required Equipment, Vendors and Bill of QuantitiesEquipment/ products

Vendors Model Key Features Quantity Location/ site

Estimated costs@

Subtotal

Site Router Linksys Linksys Flop Intelligent Mesh WiFi System, Tri-Band, 3-Pack White (AC6600)

2 MDF $449.99 899.98

Distribution and Core Switch

Cisco Cisco Catalyst 3850 Fiber Series

WS-C3850-48T-E

Platform for low-density 1 GB distribution deployments12 and 24 Gigabit SFP port modelsPoE, PoE+, StackPower, UPOESupports DNA and SD-Access100 access points supported

3 MDF $19890.00 59670

Infrastructure Switch

Cisco Blade Switches Dell, FSC, HP and IBM blade serversCan support the deployment of virtualized data centre infrastructure.Promises to significantly lower the TCO

1 MDF US$11,113.00 11,113.00

Edge Switch1  Ubiquity Networks, Inc. 

ES-48-750W Relies on asynchronous transfer mode backbone for connection to the other core networks.uses connection-oriented virtual circuitsTotal Non-Blocking Throughput:70 GbpsGigabit RJ45 Ports: 48SFP+ Ports: 2SFP Ports: 2Max. Power Consumption:750W

6 3 per IDF $2,786.00 5572

Firewall FortiGate Next Generation

High threat protection performanceHas automated visibility to stop attacks

1 MDF $300,000.00 300,000.00

1

Firewall (NGFW)FortiGate 6500F

Threat Protection: 100 GbpsSSL Inspection Throughput:130 GbpsNetwork Interfaces: Multiple 40/100 GE QSFP28, 1/10/25 GE SFP28, 1/10 GE SFP+ and GE RJ45 (Cisco, 2018)

Intrusion Prevention System

Cisco  FirePOWER™ Next-generation IPS (NGIPS)

Protocol decoding and validation for network traffic (IP, TCP, UDP, ICMP etc.)Can detect SSL/Https traffic and IPSec/VPN's traffic. Promises high uptime, Active/Standby and High Availability.Delivers better Failover (Meraki Inc, 2018)

2 MDF $144,000 288000

Wireless LAN Controller (WLC)

Cisco Cisco Catalyst 9300 Series Switches

• One RU, delivering 6.4TGbps switching capacity.• Replaces Catalyst 6880-X: 2 Tbsp catalyst• Flexible downlinks: 100-Gbps Quad Small Form FactorPluggable (QSFP28), 40-Gbps (QSFP),25-Gbps (SFP28) and 10-Gbps (SFP+) switchesWith granular port densities.• Supports high-availability capabilities likepatching, Graceful Insertion and Removal (GIR),Nonstop Forwarding with Tasteful Switchover(NSF/SSO), redundant platinum-rated power Supplies and fans, Network system

10 MDF $179.99 $1790.99

virtualization and advanced routing and Infrastructure services.

Wireless Access Point2

Cisco Meraki

MR84 Cloud-Managed, IP67-Rated, Ruggedized Highest performance 802.11ac Wave 2 with Multigigabit for tough RF and high-density environments (Cisco, 2018)MR84 Includes a dedicated, dual-band 3rd radio for RF optimization and security scanningHigh-Density Ruggedized Coverage4×4:4-stream MU-MIMOMultigigabit and external antenna connectorsRecommended for focused coverage and flexibility (Meraki Inc, 2018)

30 MDF $1,573.00 47190

Totals 714235.97

2

3.2 Cost Estimation, and DepreciationThe estimated total cost of the infrastructures, the vendors of each equipment, the model as

well as the quantity required for the proposed network system is as shown in the table.

The estimated purchase costs would be $714235.97The installation cost is: 30% of the equipment cost

$214270.791

The monthly maintenance costs are $12000$940,506.76

The equipment would be depreciated on a straight line basis meaning that after the first five

years, the equipment would depreciate by $35211.7985 annually

Pensive calculates the annual straight-line depreciation for the machine as:

Purchase cost of $714235.97– estimated salvage value of $10,000 = Depreciable asset cost of

$704235.97

1 / 5-year useful life = 5% depreciation rate per year.

5% depreciation rate x $704235.97depreciable asset cost = $35211.7985 annual depreciation.

3.3 Support's priority and guaranteed response times

Based on the company’s work/ support policies, tube speed and response times would mainly

depend on the priority levels assigned to the clients. The priority level is tied to the fee the

company charges. The company would respond to the client’s issues based on their chosen

response priority when they submit their problem tickets. In the table below, the client will

see the quick reference to the support labels that the client expect according to their ticket

priority, the issue statures as well as the support plan the client is on:

Support Plan Ticket  Priority3

Issue  Status Production Business Personalized

1 Business Critical Within 3 business hours

Within 1 hour (24x7)

Within 1 hour (24x7)

2 Degraded Service

Within 6 business hours

Within 2 business hours

Within 2 business hours

3 General Issue Within 9 business hours

Within 3 business hours

Within 3 business hours

It is important to note that the company’s business hours start from Monday 6.00am to Friday at 6 pm. The company’s guaranteed response times are not covered for any of the beta products.

Priority Levels explained

4. Priority 1, Business Critical - covers a complete loss of service 5. Priority 2, Degraded Service : Includes intermittent issues and reduced quality of

service. 6. Priority 3, General Issue : covers the product questions, feature requests and

development issues.

The whole network layout includes equipment, infrastructures and the employees on the

whole trading floor. All the infrastructures would be located at the back of the reading floor

where all the MDF would be located. The software-defined networking-SDN. The control

and data forwarding function of the company’s network equipment would be separated and

the control function of the network element would be centralized to eagle automatic and

dynamics management of the network elements as those adopted by AT&T (Grewal and

Dangi, 2012).

The model of software-defined access network (SDAN) that would be adopted. The SDAN

would use the software to manage the company’s virtualized access network. The ROI in the

proposed in fractures would be optimized when the infrastructures are shared among the

multiple service producers to optimize uptimes. The client’s physical network would be

partitioned into multiple virtual networks that correspond to each of the staff members

(users). The software would map the DSL access multiplexes to the virtual hardware while

the hardware would be managed by the service providers. Instead of using the bit-stream

3

access unbundling, the virtual network operated would be in charge of designing competitive

service products and make a real-time improvement on the network.

Part 4: Vendor ProfilesVendors Company profile Linksys Linksys is an American company that deal is data networking hardware. Its

range of products includes wired and wireless routers, Ethernet switches, VoIP equipment, wireless Internet video cameras, audiovisual products and network storage systems.

Cisco Cisco Systems, Inc. is an American MNC. The company deals in networking hardware, telecommunications equipment and other high-technology services and products. Its subsidiaries include OpenDNS, WebEx, Jabber and Jasper, Cisco specializes into specific tech markets, such as the Internet of Things (IoT), domain security and energy management.

 Ubiquity Networks, Inc. 

Ubiquity Networks is an American technology company that deals in wireless data communication

FortiGate Fortinet is an American multinational corporation headquartered that deals in cybersecurity software firewalls, anti-virus, intrusion prevention and endpoint security.

Cisco Meraki

Cisco Meraki is a cloud-managed IT company headquartered in San Francisco, California. Their solutions include wireless, switching, security, EMM, communications, and security cameras, all centrally managed from the web

Part 4: Proposed Network Implementation Plan

4.1 Staffing Bellow is an outline of the proposed systems implementation plan that would be followed

during the deployment sessions. The followed staff would be in charge of the deployment

tasks:

Staff Designation Number

System engineer 2

Network engineer 3

Projects manager 1

IT procurement supply chain manager 1

Cabling staff 10

The consultant would be in charge of vendor’s selection and purchases. It is important to note

that the consultant would issue a request for proposal or expression of interest form that

would be filled by the various vendors. The consultant would choose the vendors.

4.2 The timeline for the deploymentThe deployment shall consist of 6 milestones

UKF- Project Milestones for the proposed network

# Tasks Days Start Finish Cost Assignments1 Milestone 1: Pre-

Deployment 6 7/2/201

87/9/201

8$0.00 System engineer, Network

engineer, IT procurement supply chain manager, Projects manager, Cabling staff

2 Assemble the network equipment

1 7/2/2018

7/2/2018

$0.00 System engineer,

3 Pre-configuration of network equipment

1 7/3/2018

7/3/2018

$0.00 Network engineer, System engineer,

4 Review and test the new high-level network diagram in simulation

1 7/4/2018

7/4/2018

$0.00

5 Raise RFC for network change

1 7/5/2018

7/5/2018

$0.00 Projects manager, IT procurement supply chain manager, Cabling staff

6 Review Technical and CAB Approval Requirement and verify Request for Change (RFC)

1 7/6/2018

7/6/2018

$0.00 IT procurement supply chain manager, Projects manager, System engineer, Network engineer, Cabling staff

7 Vendor selection 1 7/9/2018

7/9/2018

$0.00 IT procurement supply chain manager

8 Milestone 2: Deployment

5 7/10/2018

7/16/2018

$0.00

9 Documentation of Existing Network Infrastructure and Inventory Complete

1 7/10/2018

7/10/2018

$0.00 IT procurement supply chain manager, Cabling staff

10 Gain Understanding of Network Infrastructure

1 7/11/2018

7/11/2018

$0.00 System engineer, Projects manager, Network engineer, IT procurement supply chain manager

11 Take Inventory of Current Hardware

1 7/12/2018

7/12/2018

$0.00 Network engineer, System engineer, Projects manager, IT procurement supply chain manager

12 Document Layout of existing Network

1 7/13/2018

7/13/2018

$0.00 Cabling staff, IT procurement supply chain manager

13 Installation 1 7/16/2018

7/16/2018

$0.00 System engineer, Network engineer

14 Milestone 3: Network Research, Design installation

5 7/17/2018

7/23/2018

$0.00

15 Configure network hardware including Hubs, Switches, Bridges, Routers, and Gateways.

1 7/17/2018

7/17/2018

$0.00 System engineer, Network engineer, Projects manager, IT procurement supply chain manager, Cabling staff

16 Switching over to a new MPLS

1 7/18/2018

7/18/2018

$0.00 System engineer, Network engineer

17 Configure ISDN adapters, and system area network cards and Wireless access points (WAPs)

1 7/19/2018

7/19/2018

$0.00 System engineer, Network engineer, Cabling staff

18 configure Network interface cards (NICs),

1 7/20/2018

7/20/2018

$0.00 System engineer, Network engineer, Projects manager, Cabling staff

19 Migrate the staff to a new platform

1 7/23/2018

7/23/2018

$0.00 Cabling staff, Projects manager

20 Milestone 4: Create Detailed support plans

1 7/24/2018

7/24/2018

$0.00

21 Detail the impact on production systems and the expected outage window required

1 7/24/2018

7/24/2018

$0.00 Projects manager

for the upgrade.22 Milestone 5:

Completion of Network deployment and migration

3 7/25/2018

7/27/2018

$0.00

23 Schedule time for upgrade/ repair

1 7/25/2018

7/25/2018

$0.00 Network engineer, Projects manager, IT procurement supply chain manager

24 inform the users of the new changes after the upgrade

1 7/26/2018

7/26/2018

$0.00 Network engineer, Projects manager

25 Execute upgrade plan

1 7/27/2018

7/27/2018

$0.00 Cabling staff, IT procurement supply chain manager, Projects manager, Network engineer, System engineer,

26 Milestone 6: Post-Deployment

1 7/30/2018

7/30/2018

$0.00

27 Post-Deployment support

1 7/30/2018

7/30/2018

$0.00 System engineer,

#

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

Task Name

Milestone 1: Pre-Deployment Assemble the network equipment

Pre-configuration of network equipment

Review and test the new high level network diagram in simulation

Raise RFC for network change

Review Technical and CAB Approval Requirement and verify Request for Change (RFC)

Vendor selection

Milestone 2: Deployment Documentation of Existing Network Infrastructure and Inventory Complete

Gain Understanding of Network Infrastructure

Take Inventory of Current Hardware

Document Layout of existing Network

Installation

Milestone 3: Network Research, Design installation Configure network hardware including: Hubs, Switches, Bridges, Routers, Gateways.

Switching over to a new MPLS

Configure ISDN adapters, and system area network cards and Wireless access points (WAPs)

configure Network interface cards (NICs),

Migrate the staff to new platform

Milestone 4: Create Detailed support plans Detail the impact on production systems and the expected outage window required for the upgrade.

Milestone 5: Completion of Network deployment and migration Schedule time for upgrade/ repair

inform the users of the new changes after the upgrade

Execute upgrade plan

Milestone 6:Post-Deployment Post-Deployment support

Days

6 1

1

1

1

1

1

5 1

1

1

1

1

5 1

1

1

1

1

1 1

3 1

1

1

1 1

Start

7/2/18 7/2/18

7/3/18

7/4/18

7/5/18

7/6/18

7/9/18

7/10/18 7/10/18

7/11/18

7/12/18

7/13/18

7/16/18

7/17/18 7/17/18

7/18/18

7/19/18

7/20/18

7/23/18

7/24/18 7/24/18

7/25/18 7/25/18

7/26/18

7/27/18

7/30/18 7/30/18

Finish

7/9/18 7/2/18

7/3/18

7/4/18

7/5/18

7/6/18

7/9/18

7/16/18 7/10/18

7/11/18

7/12/18

7/13/18

7/16/18

7/23/18 7/17/18

7/18/18

7/19/18

7/20/18

7/23/18

7/24/18 7/24/18

7/27/18 7/25/18

7/26/18

7/27/18

7/30/18 7/30/18

6/24 - 6/30 7/1 - 7/7 7/8 - 7/14 7/15 - 7/21 7/22 - 7/28 7/29 - 8/4 8/5 - 8/11 8/12 - 8/182018 Jun 2018 Jul 2018 Aug 2018 Sep

UKF- Project Milestones for the proposed network -Project KickStart Trial prints one page only.

7/1/2018 1 of 1

ReferencesAchar, R., M, S., & Dr M., A. (2014). Border Gateway Protocol Performance and Its

Protection against Disturbed Denial of Service Attack. Bonfring International Journal

Of Research In Communication Engineering, 4(1), 05-09. doi: 10.9756/bijrce.10345

Guo, H., & Chang, J. (2010). Survey on convergence problem of border gateway

protocol. Journal Of Computer Applications, 30(10), 2628-2631. doi:

10.3724/sp.j.1087.2010.02628

Sendra, S., Fernández, P., Quilez, M., & Lloret, J. (2011). Study and Performance of Interior

Gateway IP Routing Protocols. Network Protocols And Algorithms, 2(4). doi:

10.5296/npa.v2i4.547

Cisco (2018). Cisco Catalyst 9300 Vs 9400 Vs 9500 Switches. [online] Route XP. Available

at: http://www.routexp.com/2018/02/cisco-catalyst-9300-vs-9400-vs-9500.html

[Accessed 1 Jul. 2018].

Grewal, K. and Dangi, R. (2012). Comparative Analysis of QoS VPN Provisioning

Algorithm on Traditional IP based VPN and MPLS VPN using NS-2. International

Journal of Computer Applications, 48(1), pp.43-46.

Meraki Inc, I. (2018). 100% CLOUD-MANAGED IT Manage your entire network from a

centralized dashboard.. [online] Meraki.cisco.com. Available at:

https://meraki.cisco.com/ [Accessed 1 Jul. 2018].

Zhang, M. (2016). Study on Remote Access for Library Based on SSL VPN. International

Journal of Control and Automation, 9(1), pp.111-122.