VPLS is more scalable than EoMPLS and MPLS L3 VPN for layer 2 and layer 3 services respectively. VPLS works well on full mesh topologies while MPLS L3 VPN requires route reflectors. MPLS L3 VPN is more resource intensive for service providers since they must maintain customer routing tables, while VPLS and EoMPLS only require layer 2 switches at customer sites. GETVPN provides the best security and scalability for IPsec VPNs across these technologies.
VPLS is more scalable than EoMPLS and MPLS L3 VPN for layer 2 and layer 3 services respectively. VPLS works well on full mesh topologies while MPLS L3 VPN requires route reflectors. MPLS L3 VPN is more resource intensive for service providers since they must maintain customer routing tables, while VPLS and EoMPLS only require layer 2 switches at customer sites. GETVPN provides the best security and scalability for IPsec VPNs across these technologies.
VPLS is more scalable than EoMPLS and MPLS L3 VPN for layer 2 and layer 3 services respectively. VPLS works well on full mesh topologies while MPLS L3 VPN requires route reflectors. MPLS L3 VPN is more resource intensive for service providers since they must maintain customer routing tables, while VPLS and EoMPLS only require layer 2 switches at customer sites. GETVPN provides the best security and scalability for IPsec VPNs across these technologies.
Not scalable compare to VPLS and MPLS Very Scalable architecture for the layer 2 Scalability for the Customer L3 VPN service Very scalable architecture for the layer 3 service Same as EoMPLS if BGP Auto Discovery is not used, if BGP AD is used,better than Scalability for the Service Provider Not good EoMPLS Service Type Carries Layer 2 frames Carries Layer 2 Frames Carries Layer 3 IP packets Vey good with the MPBGP VPN Route Reflectors but Scalability is very bad for full mesh It works very well for the full mesh RT Constraints should be used to hide unnecessary Working on Full Mesh topology topology information from the unintended PE devices Works quite well but if the number os sites too much, scalability for both Better than EoMPLS for both the Service customer and service provider becomes Provider and Customer from the Requires extra configuration on the Service Provider Working on Hub and Spoke an issue scalability point of view side but it is doable and commonly used Suitable as WAN technology Yes but not scalable Yes it is very scalable Yes it is very scalable It is originally designed as Datacenter It is suitable but if there are so many Interconnect Technology,it is most It can be used as Layer 3 datacenter interconnect sites to interconnect, it's scalability is suitable one among all these three technology but cannot provide layer 2 extension thus Suitable as DCI technology not good options not good as DCI Who controls the Backbone Routing Customer Customer Service Provider Standard Protocol Yes IETF Standard Yes IETF Standard Yes IETF Standard Service Provider Stuff Experince Not well known Limited knowledge Well known VPLS provides LAN emulation so allows layer 2 to be streched over the customer In theory any routing protocol can run as PE-CE but All routing protocols can be enabled over locations.Any routing protocol can run most Service Provider only provides BGP and Static Routing Protocol Support Ethernet over MPLS Service over VPLS service Routing MPLS Traffic Engineering Support Yes Yes Yes Service Provider should offer, otherwise Customer has to create overlays to carry Multicast traffic, Multicast Support Yes Yes that’s why Multicast support may nor be good Same as Frame Relay, doesn't provide Same as Frame Relay,doesn't provide Same as Frame Relay,doesn't provide IPSEC by Security IPSEC by default IPSEC by default default Best technology for IPSEC GETVPN,it provides excellent scalability GETVPN,it provides excellent scalability GETVPN,it provides excellent scalability Bad since the PE devices have to keep the routing Worst since the PE devices have to keep tables of the customer but since the IP addresses Resource Requirement for the Best since the PE devices don't have to all the MAC addresses of the customer can be aggregated, some sites may not need entire Service Provider keep the customer MAC addresses and MAC addresses are not aggregatable routing table of the customer Resource Requirement for the More, it requires either Layer 3 switch or Router at Customer Basic,it requires only layer 2 switch Basic,It requires only layer 2 switch the customer site Yes, Service Provider is transparent for Yes,Service Provider is transparent for Yes with 6vPE technology it provides IPv6 supports IPv6 Support the IPv4 and IPv6 packets the IPv4 and IPv6 packets for the VPN customers With H-VPLS full mesh PW requirement is Route Reflector for the MPBGP sessions between PE Hierarchy None avoided devices In the core split horizon prevents loop. If OSPF Down Bit,IS-IS Up/Down Bit, EIGRP Site of Origin It is only point to point, there is no traffic comes from PW it is not sent back prevents loop when CE is multihomed to the MPLS L3 Loop Prevention chance to loop to another PW VPN PE
George Lamborn, Henry Maringer, and Lamar Commodities, A Partnership v. Thomas H. Dittmer and Dittmer International, Inc., 873 F.2d 522, 2d Cir. (1989)