lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 71afec1862b82c3b93dce66da7127b15ff18a923
parent fce237fe18344e4ab1b2d2470b8be5a3e8b03940
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sat, 26 Aug 2023 12:47:17 +0200

English fix

Diffstat:
Mdraft-schanzen-r5n.xml | 5+++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -1069,7 +1069,8 @@ BEGIN is created by the current hop only after the peer made its routing decision identifiying the successor peer. The peer public key is not included after the last signature as it must be that of the sender of - the message. Similarly, the predecessor of the first element of + the message and including it would thus be redundant. + Similarly, the predecessor of the first element of an untruncated path is not stated explicitly, as it must be ZERO. </t> <t> @@ -1395,7 +1396,7 @@ BEGIN <t> <tt>PutMessage</tt>s are used to store information at other peers in the DHT. Any API which allows applications to initiate <tt>PutMessage</tt>s needs to - provide sufficient, implementation-specific information needed to construct + provide sufficient, implementation-specific information to construct the initial <tt>PutMessage</tt>. For example, implementations supporting multiple applications and blocks will have block type and message flag parameters in addition to the actual data