[lsd0004] branch master updated: attempt to improve wording on path example

[gnunet]

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 c906a74  attempt to improve wording on path example
c906a74 is described below

commit c906a74c36388a58adce1d7784cac52d6331d940
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Tue Oct 25 22:43:22 2022 +0900

    attempt to improve wording on path example
---
 draft-schanzen-r5n.xml | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index ac74024..2cebd26 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1139,15 +1139,21 @@ BEGIN
           <tt>PutMessage</tt>s or <tt>ResultMessage</tt>s.
           The signature of a Path Element is created by the current hop
           after it made its routing decision identifiying the successor peer.
-          The wire format of an example path from Peers A over B and C as it
-           would be received by D in a <tt>PutMessage</tt> or 
<tt>ResultMessage</tt>
-          is illustrated in <xref target="figure_path_ex"/>.
-          A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> 
field
+        </t>
+        <t>
+          <xref target="figure_path_ex"/> shows the wire format of an example
+          path from Peers A over B and C as it would be received by D in the
+          <tt>PUTPATH</tt> of a <tt>PutMessage</tt> or the combined
+          <tt>PUTPATH</tt> and <tt>GETPATH</tt> of a <tt>ResultMessage</tt>.
+          The wire format of the Path Elements allows a natural
+          extension of the <tt>PUTPATH</tt> along the route of the 
<tt>ResultMessage</tt>
+          to the destination forming the <tt>GETPATH</tt>.
+          The <tt>PutMessage</tt> would indicate in the <tt>PATH_LEN</tt> field
           a length of 3.
-          A <tt>PutMessage</tt> would indicate a length of 3 as the sum of
-          <tt>PUTPATH_L</tt> and <tt>GETPATH_L</tt> fields.
+          The <tt>ResultMessage</tt> would indicate a path length of 3 as the
+          sum of the field values in <tt>PUTPATH_L</tt> and <tt>GETPATH_L</tt>.
         </t>
-        <figure anchor="figure_path_ex" title="Example of a path from Peer A 
to Peer D.">
+        <figure anchor="figure_path_ex" title="Example of a path as found in 
PutMessages or ResultMessages from A to D.">
           <artwork name="" type="" align="left" alt=""><![CDATA[
 0     8     16    24    32    40    48    56
 +-----+-----+-----+-----+-----+-----+-----+-----+

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