AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
devopscritical PriorityID: envoy-gateway-http3-quic-connection-migration-guardrail

Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard

Mandates deterministic QUIC Connection ID (CID) routing, eBPF socket dispatching, and cryptographic session continuity across Envoy Gateway deployments for HTTP/3 clients undergoing IP/port migrations. Enforces strict decoupling of UDP transport state from 4-tuple addressing during cellular-to-Wi-Fi network shifts to prevent connection resets and state desynchronization.

Prohibited Anti-Pattern: 4-Tuple IP-Pinned UDP Listeners and Stateless Connection ID Decoupling Causing Silent QUIC Teardowns

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard - Mandates deterministic QUIC Connection ID (CID) routing, eBPF socket dispatching, and cryptographic session continuity across Envoy Gateway deployments for HTTP/3 clients undergoing IP/port migrations. Enforces strict decoupling of UDP transport state from 4-tuple addressing during cellular-to-Wi-Fi network shifts to prevent connection resets and state desynchronization.
globs: infra/**/*.ts, k8s/**/*.ts, src/config/**/*.ts, deploy/**/*.ts
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/envoy-gateway-http3-quic-connection-migration-guardrail"
---

# Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: 4-Tuple IP-Pinned UDP Listeners and Stateless Connection ID Decoupling Causing Silent QUIC Teardowns

## System Constraints
You are a Principal Infrastructure and Network Architect enforcing strict HTTP/3 and QUIC protocol invariants in Envoy Gateway. Mandate dynamic connection migration support (RFC 9000), deterministic Connection ID (CID) dispatch via eBPF/SO_REUSEPORT, synchronized cryptographic keys across cluster workers, and zero reliance on 4-tuple IP/port persistence.

## Strict Guidelines
- Engineers MUST ALWAYS enable 'connection_migration_supported: true' within the Envoy quic_protocol_options listener configuration.
- Engineers MUST NOT bind QUIC session tracking, rate-limiting, or downstream state machines to the client 4-tuple (source IP, source port, destination IP, destination port).
- Services MUST configure synchronized, cluster-wide QUIC Connection ID (CID) encryption keys across all gateway pods to allow any worker node to decrypt and route migrated packets without connection aborts.
- Infrastructure pipelines MUST deploy eBPF reuseport socket dispatchers (BPF_PROG_TYPE_SK_REUSEPORT) or Maglev CID hashing when multi-threaded or multi-pod UDP listener groups are instantiated.
- Components NEVER drop valid QUIC PATH_CHALLENGE or PATH_RESPONSE frames at ingress firewalls, upstream LB layers, or network security groups during network transition phases.

## Bad vs Good Implementations
### Envoy Gateway HTTP/3 QUIC Listener and CID Configuration

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Omits quic_protocol_options enabling dynamic connection migration, omits cluster-shared CID encryption keys, and fails to configure an eBPF reuseport dispatcher. When a client switches from 4G/5G to Wi-Fi, the changed client IP breaks downstream packet routing, terminating the session.
```typescript
import * as k8s from '@kubernetes/client-node';

// ANTI-PATTERN: QUIC listener binds state strictly to client 4-tuple without
// connection migration or synchronized CID encryption, causing teardowns during cellular-to-Wi-Fi switches.
export function buildEnvoyQuicListener(): Record<string, unknown> {
  return {
    name: 'h3_ingress',
    address: { socket_address: { address: '0.0.0.0', port_value: 443, protocol: 'UDP' } },
    udp_listener_config: {
      downstream_socket_config: { max_rx_datagram_size: 1350 }
    },
    filter_chains: [{
      transport_socket: {
        name: 'envoy.transport_sockets.quic',
        typed_config: {
          '@type': 'type.googleapis.com/envoy.extensions.transport_sockets.quic.v3.QuicDownstreamTransport',
          enable_early_data: false
        }
      }
    }],
    // CRITICAL FLAW: Missing dynamic connection migration & deterministic CID routing
    quic_options: {}
  };
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly configures 'connection_migration_supported: true', uses a deterministic connection ID generator keyed with a synchronized cluster secret, and enables SO_REUSEPORT. This ensures packets arriving with a mutated 4-tuple during Wi-Fi transitions are reliably routed to the original worker thread holding the TLS state.
```typescript
import * as k8s from '@kubernetes/client-node';

