Virtual Private Networks - Revision history

Dangm: /* '''External Links''' */

2008-04-14T05:02:05Z

'''External Links'''

← Older revision		Revision as of 05:02, 14 April 2008
Line 152:		Line 152:
	[E12] http://en.wikipedia.org/wiki/Socks5		[E12] http://en.wikipedia.org/wiki/Socks5

		+	[E13] http://en.wikipedia.org/wiki/Firewall

		+	[E14] http://en.wikipedia.org/wiki/AAA_protocol

-	~~--[[User:Dangm\|Dangm]] 01:01, 14 April 2008 (EDT)~~

-	[~~E13] http://en.wikipedia.org/wiki/Firewall~~	+	--[[User:Dangm\|Dangm]] 01:02, 14 April 2008 (EDT)
-		+
-	[~~E14~~] ~~http~~:~~//en.wikipedia.org/wiki/AAA_protocol~~	+

Dangm: /* '''External Links''' */

2008-04-14T05:01:39Z

'''External Links'''

← Older revision		Revision as of 05:01, 14 April 2008
Line 151:		Line 151:

	[E12] http://en.wikipedia.org/wiki/Socks5		[E12] http://en.wikipedia.org/wiki/Socks5
		+
		+
		+
		+	--[[User:Dangm\|Dangm]] 01:01, 14 April 2008 (EDT)

	[E13] http://en.wikipedia.org/wiki/Firewall		[E13] http://en.wikipedia.org/wiki/Firewall

	[E14] http://en.wikipedia.org/wiki/AAA_protocol		[E14] http://en.wikipedia.org/wiki/AAA_protocol

Dangm: /* '''See Also''' */

2008-04-14T05:00:55Z

'''See Also'''

← Older revision		Revision as of 05:00, 14 April 2008
Line 103:		Line 103:

	[5] http://www.cas.mcmaster.ca/wiki/index.php/Designing_a_Small_Business_Intranet Designing a Small Business Intranet		[5] http://www.cas.mcmaster.ca/wiki/index.php/Designing_a_Small_Business_Intranet Designing a Small Business Intranet
		+
		+	[6] http://www.cas.mcmaster.ca/wiki/index.php/Honeypot Honeypots

	=='''References'''==		=='''References'''==

Dangm: /* '''See Also''' */

2008-04-14T04:59:50Z

'''See Also'''

← Older revision		Revision as of 04:59, 14 April 2008
Line 94:		Line 94:
	=='''See Also'''==		=='''See Also'''==

		+	[1] http://www.cas.mcmaster.ca/wiki/index.php/Virtual_Private_Network Virtual Private Network

		+	[2] http://www.cas.mcmaster.ca/wiki/index.php/Conventional_Encryption_Algorithms Conventional Encryption Algorithms
		+
		+	[3] http://www.cas.mcmaster.ca/wiki/index.php/Network-Based_Software_Architectures Network-based Software Architectures
		+
		+	[4] http://www.cas.mcmaster.ca/wiki/index.php/Communications_and_Computer_Network_Protocol_Design_Models Communications and Computer Network Protocol Design Models
		+
		+	[5] http://www.cas.mcmaster.ca/wiki/index.php/Designing_a_Small_Business_Intranet Designing a Small Business Intranet

	=='''References'''==		=='''References'''==

Dangm: /* '''References''' */

2008-04-14T04:56:09Z

'''References'''

← Older revision		Revision as of 04:56, 14 April 2008
Line 109:		Line 109:

	[R6] http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html VPNs Are Hot, but What Are They?		[R6] http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html VPNs Are Hot, but What Are They?
		+

Dangm: /* '''References''' */

2008-04-14T04:55:36Z

'''References'''

← Older revision		Revision as of 04:55, 14 April 2008
Line 98:		Line 98:
	=='''References'''==		=='''References'''==

-	[R1] ~~htpp~~://www.vpnc.org/vpn-technologies.html VPN Technologies: Definitions and Requirements	+	[R1] http://www.vpnc.org/vpn-technologies.html VPN Technologies: Definitions and Requirements

	[R2] http://www.intranetjournal.com/foundation/vpn-1.shtml Virtual Private Networks,An overview		[R2] http://www.intranetjournal.com/foundation/vpn-1.shtml Virtual Private Networks,An overview
Line 109:		Line 109:

	[R6] http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html VPNs Are Hot, but What Are They?		[R6] http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html VPNs Are Hot, but What Are They?
		+
		+
		+	[Ra] http://www.ietf.org/rfc/rfc2917.txt A Core MPLS IP VPN Architecture
		+
		+	[Rb] http://en.wikipedia.org/wiki/Vpn Virtual Private Network

	=='''External Links'''==		=='''External Links'''==

