s2n-quic-tests's dc doesn't reproduce configuration of s2n-quic-dc::psk #3008
Description
Security issue notifications
If you discover a potential security issue in s2n-quic we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.
Problem:
dc test coverage has a gap in coverage for network MTU=1500 + max endpoint MTU=9000 is not covered (attempting to cover it leads to some panics in test code, so while that should be added it's probably best for a separate). Noticed in #3007.
Need By Date:
n/a
Solution:
- Does this change what s2n-quic sends over the wire? No
- Does this change any public APIs? No
Requirements / Acceptance Criteria:
Add missing test coverage, including additional missing test coverage:
- Network MTU = 1500, Max MTU = 9k
- RTT settings (1ms initial RTT)
- Congestion (Data window etc.) configuration
Needs an audit of the other configuration applied in s2n-quic-dc, and potentially we should find some way to reuse that configuration directly in the tests in s2n-quic.
Out of scope:
n/a