Re: CE - Project Related Ideas & Discussions
The_Big_K
Neha, let us have a new thread for discussion on VPN (Virtual Private Network).
-The Big K-
I hope its okie to continue the discussion in the same thread. But if you think it needs a thread of its own, im sure it won't be much trouble for you to move it 😀
VPN - Virtual Private Network
-------------------------------
A virtual private network in other words can also be defined as a network within a network.
Lets imagine a scenario.
Suppose there is a big MNC in mumbai and it has another branch in chennai. Now as is always the case, the various branches in an organisation need to communicate with each other.
One of the ways of doing this is by using leased lines. In a leased line there is a direct physical connection between the chennai and mumbai branch of the MNC. This connection is an always on connection and can be obtained at various speeds depending on the requirement. And then it can be segmented depending on the usage into data and voice transmission.
The problem with a leased line connection is that it is very expensive as the geographic distance between the connecting places increases. As a result it, only big MNC's can afford such a solution because of its other significant advantages. Security being one of them. Since it is a dedicated line it is hard for eavesdropping.
Now a VPN is sort of like a leased line between the branch in chennai and mumbai, but with one big difference. The two branches are connected directly to each other but without the physical wiring or cabling that might run between them.
A VPN uses the already well established internet for direct connections. In other words, it is a network within a network. The primary means for establishing a VPN network is through a process called tunnelling.
In tunneling a VPN packet is encapsulated inside an IP packet.
This is the basic process that takes place in a VPN connection between 2 points A and B...
* A sends a message to B
* The message is first assembled in the form of a VPN packet.
* This packet is then encapsulated inside an IP packet because only IP packets can traverse the internet. VPN packets cannot. The transport layer in the OSI model can understand only IP packets.
* After it traverses the path, the packet reaches the destination. There it is ripped open by the transport layer of B.
* Another application rips open the VPN packet that was the payload of the IP packet. Some cisco hardware provide physical implementations, that can understand VPN packets.
So this way, the functionality of the leased line is achieved and the cost to benifit ratio is maximum.
I know my description is kinda crude. But if i haven't been clear anywhere, let me know.
And now to the real question as to why it shouldn't be used...
in my post i never mentioned why i shouldn't be used. i said that it could be an overkill for a messenger.
In any case, its not a question of why it shouldn't be used. The truth is, VPN has some implementation complexities. Hardware wise. But if everything is to be emulated by software, it shouldn't be a problem. But makes the whole ordeal of making a messenger too complicated if we think about the VPN feature from set go.
After some ground has been establised it will be evident to us if such a feature warrants inclusion. If it does, then there is no harm in trying.
A note: Most of the messengers out there don't provide true, direct, secure point to point VPN communication. So, such messengers are mostly appealing to induvidual consumers.
With VPN functionality included, the corporate world could be involved as well. it may be far fetched. but its not impossible.
Just like hamachi is used primarily for games, this messenger could probably have 2 modes where one looks like a messenger meant for induvidual consumers and another mode meant for corporates that uses VPN, which is by default secure because its packet level protocol is proprietary.
