gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0004] branch master updated: clarification try_connect on HELLO bloc


From: gnunet
Subject: [lsd0004] branch master updated: clarification try_connect on HELLO block result message
Date: Sun, 25 Dec 2022 12:39:33 +0100

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0004.

The following commit(s) were added to refs/heads/master by this push:
     new 2572074  clarification try_connect on HELLO block result message
2572074 is described below

commit 2572074e9b4f875e79a8fe070afc375e02e272bb
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sun Dec 25 20:39:12 2022 +0900

    clarification try_connect on HELLO block result message
---
 draft-schanzen-r5n.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 63013ab..037adc5 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1527,8 +1527,9 @@ BEGIN
              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.
+              from the HELLO block and the Underlay function 
<tt>TRY_CONNECT</tt>.
+              If a connection is established, the signal 
<tt>PEER_CONNECTED</tt> will cause
+              the peer to be 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>

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]