lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit ec09e09fec22ed70a920a7a0f96c85ca3d1cca7c
parent 143e86e92267f1324eeeeeaf0973831fa7e190ee
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Sun, 25 Dec 2022 18:30:57 +0900

Minor wording and terminology

Diffstat:
Mdraft-schanzen-r5n.xml | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -124,12 +124,12 @@ security aspects (path signatures).--> <t> This specification describes the protocol of R<sup>5</sup>N. - R<sup>5</sup>N stands for "randomized recursive routing for restricted-route + R<sup>5</sup>N is a Distributed Hash Table (DHT) is an acronym for + "randomized recursive routing for restricted-route networks" and its first academic description can be found in <xref target="R5N"/>. </t> <t> - R<sup>5</sup>N is a Distributed Hash Table (DHTs). DHTs are a key data structure for the construction of decentralized applications. and they generally provide a robust and efficient means to distribute the storage and retrieval of key-value pairs. @@ -199,8 +199,8 @@ </dd> <dt>Initiator</dt> <dd> - The peer that initially creates and sends a GetMessage (<xref target="p2p_get"/>) or - PutMessage message (<xref target="p2p_put"/>). + The peer that initially creates and sends a message (<xref target="p2p_hello"/>, + <xref target="p2p_put"/>, <xref target="p2p_get"/>, <xref target="p2p_result"/>). </dd> <dt>HELLO block</dt> <dd>