also consider HELLOs encountered as PUTs, not just as RESULTS

1 files changed, 11 insertions, 0 deletions

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
@@ -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