Gave up (closed the connection with transport error FRAME_ENCODING_ERROR ("local error") and retired none of the connection IDs this endpoint asked it to. The port's only departure from an ordinary one is the rotation: a NEW_CONNECTION_ID whose retire_prior_to retires every earlier ID) instead of recovering.
The client did something the clause forbids, or failed to do what it requires.
What was measured
- Client
- xquic — Alibaba xquic + BoringSSL, 2060a44
- 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-10-27
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 xquic at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["q-cid-rotation"]'