Ok i just wrote this up because i noticed there was no page... i work with MPLS-VPNs everyday and there is probablly a lot more info i can put into the page... Specifically i havent said much about route-refecltors and iBGP (and eBGP with multiple private AS merging multiple MPLS-VPNs) use in practicle MPLS-VPN deployments.. also i havent linked many key works to other wikipedia articles. I could get down to the nitty gritty Cisco commands used in MPLS-VPNS too but i think wikipedia might want to remain non-vendor specific? hhhh Still i guess its better than NO MPLS-VPN page, feel free to make your changes :). My grammer and sentence structure, along with spelling was never one of my strong points :).
For those interested, I work for Comindico, who i believe were one of the very first (if not the first?) to deploy a national (in Australia) MPLS network that was designed from day one to be MPLS. The network is 100% MPLS, and covers 98% (maybe more?) of Australia.
- I fixed up your spelling in a few places, expanded on some acronymns and sorted out the internal links a bit. I don't really understand the subject material so I don't have any opinion on how to expand the article, but it's a good start! Davelong 09:39, 29 Mar 2005 (UTC)
More Information requested.
If the Comindico person could please talk more about the following in brief it will be definitely useful. I have worked in this domain about 5 years ago to recollect the matter in the right order! A) CSPF (Constraint based OSPF) to provide TE. B) Martini VPNs (I believe they are usually referred to as VLL) and LDP. As far as I remember, VLL required special support in LDP to distribute labels. C) Label stacking and how it's put to use for VLL and TLS D) Finally PHP - Penultimate Hop Popping. Thanks, Kalyan
I deleted a few paragraphs here, as part of a project to document MPLS and related applications better. Some of what I deleted will reappear in more detailed articles, so don't worry about your content. The idea is that this page is a short overview of MPLS-based VPN technologies, with a short intro on each technology, just enough to tell them apart from each other. For more detail, the links should be followed to the article about that specific technology.
can I Connect to Diff
Neutrality (February 2009)
There are claims about the superiority of MPLS VPNs over IPSec, etc. These claims may be true or may have been true at the time the article was written. As technology evolves quickly, it's quite possible that any supposed advantages have been obviated by new inventions unknown to the author in 2005. Unfortunately, there's no explanation of why these claims might be true, just what feels to me like"marketing" hype. Again, I'm not disputing, I'm just saying that the information provided does not support some of the claimed advantages. BAlfson (talk) 12:48, 1 February 2009 (UTC)
Can u elaborate a bit on how MPLS VPN works or how it achieves a virtually private network ?? i hav a bit of work exp on ths tech so need more help
- That is generally a good request for improving the article. Please note though that Wikipedia is not a forum for anyone to seek help with IT-related or other problems so you shouldn't expect any quick answer. And Wikipedia is not a reliable source either. De728631 (talk) 17:52, 14 October 2011 (UTC)
I collected some info
I have collected some info from the net but I dont know if it could be used here as it may create copyrights problems.. I'll just post it here. All rights are owned by searchenterprisewan.techtarget.com . MPLS VPN basics What is an MPLS VPN? An MPLS VPN is a virtual private network built on top of a service provider’s MPLS network to deliver connectivity between enterprise locations. Available in layer 2 or layer 3 options, the VPN leverages the multiprotocol and labeling capabilities of MPLS to deliver a flat, peer-to-peer network to link all of an organization’s remote sites into a common network. In most cases, MPLS VPN services are sold without encryption, typically relying on the fact that each customer is isolated from the others on his own private network. But for those customers that require it, encryption schemes such as IPsec can be added on top of the VPN configuration. What is the difference between MPLS and MPLS VPN? The distinction between MPLS and MPLS VPN is actually straightforward, but marketing of the services, as well as customers themselves, blur the differences. When referring to MPLS services, many customers are often actually referring to an MPLS VPN service. Multiprotocol Label Switching (MPLS) is the underlining technology that enables service providers to offer customers high-speed private networks. The service provider provisions virtual circuits for each customer, insulating one customer’s data from another’s, even though both customers are on the same physical telecom gear. To the customer, an MPLS network appears similar to a leased line service, delivering a private network to link multiple corporate sites. Depending on the customer requirements, MPLS can deliver connectivity to an enterprise at either a layer 2 Ethernet level or layer 3 IP level. What is the difference between traditional VPN and MPLS VPN services?
Most VPN services create a one-to-one link between two network endpoints (referred to as a point-to-point solution). While the VPN appliance at the head end may support multiple inbound links, each link is unique, with an encrypted tunnel created between each enterprise remote site and headquarters, for example. In the point-to-point model, dedicated hardware or software is used to encrypt the traffic between the two points. For data traffic travelling between two remote sites, this scenario creates an extra hop. In order to reach another remote site, traffic from one site has to traverse the VPN tunnel to the headquarters, then route through another tunnel to its final destination. This additional stop at the hub not only adds latency in routing these packets but also requires that the hub in this configuration be equipped with enough bandwidth to handle the load from multiple remote locations. This type of VPN service is designed to create secure, encrypted links over public networks, including Internet broadband links.
MPLS VPN services, on the other hand, are designed as a multipoint technology by design, making specific VPN tunneling unnecessary. When data moves from one site to another, it looks up the site in the routing table, adds a tag for that site, and sends the packet to the next router. This approach not only reduces the latency of inter-site transfers, it also flattens the wide area network design, simplifying the approach WAN engineers can take when delivering services between sites. This approach does, however, require all remote sites to be connected to the MPLS network. What is the difference between L2 and L3 MPLS VPNs? As the names suggest, MPLS VPNs can be provisioned as a layer 2 connection, such as Ethernet, ATM or frame relay, or at layer 3 as an IP-based network. While the majority of customers opt for the IP-based option, customers with particular security or infrastructure needs may choose the layer 2 option, handling the network layer themselves. MPLS enables service providers to offer a range of options to meet their customers’ specific requirements. What are the advantages of an MPLS VPN?
High performance and ease of deployment are often cited as the advantages of an MPLS VPN over other solutions. Unlike traditional VPNs, which presume that corporate data is being transmitted on public networks, MPLS VPNs use an isolated private network, making the need to encrypt data between sites an optional feature, based on the organization’s level of trust that the service provider can effectively segregate its customers’ networks.
What are the disadvantages of an MPLS VPN?
Like any managed service, an MPLS VPN solution ultimately requires a leap of faith for both the organization and the wide area network (WAN) engineers themselves. Unlike typical point-to-point VPN solutions, which usually have been managed and maintained in-house, using MPLS requires outsourcing your VPN. While relinquishing control of the VPN can take the workload off the WAN engineer, the organization is still at the mercy of the service provider for any moves, adds or changes that need to occur. For many, having to submit a request to the service provider to have configuration changes made, instead of simply making the changes themselves, could be a significant culture shock.
This article is totally pointless. There is absolutely no description, but a zillion buzzwords. I understand that Cisco is pushing this stuff but there is no "why" anywhere. If an article can't be better than this, it should be deleted, in my opinion.126.96.36.199 (talk) 04:23, 29 June 2016 (UTC)