Dangm: /* '''References''' */

2008-04-14T04:52:42Z

'''References'''

← Older revision		Revision as of 04:52, 14 April 2008
Line 98:		Line 98:
	=='''References'''==		=='''References'''==

-	[R3] http://www.ja.net/documents/development/vpn/different-flavours-of-vpn-web.pdf	+	[R1] htpp://www.vpnc.org/vpn-technologies.html VPN Technologies: Definitions and Requirements
		+
		+	[R2] http://www.intranetjournal.com/foundation/vpn-1.shtml Virtual Private Networks,An overview
		+
		+	[R3] http://ja.net/documents/development/vpn/different-flavours-of-vpn-web.pdf Different Flavours of VPN
		+
		+	[R4] http://computer.howstuffworks.com/vpn5.htm Howstuffworks “How Virtual Private Networks work”
		+
		+	[R5] http://computer.howstuffworks.com/vpn8.htm Howstuffworks “How Virtual Private Networks work”
		+
		+	[R6] http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html VPNs Are Hot, but What Are They?

	=='''External Links'''==		=='''External Links'''==

Dangm: /* '''VPN Technology Hurdles in the Future''' */

2008-04-14T04:51:57Z

'''VPN Technology Hurdles in the Future'''

← Older revision		Revision as of 04:51, 14 April 2008
Line 82:		Line 82:
	=='''VPN Technology Hurdles in the Future'''==		=='''VPN Technology Hurdles in the Future'''==

-	As it stands, there are many challenges to both clients and providers alike. There are currently no standards in some VPN protocols such as L2TP and no standard in building VPNs. To add more to the dilemma, VPN technology is an expanding and lucrative field for providers and this makes it difficult to standardize anything, a fact made evident by interoperability issues between vendor implementations. Also, almost all research advancements and proposed standards are made by competing vendors in the industry such as Cisco, Nortel and large ISPs, making such problems difficult to solve. However, because of such fierce competition, it can be expected that much advancements can be made, and that is usually to the clients’ benefits. <sup>[~~R10~~]</sup>	+	As it stands, there are many challenges to both clients and providers alike. There are currently no standards in some VPN protocols such as L2TP and no standard in building VPNs. To add more to the dilemma, VPN technology is an expanding and lucrative field for providers and this makes it difficult to standardize anything, a fact made evident by interoperability issues between vendor implementations. Also, almost all research advancements and proposed standards are made by competing vendors in the industry such as Cisco, Nortel and large ISPs, making such problems difficult to solve. However, because of such fierce competition, it can be expected that much advancements can be made, and that is usually to the clients’ benefits. <sup>[http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html R6]</sup>


-	Another major hurdle for VPNs is the leased line market. Currently, there are only a finite number of leased lines, and large telecommunication companies control many of them. The difficulty lies in deploying new lines to service more VPNs and it usually takes six weeks to deploy. This problem will continue to be a major hurdle unless there are new, cheaper methods of deployment.<sup>[~~R11~~]</sup>	+	Another major hurdle for VPNs is the leased line market. Currently, there are only a finite number of leased lines, and large telecommunication companies control many of them. The difficulty lies in deploying new lines to service more VPNs and it usually takes six weeks to deploy. This problem will continue to be a major hurdle unless there are new, cheaper methods of deployment.<sup>[http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html R6]</sup>

-	A third obstacle for VPN providers and clients is the number of technologies that are required to create a VPN. As more and more people jump onto the VPN bandwagon, more people expect one seamless, integrated product, a concept extremely far from what we currently have. The complete simulation of a physical private network with low complexity, cost, and full functionality is still a dream. <sup>[~~R12~~]</sup>	+	A third obstacle for VPN providers and clients is the number of technologies that are required to create a VPN. As more and more people jump onto the VPN bandwagon, more people expect one seamless, integrated product, a concept extremely far from what we currently have. The complete simulation of a physical private network with low complexity, cost, and full functionality is still a dream. <sup>[http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html R6]</sup>

	As it stands today, security is the focus of VPN implementations, and as a result, does not address performance and availability issues. QoS is not guaranteed since it is not necessary because most solutions today only provide certain functionalities for the users in the network do not affect the performance of the network. However, if the Internet is used as the medium, any cost savings that a VPN provides are quickly negated if users are forced to sacrifice QoS beyond certain limits. Hence, end-to-end performance guarantees will be difficult to implement.		As it stands today, security is the focus of VPN implementations, and as a result, does not address performance and availability issues. QoS is not guaranteed since it is not necessary because most solutions today only provide certain functionalities for the users in the network do not affect the performance of the network. However, if the Internet is used as the medium, any cost savings that a VPN provides are quickly negated if users are forced to sacrifice QoS beyond certain limits. Hence, end-to-end performance guarantees will be difficult to implement.
