commit 46c4ebbc21be1952bb23ee3a9203d8eaa228f80a
parent 3b0ef33a5911b6f188c6085c310fa437733d0aa2
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Thu, 17 Feb 2022 17:44:23 +0100
fixed
Diffstat:
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -583,7 +583,8 @@ Connectivity | |Underlay| |Underlay|
</t>
<t>
In order to find more close peers in the network, an
- implementation MUST now periodically <xref target="find_peer"/> messages.
+ implementation MUST now periodically send find peer messages
+ <xref target="find_peer"/>.
</t>
<t>
In both cases the frequency of advertisements and peer discovery
@@ -593,7 +594,7 @@ Connectivity | |Underlay| |Underlay|
</t>
<t>
Any implementation encountering a HELLO GET request initially
- sends its own peer address if it.
+ sends its own peer address.
</t>
</section>
<section anchor="routing" numbered="true" toc="default">
@@ -1324,10 +1325,10 @@ Connectivity | |Underlay| |Underlay|
list of pending local queries, the <tt>QUERY_HASH</tt> and <tt>XQUERY</tt>
are validated against the requested BTYPE using the respective
block type implementation of <tt>ValidateBlockReply</tt>.
- If the BTYPE is not supported, or if the block key
- does not match the BTYPE or if the XQUERY is malformed,
- the message MUST be discarded.
- <!-- FIXME: "Does not match would mean equals. Is that correct?
+ If the approximate flag is set and the BTYPE allows the
+ implementation to compute the key from the block it must match
+ the QUERY_HASH. If the XQUERY is malformed, the message MUST be discarded.
+ <!-- FIXME: This should be reviewed.
<= approximate flag -->
</li>
<li>
