Timeline for Estimating the Round-Trip Time in TCP
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17, 2020 at 11:11 | comment | added | Zac67♦ | Thanks @JeffWheeler - I've added timestamping to the answer, but I can't vote more than once for yours. Once again it shows that textbooks are most often not up to date or even obsolete. | |
| Aug 17, 2020 at 11:09 | history | edited | Zac67♦ | CC BY-SA 4.0 | added 269 characters in body |
| Aug 17, 2020 at 11:01 | comment | added | Jeff Wheeler | It's unfortunate that this answer became the accepted one since it's not correct for modern TCP implementations. For example, Linux really does keep track of the time segments were transmitted and acknowledged. You don't have to take my word for it. elixir.bootlin.com/linux/latest/source/net/ipv4/tcp_rate.c | |
| Aug 17, 2020 at 7:45 | comment | added | Zac67♦ | Implementation specifics are really off-topic here, but the easiest way is to track the first segment, when that's ACKed, track the very next segment to send and so on. | |
| Aug 17, 2020 at 0:59 | comment | added | amjad | so TCP just radomly choose one segment within the many segments(pipeline) the send window? what happen if the chosen one is timeout later then TCP cannot go back to measure another segment in previous window? | |
| Aug 17, 2020 at 0:57 | vote | accept | amjad | ||
| Aug 16, 2020 at 15:25 | history | answered | Zac67♦ | CC BY-SA 4.0 |