Section Routing Fundamentals: From MPLS to SRv6

Understanding the fundamentals of section routing
This weblog goals to take you on a journey via some basic ideas of Section Routing, highlighting an important options and looking out behind the scenes on the technical implementation.
How section routing works
You may ask, “What on earth is a section?”
The reply is straightforward; a section is a path in a community from one node to a different. To tell apart between a number of segments, every section is assigned a section ID (SID).
If this sounds a bit summary, do not forget that Section Routing is a packet-switching idea whose basic precept is to route packets via the community through a sequence of segments. The packets thus embrace an inventory of SIDs within the right order, and as soon as a packet has accomplished a section, the SID is faraway from the checklist.
Should you’re questioning what sort of community we’re speaking about and the place such a section runs, don’t fear! Trade requirements present exact definitions of segments that make clear this. Learn on to study extra in regards to the format of the section ID and implementation of the SID checklist.
Evaluating information planes: SR MPLS vs. SRv6
Traditionally, section routing was carried out over MPLS networks, the place label-based operation appeared perfect for assembly section routing necessities. Now, these SR MPLS labels are used as SIDs. The SID checklist attaches to the packets as a label stack. It’s that simple with MPLS!
It was later clear that IPv6 networks might additionally implement Section Routing. On this case, specifically formatted IPv6 addresses function SIDs, and the SID checklist is included with packets in what was known as the Routing Extension Header however was promptly renamed the Section Routing Header. The packet’s present SID serves because the IPv6 vacation spot tackle.
Why SRv6 is gaining traction
Finally, the IPv6-based implementation was merely dubbed “SRv6,” since a comparability between the 2 confirmed that SRv6 necessities have been much less demanding.
You solely want IPv6 routing, which even easy routers and switches can deal with. SR MPLS, however, requires end-to-end label switching, supported solely by carrier-grade routers, which aren’t low-cost however supply excessive efficiency.
The underside line—SRv6’s decrease necessities allow bigger community building than SR MPLS networks enable. So it’s now simpler to arrange end-to-end providers that use an SRv6 community as an information aircraft, leading to a noticeable pattern towards IPv6. Now we should face the unpopular subject of migration. However extra on that later!
Superior visitors engineering with section routing
From my expertise instructing many Section Routing programs, I’ve discovered that members typically initially see it as mysterious—even somewhat magical—how the community decides, on the entry level, which segments a packet ought to observe and which SID checklist to connect.
Many individuals assume some new form of intelligence—possibly even synthetic intelligence—has been added to the community.
What is definitely getting used here’s a tried-and-true methodology that’s been obtainable because the starting of MPLS networking: visitors engineering, which is now used inside the context of Section Routing’s data-forwarding idea.
It really works in two steps. First, the community calculates one of the best path to a vacation spot based mostly on limits and optimization objectives. Second, it attaches an identical SID checklist to the packet to information it exactly alongside this calculated path via the community.
You’ll rightly hear in lots of Cisco shows, “The trail is encoded within the packet!” That path provides visitors engineering a serious benefit over the standard strategy utilizing RSVP-TE, which leaves plenty of state within the community (information that routers should retailer). In order that they scale poorly.
Site visitors engineering with Section Routing requires no extra state within the community as a result of the state is carried within the packet as a SID checklist. So are we witnessing a renaissance of visitors engineering with Section Routing? Not essentially; there’s nonetheless administrative overhead to handle.
When push involves shove, such an SID checklist for visitors engineering will also be created manually. Nonetheless, the administrator should actually know their community (a part of the executive effort wanted in visitors engineering)!
Implementing topology impartial loop-free alternate (TI-LFA)
Amid all this enthusiasm for Section Routing, we mustn’t overlook one other key characteristic: Topology Unbiased Loop-Free Alternate (TI-LFA). This characteristic additionally advantages from Section Routing’s stateless strategy: it makes use of an inventory of SIDs to route packets alongside a loop-free alternate path that’s calculated upfront.
What makes it particular is that, with Section Routing, it really works in any topology—therefore the time period “topology impartial.”
This functionality existed even earlier than Section Routing, based mostly on traditional MPLS protocols or just primary routing. Nonetheless, these options weren’t topology-independent. Actually, TI-LFA has grow to be greatest apply in manufacturing Section Routing networks.
Each Site visitors Engineering and TI-LFA connect a SID checklist to packets to route them via a selected sequence of segments.
Key elements of the SR structure
This brings us again to a query that wants a solution: How precisely is a section outlined, and who or what determines its path via the community?
You’ll discover that the talked about use instances for Section Routing—visitors engineering and TI-LFA—have been outlined independently of the particular implementation (i.e., SR MPLS or SRv6), which suggests they’re doable with each.
The identical applies to the 2 most essential section definitions:
- IGP Prefix Section
- Adjacency Section
Understanding IGP prefix segments
The IGP Prefix Section refers to an Inside Gateway Protocol (IGP).
That is an umbrella time period for protocols comparable to IS-IS or OSPF. What they’ve in widespread is that they function on a topology-based foundation; in technical circles, they’re additionally known as Hyperlink State Protocols. That is important for Section Routing, as link-related data have to be marketed all through the community. And this is applicable equally to SR MPLS and SRv6.
What’s the primary process of the IGP? The reply is straightforward! It’s designed to calculate one of the best path to all IPv4 and IPv6 addresses on the community.
This calculation is predicated on summary prices assigned to every interface. The result’s the so-called least-cost path, the place the sum of the prices is minimal. That is exactly what the definition of the IGP prefix section is predicated on: the least-cost path to a prefix routed by the IGP.
In SR MPLS, that is at all times an IPv4 prefix, whereas SRv6 makes use of IPv6 prefixes. For these conversant in the topic, the prefix used on this context is often an IPv4 or IPv6 loopback tackle, comparable to 1.1.1.1/32 or fcaa:aa00::1/128. This makes it simple for the BGP management aircraft for Layer 3 or Layer 2 providers to entry the Section Routing information aircraft.
The only doable Section Routing community makes use of solely IGP prefix segments and thus behaves equally to a traditional MPLS community that makes use of LDP to dynamically set up Label-Switched Paths.
It’s legitimate to ask whether or not Section Routing is helpful in any respect on this case. The packets journey alongside the identical paths as earlier than. Fortuitously, that’s certainly the case. Community operations are grateful that the label doesn’t change alongside the section, and TI-LFA can be utilized to guard the trail.
For SRv6, these arguments additionally maintain true with nearly no adjustments. In any case, every part is less complicated as a result of packets are routed alongside the IGP prefix section solely based mostly on IPv6 routing choices, and it’s inherent to the character of routing that the IPv6 vacation spot tackle—within the case of SRv6, the SID of the IGP prefix section—doesn’t change.
Using adjacency segments for granular management
Following these in-depth reflections on the IGP prefix section, let’s have a look at the adjacency section, which addresses the shortest doable section in a community—a hyperlink between two routers. It doesn’t get any shorter than that.
The time period “adjacency” alludes to the truth that its very definition is predicated on IGP adjacencies. In most backbones, nevertheless, these coincide with the bodily hyperlinks, so this simplified strategy is totally justified.
An adjacency section has a SID, the adjacency SID. Packets arriving at a router with this SID are pressured onto the hyperlink to which the adjacency SID has been assigned. In Section Routing circles, this is named a SID with native scope. However what’s the adjacency section good for? The place can it show its potential?
Two essential use instances we’ve already lined show the necessity to drive visitors over a hyperlink that will not in any other case accomplish that.
The way forward for section routing
Regardless of all of the complexity that Section Routing reveals behind the scenes, we mustn’t ever lose sight of why we’re doing all this within the first place.
Section Routing is designed to deal with information transport for Layer 3 and Layer 2 VPN providers. Specialists seek advice from this as the information aircraft, whereas the management aircraft of those providers (at the very least generally as we speak) is predicated on BGP.
There’s nonetheless rather more to find on the earth of Section Routing. We’ve explored Section Routing primarily at an summary degree and from an MPLS perspective. Within the second a part of the weblog, we’ll shift our focus towards SRv6 and take a more in-depth look behind the scenes.



