←back to thread

292 points kixelated | 1 comments | | HN request time: 0.2s | source
Show context
englishm ◴[] No.44988596[source]
Hi! Cloudflare MoQ dev here, happy to answer questions!

Thanks for the award, kixelated. xD

replies(6): >>44989011 #>>44989230 #>>44989615 #>>44989828 #>>44990875 #>>45005783 #
torginus ◴[] No.44989230[source]
Hi! I have a few :)

How close are we to having QUIC actually usable in browsers (meaning both browsers and infrastructure supports it, and it 'just works')

How does QUIC get around the NAT problem? WebRTC requires STUN/TURN to get through full cone NAT, particularly the latter is problematic, since it requires a bunch of infra to run.

replies(3): >>44989495 #>>44989583 #>>44994075 #
kixelated ◴[] No.44989495[source]
Chrome and Firefox support WebTransport. Safari has announced intent to support it and they already use QUIC under the hood for HTTP/3.

Cloud services are pretty TCP/HTTP centric which can be annoying. Any provider that gives you UDP support can be used with QUIC, but you're in charge of certificates and load balancing.

QUIC is client->server so NATs are not a problem; 1 RTT to establish a connection. Iroh is an attempt at P2P QUIC using similar techniques to WebRTC but I don't think browser support will be a thing.

replies(2): >>44989727 #>>44997217 #
valorzard ◴[] No.44989727[source]
Last I checked, Iroh is gonna use WebRTC datachannels to run QUIC over SCTP
replies(1): >>44989823 #
1. kixelated ◴[] No.44989823[source]
That is all sorts of miserable. I had an initial prototype that emulated UDP over SCTP, running QUIC (without encryption) on top. The problem is that SCTP becomes the bottleneck, plus it's super complicated.

I immediately jumped ship to WebTransport when Chrome added support. But I suppose there's no other option if you need P2P support in the browser.