lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 12029d01ddbbf49ba1d16ddeb6ec25b56eba427c
parent 1ca92cf30534152e67a8e36f048fe7c30d8e183d
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sat, 12 Mar 2022 08:05:26 +0100

also consider HELLOs encountered as PUTs, not just as RESULTS

Diffstat:
Mdraft-schanzen-r5n.xml | 11+++++++++++
1 file changed, 11 insertions(+), 0 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -1383,6 +1383,17 @@ bchar = *(ALPHA / DIGIT) be stored locally in the block storage. </li> <li> + If the <tt>MTYPE</tt> of the message indicates a HELLO block, the + peer <bcp14>MUST</bcp14> be considered for the local routing + table if the respective k-bucket is not yet full. In this case, + the local peer <bcp14>MUST</bcp14> try to establish a connection + to the peer indicated in the HELLO block using the address information + from the HELLO block. If a connection is established, + the peer is added to the respective k-bucket of the routing table. + Note that the k-bucket <bcp14>MUST</bcp14> be determined by the + key computed using <tt>DeriveBlockKey</tt> and not by the <tt>QUERY_HASH</tt>. + </li> + <li> Given the value in <tt>REPL_LVL</tt>, <tt>HOPCOUNT</tt> and the result of <tt>IsClosestpeer(SELF, BLOCK_KEY)</tt> the number of peers to forward to <bcp14>MUST</bcp14> be calculated