August 8, 2010

Introduction to Carrier Ethernet VPNs

There are a wide range of VPN technologies available. MPLS-based VPNs are the most prevalent technology types used today, with many based on the use of Ethernet transport to provide high-speed communications. This paper describes the various MPLS-based Ethernet VPN services and technologies which Juniper Networks® supports. These include Juniper's best-in-class VPN implementations, as well as alternatives which provide interoperability with deployed non-Juniper products. This paper is intended for marketing managers seeking to understand Ethernet VPN options, as well as technical managers seeking an overview of their technical alternatives.

This paper describes the Ethernet VPN capabilities supported by Juniper Networks. Although Ethernet VPNs can be implemented using various methods such as generic routing encapsulation (GRE), IPsec, Ethernet VLAN stacking, and MAC-in-MAC, the focus here is on the prevalent MPLS-based techniques.

Download Paper
(Webtorials registration required for downloads. Click here if you forgot your username/password.)


This paper provides a GREAT complement to yesterday's paper on VPLS. Once again, there's a super amount of technical information. In particular, the discussion of Layer 2 versus Layer 3 MPLS VPNS and the components and services are great.

The end of the paper describes Juniper's implementation options, giving a great benchmark regardless of your exact choice of supplier.

Hi Steven, thanks for publishing this really a good summary. I've been wondering for a while how the market will evolve between L2 and L3 services in the next few years (the usual "it's cheaper" being just a short term marketing story - imho), and I must admit that, having not been convinced by my current readings, I'm confused - Any clues from your readers or yourself will be appreciated.
Another point I would like to raise is the interest for Telcos to set-up their new application-aware managed services in a unified way for both L2 and L3 services. Although it may appear weird at a first look (L2 services being selected for leaving CPE routing control to the enterprise, so why would they let their L7 back to the Telcos?), I trust this is a good approach as long as the application-service can be controlled by the enterprise in a co-managed mode. I would also be glad to get feed-back about this topic.
Keep well - Thierry

Search Webtorials

Get E-News and Notices via Email




I accept Webtorials' Terms and Conditions.

Trending Discussions

See more discussions...

Featured Sponsor Microsites



Please note: By downloading this information, you acknowledge that the sponsor(s) of this information may contact you, providing that they give you the option of opting out of further communications from them concerning this information.  Also, by your downloading this information, you agree that the information is for your personal use only and that this information may not be retransmitted to others or reposted on another web site.  Continuing past this point indicates your acceptance of our terms of use as specified at Terms of Use.

Webtorial® is a registered servicemark of Distributed Networking Associates. The Webtorial logo is a servicemark of Distributed Networking Associates. Copyright 1999-2018, Distributed Networking Associates, Inc.