lsquic — ACK Frequency extension offered

Pass

Handled it: ignored the extension, which the specification permits.

The client did what the clause requires.

What was measured

Client

lsquic — LiteSpeed lsquic + BoringSSL, 4.9.4

Test

ACK Frequency extension offered — q-ack-frequency

Clause

draft-ietf-quic-ack-frequency (MAY)

Class

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

Required behaviour

Negotiate the extension, or ignore it. Either is correct; failing is not.

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-ack-frequency"]'