MPLS is now widely used by service providers for various services like L2 and L3 VPNs, and
SLA services. Service providers use MPLS with control protocols like LDP to distribute labels for
achieving traffic forwarding. LDP relies on the IGP state and sometimes there is a sync issue
between LDP and IGP. Also, labels are assigned by IGP so they are locally significant and they
are assigned at every hop which takes a lot of computational power. Traditional MPLS works great
while moving traffic throughout the MPLS-enabled network. But it has become expensive to
manage over time. And regarding traffic engineering, which is taking control over the paths, it
uses RSVP-TE but it’s very complex and there is a scalability issue with RSVP. Also, now in the
SDN era, cloud and service providers need more control of the traffic flow as SDN controllers are
using parameters like available BW, latency, path cost, and distance in their computational
algorithm so they are looking for a better solution for flexible and intelligent source-based routing
which can bridge the gap between current network deployment and SDN-enabled networks.
Segment Routing can address these issues. It removes the necessity of signaling and labels
distribution protocols like LDP and RSVP-TE. The number of labels is less, and nodes and prefixes
have a globally unique label which reduces the data plane state. It also uses Path Computation
Engine (PCE) which makes each packet path completely programmable, and it controls not only
path selection but also traffic engineering. SR-MPLS uses source routing in which it calculates
and programs the path of the packet to its destination at the first router which is called the “source
router”.
In this seminar project, I will first analyze the performance of SR-based MPLS against Traditional
MPLS by building a topology in GNS3 or EVE-NG, where I will first check parameters such as
latency, packet loss, jitter, etc. one by using SR-MPLS and another by not using. Then I will look
into SR-Traffic Engineering and SR-PCE by observing its traffic flow in different conditions for
example path failure, backup path, and after restoration.