lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 4c2d9e410a6719adb8531a715862885e52183c04
parent 2124404d5749bf30e89f7ebec7cec2355107b8cb
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon,  1 Aug 2022 09:27:16 +0200

fix

Diffstat:
Mdraft-schanzen-r5n.xml | 27++++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -1093,30 +1093,35 @@ BEGIN </dl> </section> <section anchor="p2p_pathelement"> + <!-- TODO-GROTHOFF: Discuss this change again. The text is currently not correct + it is very difficult to understand. Is it worth 32 byte --> <name>Path Element</name> <t> A Path Element represents a hop in the path a message has taken through the network. An ordered list of Path Elements may be appended to any routed <tt>PutMessage</tt>s or <tt>ResultMessage</tt>s. - A Path Element identifies a peer on the path. - The Path Element is signed by the next peer on the path after - the next peer made its routing decision. - This signature is also part of the Path Element along with the - Peer ID of the previous peer. + The signature of a Path Element is created by the current hop + after it made its routing decision identifiying the successor peer. </t> <t> - The public key of the peer which created the signature is in the - next path element, or is the sender of the message if this was the - last path element. + A path may be truncated in which case the signature of the truncated + Path Element is omitted leaving only the Peer ID required for the + verification of the subsequent Path Element signature. + Such a truncated path is indicated with the respective flag. + 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 Path Element is illustrated in <xref target="figure_pathelement"/>. </t> + <!-- TODO-GROTHOFF: We could swap the fields in order to facilitate easier processging + => Yes, swap. + --> <figure anchor="figure_pathelement" title="The Wire Format of a Path Element."> <artwork name="" type="" align="left" alt=""><![CDATA[ 0 8 16 24 32 40 48 56 +-----+-----+-----+-----+-----+-----+-----+-----+ -| PEER PREDECESSOR | +| PEER ID | | (32 byte) | | | | | @@ -1134,9 +1139,9 @@ BEGIN </figure> <t>where:</t> <dl> - <dt>PEER PREDECESSOR</dt> + <dt>PEER ID</dt> <dd> - is the Peer ID of the previous hop. + is the EdDSA public key of the peer on the path. </dd> <dt>SIGNATURE</dt> <dd>