PQ Crypta Logo

Path MTU black hole above a threshold

Detect the black hole, probe down to a working size, and keep the connection. Path-MTU discovery is driven past the limit on this port, so it engages on every connection.

PQ CRYPTA PLATFORM

🏠 Main

🧪 Interactive Apps

📰 News

🛡️ PQ Crypta Proxy

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

q-pmtu-blackhole · RFC 9000 §14, RFC 8899 · resilience · layer quic · udp/4469 · SHOULD

Passing this means: Recovered rather than giving up.

Anomaly type: transport

How each client answered

ClientVersionVerdictWhat happened
curl ngtcp2/1.11.0 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (33 datagram(s) swallowed).
quinn noq fork Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (45 datagram(s) swallowed).
aioquic 1.3.0 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (59 datagram(s) swallowed).
chromium build 1223 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (73 datagram(s) swallowed).
quic-go quic-go v0.61.0 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (87 datagram(s) swallowed).
quiche 0.30.0 Pass Recovered: detected the black hole 1 time(s) and settled on a 1275-byte path MTU (99 datagram(s) swallowed).
neqo 0.31.1 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (113 datagram(s) swallowed).

What the clause requires

Detect the black hole, probe down to a working size, and keep the connection. Path-MTU discovery is driven past the limit on this port, so it engages on every connection.

Judged against RFC 9000, RFC 8899.

Run this one yourself

Every test is reachable from your own client. Nothing here needs an account.

curl -s https://conformance.pqcrypta.com/catalog.json \
  | jq '.tests[] | select(.id == "q-pmtu-blackhole")'

What this suite is · The full grid · All clients · All tests · Findings