Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant. The client process had already exited 952ms in, before this test's reaction point at 3005ms, so the silence after that is not evidence either way.
The client did what the clause requires.
What was measured
- Client
- lsquic — LiteSpeed lsquic + BoringSSL, 4.9.4 (2b30189)
- Test
- Datagrams arriving from a second server address —
q-connection-migration - Clause
- RFC 9000 §9.6 (SHOULD)
- Class
- discretionary — The RFC permits either behaviour; the report says which was chosen.
- Required behaviour
- Keep using the address you are already talking to. §9.6 says a client "SHOULD ignore packets received from a server address other than the one it is currently using for sending packets" — a SHOULD, so quietly discarding them and objecting are both conformant. Following the new address is not: nothing is listening there, and a server may only move a client to an address it advertised as its preferred one.
- 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 lsquic at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["q-connection-migration"]'