Black Friday SaleIT 360 Bundle complimentary with every master programSee the offer

Understanding Segment Routing and SRv6, the Next Evolution of IP Networking

Learn what Segment Routing and SRv6 are, how the SRH and SIDs work, and how SRv6 compares with MPLS, with real-world use cases for network engineers.

By Network Kings · Published 13 November 2026

Understanding Segment Routing and SRv6, the Next Evolution of IP Networking
In this article

Modern IP networks must handle increasing traffic demands, cloud connectivity, 5G services, and applications that require predictable performance. Traditional routing protocols provide reliable connectivity, but managing complex traffic paths and optimizing network resources can become challenging as infrastructure grows. This is where Segment Routing and SRv6 are changing how network engineers approach routing, traffic engineering, and network programmability.

Segment Routing introduces a simpler way to control packet forwarding by defining the path a packet should follow through a network. Its IPv6-based implementation, known as Segment Routing over IPv6 (SRv6), extends these capabilities using IPv6 addressing. Together, these technologies are helping service providers and enterprises build more flexible, scalable, and programmable IP networks.

What Is Segment Routing in Networking?

Segment Routing is a source routing technique defined in RFC 8402. The ingress node places an ordered list of instructions, called segments, on the packet. Each segment tells a router what to do next, such as reaching a node by its shortest path or leaving through a specific link.

Two segment types matter most:

  • Prefix segments identify a node or prefix and follow the IGP shortest path.
  • Adjacency segments identify a specific link to a neighbor and force the packet over it.

IS-IS or OSPF advertises these segments, so no separate label distribution protocol is needed. Transit routers keep no per-flow state because the path lives in the packet. That is the key difference from RSVP-TE, where every router along a tunnel holds signaling state.

What Is SRv6?

SRv6 is Segment Routing implemented over the IPv6 data plane. Instead of MPLS labels, a segment is an IPv6 address called a Segment Identifier (SID). RFC 8754 defines the header, and RFC 8986 defines the network programming behaviors.

An intermediate router without SRv6 support can forward an SRv6 packet using ordinary IPv6 forwarding when the packet is addressed to a routable destination. However, it cannot execute SRv6 endpoint behaviors or process the SRH as an SRv6 node. Those routers simply route the packet toward its destination address. This makes gradual deployment practical.

How Does SRv6 Work?

SRv6 SIDs

A 128-bit SID typically has three parts: a locator, a function, and optional arguments. The locator is a routable prefix that leads to the node owning the SID. The function defines the behavior. End performs basic endpoint processing, End.X forwards to a specific neighbor, and End.DT4 or End.DT6 decapsulates the packet and looks up the inner destination in a VRF. This is how SRv6 carries VPN services without a separate service label.

The Segment Routing Header

The Segment Routing Header (SRH) is an IPv6 routing extension header, type 4. It holds a segment list and a Segments Left field. The list is encoded in reverse order, and the IPv6 destination address always carries the active segment.

A packet walk example

Imagine a low-latency path from PE1 to PE4 that must pass through P2 and P3.

  1. PE1 encapsulates the customer packet in an outer IPv6 header with an SRH listing P2, P3, and the PE4 service SID. It sets the destination address to P2's SID.
  2. P2 runs the End behavior, decrements Segments Left, copies the next SID into the destination address, and forwards the packet.
  3. P3 does the same.
  4. PE4 runs a behavior such as End.DT4, removes the outer header and delivers the packet into the customer VRF.

Key Benefits of Segment Routing and SRv6

  • Simplification: the IGP distributes segments, so LDP and RSVP-TE can be retired.
  • Scalability: path state sits at the ingress node instead of every transit router.
  • Traffic engineering: SR policies steer flows by latency, affinity, or disjointness. TI-LFA provides fast reroute, and Flexible Algorithm lets you build separate topologies with different metrics.
  • Service programmability: network instructions and VPN services share one data plane.
  • Operational efficiency: a controller using PCEP or BGP can program policies centrally.

There are trade-offs. Long segment lists add header overhead, and compression approaches such as micro-SID (uSID) reduce it. Hardware and software support also varies by vendor, so check platform capabilities before planning a rollout.

Segment Routing vs Traditional Routing vs MPLS

AspectTraditional IP RoutingConventional MPLSSR-MPLSSRv6
Forwarding modelHop-by-hop IP forwardingLabel-based forwarding along LSPsSegment-based forwarding using MPLS labelsSegment-based forwarding using IPv6 SIDs
Data planeIPv4 or IPv6MPLSMPLSIPv6
Control protocolsIGP, BGPIGP, LDP, RSVP-TE, BGP, depending on designIGP with Segment Routing extensions; BGP where requiredIGP with SRv6 extensions; BGP and optional controller protocols
Path controlBased on routing tables, metrics, and policiesSupports explicit paths through mechanisms such as RSVP-TESupports policy-based path control using segment listsSupports policy-based path control using SR policies
Transit router stateMaintains routing and forwarding informationMaintains label forwarding stateAvoids per-flow state in transit routersAvoids per-flow state in transit routers
Service deliveryUses IP routing and additional service mechanismsSupports VPN services using mechanisms such as VPN labelsSupports VPN services using MPLS labels and Segment RoutingSupports VPN services using IPv6 SIDs and endpoint behaviors
Traffic engineeringRequires additional mechanismsSupported through RSVP-TE and other approachesSupported through SR policiesSupported through SR policies
Segment identificationIP addressesMPLS labelsMPLS labels representing segments128-bit IPv6 Segment Identifiers (SIDs)

