lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 9c408ef1532e82763c012e0d513096fdd9409264
parent 75f21360b27f8707ffc49c4a32f10948d2f2778f
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Wed, 12 Jan 2022 21:56:40 +0100

minor

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

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -489,7 +489,7 @@ Connectivity | |Underlay| |Underlay| peer <tt>P</tt>. FIXME what is this needed for? </dd> <dt> - <tt>RECEIVE(P, M)</tt> + <tt>M = RECEIVE(P)</tt> </dt> <dd> A function or event that allows the local node to receive a protocol @@ -504,7 +504,7 @@ Connectivity | |Underlay| |Underlay| If call to SEND fails, the message has not been sent. </dd> <dt> - <tt>ESTIMATE_NETWORK_SIZE() -> S</tt> + <tt>S = ESTIMATE_NETWORK_SIZE()</tt> </dt> <dd> A procedure that provides estimates on the network size @@ -513,9 +513,9 @@ Connectivity | |Underlay| |Underlay| </dd> </dl> <t> - In addition to the above procedures, which can only be actively - triggered by the implementation, the following callbacks or signals - drive updates of the routing table: + In addition to the above procedures, which are meant to be actively + executed by the implementation as part of the peer-to-peer protocol, + the following callbacks or signals drive updates of the routing table: </t> <dl> <dt>