lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 174c87977bfc0940208b872160519d4698d47511
parent a4d1d012678e339cc7b5d29386ea20aa3790444b
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Sun, 14 Jul 2024 09:44:41 +0200

no bcp in underlay

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

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -582,7 +582,7 @@ Connectivity | |Underlay| |Underlay| | Underlay | ... <section anchor="underlay" numbered="true" toc="default"> <name>Underlay</name> <t> - A peer <bcp14>MUST</bcp14> implement one or more underlay + A peer <bcp14>MUST</bcp14> support one or more underlay protocols. Peers supporting multiple underlays effectively create a bridge between different networks. How peers are @@ -595,7 +595,7 @@ Connectivity | |Underlay| |Underlay| | Underlay | ... <em>peers</em> in the DHT overlay. This standardized format is the <em>HELLO Block</em> (described in <xref target="hello_block"/>), which contains sets of addresses. If - the address is a URI, it <bcp14>MAY</bcp14> indicate which + the address is a URI, it may indicate which underlay understands the respective <em>address</em>. </t> <!-- @@ -690,8 +690,8 @@ Connectivity | |Underlay| |Underlay| | Underlay | ... <tt>M</tt> to a peer <tt>P</tt>. Sending messages is expected to be done on a best-effort basis, thus the underlay does not have to guarantee delivery or message ordering. If the underlay - implements flow- or congestion-control, it <bcp14>MAY</bcp14> - also discard messages to limit its queue size. + implements flow- or congestion-control, it may + discard messages to limit its queue size. </dd> <dt> <tt>ESTIMATE_NETWORK_SIZE() -> L2NSE</tt> @@ -746,7 +746,7 @@ Connectivity | |Underlay| |Underlay| | Underlay | ... was added for our local peer and that henceforth the peer may be reachable under this address. This information is used to advertise connectivity information about the local - peer to other peers. <tt>A</tt> <bcp14>MUST</bcp14> be an + peer to other peers. <tt>A</tt> is an address suitable for inclusion in a <tt>HELLO</tt> payload <xref target="hello_block"/>. </dd> @@ -756,8 +756,7 @@ Connectivity | |Underlay| |Underlay| | Underlay | ... <dd> This underlay signal indicates that an address <tt>A</tt> was removed from the set of addresses the local peer is - possibly reachable under. Addresses <bcp14>MUST</bcp14> have - been added before they may be deleted. The signal is used + possibly reachable under. The signal is used to stop advertising this address to other peers. </dd> <dt>