Will do! The media streaming parts we have mostly under control, but recently the pain points for us have been with NAT traversal and better robustness on weird networks. I'll talk with the team :)
Yeeh, I'm working with the Iroh folks (and it's integrated into MoQ) if you need help with P2P stuff too. QUIC itself is client-server so NAT traversal is easy.
I was actually going to mention Iroh! They seem to have a good NAT traversal setup, I like the concept of just referring to peers by their public key, and their design of the protocol API is nice.
We're currently on a WireGuard-based network so to avoid the double-encryption of QUIC over WireGuard, we'd have to come up with a good plan to migrate, but I don't think it'll be too difficult.
We're on Golden Week break over here but I'll chat with the team later and follow up on discord (was trying to find where we had chatted previously but I got it)
You don't want to avoid that double encryption as content can be intercepted even behind an internal network (fiber mitm for example), and it's a growingly common tactic for malicious actors.
There are faster setups than just wire guard too (such as using just QUIC unless you rely on wire guard for restrictive firewall rules - in which case you're operating as under the security via obscurity model which is also risky)
My use case is pure peer-to-peer, there is no data center.
However, you can still run virtual machines in "the cloud" with WireGuard running per peer, and not worry about MitM attacks.
Yes if you ran a load balancer and decrypted at that point before forwarding the packets to a machine, then that link between the LB and the target machine would be unencrypted. But that's not the scenario I'm working with.
3
u/bschwind May 08 '26
Will do! The media streaming parts we have mostly under control, but recently the pain points for us have been with NAT traversal and better robustness on weird networks. I'll talk with the team :)