Rejected, but with error 0x105 where the specification requires 0x108. The violation was detected; the code reported is wrong.
The client did something the clause forbids, or failed to do what it requires.
What was measured
- Client
- quinn — quinn + h3 (our fork), noq fork
- Test
- CANCEL_PUSH for a push ID that was never promised —
h-cancel-push-unsolicited - Clause
- RFC 9114 §7.2.3 (MUST)
- Class
- correctness — Rejected something invalid, with the code the RFC names.
- Required behaviour
- Close the connection with H3_ID_ERROR. No MAX_PUSH_ID was granted, so every push ID is greater than currently allowed, and §7.2.3 requires a CANCEL_PUSH referencing one to be treated as a connection error of that type.
- Measured
- 2026-09-17
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 quinn at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-cancel-push-unsolicited"]'
What this suite is · The full grid · All clients · All tests · Findings