lsd0004

commit 5dd60db32fc63ba93fc8c5a76b363ada836a4308
parent 013ed2add08b85ce1949b42fa5f160342c4740aa
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Wed, 26 Oct 2022 15:00:18 +0900

handle ANY better

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

1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
@@ -1580,6 +1580,7 @@ BEGIN
               If the <tt>BTYPE</tt> is not supported by the implementation,
               no validation of the block payload is performed and processing
               continues at (5).
+              If the <tt>BTYPE</tt> is <tt>ANY</tt>, then the message <bcp14>MUST</bcp14> be discarded.
               Else, the block <bcp14>MUST</bcp14> be validated as defined in (3) and (4).
             </li>
             <li>
@@ -1794,7 +1795,8 @@ BEGIN
                 <!-- FIXME: It is not clear that this is a fallthrough statement -->
                 <!-- FIXME: Are HELLO blocks according to the spec stored in block storage but never looked for? -->
                 <li>
-                  If <tt>BTYPE</tt> indicates a request for a HELLO block,
+                  If <tt>BTYPE</tt> indicates a request for a HELLO block or
+                  <tt>ANY</tt>,
                   the peer <bcp14>MUST</bcp14> consult the HELLOs it has cached for the
                   peers in its routing table instead of the local block
                   storage (while continuing to respect flags like