commit 0a57cf768b93005f089beb9f6277e5b0b31e06c8 parent eda58051a5604bbf3bdb3a572d59a4e0e5a47e9c Author: ch3 <ch3@mailbox.org> Date: Thu, 31 Jul 2025 21:51:56 +0200 libp2p: briefly address different implementations Diffstat:
| M | draft-gnunet-communicators.xml | | | 11 | +++++++++++ |
1 file changed, 11 insertions(+), 0 deletions(-)
diff --git a/draft-gnunet-communicators.xml b/draft-gnunet-communicators.xml @@ -1488,6 +1488,17 @@ content-length: LENGTH OF MESSAGE The documentation of the libp2p multiaddress can be found here: https://docs.rs/libp2p/latest/libp2p/struct.Multiaddr.html </t> + <t> + One of the first consideration, when connecting the two networks, is the + language. libp2p has implementations in many languages which all have + different capabilities. (An overview is provided at + https://libp2p.io/implementations.) + In order to decide on the implementation mainly two factors have to be + considered: Which features are needed and how difficult is the technical + connection of the implementation? Depending on the implementation + different wrappers and converters have to be implemented before being able + to use them. + </t> </section> <section anchor="security" numbered="true" toc="default"> <name>Security and Privacy Considerations</name>