Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lower bound for congestion window (drops or classic ECN) #83

Closed
goelvidhi opened this issue Aug 31, 2021 · 1 comment · Fixed by #124
Closed

Lower bound for congestion window (drops or classic ECN) #83

goelvidhi opened this issue Aug 31, 2021 · 1 comment · Fixed by #124
Assignees

Comments

@goelvidhi
Copy link
Collaborator

@goelvidhi goelvidhi commented Aug 31, 2021

Markku Kojo said,

The draft modifies RFC 3168 when ECE arrives and would result
in cwnd < 2 MSS by setting a lower bound of 2 MSS for cwnd (only
ssthresh is supposed to have a lower bound of 2 MSS).
This is in conflict with RFC 3168, RFC 5033, and RFC 2914 which
require "full backoff", that is, a sender must continue decreasing
sending rate as long as congestion persists. This is a fundamental
property for any congestion control mechanism. For ECN, RFC 3168
(sec 6.1.2) requires that cwnd is halved until the minimum cwnd
of one MSS is received, and then the sender continues reducing
sending rate by using a timer with exponential backoff, if more
ECE-echo packets keep on arriving.

This implementation bug has been long with Linux and is present
in other stacks as well and should get corrected ASAP with
appropriate advise in all published RFCs, instead of replicating
the bug in the RFC series.

@goelvidhi goelvidhi changed the title Lower bound for congestion window for drops or classic ECN Lower bound for congestion window (drops or classic ECN) Aug 31, 2021
@goelvidhi goelvidhi self-assigned this Sep 1, 2021
@lisongxu lisongxu mentioned this issue Sep 1, 2021
@bbriscoe bbriscoe mentioned this issue Sep 15, 2021
@larseggert
Copy link
Member

@larseggert larseggert commented Oct 11, 2021

Where are we with this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants