ngtcp2 — Field lines referencing dynamic table insertions

Inconclusive

The run did not exercise this test: the client advertised SETTINGS_QPACK_MAX_TABLE_CAPACITY of 0 and SETTINGS_QPACK_BLOCKED_STREAMS of 0, which forbid the server's encoder from using the dynamic table at all.

The run did not establish what this client does here — either it was never put in the situation, or its answer admits more than one reading. Not a failure, and never counted as one.

What was measured

Client

ngtcp2 — ngtcp2 + nghttp3 (direct), 3c23148

Test

Field lines referencing dynamic table insertions — h-qpack-dynamic-table

Clause

RFC 9204 §4.3.3, §4.5.2 (MUST)

Class

interoperability — Correctly decoded something valid but demanding.

Required behaviour

Apply the encoder-stream insertions and decode the headers correctly.

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