aws/s2n-quic

Allow for per-connection MTU configuration

Closed this issue · 1 comments

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

Completed in #2232