MIMIQ: Masking IPs with Migration in QUIC
summary
System leverages QUIC connection migration plus a client agent, an allocation server and an edge switch to rotate client IPs frequently without breaking flows. It embeds a fixed switch identifier (SID) in assigned IPs so the edge switch forwards by SID instead of per-client state. Prototype uses an off‑the‑shelf DHCP allocator and shows migrating every 25 packets (4 migrations per 100 packets) yields ~10% throughput penalty at 50 ms RTT. Threat model assumes a passive network adversary and some compromised local clients.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:39Existing Solutions for Hiding IP
- 1:18Our Goal
- 1:49Scenario: censorship circumvention
- 2:27But How?
- 2:50What is QUIC?
- 3:54Threat Model Internet
- 4:26Privacy Goals
- 4:55Some Other Challenges
- 5:55Address Allocation
- 6:57Forwarding Return Traffic to Clients
- 7:31Routing Design
- 8:23QUIC Connection Migration
- 9:21Evaluation - Impact of Migration
- 9:57Evaluation - Results
- 10:50Evaluation - Prototype DHCP
- 11:09Future Work
- 11:25Conclusion
related talks
19mThe Future With QUIC
42mMQTT over QUIC: Opportunities and Challenges
12mThe QUIC-ematic universe season 2020-2021 preview
30mOffloading QUIC Encryption to Enabled NICs
22mQ&A Session 2 – Bharat Parekh
21mImproving L4 Routing Consistency
18mImproving Transfer Times in the Backbone Network Using QUIC Jump Start
38mOver, Under, Around, and Through: A Detailed Comparison...