Congestion Control in IP/TCP Internetworks¶
Nagle, J. (1984). Congestion Control in IP/TCP Internetworks.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Carrying Capacity
- Past it, the system enters a collapse zone that erodes its own substrate: request queues consume memory, timed-out clients retry and add load, threads block on contended locks, and throughput actually falls as offered load rises — congestion collapse, where sustained overload consumes the very capacity that produced it.
This sourceDescribes congestion collapse, in which sustained overload causes throughput to fall as offered load rises, consuming the capacity that produced it.
- Past it, the system enters a collapse zone that erodes its own substrate: request queues consume memory, timed-out clients retry and add load, threads block on contended locks, and throughput actually falls as offered load rises — congestion collapse, where sustained overload consumes the very capacity that produced it.
- Overshoot and Collapse
Mechanisms¶
- Data Network Routing Policy
- A policy that herds too much traffic onto a single "best" path can trigger congestion collapse — throughput falling toward zero as overload begets retransmission that begets more overload.
This sourceExplains classical congestion collapse as retransmission adding duplicate traffic until buffers fill and useful throughput degrades.
- A policy that herds too much traffic onto a single "best" path can trigger congestion collapse — throughput falling toward zero as overload begets retransmission that begets more overload.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
Registry ID ref:39bb6f2509da · see in the full table