commit 499f4dd5d48d575c5dad3fa22ba236147b98b5e8
parent da057ab95248317969b0fa68bd53070c6d3f4bef
Author: ch3 <ch3@mailbox.org>
Date: Thu, 31 Jul 2025 22:49:03 +0200
libp2p: add comment for clarification
(disable examples of address representation for now)
Diffstat:
1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/draft-gnunet-communicators.xml b/draft-gnunet-communicators.xml
@@ -1507,6 +1507,7 @@ content-length: LENGTH OF MESSAGE
communicate over. Due to the similarity in representation, an adaption is
needed to either (a) properly embed the one in the other without parsing
issues, or (b) being able to directly parse both.
+ <!-- seems not to be parsed and displayed on the web representation:
For a better understanding, here is an exemplary libp2p multiaddress:
<artwork anchor="libp2p multiaddress" name="" type="" align="left" alt=""><![CDATA[
/ip4/198.51.100/tcp/1234/p2p/QmYyQSo1c1Ym7orWxLYvCrM2EmxFTANf8wXmmE7DWjhx5N
@@ -1516,7 +1517,12 @@ content-length: LENGTH OF MESSAGE
<artwork anchor="gnunet HELLO" name="" type="" align="left" alt=""><![CDATA[
gnunet://hello/HFXP<...>Y0/WDV0<...>WE20/1754<...>40?udp=%5Bfe80%3A%3Ad284%3A<...>3A2086&udp=%5B2003%3Acb%3A<...>%5D%3A2086<...>&tcp=%5Bfe80%3A%3A<...>%5D%3A2086&tcp=192.168.2.135%3A2086
]]></artwork>
+ -->
For the specification of libp2p multiaddresses see https://github.com/libp2p/specs/tree/master/addressing
+ For just connecting two gnunet nodes via libp2p communicators, the main
+ adaption needed is the compatibility between addressing schemes, as gnunet
+ internally processes (signs with its peer id) the underlying addresses in
+ order to exchange them via its bootstap system.
</t>
<t>
Peer IDs: While gnunet only uses a single cryptographic primitive (EdDSA
