Congestion Control for High BandwidthDelay Product Environments Dina

Congestion Control for High Bandwidth-Delay Product Environments Dina Katabi Mark Handley Charlie Rohrs

TCP congestion control performs poorly as bandwidth or delay increases 50 flows in both directions Buffer = BW x Delay RTT = 80 ms Avg. TCP Utilization Shown analytically in [Low 01] and via simulations 50 flows in both directions Buffer = BW x Delay BW = 155 Mb/s Because TCP lacks fast response • Spare bandwidth is available TCP increases by 1 pkt/RTT even if spare bandwidth is huge • When a TCP starts, it increases exponentially Too many drops Flows ramp up by 1 pkt/RTT, taking forever to grab the large bandwidth Bottleneck Bandwidth (Mb/s) Round Trip Delay (sec)

Proposed Solution: Decouple Congestion Control from Fairness High Utilization; Small Queues; Few Drops Bandwidth Allocation Policy

Proposed Solution: Decouple Congestion Control from Fairness Coupled because a single mechanism controls both Example: In TCP, Additive-Increase Multiplicative. Decrease (AIMD) controls both How does decoupling solve the problem? 1. To control congestion: use MIMD which shows fast response 2. To control fairness: use AIMD which converges to fairness

Characteristics of Our Solution 1. Improved Congestion Control (in high bandwidthdelay & conventional environments): • Small queues • Almost no drops 2. Improved Fairness 3. Scalable (no per-flow state) 4. Flexible bandwidth allocation: min-max fairness, proportional fairness, differential bandwidth allocation, …

XCP: An e. Xplicit Control Protocol 1. Congestion Controller 2. Fairness Controller

How does XCP Work? Round Trip Round Time Trip Time Congestion Window Feedback = + 0. 1 packet Congestion Header

How does XCP Work? Round Trip Time Congestion Window Feedback == Feedback +- 0. 3 0. 1 packet

How does XCP Work? Congestion Window = Congestion Window + Feedback XCP extends ECN and CSFQ Routers compute feedback without any per-flow state

How Does an XCP Router Compute the Feedback? Congestion Controller Congestion Goal: Matches input traffic to link capacity. Controller & drains the queue Fairness Controller Goal: Fairness Divides between flows Controller to converge to fairness Looks at aggregate traffic & queue Looks at a flow’s state in Congestion Header Algorithm: Aggregate traffic changes by ~ Spare Bandwidth ~ - Queue Size So, = davg Spare - Queue Algorithm: If > 0 Divide equally between flows If < 0 Divide between flows proportionally to their current rates MIMD AIMD

Getting the devil out of the details … Congestion Controller = davg Spare - Queue Theorem: System converges to optimal utilization (i. e. , stable) for any link bandwidth, delay, number of sources if: No Parameter Tuning (Proof based on Nyquist Criterion) Fairness Controller Algorithm: If > 0 Divide equally between flows If < 0 Divide between flows proportionally to their current rates Need to estimate number of flows N No Per-Flow State RTTpkt : Round Trip Time in header Cwndpkt : Congestion Window in header T: Counting Interval

Implementation uses few multiplications & additions per packet Practical! Liars? • Policing agents at edges of the network or statistical monitoring • Easier to detect than in TCP Gradual Deployment XCP can co-exist with TCP and can be deployed gradually

Performance

Subset of Results S 1 Bottleneck S 2 R 1, R 2, …, Rn Sn Similar behavior over:

XCP Remains Efficient as Bandwidth or Delay Increases Utilization as a function of Delay Bottleneck Bandwidth (Mb/s) Avg. Utilization as a function of Bandwidth Round Trip Delay (sec)

XCP Remains Efficient as Bandwidth or Delay Increases XCP increases proportionally to spare bandwidth Bottleneck Bandwidth (Mb/s) Utilization as a function of Delay Avg. Utilization as a function of Bandwidth and chosen to make XCP robust to delay Round Trip Delay (sec)

XCP Shows Faster Response than TCP Start 40 Flows Stop the 40 Flows XCP shows fast response!

XCP Deals Well with Short Web-Like Flows Average Utilization Average Queue Drops Arrivals of Short Flows/sec

XCP is Fairer than TCP Same RTT Avg. Throughput Different RTT Flow ID (RTT is 40 ms 330 ms )

XCP Summary • XCP Outperforms TCP o Efficient for any bandwidth o Efficient for any delay o Scalable o • Benefits of Decoupling Use MIMD for congestion control which can grab/release large bandwidth quickly o Use AIMD for fairness which converges to fair bandwidth allocation o

Questions? NS Code & More Information at: http: //ana. lcs. mit. edu/dina/XCP