OneNoughtOne
0/240
Loading content...
Read aloud is unavailable in this browser.
Imagine a highway during rush hour. Without traffic signals, lane mergers become chaos—aggressive drivers cut ahead while others wait indefinitely. Some reach their destination quickly while others are stuck for hours. Now imagine the same highway with intelligent traffic management: vehicles enter at controlled rates, high-priority emergency vehicles get dedicated lanes, and everyone's journey becomes predictable.
Traffic shaping in computer networks works on the same principle. It's the sophisticated art of controlling when, how fast, and in what order data packets traverse a network. Without traffic shaping, bursty applications can monopolize bandwidth, latency becomes unpredictable, and network fairness collapses. With proper traffic shaping, networks become predictable, fair, and capable of delivering differentiated service quality.
By the end of this page, you will understand what traffic shaping is, why it's essential for modern networks, how it differs from related concepts like traffic policing, and the fundamental principles that underpin all traffic shaping algorithms. You will gain the conceptual foundation necessary to understand specific algorithms like leaky bucket and token bucket covered in subsequent pages.
Traffic shaping (also known as packet shaping or bandwidth shaping) is a network traffic management technique that deliberately delays some or all packets to bring them into compliance with a desired traffic profile or contract. It's a proactive mechanism that smooths out bursty traffic into a more predictable, steady stream.
Formally, traffic shaping is defined as:
A bandwidth management technique that delays some packets to meet a desired traffic profile, ensuring outgoing traffic conforms to a traffic contract and smoothing bursty flows into more regular patterns.
The key insight is that traffic shaping doesn't discard packets—it delays them. This is fundamentally different from traffic policing, which drops or marks excess traffic. Traffic shaping works by buffering packets and releasing them at a controlled rate.
| Characteristic | Description | Implication |
|---|---|---|
| Delay-Based | Packets are queued and released at controlled times | Zero packet loss from shaping itself (though buffer overflow is possible) |
| Proactive | Operates before congestion occurs | Prevents problems rather than reacting to them |
| Sender-Side | Typically applied at the traffic source or ingress point | Source controls its own traffic behavior |
| Contract Compliance | Ensures traffic meets agreed parameters (rate, burst) | Enables Service Level Agreements (SLAs) |
| Smoothing | Converts bursty traffic to steady streams | Improves network predictability and fairness |
Think of traffic shaping as a 'pace car' for network traffic. Just as a pace car controls the speed of vehicles entering a race, traffic shaping controls the rate at which packets enter the network. The goal isn't to slow things down—it's to ensure everyone can proceed smoothly and predictably.
Traffic shaping emerged as a solution to several fundamental problems in computer networks. Understanding these problems is essential to appreciating the elegance and necessity of traffic shaping mechanisms.
The Bursty Traffic Problem:
Real network traffic is inherently bursty—it comes in irregular, unpredictable bursts rather than smooth, constant flows. Consider these examples:
This burstiness creates instantaneous overload even when average utilization is low. A 100 Mbps link might see bursts of 500 Mbps lasting milliseconds—far exceeding capacity.
The Network Economics Problem:
Networks are shared resources with finite capacity. Service providers must:
Traffic shaping is the enforcement mechanism that makes these guarantees possible. Without it, the customer paying for 10 Mbps can burst to 100 Mbps, degrading service for everyone else.
In a shared network, you cannot trust all endpoints to be well-behaved. A single misbehaving source—intentional or accidental—can degrade the entire network. Traffic shaping provides network operators with a 'trust but verify' mechanism that enforces contracted behavior regardless of endpoint behavior.
Two closely related but fundamentally different mechanisms exist for enforcing traffic contracts: shaping and policing. Understanding the distinction is critical for network design and troubleshooting.
Traffic Shaping:
Traffic Policing:
When to Use Each:
Use Traffic Shaping when:
Use Traffic Policing when:
When a policer drops packets from a TCP flow, TCP interprets this as congestion and reduces its sending rate—potentially far below what the policer would allow. This creates a paradox where the user gets significantly less throughput than their contracted rate. Traffic shaping avoids this problem by never triggering TCP's congestion response.
Traffic shaping operates according to a traffic contract—a set of parameters that define the allowable traffic profile. Understanding these parameters is essential for configuring and analyzing traffic shapers.
Core Traffic Parameters:
Every traffic contract specifies some combination of the following parameters:
| Parameter | Symbol | Definition | Typical Units |
|---|---|---|---|
| Committed Information Rate (CIR) | r | The guaranteed average rate of traffic | bits per second (bps) |
| Peak Information Rate (PIR) | P | The maximum instantaneous rate allowed | bits per second (bps) |
| Committed Burst Size (CBS) | Bc | Maximum burst size at CIR | bits or bytes |
| Excess Burst Size (EBS) | Be | Additional burst allowed above CIR | bits or bytes |
| Time Interval (Tc) | Tc | Measurement interval for rate calculation | milliseconds or seconds |
Understanding CIR and Burst:
The relationship between rate and burst is subtle but critical. Consider a 10 Mbps CIR with a 100 KB burst:
The Bucket Intuition:
Imagine a bucket that fills with 'tokens' at the CIR rate:
A larger burst size allows more traffic to be sent immediately, improving responsiveness for bursty applications. However, it also allows larger queue buildups downstream. The art of configuration is balancing burst size against downstream buffer capacity and latency requirements.
Real-World Contract Example:
A typical enterprise WAN circuit might have:
CIR: 100 Mbps (guaranteed average rate)
PIR: 150 Mbps (peak allowed during bursts)
CBS: 1 MB (committed burst size)
EBS: 500 KB (excess burst, marked as lower priority)
This contract says:
The shaping buffer is a critical component of any traffic shaper. It's where packets wait when they arrive faster than the shaper's configured output rate. Understanding buffer dynamics is essential for both configuration and troubleshooting.
Buffer Mechanics:
When traffic arrives faster than the configured rate:
Buffer Sizing Considerations:
Buffer size involves critical tradeoffs:
| Buffer Size | Advantages | Disadvantages |
|---|---|---|
| Too Small | Low latency, fast feedback to sender | High packet loss during bursts, poor throughput |
| Too Large | No packet loss, smooth throughput | High latency (bufferbloat), poor interactive performance |
| Optimal | Balanced latency and throughput | Requires careful tuning to traffic patterns |
The Bufferbloat Problem:
Excessively large buffers create bufferbloat—a pathological condition where packets experience enormous delays in overloaded buffers. This is particularly harmful because:
Buffer Sizing Rules of Thumb:
For traditional TCP traffic:
Buffer Size = Bandwidth × RTT
For a 100 Mbps link with 20ms RTT:
Buffer = 100 Mbps × 0.020s = 2 Mb = 250 KB
Modern recommendations (with many flows) suggest even smaller buffers:
Buffer Size = (Bandwidth × RTT) / √n
where n is the number of concurrent flows.
Modern traffic shapers often implement Active Queue Management (AQM) algorithms like CoDel or PIE that proactively drop packets before the buffer fills. This provides early congestion signals to TCP while maintaining low latency. AQM is particularly important for combating bufferbloat in shaping buffers.
Traffic shaping can be implemented at various points in the network, each with different characteristics and use cases.
End-Host Shaping:
Traffic shaping at the source (end host) is the most cooperative form:
Edge Shaping:
Traffic shaping at the network edge (first-hop router/switch):
Ingress vs Egress Shaping:
Egress (Outbound) Shaping:
Ingress (Inbound) Shaping:
The general principle is to shape traffic as close to the source as possible. Once traffic enters the network, you cannot 'un-send' it. Upstream congestion cannot be fixed by downstream shaping—the damage (packet drops, queuing delays) has already occurred.
Traffic shaping rarely applies uniformly to all traffic. Instead, traffic is classified into different categories, each with its own shaping policy. This classification is fundamental to Quality of Service (QoS) implementations.
Classification Methods:
| Classification Method | Layer | Description | Example |
|---|---|---|---|
| Layer 2 (Data Link) | L2 | VLAN tag, MAC address, CoS (802.1p) | Shape all VLAN 100 traffic to 50 Mbps |
| Layer 3 (Network) | L3 | IP address, DSCP/ToS, protocol | Shape all traffic to 10.0.0.0/8 to 10 Mbps |
| Layer 4 (Transport) | L4 | Port numbers, TCP/UDP | Shape port 80/443 traffic separately |
| Layer 7 (Application) | L7 | Application identification via DPI | Shape YouTube to 5 Mbps per user |
| Flow-Based | Multi | 5-tuple (src/dst IP, src/dst port, protocol) | Per-flow fair queuing |
DSCP (Differentiated Services Code Point):
DSCP is the primary marking mechanism in modern IP networks. It uses 6 bits of the IP header's ToS (Type of Service) byte to indicate traffic class:
Typical Class-Based Shaping Policy:
Class: Voice (EF, DSCP 46)
- Priority: Strict priority queuing
- Max Rate: 5 Mbps (prevents starvation of other classes)
- Burst: Low (latency-sensitive)
Class: Video (AF41, DSCP 34)
- Priority: Second priority
- Min Rate: 20 Mbps (guaranteed)
- Max Rate: 50 Mbps (ceiling)
- Burst: Medium
Class: Business Data (AF21, DSCP 18)
- Priority: Normal
- Min Rate: 30 Mbps (guaranteed)
- Burst: Large (tolerant of delay)
Class: Best Effort (DSCP 0)
- Priority: Lowest
- Rate: Whatever remains
In practice, traffic markings from untrusted sources (e.g., internet-facing interfaces) are typically reset to a default value at trust boundaries. Trusting external DSCP markings would allow attackers to gain priority by simply marking their traffic as high-priority.
Traffic shaping is ubiquitous in modern networking, appearing in contexts from home routers to global cloud infrastructure. Understanding these applications helps cement the conceptual understanding.
ISP Customer Rate Limiting:
Your home internet connection's speed is enforced by traffic shaping:
Case Study: Video Streaming Traffic Shaping
Netflix and similar services use sophisticated traffic shaping:
This shaping is why Netflix starts with lower quality and improves—it's probing available bandwidth and shaping delivery accordingly.
Almost every network service you use involves traffic shaping somewhere. The fact that you don't notice it is a testament to its effectiveness—good traffic shaping is invisible, creating the illusion of abundant, fair, predictable network resources.
We've established the foundational understanding of traffic shaping—the critical network mechanism that transforms chaotic, bursty traffic into predictable, manageable flows.
What's Next:
Now that we understand the concept and purpose of traffic shaping, we'll dive into the specific algorithms that implement it. The next page explores the Leaky Bucket Algorithm—one of the two fundamental traffic shaping mechanisms that provides a beautifully simple model for enforcing constant output rates.
You now understand what traffic shaping is, why it exists, and how it fits into the broader network QoS landscape. With this foundation, you're ready to explore the specific algorithms—leaky bucket and token bucket—that make traffic shaping a reality.