[lsd0004] branch master updated: fix path len names

[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 073a6c3  fix path len names
073a6c3 is described below

commit 073a6c3c3125a4b017c00b62f1485a9119dd7795
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Wed Aug 3 09:45:42 2022 +0200

    fix path len names
---
 draft-schanzen-r5n.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 6ddf81e..d1169c6 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1899,14 +1899,14 @@ BEGIN
               is a 32-bit block type field. The block type indicates the 
content
               type of the payload. In network byte order.
             </dd>
-            <dt>PUTPATH_LEN</dt>
+            <dt>PUTPATH_L</dt>
             <dd>
               is a 16-bit number indicating the length of the PUT path recorded
               in <tt>PUTPATH</tt>. As <tt>PUTPATH</tt> is optional, this value 
may be zero
              even if the message has traversed several peers.
               In network byte order.
             </dd>
-            <dt>GET_PATH_LEN</dt>
+            <dt>GETPATH_L</dt>
             <dd>
               is a 16-bit number indicating the length of the GET path recorded
               in <tt>GETPATH</tt>. As <tt>GETPATH</tt> is optional, this value 
may be zero
@@ -1940,12 +1940,12 @@ BEGIN
             <dt>PUTPATH</dt>
             <dd>
               the variable-length PUT path.
-              The path consists of a list of <tt>PUT_PATH_LEN</tt> Path 
Elements.
+              The path consists of a list of <tt>PUTPATH_L</tt> Path Elements.
             </dd>
             <dt>GETPATH</dt>
             <dd>
               the variable-length PUT path.
-              The path consists of a list of <tt>GET_PATH_LEN</tt> Path 
Elements.
+              The path consists of a list of <tt>GETPATH_L</tt> Path Elements.
             </dd>
             <dt>LAST HOP SIGNATURE</dt>
             <dd>
@@ -1985,7 +1985,7 @@ BEGIN
              discarded.
             </li>
             <li>
-              If the <tt>PUT_PATH_LEN</tt> or the <tt>GET_PATH_LEN</tt> are 
non-zero,
+              If the <tt>PUTPATH_L</tt> or the <tt>GETPATH_L</tt> are non-zero,
               the local peer <bcp14>SHOULD</bcp14> verify the signatures from 
the <tt>PUTPATH</tt>
              and the <tt>GETPATH</tt>.
              Verification <bcp14>MAY</bcp14> involve checking all signatures 
or any random
@@ -1994,7 +1994,7 @@ BEGIN
              verification a bottleneck.  If an invalid signature is found, the
              path <bcp14>MUST</bcp14> be truncated to only include the elements
              following the invalid signature.  In particular, any invalid 
signature
-             on the <tt>GETPATH</tt> will cause <tt>PUT_PATH_LEN</tt> to be 
set to 0.
+             on the <tt>GETPATH</tt> will cause <tt>PUTPATH_L</tt> to be set 
to 0.
             </li>
            <li>
              The peer also attempts to compute the
@@ -2049,7 +2049,7 @@ BEGIN
                   of the message and the respective signature 
<bcp14>MUST</bcp14> be
                   set using the query origin as the <tt>PEER SUCCESSOR</tt> 
and the
                  response origin as the <tt>PEER PREDECESSOR</tt>.  If the 
flag is not set,
-                  the <tt>GET_PATH_LEN</tt> and <tt>PUT_PATH_LEN</tt>
+                  the <tt>GETPATH_L</tt> and <tt>PUTPATH_L</tt>
                  <bcp14>MUST</bcp14> be set to zero when forwarding the result.
                 </li>
               </ol>

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