MQTT over QUIC: Opportunities and Challenges
summary
EMQX implements a proof‑of‑concept MQTT-over-QUIC binding (MQTT on a single QUIC connection with one bidirectional stream per client) and demonstrates reduced handshake latency via 1 RTT handshake and resumed sessions with 0 RTT session tickets, plus live IP changes using connection migration. Experiments use Wireshark and QUIC (RFC 9000) stacks, show functionality but reveal limits: 1200‑byte minimum MTU, padding and CPU overhead, TCP fallback in ~3–7% of attempts, and scaling risks (a 1% reconnect of 100M clients equals ~1M reconnects).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:40Welcome
- 1:19What is MQTT
- 3:02Where is MQTT used
- 12:24Reduce reconnect overhead
- 18:07multiplexing
- 22:39MQTT
- 28:14Challenges
- 34:50Questions
related talks
19mThe Future With QUIC
54mQUIC illustrated
12mThe QUIC-ematic universe season 2020-2021 preview
30mThere and back again: reinventing UDP streaming with QUIC
30mQUIC, in Theory and Practice
38mWebRTC and QUIC: how hard can it be?
38mOver, Under, Around, and Through: A Detailed Comparison...
51mDown the line: Evolving HTTP and making things QUIC