Conventional MPLS, SR-MPLS, and SRv6 use different forwarding approaches. SR-MPLS retains the MPLS data plane while using Segment Routing, whereas SRv6 uses IPv6 addresses as Segment Identifiers. Both SR-MPLS and SRv6 can reduce the need for per-flow state in transit routers.

Segment Routing

Real-World Applications of SRv6

  • Service provider networks: this is the most established use. L3VPN and EVPN services run over SRv6 cores with traffic-engineered paths.
  • Data centers: SRv6 can extend to top-of-rack switches or hosts for path control, though this is still an emerging area.
  • 5G transport: operators use Flexible Algorithm and SR policies to separate traffic with different latency needs. Slicing designs are still maturing.
  • Cloud connectivity: IPv6 reachability lets operators stitch enterprise and cloud segments with consistent policy.
  • Network automation: controllers compute paths and push policies, which suits intent-based operations.

The Future of IP Networking with SRv6

As networks evolve toward cloud-native infrastructure, 5G connectivity, and automated operations, traditional forwarding approaches increasingly need to support greater flexibility.

SRv6 provides a programmable IPv6-based framework that allows operators to combine routing, traffic engineering, and service-specific forwarding behaviors.

It also creates opportunities for more efficient network slicing, service chaining, and policy-driven connectivity.

Although SRv6 is not a universal replacement for MPLS or traditional IP routing, it represents an important development in modern network architecture. Its adoption will depend on operational requirements, existing infrastructure, and deployment economics.

Conclusion

Segment Routing and SRv6 reduce protocol complexity while giving engineers precise control over paths and services. For CCNA and CCNP learners and working engineers alike, understanding SIDs, the SRH, and SR policies is becoming essential for designing modern networks.

Frequently asked questions

What is Segment Routing?

Segment Routing is a source-routing method where the ingress router encodes an ordered list of segments in the packet, and the network follows those instructions.

What is SRv6?

SRv6 is Segment Routing over IPv6. Segments are IPv6 addresses (SIDs), and the Segment Routing Header carries the list.

How does SRv6 work?

The ingress node adds an SRH with a segment list. Each endpoint node runs the behavior tied to its SID, updates the destination address, and forwards the packet to the next segment.

What is the difference between SRv6 and MPLS?

MPLS forwards packets using labels, with mechanisms such as LDP, RSVP-TE, or Segment Routing used in different architectures. SRv6 uses IPv6 SIDs and the IPv6 data plane, with its control and management mechanisms depending on the deployment.

Does SRv6 replace MPLS?

Not automatically. Many networks use SR-MPLS first and move to SRv6 as hardware, tooling, and IPv6 readiness allow.

What is a Segment Routing Header?

It is an IPv6 extension header (routing type 4) containing the segment list and a Segments Left counter.

Is SRv6 only for service providers?

Service providers lead adoption, but data center and enterprise use cases are emerging.

Why learn from the top 1% of engineers?

Because passing an exam and doing the job are different skills, and only experience closes the gap. Network Kings mentors have spent 11 to 20+ years building and running networks, cloud platforms and pipelines at companies like Apple, Juniper Networks, IBM and CDAC. They teach what breaks in production, why, and how engineers fix it under pressure.

  • Atul Sharma, Founder & CEO mentor at Network KingsAtul Sharma, Founder & CEO
  • Lazaro (Laz) Diaz, Networking mentor at Network KingsLazaro (Laz) Diaz, Networking
  • Sanjay Sharma, AWS mentor at Network KingsSanjay Sharma, AWS
  • Vikas Kumar, Azure mentor at Network KingsVikas Kumar, Azure
  • Ajay, Azure mentor at Network KingsAjay, Azure
  • Amit Bhatt, Linux & DevOps mentor at Network KingsAmit Bhatt, Linux & DevOps

Atul Sharma (Founder & CEO, 12+ yrs), Lazaro (Networking), Sanjay Sharma (AWS, 20+ yrs) and more. Meet the mentors

Same problem, two answers. Pick a track:

On the job: Two routers' OSPF neighbours are stuck in ExStart and never reach Full.

The textbook answer

OSPF moves through Down, Init, 2-Way, ExStart, Exchange, Loading and Full. Memorise the neighbour states for the exam.

Correct. Not enough to fix it.

How a production engineer teaches it

  1. Suspect an MTU mismatch first. ExStart and Exchange stalls usually come down to it.
  2. Compare show ip ospf interface on both ends and fix the interface MTU.
  3. Use ip ospf mtu-ignore only as a stopgap, and say so in the change record.
  4. Write down why it happened, so the next engineer finds it in minutes.
  • The why behind every command, not just the syntax.
  • Hands-on labs for every topic, so the first fault you fix is not at work.
  • Doubts answered by someone who has fixed it in a live network, cloud or pipeline.