[lsd0004] branch master updated (1ca92cf -> 8456369)

[gnunet]

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

grothoff pushed a change to branch master
in repository lsd0004.

    from 1ca92cf  may be
     new 12029d0  also consider HELLOs encountered as PUTs, not just as RESULTS
     new 8456369  with path signatures, truncation like this is not 
implementable

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 draft-schanzen-r5n.xml | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index edf46dc..1ba2aab 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
@@ -1750,11 +1761,6 @@ bchar = *(ALPHA / DIGIT)
              The result is used later.  Note that even if a key was computed, 
it
              does not have to match the <tt>QUERY_HASH</tt>.
            </li>
-            <li>
-              If the sender of the message is already found on the
-              <tt>GETPATH</tt>, the path <bcp14>MUST</bcp14> be truncated at 
this position.
-              The implementation <bcp14>MAY</bcp14> log a warning in such a 
case.
-            </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 

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