Implement TUIC Proxy support to Firefox

[Dalex]

Executive Summary

Firefox should evaluate adding native or experimental support for TUIC (TCP & UDP over Internet Connection) proxy protocols. Traditional browser proxy mechanisms (HTTP/HTTPS and SOCKS5) rely on aging networking architectures that struggle on modern, high-latency, and lossy networks. Integrating a QUIC-native proxy protocol would significantly improve transport reliability, connection establishment times, and UDP throughput directly within Firefox.

The Problem: Architectural Limitations of Legacy Proxy Protocols

1. SOCKS5 & Traditional HTTP Are Architecturally Outdated

• Lack of Modern Security Standards: Standard SOCKS5 (RFC 1928, published in 1996) lacks integrated encryption and modern authentication handshakes, requiring fragile secondary tunneling layers for basic transport security.

• TCP Head-of-Line (HoL) Blocking: Legacy proxies multiplex traffic over standard TCP/TLS connections. When packets are lost on unstable connections, all multiplexed browser streams stall simultaneously, introducing significant latency spikes.

• Inefficient Multi-Round-Trip Handshakes: Establishing a proxied connection using legacy protocols requires compounding network round trips (TCP handshake + TLS handshake + proxy authentication + target connection setup), severely delaying Time to First Byte (TTFB).

2. Poor Handling of Modern UDP Traffic

The modern web relies extensively on UDP-based protocols, including WebRTC, real-time media, and HTTP/3. Legacy HTTP CONNECT proxies were designed primarily for TCP streams, making low-latency, bi-directional UDP forwarding inefficient or complex to implement reliably.

Why TUIC?

TUIC is a lightweight, high-performance proxy protocol built directly on top of QUIC (RFC 9000) and HTTP/3 primitives. Supporting TUIC natively in Firefox offers major technical advantages:

1. Independent Multiplexing Without HoL Blocking

Because TUIC operates over QUIC datagrams and streams, packet loss on a single background tab or subresource request does not affect unrelated streams. This ensures smooth, consistent page rendering on erratic or congested connections.

2. First-Class UDP Relay Capabilities

TUIC treats UDP datagrams as native transport units. This allows seamless forwarding of latency-sensitive WebRTC sessions and DNS queries without the overhead of TCP encapsulation.

3. 0-RTT Connection Establishment

Leveraging QUIC TLS 1.3 handshake semantics, TUIC minimizes round trips during initial connection setup and session resumption. This dramatically cuts proxy overhead compared to classic TLS-over-TCP proxies.

4. Advanced Congestion Control Integration

TUIC benefits directly from user-space QUIC congestion control algorithms (such as BBR). This enables optimized throughput and lower bufferbloat across challenging network paths.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.