bcp fix

1 files changed, 11 insertions, 3 deletions

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 3c75039..b1e3740 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1127,9 +1127,17 @@ BEGIN
           store entries for the last <tt>MAX_RECENT</tt> requests
           the peer has encountered.  To ensure that the peer does
           not run out of memory, information about older requests
-          is discarded.  The value of <tt>MAX_RECENT</tt> <bcp14>MAY</bcp14> be
-          configurable and <bcp14>SHOULD</bcp14> be at least 128 * 10<sup>3</sup>.
-        </t>
+    is discarded.
+    The value of <tt>MAX_RECENT</tt> <bcp14>MAY</bcp14> be configurable.
+    <tt>MAX_RECENT</tt> <bcp14>SHOULD</bcp14>
+    be at least 128 * 10<sup>3</sup>.
+    If the pending table is smaller, the likelihood grows that a peer
+    receives a response to a query but is unable to forward it to the
+    initiator because it forgot the predecessor.  Eventually, the
+    initiator would likely succeed by repeating the query.
+    However, this would be much more expensive than peers having an adequately
+    sized pending table.
+  </t>
         <t>
           For each entry in the pending table, the DHT
           <bcp14>MUST</bcp14> track the query key, the peer identity