lsd0007

LSD0007: GNUnet communicators
Log | Files | Refs

commit 6a035cd3737bf427e6e739da438830ce82388581
parent 805d397c7feceeab1b0b2f3cdaf372d8d5936303
Author: ch3 <ch3@mailbox.org>
Date:   Thu, 31 Jul 2025 17:44:51 +0200

libp2p: start libp2p with motivation

Diffstat:
Mdraft-gnunet-communicators.xml | 21+++++++++++++++++++++
1 file changed, 21 insertions(+), 0 deletions(-)

diff --git a/draft-gnunet-communicators.xml b/draft-gnunet-communicators.xml @@ -1441,6 +1441,27 @@ content-length: LENGTH OF MESSAGE </t> </section> </section> + <section anchor="libp2p_comm" numbered="true" toc="default"> + <name>libp2p communicator</name> + <t> + The libp2p communicator uses libp2p as a means of communication. + libp2p is "a modular networking framework bundled together as a full stack + of protocols for peer-to-peer systems" and thus shares the general + approach and a similar vision. + The first goal would have been to integrate libp2p directly below core as + an alternative/addition to the transport service as a first step of trying + to get two different p2p networks and their implementations closer to each + other. The long term goal would be to make the two networks compatible + with each other and on the way learn from the respectively other network + and apply the learnings to the respective on network. + But it became soon clear that this was too ambitious for the short term + and the short term goal was simplified to make libp2p a communicator for + transport without loosing the perspective of integrating the two networks + further in the future. + </t> + <t> + </t> + </section> <section anchor="security" numbered="true" toc="default"> <name>Security and Privacy Considerations</name> <section anchor="security_kem" numbered="true" toc="default">