feat(quic-interop): enable retry + ipv6 testcases; document phase 3

Two more testcases now dispatched through runTransferTest:
  - retry  — exercises the RFC 9000 §17.2.5 + RFC 9001 §5.8 Retry
             handling that landed in d03e17981 / 671f9c705 (DCID swap,
             integrity-tag verify, key re-derivation, token threading).
  - ipv6   — same flow over an IPv6 socket. JDK's DatagramChannel.connect
             handles the v6 address resolution natively; if anything
             breaks it'll be an actual bug worth surfacing.

Plan doc updated to reflect Phase 3 landings (ALPN per testcase,
HqInteropGetClient, multi-stream FIN delivery fix) and the current
validation matrix across aioquic / picoquic / quic-go.

https://claude.ai/code/session_01HcvfQq1ttPV9PkRoJb4nyT
This commit is contained in:
Claude
2026-05-07 00:06:25 +00:00
parent e5bbf85096
commit 038eb18617
2 changed files with 35 additions and 2 deletions
@@ -117,9 +117,17 @@ fun main() {
// scenarios.
// multiplexing — H3 GETs issued in parallel; runner
// verifies overlap on the wire via tshark.
// retry — server sends a Retry packet first; our
// applyRetry path (RFC 9000 §17.2.5 +
// RFC 9001 §5.8) handles DCID swap +
// token threading + key re-derivation.
// ipv6 — same flow over an IPv6 socket;
// JDK DatagramChannel.connect handles
// the v6 address resolution natively.
"handshake", "chacha20", "handshakeloss",
"transfer", "http3", "multiplexing",
"transferloss", "transfercorruption", "longrtt", "goodput", "crosstraffic",
"retry", "ipv6",
-> {
runTransferTest(
requests = requests,