Wesley Rosenblum

We do have a public QNS image you can use to reproduce this now: public.ecr.aws/s2n/s2n-quic-qns:latest

Thanks Peter. I dug into this, and haven't been able to find any issue with the s2n-quic server itself. I've opened [an issue](https://github.com/hyperium/h3/issues/118) to hyperium/h3, which is the HTTP/3 implementation...

Did you see this case happen? I'm not sure how `w_max` could become less than 2MSS, maybe this could just be a debug assertion?

Ok, maybe add a unit test that triggers this condition so we can verify it is fixed

Yeah looks like they remove the old runs, you can view the latest runs here: https://interop.seemann.io/?test=3&client=kwik, just click the red "3" to see the logs and packet captures

> Additionally, a server MAY consider the client address validated if the client uses a connection ID chosen by the server and the connection ID contains at least 64 bits...

> Are RFC 8899 and RFC 9002 contradicting each other? I believe RFC 8899 is referring to the current congestion window at the moment the MTU is increased, while RFC...

https://github.com/MarcoIeni/release-plz

Can you provide more details about your environment setup and a repro so we can look into this?

This might be happening again: - https://github.com/aws/s2n-quic/actions/runs/8742616782/job/23991319945?pr=2184 - https://github.com/aws/s2n-quic/actions/runs/8742616782/job/23993046067?pr=2184#step:3:36574