Why doesn't tcp blindly rettansmits all chunks of data?

Started by networkloser, July 04, 2025, 07:10:36 AM

Previous topic - Next topic

networkloser

Host a sends data 92 to 100.
Again host a sends 100 to 120.

The acknowledgement from b hasn't arrived and doesn't arrive within specified timeout interval.

Now my question is why doesn't host a retransmits both 92 to 100 and 100 to 120 when next timer starts. I know it does to make sure it doesn't applies too much pressure in network and wants to verify if there is some problems with receiver. But i forgot where i had read it. Can u send me?

I was following kurose ross networking book but can't find that specific line there no matter how much i searched so far...

deanwebb

Start with 92-100. If no ack, then retry those a third time.

It's the "sliding window" idea. If transmissions are good, send larger and larger chunks up to a limit. If there is an interruption, start small again and see if that gets through. If not, then there's no point in sending all the other stuff.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.