HelloMessage processing the connection establishment clarification.

1 files changed, 9 insertions, 12 deletions

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 2e1bf76..0024d8e 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1307,7 +1307,11 @@ BEGIN
         <section anchor="p2p_hello_processing">
           <name>Processing</name>
           <t>
-            Upon receiving a <tt>HelloMessage</tt> from a peer <tt>P</tt>
+            If the initiator of a <tt>HelloMessage</tt> is <tt>SELF</tt>, the message
+            is simply sent to all neighbors <tt>P</tt> currently in the routing table
+            using <tt>SEND</tt>.
+          <t>
+            Otherwise, upon receiving a <tt>HelloMessage</tt> from a peer <tt>P</tt>
             an implementation <bcp14>MUST</bcp14> process it step by step as follows:
           </t>
           <ol>
@@ -1325,21 +1329,14 @@ BEGIN
               <!-- FIXME same problem as for <tt>HELLO</tt> blocks: We do not need to TRY_CONNECT here because we already have
                    a connection, obviously. But we may want to TRY_CONNECT on the new addresses? Adding for now -->
               The implementation <bcp14>MAY</bcp14> instruct the Underlay to connect to all now available addresses
-              using <tt>TRY_CONNECT</tt> in order to make the underlay aware of alternative addresses for this connection.
+              using <tt>TRY_CONNECT</tt> in order to make the underlay aware of alternative addresses for this connection and
+              to maintain optimal connectivity.
             </li>
             <li>
-              <!-- We need a statement like this here. Should they? Can they? What if they are (not)? -->
-              <tt>HelloMessages</tt> <bcp14>SHOULD NOT</bcp14> be forwarded.
+              <!-- FIXME: We need a statement like this here. Should they? Can they? What if they are (not)? -->
+              Received <tt>HelloMessages</tt> <bcp14>MUST NOT</bcp14> be forwarded.
             </li>
           </ol>
-          <t>
-            <!-- FIXME: How? What function of the underlay? The underlay also already knows so...
-                 what is the point? -->
-            The address information about P should then also be made
-            available to each respective Underlays to enable the
-            Underlay to maintain optimal connectivity to the
-            neighbor.
-          </t>
         </section>
       </section>
       <section anchor="p2p_put" numbered="true" toc="default">