You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IPv8 has no realistic way of using a different transport protocol than UDP. This is desired for multiple reasons.
The biggest reason is to allow connections from the web. If you would allow multiple protocols web can be connected trough WebRTC, which would open a whole range of new use cases. The second reason is connectablility. A lot of networks (especially corporate) filter out UDP. Having more transport protocols would mean that you could circumvent a lot of these blockades, making it possible to connect a lot more devices to the network.
Suggested solution
You could add a list of supported protocols in the introduction requests, which the other node would choose one to create the connection, this is similar to how TLS agrees on the algorithm to use. After this is decided both nodes attempt to switch to the used protocol. This would give both of the nodes the ability to choose the protocols to be used. This would also add the ability to mix and match the different protocols, depending on the situation.
The text was updated successfully, but these errors were encountered:
Would you kindly look into this paper? I guess you were interested in Pastry DHT. Well, that paper is even more promising in regards to proper message routing.
(It is funny that its author essentially employs the Watts-Strogatz model, yet never mentions it in the paper...)
The problem
IPv8 has no realistic way of using a different transport protocol than UDP. This is desired for multiple reasons.
The biggest reason is to allow connections from the web. If you would allow multiple protocols web can be connected trough WebRTC, which would open a whole range of new use cases. The second reason is connectablility. A lot of networks (especially corporate) filter out UDP. Having more transport protocols would mean that you could circumvent a lot of these blockades, making it possible to connect a lot more devices to the network.
Suggested solution
You could add a list of supported protocols in the introduction requests, which the other node would choose one to create the connection, this is similar to how TLS agrees on the algorithm to use. After this is decided both nodes attempt to switch to the used protocol. This would give both of the nodes the ability to choose the protocols to be used. This would also add the ability to mix and match the different protocols, depending on the situation.
The text was updated successfully, but these errors were encountered: