xquic — A second path offered mid-connection

Pass

Handled it: declined the multipath offer and stayed on one path, which is conformant.

The client did what the clause requires.

What was measured

Client

xquic — Alibaba xquic + BoringSSL, 2060a44

Test

A second path offered mid-connection — q-multipath

Clause

draft-ietf-quic-multipath (MAY)

Class

discretionary — The RFC permits either behaviour; the report says which was chosen.

Required behaviour

Use the additional path, or decline it cleanly. Do not abort the connection.

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