[lsd0003] branch master updated: Added links to messages

[gnunet]

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

elias-summermatter pushed a commit to branch master
in repository lsd0003.

The following commit(s) were added to refs/heads/master by this push:
     new b02ef2d  Added links to messages
b02ef2d is described below

commit b02ef2d2fc87716a30de05f3e072e79b50cba061
Author: Elias Summermatter <elias.summermatter@seccom.ch>
AuthorDate: Mon Dec 21 14:39:52 2020 +0100

    Added links to messages
---
 draft-summermatter-set-union.xml | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/draft-summermatter-set-union.xml b/draft-summermatter-set-union.xml
index 44e9959..3e0b018 100644
--- a/draft-summermatter-set-union.xml
+++ b/draft-summermatter-set-union.xml
@@ -395,11 +395,11 @@
                 ############# IMAGE ##################
             </t>
 
-            <t>
+            <t>.
                 The initiating peer is initially in the <strong>Initiating 
Connection</strong> state and the receiving peer in the <strong>Expecting 
Connection</strong>
-                state. The first step of the protocol for the initiating peer 
is to send an <em>Operation Request</em> to the receiving peer and
-                change into <strong>Expect SE</strong> state. After receiving 
the <em>Operation Request</em> the receiving peer changes in <strong>Expecting 
IBF"</strong> state and answers with the
-                Strata Estimator (<em>SE</em>) . After the initiating peer has 
received the Strata Estimator the initiating peer decides
+                state. The first step of the protocol for the initiating peer 
is to send an <em><xref target="messages_operation_request" format="title" 
/></em> to the receiving peer and
+                change into <strong>Expect SE</strong> state. After receiving 
the <em><xref target="messages_operation_request" format="title" /></em> the 
receiving peer changes in <strong>Expecting IBF"</strong> state and answers 
with the
+                Strata Estimator (<em><xref target="messages_se" 
format="title" /></em>) . After the initiating peer has received the Strata 
Estimator the initiating peer decides
                 with heuristics which operation mode is best fitted for the 
the estimated set difference and the environment.
                 The detailed tradeoff between the "Full Synchronisation Mode" 
and the "Individual Element Synchronisation Mode"
                 is explained in the section "Combined Mode".
@@ -409,8 +409,8 @@
 
                 <t>
                     In full synchronisation mode, if the set of the initiating 
peer is bigger than the set of the receiving peer, the initiating
-                    peer sends a <em>Request Full</em> message and change from 
<strong>Expecting SE</strong> to the <strong>Full Receiving</strong> State.
-                    In all other cases the initiating peer sends all set 
elements to the other peer followed by the <em>Full Done</em> message and
+                    peer sends a <em><xref target="messages_request_full" 
format="title" /></em> message and change from <strong>Expecting SE</strong> to 
the <strong>Full Receiving</strong> State.
+                    In all other cases the initiating peer sends all set 
elements to the other peer followed by the <em><xref 
target="messages_full_done" format="title" /></em> message and
                     changes into <strong>Full Sending</strong> state.
                 </t>
                 <t>
@@ -420,19 +420,19 @@
                 <dl>
                     <dt><strong>Expecting IBF:</strong></dt>
                     <dd>
-                        If a peer in the in state <strong>Expecting 
IBF</strong> receives a <em>Request Full</em> message from the other peer, the
-                        peer starts sending all the elements of the set 
followed by a <em>Full Done</em> message and change to the
-                        <strong>Full Sending</strong> State. If the peer 
receives an <em>Full Element</em> the peer changes to the state <strong>Full 
Receiving</strong>.
+                        If a peer in the in state <strong>Expecting 
IBF</strong> receives a <em><xref target="messages_request_full" format="title" 
/></em> message from the other peer, the
+                        peer starts sending all the elements of the set 
followed by a <em><xref target="messages_full_done" format="title" /></em> 
message and change to the
+                        <strong>Full Sending</strong> State. If the peer 
receives an <em><xref target="messages_full_element" format="title" /></em> the 
peer changes to the state <strong>Full Receiving</strong>.
                     </dd>
                     <dt><strong>Full Sending:</strong></dt>
                     <dd>
                         While a peer is in <strong>Full Sending</strong> state 
the peer expects to continuously receiving elements from the other
-                        peer. As soon as a the <em>Full Done</em> message is 
received the peer changes into <strong>Finished</strong> state.
+                        peer. As soon as a the <em><xref 
target="messages_full_done" format="title" /></em> message is received the peer 
changes into <strong>Finished</strong> state.
                     </dd>
                     <dt><strong>Full Receiving (In code: Expecting IBF): 
</strong></dt>
                     <dd>
                         While a peer is in <strong>Full Receiving</strong> 
state the peer expects to continuously receiving elements from the other
-                        peer. As soon as a the <em>Full Done</em> message is 
received the peer sends the remaining elements set to the other
+                        peer. As soon as a the <em><xref 
target="messages_full_done" format="title" /></em> message is received the peer 
sends the remaining elements set to the other
                         peer followed by a <em>Full Done</em>. After sending 
the last message the peer changes into <strong>Finished</strong> state.
                     </dd>
                 </dl>

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