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

📰 News

👤 Account

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions

Jump to an anomaly59

Every one of these is a page: what the server emits, the clause it is judged against, and how each client answered. The full list carries the verdict tallies too.

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 libcurl/8.23.0 ngtcp2/1.25.0 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
quinn noq fork (189b0ed) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
aioquic 1.3.0 (PyPI wheel) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
chromium build 1248 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
quic-go quic-go v0.61.0 (h1:9So2anK4Tp22) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
quiche 0.30.0 (1c8e976) Pass Recovered: detected the black hole 1 time(s) and settled on a 1275-byte path MTU (0 datagram(s) swallowed).
neqo 0.31.1 (cac2b74) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
picoquic 8162550 Pass Recovered: detected the black hole 1 time(s) and settled on a 1289-byte path MTU (0 datagram(s) swallowed).
ngtcp2 3c23148 Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
lsquic 4.9.4 (2b30189) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
xquic 2060a44 Unsupported does not raise its path MTU above the 1200-byte minimum, so there is no black hole for it to detect. The server streamed 96 KiB at it and the path swallows anything over 1300, but nothing it sent was ever that large.
msquic 2.7.0 (7e6525d) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 datagram(s) swallowed).
quico 0.7.0 (npm) Pass Recovered: detected the black hole 1 time(s) and settled on a 1293-byte path MTU (0 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")'