Protocol Anomalies the Server Emits

Every anomaly the server will emit on request. Each names the clause it is judged against and the class of behaviour that clause requires — which is not the same everywhere: some of these a client must ignore, some it must reject with a specific code, and some it may answer either way.

• Version Negotiation offering a reserved version alongside v1

  q-version-negotiation

  RFC 9000 §6

  correctnessquic

  13 of 13 passed

  13 Pass

• Retry packet for source-address validation

  q-retry

  RFC 9000 §8.1.2

  correctnessquic

  13 of 13 passed

  13 Pass

• Reserved transport parameter (31·N+27)

  q-reserved-transport-param

  RFC 9000 §18.1

  extensibilityquic

  13 of 13 passed

  13 Pass

• Unknown frame type in a 1-RTT packet

  q-reserved-frame

  RFC 9000 §12.4

  correctnessquic

  10 of 13 passed

  10 Pass3 Fail

• NEW_CONNECTION_ID followed by RETIRE_CONNECTION_ID

  q-cid-rotation

  RFC 9000 §5.1

  resiliencequic

  12 of 13 passed

  12 Pass1 Fail

• Stateless reset

  q-stateless-reset

  RFC 9000 §10.3

  correctnessquic

  11 of 13 passed

  11 Pass2 Fail

• Deliberately tight MAX_DATA and MAX_STREAM_DATA

  q-flow-control

  RFC 9000 §4

  discretionaryquic

  12 of 13 passed

  12 Pass1 Unsupported

• ACK Frequency extension offered

  q-ack-frequency

  draft-ietf-quic-ack-frequency

  discretionaryquic

  13 of 13 passed

  13 Pass

• Packets marked ECT(0)

  q-ecn

  RFC 9000 §13.4

  correctnessquic

  8 of 13 passed

  8 Pass5 Unsupported

• Path MTU black hole above a threshold

  q-pmtu-blackhole

  RFC 9000 §14, RFC 8899

  resiliencequic

  12 of 13 passed

  12 Pass1 Unsupported

• Server-initiated PATH_CHALLENGE

  q-path-challenge

  RFC 9000 §8.2

  correctnessquic

  13 of 13 passed

  13 Pass

• 0-RTT rejected after the client sends early data

  q-zero-rtt-reject

  RFC 9001 §4.6.2

  resiliencequic

  10 of 13 passed

  10 Pass1 Fail2 Unsupported

• A second path offered mid-connection

  q-multipath

  draft-ietf-quic-multipath

  discretionaryquic

  13 of 13 passed

  13 Pass

• Spontaneous 1-RTT key update

  q-key-update

  RFC 9001 §6.2

  interoperabilityquic

  13 of 13 passed

  13 Pass

• Stream limits set to the minimum a request needs

  q-stream-limit

  RFC 9000 §4.6

  discretionaryquic

  13 of 13 passed

  13 Pass

• One datagram in twelve dropped once the path is established

  q-loss-recovery

  RFC 9000 §2.2, §13.3

  resiliencequic

  13 of 13 passed

  13 Pass

• Datagrams arriving from a second server address

  q-connection-migration

  RFC 9000 §9.6

  discretionaryquic

  13 of 13 passed

  13 Pass

• Transport parameter carrying a value the specification forbids

  q-invalid-transport-param

  RFC 9000 §7.4, §18.2

  correctnessquic

  7 of 13 passed

  7 Pass6 Fail

• 425 (Too Early) in answer to a request sent as early data

  q-zero-rtt-replay

  RFC 8470 §5.2

  discretionaryquic

  11 of 13 passed

  11 Pass2 Unsupported

• Path marking packets CE, not just ECT(0)

  q-ecn-congestion

  RFC 9000 §13.4

  correctnessquic

  8 of 13 passed

  8 Pass5 Unsupported

• A second key update after the first is acknowledged

  q-key-update-repeated

  RFC 9001 §6.1, §6.5

  interoperabilityquic

  13 of 13 passed

  13 Pass

