Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

"TCP-Friendly" is a bit misleading #38

Closed
martinthomson opened this issue Dec 22, 2020 · 2 comments · Fixed by #41
Closed

"TCP-Friendly" is a bit misleading #38

martinthomson opened this issue Dec 22, 2020 · 2 comments · Fixed by #41
Assignees

Comments

@martinthomson
Copy link
Contributor

Given that a lot of TCP deployments use Cubic, I think that the intent here is to be friendly to Reno instead. As the text establishes, it is AIMD(1, 0.5) that this wants to be sensitive to.

It might have made sense to talk about TCP when Cubic wasn't widely deployed, but now it is just confusing.

@larseggert
Copy link
Contributor

Agreed. We need to do a larger rewrite of much of the beginning of the document, which was historically correct but is now outdated, given that all stacks default to CUBIC.

@larseggert larseggert added the help wanted Looking for someone resolve this issue label Feb 2, 2021
@lisongxu
Copy link
Contributor

lisongxu commented Feb 3, 2021

I can also help to revise the text later next week, is it ok? Thanks, Lars

@goelvidhi goelvidhi removed the help wanted Looking for someone resolve this issue label Feb 4, 2021
@larseggert larseggert linked a pull request Feb 18, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants