lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 2a76b576c567f1b6cdf83feea154132142772e9e
parent 78ffb3e52411761126e36de6116eaac95fef2ecd
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sun, 20 Aug 2023 17:47:25 +0200

improve English

Diffstat:
Mdraft-schanzen-r5n.xml | 13+++++++------
1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -990,8 +990,8 @@ BEGIN This bit indicates that each peer along the way should process the request. If the bit is not set, intermediate peers only route the message and only peers which consider themselves closest to the key look for answers - in their local storage for <tt>GetMessage</tt>s and cache the - block in their local storage for <tt>PutMessage</tt>s and <tt>ResultMessage</tt>s. + in their local storage for <tt>GetMessage</tt>s, or respectively cache the + block in their local storage for <tt>PutMessage</tt>s and <tt>ResultMessage</tt>s. </dd> <dt>1: RecordRoute</dt> <dd> @@ -1000,13 +1000,14 @@ BEGIN </dd> <dt>2: FindApproximate</dt> <dd> - This bit allows results where the key does not match exactly. + This bit asks peers to return results even if the <em>key</em> + does not exactly match the query hash. </dd> <dt>3: Truncated</dt> <dd> This is a special flag which is set if a peer truncated the path and thus the first hop on the path is given without a signature - to enable checking of the next signature. MUST never be set in + to enable checking of the next signature. This flag MUST never be set in a query. </dd> <dt>4-15: Reserved</dt> @@ -1033,7 +1034,7 @@ BEGIN 0 8 16 24 32 40 48 56 +-----+-----+-----+-----+-----+-----+-----+-----+ | SIGNATURE | -| (64 byte) | +| (64 bytes) | | | | | | | @@ -1042,7 +1043,7 @@ BEGIN | | +-----+-----+-----+-----+-----+-----+-----+-----+ | PEER ID | -| (32 byte) | +| (32 bytes) | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+