Summary
1. For the last 5+ years, MPLS has been there as the implementation for end-to-end connectivity at Layer 2 ½, Layer 3. 2. This protocol is used to set up the communication links and tear them down. 3. It seems that with carrier Ethernet not trying to stay just local, such as with just between a couple of switches, and in becoming more broad-stroke based, it needs to form more of an MPLS kind of a handshake implementation.
Analysis
It has been common for some analysts to debate “MPLS vs Carrier Ethernet.” While the idea of a clash between the two may sell more market research reports, they are increasingly working in harmony. More importantly, as the source article states, “MPLS is a technology, not a service.”
Starting about five years ago, MPLS was looked upon as the way to do connectivity for Ethernet-based services in general as part of timing protocols. So, there is nothing new involving the process with carrier Ethernet. It is now adopting more of the MPLS protocol for the connection setup. If Ethernet was just going to be between two cities or two buildings, or one metro and 15 customers, it could probably be easily managed at Layer 2. But if it is going to be put across multiple carriers, there are going to be breakdowns. Therefore, MPLS becomes more important as the glue from the standpoint of the handshake between two carriers.
