[lsd0004] branch master updated: more GANA

[gnunet]

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

grothoff pushed a commit to branch master
in repository lsd0004.

The following commit(s) were added to refs/heads/master by this push:
     new d561f40  more GANA
d561f40 is described below

commit d561f4071670e44eeeba191d84d2555c7d9970e6
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Fri Mar 11 06:43:57 2022 +0100

    more GANA
---
 draft-schanzen-r5n.xml | 35 ++++++++++++++++++++++++++++++++++-
 1 file changed, 34 insertions(+), 1 deletion(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 6b64440..0be12c6 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1105,6 +1105,20 @@ bchar = *(ALPHA / DIGIT)
       </section>
       <section anchor="p2p_hello" numbered="true" toc="default">
         <name>HelloMessage</name>
+       <t>
+         <tt>HelloMessage</tt>s are used to inform neighbours of 
+         a peer about the sender's available addresses. The
+         recipients use these messages to inform their respective
+         Underlays about ways to sustain the connections and to
+         generate HELLO blocks to answer peer discovery queries
+         from other peers. In contrast to HELLO blocks, a
+         <tt>HelloMessage</tt> does not contain the peer ID of
+         the peer the address information is about, as a
+         <tt>HelloMessage</tt> is always about the sender. As
+         the Underlay is responsible to determine the
+         peer ID of the sender for all messages, it would be
+         redundant to also include it in the <tt>HelloMessage</tt>.
+        </t>
         <section anchor="p2p_hello_wire">
           <name>Wire Format</name>
           <figure anchor="figure_hellomsg" title="The HelloMessage Wire 
Format.">
@@ -1149,7 +1163,7 @@ bchar = *(ALPHA / DIGIT)
               is a 64 byte EdDSA signature using the sender's private
               key affirming the information contained in the message.
               The signature is signing exactly the same data that is being
-              signed in a HELLO block as described in section XXX.
+              signed in a HELLO block as described in <xref 
target="hello_block"/>.
             </dd>
             <dt>EXPIRATION</dt>
             <dd>
@@ -2153,6 +2167,25 @@ ADDRESS          N/A       N/A          Network address.
         <artwork name="" type="" align="left" alt=""><![CDATA[
 Purpose | Name            | References | Description
 --------+-----------------+------------+---------------
+6         DHT PATH Element  [This.I-D]   DHT message routing data
+40        HELLO Payload     [This.I-D]   Peer contact information
+
+]]></artwork>
+      </figure>
+
+      <t>
+        GANA is requested to amend the "GNUnet Message Type" registry
+        as follows:
+      </t>
+      <figure anchor="figure_messagetypeenums" title="The Message Type 
Registry Entries.">
+        <artwork name="" type="" align="left" alt=""><![CDATA[
+Type    | Name            | References | Description
+--------+-----------------+------------+---------------
+146       DHT PUT          [This.I-D]    Store information in DHT
+147       DHT GET          [This.I-D]    Request information from DHT
+148       DHT RESULT       [This.I-D]    Return information from DHT
+157       HELLO Message    [This.I-D]    Peer contact information
+
 ]]></artwork>
       </figure>
     </section>

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