PQ Crypta Logo

quico — NEW_CONNECTION_ID followed by RETIRE_CONNECTION_ID

The client did what the clause requires.

PQ CRYPTA PLATFORM

🏠 Main

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

Jump to an anomaly59

Every one of these is a page: what the server emits, the clause it is judged against, and how each client answered. The full list carries the verdict tallies too.

Pass

Recovered: rotated connection IDs and retired 6 of them.

The client did what the clause requires.

What was measured

Client
quico — quico + lemon-tls, 0.7.0 (npm)
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-15

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 quico at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["q-cid-rotation"]'