-	<sup>[~~R13~~]</sup>	+	<sup>[http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html R6]</sup>

	=='''See Also'''==		=='''See Also'''==

Dangm: /* '''Types of VPN Services''' */

2008-04-14T04:51:21Z

'''Types of VPN Services'''

← Older revision		Revision as of 04:51, 14 April 2008
Line 72:		Line 72:

	'''Encrypted VPNs'''		'''Encrypted VPNs'''
-	On VPNs, user data is encrypted so that potential eavesdroppers cannot understand the content even if it was intercepted. Secure data exchange through a public network provided by encrypted VPNs functions alongside a company’s firewall service that protects the data inside the network. Today, almost all companies with home-working employees use encrypted VPNs to give them secure remote access. Encryption can always be added to other types of VPN however, encryption is usually provided by a third party and a company must decide whether or not it is a security risk to involve a third party and there are also legal ramifications if the third party happens to stumble upon decrypted information.<sup>[R8]</sup>	+	On VPNs, user data is encrypted so that potential eavesdroppers cannot understand the content even if it was intercepted. Secure data exchange through a public network provided by encrypted VPNs functions alongside a company’s firewall service that protects the data inside the network. Today, almost all companies with home-working employees use encrypted VPNs to give them secure remote access. Encryption can always be added to other types of VPN however, encryption is usually provided by a third party and a company must decide whether or not it is a security risk to involve a third party and there are also legal ramifications if the third party happens to stumble upon decrypted information.<sup>[http://www.ja.net/documents/development/vpn/different-flavours-of-vpn-web.pdf R3]</sup>

	'''Tunnel-based VPNs'''		'''Tunnel-based VPNs'''
-	There are several types of VPN that results depending on the networking technologies that are used for tunnel-based VPNs, but they all have one thing in common: transmitting traffic between VPN sites using tunnels. Such a VPN provides improved data security and improved site security because user data is isolated from other user data and the provider has control over the connectivity between each of their user sites. Another result of a tunnel-based VPN albeit indirect is improved network performance and reliability. VPNs within a public network can simplify QoS implementations as it provides increased knowledge of individual traffic flows hence, greater control of network traffic.<sup>[R9]</sup>	+	There are several types of VPN that results depending on the networking technologies that are used for tunnel-based VPNs, but they all have one thing in common: transmitting traffic between VPN sites using tunnels. Such a VPN provides improved data security and improved site security because user data is isolated from other user data and the provider has control over the connectivity between each of their user sites. Another result of a tunnel-based VPN albeit indirect is improved network performance and reliability. VPNs within a public network can simplify QoS implementations as it provides increased knowledge of individual traffic flows hence, greater control of network traffic.<sup>[http://www.ja.net/documents/development/vpn/different-flavours-of-vpn-web.pdf R3]</sup>


-	Currently, there are no widely accepted standard for implementing a VPN hence, many companies have developed turn-key solutions on their own while others rely on ISPs that offer VPN solutions that are insufficient by themselves.	+	Currently, there are no widely accepted standard for implementing a VPN hence, many companies have developed turn-key solutions on their own while others rely on ISPs that offer VPN solutions that are insufficient by themselves.<sup>[http://www.intranetjournal.com/text/articles/199911/ft_11_16_99a.html R6]</sup>

	=='''VPN Technology Hurdles in the Future'''==		=='''VPN Technology Hurdles in the Future'''==

Dangm: /* ''Features of a VPN'' */

2008-04-14T04:49:04Z

''Features of a VPN''

← Older revision		Revision as of 04:49, 14 April 2008
Line 33:		Line 33:
	===''Features of a VPN''===		===''Features of a VPN''===

-	In the past, VPNs were secure by virtue of it being leased by a provider for only the customers’ use. With the Internet and improved networking technology, this became expensive hence and cumbersome hence, the requirements for a well-designed VPN had changed. The following list of requirements is the unofficial standard today of a well-designed VPN.<sup>[R5]</sup>	+	In the past, VPNs were secure by virtue of it being leased by a provider for only the customers’ use. With the Internet and improved networking technology, this became expensive hence and cumbersome hence, the requirements for a well-designed VPN had changed. The following list of requirements is the unofficial standard today of a well-designed VPN.<sup>[http://www.ja.net/documents/development/vpn/different-flavours-of-vpn-web.pdf R3]</sup>