[lsd0004] branch master updated: more explanations

[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 484c367  more explanations
484c367 is described below

commit 484c36781226ea9a7162a596825844e491ac0e29
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Mon Aug 1 11:03:30 2022 +0200

    more explanations
---
 draft-schanzen-r5n.xml | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index a5b5e26..14665c7 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1139,10 +1139,15 @@ 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 to D is
-          illustrated in <xref target="figure_path_ex"/>.
+          The wire format of an example path from Peers A over B and C as it
+          would be received by D in a is illustrated in <xref 
target="figure_path_ex"/>.
+          <tt>PutMessage</tt> or <tt>ResultMessage</tt>.
+          A <tt>ResultMessage</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.
         </t>
-        <figure anchor="figure_path_ex" title="Example of a path with a path 
length of 3. As illustrated, the Peer ID of the last hop is omitted.">
+        <figure anchor="figure_path_ex" title="Example of a path from Peer A 
to Peer D.">
           <artwork name="" type="" align="left" alt=""><![CDATA[
 0     8     16    24    32    40    48    56
 +-----+-----+-----+-----+-----+-----+-----+-----+
@@ -1208,9 +1213,16 @@ BEGIN
           The Peer ID of the last Path Element is omitted as it must be that of
           the sender of the PutMesssage or ResultMessage.
           The wire format of a truncated example path from Peers B over C to D
-          is illustrated in <xref target="figure_path_ex_trunc"/>.
+            is illustrated in <xref target="figure_path_ex_trunc"/>.
+          The wire format of an example path from Peers B over C as it
+          would be received by D in a is illustrated in <xref 
target="figure_path_ex_trunc"/>.
+          <tt>PutMessage</tt> or <tt>ResultMessage</tt>.
+          A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> 
field
+          a length of 1.
+          A <tt>PutMessage</tt> would indicate a length of 1 as the sum of
+          <tt>PUTPATH_L</tt> and <tt>GETPATH_L</tt> fields.
         </t>
-        <figure anchor="figure_path_ex_trunc" title="Example of a truncated 
path with a path length of 1. As illustrated, the Peer ID of the last hop is 
omitted.">
+        <figure anchor="figure_path_ex_trunc" title="Example of a truncated 
path from Peer B to Peer 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.