Is there a "can I use" for networks/middleboxes/etc and the problems that arise with them, that talks about the real-world aspects of trying to use QUIC universally?<p>I'd love to use QUIC between a (non-browser) client and server for which both ends are code I've written, without having to have fallbacks to HTTP/1.1 or HTTP/2. (Among other things, I love the idea of just establishing one connection and using it for two-way communication, without worrying about things like WebSocket.)<p>However, the client also needs to run in random places, and while it doesn't necessarily need to support <i>hostile</i> networks, it does need to support <i>broken</i> networks, which to a first approximation can be similar.<p>Are there statistics available for whether and how often QUIC (or more generally UDP) works with:<p>- Random ISPs of varying quality
- Cell data connections
- Shops and airports and similar, which commonly use captive portals and try to intercept traffic when they shouldn't, and come pretty close to being hostile networks
- Vaguely reasonable corporate networks, that aren't <i>trying</i> to block QUIC but might do so through misconfiguration or through some misguided policy put in place for unrelated reasons (e.g "our firewall rules are written about TCP and just drop all UDP and ICMP, and people complain but nobody with the power to change it")
- Somewhat less reasonable corporate networks, that force everything through a proxy and may require things like CONNECT-UDP or SOCKS, but still aren't actively <i>trying</i> to block QUIC<p>I'm hoping that efforts like fly.io's userspace wireguard stack (which uses UDP) might have data here.<p>I'm specifically not asking about the case of networks that are actually <i>trying</i> to be hostile (to QUIC or otherwise), both because such networks may break any number of things including TLS or WebSockets, and because I'd like to avoid restarting the recurring discussion about whether QUIC/etc are a conspiracy to disempower network administrators. I'd love to know the statistics there too, though, if they're available.<p>I'm also curious about the best-known method to reliably and efficiently tunnel QUIC out of a network within a client, for the purposes of separating always-QUIC logic from weird-network-handling logic. Does it make sense, for instance, to have a standard way to tunnel a secure QUIC connection through an insecure TCP connection?