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

advice on how to disable ECN is problematic when multiplexing multiple connections #4122

Closed
marten-seemann opened this issue Sep 22, 2020 · 3 comments

Comments

@marten-seemann
Copy link
Contributor

The spec says:

If validation fails, then the endpoint MUST disable ECN. It stops setting the ECT codepoint in IP packets that it sends, assuming that either the network path or the peer does not support ECN.

This is fine advice when a single QUIC connection uses a socket. When multiplexing multiple connections on the same socket, it won't be possible to disable ECN on a per-packet basis, unless you want to call setsockopt before every datagram that is sent.

@larseggert larseggert added this to Triage in Late Stage Processing via automation Sep 22, 2020
@larseggert
Copy link
Member

larseggert commented Sep 22, 2020

Not true. You can use ancillary data with sendmsg to specify different ECN codepoints for each packet to be transmitted.

@marten-seemann
Copy link
Contributor Author

Interesting, I didn't know that. I guess we can close this issue with no action then?

@larseggert
Copy link
Member

I would think so.

Late Stage Processing automation moved this from Triage to Issue Handled Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Late Stage Processing
  
Issue Handled
Development

No branches or pull requests

2 participants