lsd0004

commit 22d83eb662bb27cca0bbd714ccfdd4d8d3f9ba76
parent c7b29b045da9568cc13c3740c512d31d6ff70fde
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 13 Jul 2024 13:27:30 +0200

finish sec 7

Diffstat:
M
draft-schanzen-r5n.xml
 | 
34
+++++++++++++++++-----------------

1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -2137,7 +2137,7 @@ BEGIN
               requests, and peers thus <bcp14>MUST</bcp14> discard the
               oldest existing request if memory constraints on the
               pending table are encountered. Note that peers
-              <bcp14>MAY</bcp14> clean up state for queries that had
+              <bcp14>MUST</bcp14> clean up state for queries that had
               response with a status of <tt>FILTER_LAST</tt> even if
               they are not the oldest query in the pending table.
             </li>
@@ -2398,8 +2398,8 @@ BEGIN
               aware of multiple addresses for this connection.  When a
               connection is established, the signal
               <tt>PEER_CONNECTED</tt> will cause the peer to be added
-              to the respective k-bucket of the routing table (<xref
-              target="routing"/>).
+              to the respective k-bucket of the routing table (see
+              <xref target="routing"/>).
             </li>
             <li>
               If the <tt>QUERY_HASH</tt> of this
@@ -2413,12 +2413,12 @@ BEGIN
 	      <ol type="%c)">
 		<li>
 		  If the <tt>FindApproximate</tt> flag was not set in
-		  the query and the <tt>BTYPE</tt> allowed the
+		  the query and the <tt>BTYPE</tt> enabled the
 		  implementation to compute the key from the block,
 		  the computed key must exactly match the
 		  <tt>QUERY_HASH</tt>, otherwise the result does not
 		  match the pending query and processing continues
-		  with the next pending query.
+		  with the next pending table entry.
                 </li>
 		<li>
                   If the <tt>BTYPE</tt> is supported, result block
@@ -2439,16 +2439,16 @@ BEGIN
 		  <tt>FILTER_DUPLICATE</tt>.
                 </li>
 		<li>
-		  If the <tt>RecordRoute</tt> flag is set in FLAGS,
-		  the local peer identity <bcp14>MUST</bcp14> be
-		  appended to the <tt>GETPATH</tt> of the message and
-		  the respective signature <bcp14>MUST</bcp14> be set
-		  using the query origin as the <tt>PEER
-		  SUCCESSOR</tt> and the response origin as the
-		  <tt>PEER PREDECESSOR</tt>.  If the flag is not set,
-		  the <tt>GETPATH_L</tt> and <tt>PUTPATH_L</tt>
-		  <bcp14>MUST</bcp14> be set to zero when forwarding
-		  the result.
+		  If the <tt>RecordRoute</tt> flag is set in
+		  <tt>FLAGS</tt>, the local peer identity
+		  <bcp14>MUST</bcp14> be appended to the
+		  <tt>GETPATH</tt> of the message and the respective
+		  signature <bcp14>MUST</bcp14> be set using the query
+		  origin as the <tt>PEER SUCCESSOR</tt> and the
+		  response origin as the <tt>PEER PREDECESSOR</tt>.
+		  If the flag is not set, the <tt>GETPATH_L</tt> and
+		  <tt>PUTPATH_L</tt> <bcp14>MUST</bcp14> be set to
+		  zero when forwarding the result.
                 </li>
                 <li>
 		  If the result filter result is either
@@ -2461,8 +2461,8 @@ BEGIN
 		  the result is forwarded using <tt>SEND(P,
 		  ResultMessage')</tt> where <tt>ResultMessage'</tt>
 		  is the now modified message.  If the result was
-		  <tt>FILTER_LAST</tt>, the query is removed from the
-		  pending table.
+		  <tt>FILTER_LAST</tt>, the query <bcp14>MUST</bcp14>
+		  be removed from the pending table.
 	        </li>
               </ol>
             </li>