• No stream credit at first, then MAX_STREAMS mid-connection

  q-max-streams-credit

  RFC 9000 §4.6

  discretionaryquic

  12 of 13 passed

  12 Pass1 Unsupported

• Reserved SETTINGS identifier (0x1f·N+0x21)

  h-grease-settings

  RFC 9114 §7.2.4.1

  extensibilityhttp3

  13 of 13 passed

  13 Pass

• Reserved frame type on the response stream

  h-grease-frame

  RFC 9114 §7.2.8

  extensibilityhttp3

  13 of 13 passed

  13 Pass

• Unidirectional stream with a reserved stream type

  h-reserved-uni-stream

  RFC 9114 §6.2.3

  extensibilityhttp3

  12 of 13 passed

  12 Pass1 Unsupported

• SETTINGS containing the same identifier twice

  h-duplicate-setting

  RFC 9114 §7.2.4

  discretionaryhttp3

  13 of 13 passed

  13 Pass

• A DATA frame on the control stream

  h-control-frame-unexpected

  RFC 9114 §7.2.1

  correctnesshttp3

  10 of 13 passed

  10 Pass3 Fail

• Control stream whose first frame is not SETTINGS

  h-missing-settings

  RFC 9114 §6.2.1

  correctnesshttp3

  10 of 13 passed

  10 Pass3 Fail

• A second control stream opened by the server

  h-second-control-stream

  RFC 9114 §6.2.1

  correctnesshttp3

  9 of 13 passed

  9 Pass3 Fail1 Unsupported

• Field lines referencing dynamic table insertions

  h-qpack-dynamic-table

  RFC 9204 §4.3.3, §4.5.2

  interoperabilityhttp3

  8 of 13 passed

  8 Pass5 Unsupported

• Huffman-coded field lines with maximal padding

  h-qpack-huffman

  RFC 9204 §4.1.2, RFC 7541 §5.2

  interoperabilityhttp3

  13 of 13 passed

  13 Pass

• Field section larger than the client's advertised maximum

  h-oversized-field-section

  RFC 9114 §4.2.2

  interoperabilityhttp3

  6 of 13 passed

  6 Pass2 Fail5 Unsupported

• Trailing field section after the body

  h-trailers

  RFC 9114 §4.1

  interoperabilityhttp3

  11 of 13 passed

  11 Pass1 Fail1 Inconclusive

• 103 Early Hints before the final response

  h-early-hints

  RFC 9110 §15.2, RFC 8297

  resiliencehttp3

  12 of 13 passed

  12 Pass1 Fail

• GOAWAY sent mid-connection

  h-goaway

  RFC 9114 §5.2

  resiliencehttp3

  13 of 13 passed

  13 Pass

• MAX_PUSH_ID sent by the server

  h-max-push-id

  RFC 9114 §7.2.7

  correctnesshttp3

  9 of 13 passed

  9 Pass4 Fail

• SETTINGS frame on a request stream

  h-settings-on-request-stream

  RFC 9114 §7.2.4

  correctnesshttp3

  12 of 13 passed

  12 Pass1 Fail

• DATA frame before any HEADERS on the response stream

  h-data-before-headers

  RFC 9114 §4.1

  correctnesshttp3

  10 of 13 passed

  10 Pass3 Fail

• CANCEL_PUSH for a push ID that was never promised

  h-cancel-push-unsolicited

  RFC 9114 §7.2.3

  correctnesshttp3

  5 of 13 passed

  5 Pass8 Fail

• Field section that blocks until the encoder stream catches up

  h-qpack-blocked-stream

  RFC 9204 §2.1.2, §2.2.1

  interoperabilityhttp3

  8 of 13 passed

  8 Pass5 Unsupported

• Response stream reset mid-body with H3_REQUEST_CANCELLED

  h-response-stream-reset

  RFC 9114 §8, §4.1

  discretionaryhttp3

  13 of 13 passed

  13 Pass

• PRIORITY_UPDATE sent by the server

  h-priority-update

  RFC 9218 §7.2

  discretionaryhttp3

  13 of 13 passed

  13 Pass

