{"id":5613,"date":"2025-12-04T10:10:51","date_gmt":"2025-12-04T09:10:51","guid":{"rendered":"https:\/\/perso.uclouvain.be\/tom.barbette\/?p=5613"},"modified":"2025-12-04T10:12:29","modified_gmt":"2025-12-04T09:12:29","slug":"multiend","status":"publish","type":"post","link":"https:\/\/perso.uclouvain.be\/tom.barbette\/multiend\/","title":{"rendered":"Multi-End QUIC: A Transport Protocol to Enable One-to-Many Communications"},"content":{"rendered":"\n
\nhttps:\/\/dl.acm.org\/doi\/10.1145\/3769700.3771696\n<\/div><\/figure>\n\n\n\n

El Mehdi Makhroute<\/a>, Quentin De Coninck<\/a>, Tom Barbette<\/a><\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The Internet has shifted from an end-to-end paradigm to an end-to-ends paradigm, i.e. to serve a provider’s content (e.g. a web page, an app feed, \u2026) the client must connect to many ends to fetch various types of resources like web documents, pictures, scripts, news feed, videos, etc\u2026 However, even the recent QUIC transport protocol failed to catch up with this change of paradigm, and the user is forced to waste many round-trip times to fetch the entire content from multiple servers. In this paper, we propose Multi-End QUIC, an extension of Multipath QUIC that enables the establishment of sub-streams directly to backend servers or third-party servers. Multi-End QUIC alleviates the need for proxies in the edge that re-encode and delay those sub-streams, that is able to bypass the relays entirely. This leads to a ~50% latency improvement in a preliminary experiment.<\/p>\n\n\n\n