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

Allow for per-connection MTU configuration #2206

Closed
WesleyRosenblum opened this issue May 9, 2024 · 1 comment
Closed

Allow for per-connection MTU configuration #2206

WesleyRosenblum opened this issue May 9, 2024 · 1 comment

Comments

@WesleyRosenblum
Copy link
Contributor

Problem:

MTU configuration is currently set on the builder for the tokio IO provider, meaning the configuration is the same across connections on an endpoint. There may be scenarios where finer-grained control of the MTU configuration is necessary,.

Solution:

Add mtu Configuration to the connection limits provider, so that each connection may receive a different MTU configuration.

  • Does this change what s2n-quic sends over the wire? Potentially changes the size of packets sent over the wire
  • Does this change any public APIs? --> Adds to the connection limit provider API

Requirements / Acceptance Criteria:

The user is able to configure MTU settings on the connection limit provider

@WesleyRosenblum
Copy link
Contributor Author

Completed in #2232

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

No branches or pull requests

1 participant