[lsd0004] 01/02: also consider HELLOs encountered as PUTs, not just as RESULTS

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository lsd0004.

commit 12029d01ddbbf49ba1d16ddeb6ec25b56eba427c
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Sat Mar 12 08:05:26 2022 +0100

    also consider HELLOs encountered as PUTs, not just as RESULTS
---
 draft-schanzen-r5n.xml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index edf46dc..f59e47b 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1382,6 +1382,17 @@ bchar = *(ALPHA / DIGIT)
               flag ist set, the message <bcp14>MUST</bcp14>
               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

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.