Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant.
The client did what the clause requires.
What was measured
- Client
- neqo — neqo (Firefox), 0.31.1
- Test
- Stream limits set to the minimum a request needs —
q-stream-limit - Clause
- RFC 9000 §4.6 (MUST NOT)
- Class
- discretionary — The RFC permits either behaviour; the report says which was chosen.
- Required behaviour
- Stay inside the advertised limits. Respecting them is a MUST — §4.6 says "Endpoints MUST NOT exceed the limit set by their peer" — but announcing the stall with STREAMS_BLOCKED is only a SHOULD, so a client that stays silent is still conformant.
- Measured
- 2026-09-18
Reproduce it
The suite is the judge, so the reproduction is to point the same client at the same test and let the server report what it saw.
SESSION=$(curl -sX POST https://conformance.pqcrypta.com/session | jq -r .id)
# then drive neqo at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["q-stream-limit"]'