Ignored the unrecognised element and completed the follow-up request. The client process had already exited 4409ms in, before this test's reaction point at never observed, so the silence after that is not evidence either way.
The client did what the clause requires.
What was measured
- Client
- quico — quico + lemon-tls, 0.7.0 (npm)
- Test
- Unidirectional stream with a reserved stream type —
h-reserved-uni-stream - Clause
- RFC 9114 §6.2.3 (MUST)
- Class
- extensibility — Ignored something unknown and carried on.
- Required behaviour
- Abort reading the stream or discard it — §6.2.3 permits either. What it forbids is treating it as meaningful, or as fatal to the connection.
- Measured
- 2026-10-15
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 quico at the test URL and read the verdict:
curl -s https://conformance.pqcrypta.com/report/$SESSION.json | jq '.results["h-reserved-uni-stream"]'