lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 83ffb4d936894800b6f68b17a2b9e56908ab8bb4
parent 93e3d61b2448b1d919b7d20199469ac80c244def
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Tue, 30 Nov 2021 16:00:50 +0100

restructure

Diffstat:
Mdraft-schanzen-r5n.xml | 32++++++++++++++++++++------------
1 file changed, 20 insertions(+), 12 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -199,18 +199,6 @@ Connectivity | |Underlay| |Underlay| <section anchor="underlay" numbered="true" toc="default"> <name>Underlay</name> <t> - Discuss the DHT underlay concept here. - </t> - </section> - <section anchor="connectivity" numbered="true" toc="default"> - <name>Connectivity and addressing</name> - <t> - In the DHT overlay, a peer is addressable by its Peer ID. - The Peer ID is the 256-bit hash of the peer public key. - The peer public key is the public key of the corresponding - Ed25519<xref target="ed25519" /> peer private key. - </t> - <t> In the network underlay, a peer is addressable by traditional means out of scope of this document. For example, the peer may have a TCP/IP address, or a HTTPS endpoint. @@ -255,6 +243,8 @@ Y924NSHMMZ1N1SQCE5TXF93ED6S6JY311K0QT86G9WJC68F6XVZ0 \ tor+onionv3://rasdflkjasdfliasduf.onion/ ]]></artwork> </figure> + + <!-- 1) The current API is always fire+forget, it doesn't allow for flow control. I think we need to add that, possibly for sending and receiving. @@ -344,6 +334,24 @@ see how we can offer even the most minimal protections against peer </dd> </dl> </section> + + <section anchor="overlay" numbered="true" toc="default"> + <name>Overlay</name> + <t> + In the DHT overlay, a peer is addressable by its Peer ID. + The Peer ID is the 256-bit hash of the peer public key. + The peer public key is the public key of the corresponding + Ed25519<xref target="ed25519" /> peer private key. + </t> + </section> + <section anchor="blockstorage" numbered="true" toc="default"> + <name>Block Storage</name> + <t> + </t> + </section> + <section anchor="messages" numbered="true" toc="default"> + <name>Message Processing</name> + </section> <section anchor="routing" numbered="true" toc="default"> <name>Routing</name> <section anchor="peer_selection" numbered="true" toc="default">