• SETTINGS_ENABLE_CONNECT_PROTOCOL with a value outside 0 and 1

  h-extended-connect

  RFC 9220 §3, RFC 8441 §3

  discretionaryhttp3

  13 of 13 passed

  13 Pass

• PUSH_PROMISE for a push the client never allowed

  h-push-promise-unsolicited

  RFC 9114 §7.2.5, §4.6

  correctnesshttp3

  5 of 13 passed

  5 Pass8 Fail

• SETTINGS_H3_DATAGRAM with a value that is neither 0 nor 1

  h-datagram-setting-invalid

  RFC 9297 §2.1.1

  correctnesshttp3

  7 of 13 passed

  7 Pass6 Fail

• Encoder stream setting a dynamic table capacity above the client's limit

  h-qpack-encoder-overflow

  RFC 9204 §4.3.1, §6

  correctnesshttp3

  7 of 13 passed

  7 Pass5 Fail1 Unsupported

• A second GOAWAY naming a larger identifier than the first

  h-goaway-increasing

  RFC 9114 §5.2

  correctnesshttp3

  8 of 13 passed

  8 Pass5 Fail

• Push stream opened for a push nobody allowed

  h-push-stream-unpromised

  RFC 9114 §6.2.2

  correctnesshttp3

  5 of 13 passed

  5 Pass7 Fail1 Unsupported

• Field line indexing a static table entry that does not exist

  h-qpack-static-index-invalid

  RFC 9204 §3.1, §4.5.2

  correctnesshttp3

  9 of 13 passed

  9 Pass4 Fail

• Datagrams delivered out of order

  q-packet-reordering

  RFC 9000 §2.2

  resiliencequic

  13 of 13 passed

  13 Pass

• Encoder instruction naming a static index that does not exist

  h-qpack-encoder-bad-name-index

  RFC 9204 §3.1, §4.3.2

  correctnesshttp3

  7 of 13 passed

  7 Pass5 Fail1 Unsupported

• Server negotiates only the post-quantum hybrid X25519MLKEM768

  t-hybrid-only

  RFC 8446 §4.1.4, draft-ietf-tls-hybrid-design

  interoperabilitytls

  10 of 13 passed

  10 Pass3 Unsupported

• Server negotiates only classical X25519 against a hybrid offer

  t-classical-only

  RFC 8446 §4.1.1, draft-ietf-tls-hybrid-design §5

  discretionarytls

  13 of 13 passed

  13 Pass

• Hybrid key share large enough to split the Initial across packets

  t-hybrid-large-hello

  RFC 9000 §8.1, §14.1, RFC 9001 §4.4

  resiliencetls

  10 of 13 passed

  10 Pass3 Unsupported

• Server selects a key exchange group the client never offered

  t-group-not-offered

  RFC 8446 §4.1.3, §4.2.8, RFC 9001 §4.8

  correctnesstls

  9 of 13 passed

  9 Pass2 Fail2 Unsupported

• Hybrid key share with an intact X25519 half and a corrupt ML-KEM half

  t-corrupt-hybrid-share

  draft-ietf-tls-hybrid-design §3.2, RFC 8446 §4.1.3

  correctnesstls

  11 of 13 passed

  11 Pass2 Unsupported

• Hybrid key share whose length does not match the group named with it

  t-hybrid-share-length

  draft-kwiatkowski-tls-ecdhe-mlkem §3.1.2, RFC 8446 §6.2, RFC 9001 §4.8

  correctnesstls

  9 of 13 passed

  9 Pass2 Fail2 Unsupported

• Post-quantum certificate chain, compressed per RFC 8879

  t-cert-compression-pq

  RFC 8879 §4, RFC 8446 §4.4.2

  discretionarytls

  7 of 13 passed

  7 Pass5 Unsupported1 Inconclusive

• GREASE named group a client must tolerate

  t-grease-group

  RFC 8701 §4, RFC 8446 §4.2.7

  extensibilitytls

  10 of 13 passed

  10 Pass3 Unsupported