Claude be96d4b28f fix(quic): RFC 9000 §3.2 stream state — STREAM after RESET_STREAM rejected ...

Once the peer has sent RESET_STREAM the receive side enters the "Reset
Recvd" terminal state per §3.2; any subsequent STREAM frame on that id
is a peer protocol violation and MUST close the connection with
STREAM_STATE_ERROR.

Pre-fix the parser silently absorbed the bytes — a peer that violated
the spec would leave us with a phantom mid-reset stream the peer
believed was already dead, with reset/byte bookkeeping diverging.

Implementation: a per-stream `peerResetReceived: Boolean` flag set in
the RESET_STREAM handler and checked at the top of the STREAM handler.
The flag is independent of our local-side `resetState` (which tracks
OUR RESET emission).

Test: `StreamAfterResetTest` (4 cases) covers STREAM-after-reset
closure, FIN-bearing STREAM-after-reset, the legal FIN-then-RESET
shape (no false-positive), and per-stream isolation (reset on stream 3
doesn't poison stream 7).

https://claude.ai/code/session_01XGmmaVuy2wsSZQx2AqN2ik

2026-05-09 04:46:49 +00:00

..

interop

fix(quic-interop): bump HANDSHAKE_TIMEOUT_SEC 10s → 30s for amplificationlimit

2026-05-08 17:06:28 -04:00

plans

fix(quic): RFC 9000 §17.2/§17.3 fixed-bit + §10.1 idle-timeout enforcement

2026-05-09 04:29:32 +00:00

scripts

feat(quic): live interop harness — picoquic Docker + InteropRunner main

2026-04-25 23:08:18 +00:00

src

fix(quic): RFC 9000 §3.2 stream state — STREAM after RESET_STREAM rejected

2026-05-09 04:46:49 +00:00

build.gradle.kts

feat(quic): heap-sampling soak test, FD-leak canary, phantom-stream guard, loss harness

2026-05-07 23:44:13 +00:00