// PRODUCTION INVARIANT: Enables dynamic QUIC connection migration, synchronized
// CID routing across worker threads, and path validation continuity.
export function buildEnvoyQuicListener(sharedCidKeySecret: string): Record<string, unknown> {
  return {
    name: 'h3_ingress',
    address: { socket_address: { address: '0.0.0.0', port_value: 443, protocol: 'UDP' } },
    udp_listener_config: {
      downstream_socket_config: { max_rx_datagram_size: 1350 },
      quic_options: {
        quic_protocol_options: {
          // Invariant: Allow endpoints to dynamically rebind IPs without session drop
          connection_migration_supported: true,
          max_concurrent_streams: 100,
          idle_timeout: '30s'
        },
        // Invariant: Consistent connection-ID generation for multi-worker/pod eBPF routing
        connection_id_generator_config: {
          name: 'envoy.quic.deterministic_connection_id_generator',
          typed_config: {
            '@type': 'type.googleapis.com/envoy.extensions.quic.connection_id_generator.v3.DeterministicConnectionIdGeneratorConfig',
            server_connection_id_length: 20,
            key: { inline_string: sharedCidKeySecret }
          }
        }
      }
    },
    // Enforces reuseport for seamless socket handover across worker threads
    enable_reuse_port: true,
    filter_chains: [{
      transport_socket: {
        name: 'envoy.transport_sockets.quic',
        typed_config: {
          '@type': 'type.googleapis.com/envoy.extensions.transport_sockets.quic.v3.QuicDownstreamTransport',
          enable_early_data: true
        }
      }
    }]
  };
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Kubernetes Resource Inspector
Validates Envoy Gateway Custom Resources and EnvoyProxy configurations directly against live clusters.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Envoy Gateway Diagnostic CLI
Inspects listener stats, QUIC migration success metrics, and eBPF reuseport map distributions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard

Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard defines an industrial-grade behavioral standard for devops engineering. Mandates deterministic QUIC Connection ID (CID) routing, eBPF socket dispatching, and cryptographic session continuity across Envoy Gateway deployments for HTTP/3 clients undergoing IP/port migrations. Enforces strict decoupling of UDP transport state from 4-tuple addressing during cellular-to-Wi-Fi network shifts to prevent connection resets and state desynchronization. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: 4-Tuple IP-Pinned UDP Listeners and Stateless Connection ID Decoupling Causing Silent QUIC Teardowns Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation Drift4-Tuple IP-Pinned UDP Listeners and Stateless Connection ID Decoupling Causing Silent QUIC TeardownsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS enable 'connection_migration_supported

Engineers MUST ALWAYS enable 'connection_migration_supported: true' within the Envoy quic_protocol_options listener configuration.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT bind QUIC session tracking, rate-limiting, or downstream state machines to the client 4-tuple (source IP, source port, destination IP, destination port).

Engineers MUST NOT bind QUIC session tracking, rate-limiting, or downstream state machines to the client 4-tuple (source IP, source port, destination IP, destination port).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Services MUST configure synchronized, cluster-wide QUIC Connection ID (CID) encryption keys across all gateway pods to allow any worker node to decrypt and route migrated packets without connection aborts.

Services MUST configure synchronized, cluster-wide QUIC Connection ID (CID) encryption keys across all gateway pods to allow any worker node to decrypt and route migrated packets without connection aborts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Infrastructure pipelines MUST deploy eBPF reuseport socket dispatchers (BPF_PROG_TYPE_SK_REUSEPORT) or Maglev CID hashing when multi-threaded or multi-pod UDP listener groups are instantiated.

Infrastructure pipelines MUST deploy eBPF reuseport socket dispatchers (BPF_PROG_TYPE_SK_REUSEPORT) or Maglev CID hashing when multi-threaded or multi-pod UDP listener groups are instantiated.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER drop valid QUIC PATH_CHALLENGE or PATH_RESPONSE frames at ingress firewalls, upstream LB layers, or network security groups during network transition phases.

Components NEVER drop valid QUIC PATH_CHALLENGE or PATH_RESPONSE frames at ingress firewalls, upstream LB layers, or network security groups during network transition phases.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Envoy Gateway HTTP/3 QUIC Dynamic Connection Migration & Session Continuity Standard critical for AI coding assistants?

Mandates deterministic QUIC Connection ID (CID) routing, eBPF socket dispatching, and cryptographic session continuity across Envoy Gateway deployments for HTTP/3 clients undergoing IP/port migrations. Enforces strict decoupling of UDP transport state from 4-tuple addressing during cellular-to-Wi-Fi network shifts to prevent connection resets and state desynchronization. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (4-Tuple IP-Pinned UDP Listeners and Stateless Connection ID Decoupling Causing Silent QUIC Teardowns) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

Envoy