q-flow-control
· RFC 9000 §4 · discretionary · layer quic · udp/4466 · SHOULD
Passing this means: The RFC permits either behaviour; the report says which was chosen.
Anomaly type: transport
How each client answered
| Client | Version | Verdict | What happened |
|---|---|---|---|
| curl | ngtcp2/1.11.0 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| quinn | noq fork | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| aioquic | 1.3.0 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| chromium | build 1223 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| quic-go | quic-go v0.61.0 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| quiche | 0.30.0 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
| neqo | 0.31.1 | Pass | Handled it: respected the window without sending a BLOCKED frame, which §4.1 permits. |
What the clause requires
Respect the limit. Announcing the stall with DATA_BLOCKED or STREAM_DATA_BLOCKED is a SHOULD in §4.1, not a MUST, so a client that stays silent is still conformant.
Judged against RFC 9000.
Run this one yourself
Every test is reachable from your own client. Nothing here needs an account.
curl -s https://conformance.pqcrypta.com/catalog.json \
| jq '.tests[] | select(.id == "q-flow-control")'What this suite is · The full grid · All clients · All tests · Findings