Congestion Control in IP/TCP Internetworks¶
Nagle, J. (1984). Congestion Control in IP/TCP Internetworks.
Cited by¶
4 citations across 4 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.
Supported in partVerified against the work's full text
Nagle describes retransmission-driven congestion collapse in which throughput falls to a small fraction of normal, but only for packet networks.
“every packet is being transmitted several times and throughput is reduced to a small fraction of normal”
- 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
- in computing, an admission rate beneficial to throughput inverts past a capacity ceiling into thrashing or congestion collapse, depleting the buffer and cache reserves whose exhaustion sustains the degraded regime.
Supported in partVerified against the work's full text
RFC 896 describes congestion collapse: retransmissions fill all switch buffers and the network stays in a stable degraded state at a fraction of normal throughput.
“Eventually all available buffers in the switching nodes will be full and packets must be dropped.”
- in computing, an admission rate beneficial to throughput inverts past a capacity ceiling into thrashing or congestion collapse, depleting the buffer and cache reserves whose exhaustion sustains the degraded regime.
Domain-specific¶
- Network Congestion
- Network congestion is an overload condition at a specified communication resource: traffic offered for forwarding or call establishment presses beyond that resource's effective service capacity, and communication service deteriorates.
This sourceOriginal engineering discussion memo, not a standard. https://www.rfc-editor.org/info/rfc896/
- Network congestion is an overload condition at a specified communication resource: traffic offered for forwarding or call establishment presses beyond that resource's effective service capacity, and communication service deteriorates.
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¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 2 of 4 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 3 other ways.
- https://doi.org/10.17487/RFC0896 ×1
- https://www.rfc-editor.org/info/rfc896/ ×1
- https://www.rfc-editor.org/rfc/rfc896.html ×1
Registry ID ref:39bb6f2509da · see in the full table