[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0004] branch master updated: add options

From: gnunet
Subject: [lsd0004] branch master updated: add options
Date: Tue, 30 Nov 2021 17:01:44 +0100

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 f3a4fac  add options
f3a4fac is described below

commit f3a4facc5c516c306420e191e7eb023390782f47
Author: Martin Schanzenbach <>
AuthorDate: Tue Nov 30 17:01:40 2021 +0100

    add options
 draft-schanzen-r5n.xml | 37 +++++++++++++++++++++++++++++++++++--
 1 file changed, 35 insertions(+), 2 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index ff30ca9..5388123 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -403,21 +403,54 @@ END
           In order to prevent circular routes, GET and PUT messages contain
-          a 128-bit Bloom filter. The Bloom filter is used to detect duplicate
+          a 128-bit Bloom filter (m=128). The Bloom filter is used to detect 
           peer IDs along the route.
           A Bloom filter "bf" is initially empty, consisting only of zeroes.
           There are two functions which can be invoked on the Bloom filter:
           ADD(bf, e) and TEST(bf, e) where "e" is an element which is to added
           to the Bloom filter or queried against the set.
-          Any bloom filter uses k different hash functions each of which is
+          Any bloom filter uses k=16 different hash functions each of which is
           defined as follows:
       <section anchor="p2p_opts" numbered="true" toc="default">
         <name>Processing options</name>
+        <t>
+          In order to indicate certain processing requirements for messages
+          a number of processing options may be specificied in the respective
+          field of the signalling messages.
+          The options field is 8 octets in length and each options is encoded
+          in a single bit.
+        </t>
+       <dl>
+         <dt>Demultiplex everywhere</dt>
+         <dd>
+           Each peer along the way should look at 'enc'. Otherwise
+           only the k-peers closest to the key should look at it.
+         </dd>
+         <dt>Record route</dt>
+         <dd>
+           Indicates to keep track of the route that the message
+           took in the P2P network.
+         </dd>
+         <dt>Find peer</dt>
+         <dd>
+           Indicates a 'FIND-PEER' request. Implies that approximate results 
+           acceptable.
+         </dd>
+         <dt>Random key</dt>
+         <dd>
+           Option for query key randomization. (TODO)
+         </dd>
+         <dt>Random key</dt>
+         <dd>
+           Indicates if this was the last hop for a GET/PUT.
+         </dd>
+       </dl>
       <section anchor="p2p_xq" numbered="true" toc="default">
         <name>Extended query</name>
+        <t>TODO: What is this for? Not documented anywhere</t>
      <section anchor="p2p_put" numbered="true" toc="default">
        <name>PUT message</name>

To stop receiving notification emails like this one, please contact

reply via email to

[Prev in Thread] Current Thread [Next in Thread]