-
Notifications
You must be signed in to change notification settings - Fork 3
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
Should app-guide really recommend DCTCP? #44
Comments
DCTCP can be used as the scalable congestion control in L4S safely. |
@VMatrix1900 , RFC9332 says "Prague fixes a number of problems with the Linux DCTCP code that make it unsuitable for the public Internet". Do you know if those problems have been fixed? (Even if they have, it would probably be wise for this doc to recommend only using the versions subsequent to the fix) |
@Ealdwulf I got your point. I am not aware if the problem in the Linux DCTCP is an Linux implementation issue or inherent to DCTCP RFC. AFAIK, Windows server and FreeBSD both implement DCTCP even before Linux. |
There is a bit more information in rfc9330: Section 6.4.2: "DCTCP needs some safety concerns to be fixed for general use over the public Internet (see Section 4.3 of the L4S ECN spec [RFC9331]), but DCTCP is not on by default, so these issues can be managed within controlled deployments or controlled trials." That sounds like the issues also affect other implementations. I suspect it would be simplest just to remove the reference to DCTCP, but at the least it should only recommend it for controlled environments. |
Got it. A function to detect the above problems with an ECN-capable AQM MUST also be implemented and used." DCTCP does not implement such a function. I agree that DCTCP should only be recommended in controlled environments. |
I'm not completely familiar with the context in which these trials will run, but if it's expected to be over the public internet then it doesn't seem like a good idea to recommend DCTCP as a congestion control.
The text was updated successfully, but these errors were encountered: