lsquic — One datagram in twelve dropped once the path is established

Pass

Recovered and completed the follow-up request.

The client did what the clause requires.

What was measured

Client

lsquic — LiteSpeed lsquic + BoringSSL, 4.9.4

Test

One datagram in twelve dropped once the path is established — q-loss-recovery

Clause

RFC 9000 §2.2, §13.3 (MUST)

Class

resilience — Recovered rather than giving up.

Required behaviour

Reassemble the stream and deliver the whole body. §2.2 requires an endpoint to buffer data received out of order and deliver it as an ordered byte stream, and §13.3 has the lost data sent again in new STREAM frames — so a response full of gaps must still arrive complete and in order.

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