On Tue, Oct 29, 2024 at 3:44 AM Marten Seemann <[email protected]> wrote:
Hi Marten, Christian and I have published a blog post describing our vision for a p2p > extension of QUIC: https://seemann.io/posts/2024-10-26---p2p-quic/. The > idea is to do everything inside of QUIC: Imagine two p2p nodes first > establishing a proxied connection via a relay (immediately starting to > exchange application data), and the QUIC stack migrating this connection > towards a direct path between the two nodes in the background. > This is one of our use cases. We've been using QUIC in our product for peer-to-peer tunnels for a while now. Previously, through-relay tunnels were TCP-based, but we are about to roll out a QUIC-based through-relay tunnel as well (quic-go is used in the relay code :-). In this setup, peers establish QUIC connections to relays, and then create end-to-end QUIC connections (tunnels) between each other using QUIC DATAGRAM frames within these outer QUIC connections. One of our goals is to migrate such end-to-end inner QUIC connections to a direct path where possible. In principal, other migrations could be possible as well, e.g. back to relay, from one relay to another, or even to a TCP-based through-relay tunnel. All of this would occur while the tunnel is actively in use by users (our product is a remote access solution), such as for SSH sessions or long-duration data transfers. We are keen on using official or standard solutions whenever possible and contributing to their development or improvement. Kind regards, Dmitry
