Juniper Networks has a distinguished record as a disruptor and a change leader in the networking industry. Juniper technologies helped fuel the rapid growth of the internet in the early 2000s by decoupling the data-plane of an IP router from its control plane and creating routers that moved IP traffic many times faster and more economically than before.
In last week’s blog, we followed a typical service provider through the early stages of SR deployment. While this blog did not reflect the actual deployment experiences of a real service provider, it did reflect issues that a real service provider faces as it plans for SR deployment. In this week’s blog, we will continue to address those issues as we continue to follow our typical service provider through the stages of SR deployment.
Initially, the service provider operated the IPv4 network depicted below.
In previous blogs, we introduced Segment Routing (SR) paths, segments, and label stacks. Now that we are familiar with SR fundamentals, we can discuss the most common SR application, Traffic Engineering (TE).
In last week’s blog, we explained that a Segment Routing (SR) path is an ordered list of segments. We also explained that a segment is an instruction that causes a packet to traverse one or more links.
This week, we will discuss a class of SR implementations that leverage MPLS. We refer to these implementations as SR-MPLS. A thorough understanding of SR-MPLS will help you understand next week’s blog, in which we explain how SR supports traffic engineering applications.
In last week’s blog, we introduced Segment Routing (SR) as an innovative traffic steering mechanism. We also introduced SR domains, policies, paths and segments. This week, we will explore them further.
The Internet was initially designed to provide best-effort connectivity over a least-cost path. Relatively few sites were connected to the Internet, and within those sites, only applications that satisfied an acceptable use policy could be connected.
Today, billions of businesses, households and devices are connected to the Internet. Critical applications include telemedicine, traffic control and financial transactions. Some applications (e.g., email) are tolerant of loss, latency and latency variation, while other applications (e.g., gaming) are significantly less tolerant.