rfc
rfc copied to clipboard
vacp2p
2/MVDS: MVDS over libp2p
@dryajov was experimenting with this in https://github.com/status-im/nim-libp2p, work will likely continue there.
https://discuss.ipfs.io/t/the-protocols-interface-for-unreliable-transport for reference
@dryajov any update on this one? Also @raulk mentioned some google doc that explained their packet routing design
@oskarth not right now. I'm still wrapping up some things with the minimal libp2p implementation (gossipsub). I don't expect to be able to start on this again until later, perhaps next week at the earliest.
@dryajov curious if something happened with this?
also cc @staheri14 for awareness
No progress has been made in nim-libp2p and I don't believe that there is any progress at the libp2p spec level either.
On the other hand, with QUIC, we mitigate the need for unreliable transports at the libp2p level for the most part, in part this is one reason for not investing much time in it. QUIC brings the best of both worlds, it eliminates "Head of line blocking", but at the same keeps the reliable part of TCP.
Is there any specific use case for unreliable transports that something like QUIC wouldn't be able to address?
I think this issue is more about end-to-end reliability over (e.g.) a gossip network / forwarding kademlia or similar, not peer-to-peer reliable transport. Perhaps that was an initial misunderstanding?
All good, no specific need here, just wanted to make sure we followed up on this as I remember this was a line of inquiry before
