The run did not exercise this test: the connection was too short-lived to require a rotation.
The suite could not establish what this client does here. That is a shortcoming of the run rather than anything about the client, and every one of these is on our list to remove.
What was measured
- Client
- quinn — quinn + h3 (our fork), noq fork
- Test
- NEW_CONNECTION_ID followed by RETIRE_CONNECTION_ID —
q-cid-rotation - Clause
- RFC 9000 §5.1 (MUST)
- Class
- resilience — Recovered rather than giving up.
- Required behaviour
- Adopt the new connection ID, retire the old one, and stay connected.
- 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 quinn at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["q-cid-rotation"]'