Congestion Control and Sharing a Link
Nothing tells a sender how much of the path is free, so it probes: increase the rate while packets get through, and cut it sharply when they do not. That rule is what keeps a shared network from collapsing, and it makes loss a signal rather than only a fault.
What a learner can do afterwards
- Explain why a sender treats a lost packet as evidence about the path
- Sketch how a sending rate rises and falls over time under this rule
- Say what happens if one sender ignores the rule while others follow it
1 · Read
No sign tells a sender how much path is free, so it probes. It raises its rate while packets land, and it cuts sharply when one is lost. A lost packet is treated as news that the path is full, not only as a fault.
Watch one sender over time and you see teeth: a steady climb while all lands, a sharp drop at the first loss, then a climb again. That sawtooth is the probe at work, always testing for fresh room.
If one sender ignores the rule and never slows, it grabs the queue while polite senders back off. Queues bloat, delays spike, and the shared link serves all of them worse. One cheat punishes the whole crowd.
Read every loss as a signal to slow, not as bad luck. Back off fast, then climb gently to reclaim room.
Probe gently, cut fast on loss, since ignoring the rule wrecks the shared link.
2 · Watch
Take it off screen
Where it sits
Learn first
This opens up
8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.