[lsd0004] 02/05: add version field to flags -- removed again, truncated flags to 8 bit for consistency with later sections

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository lsd0004.

commit ef6f43fc8b1291e14ec6c4f08941eaae6cb1b42d
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Sat Aug 26 12:48:54 2023 +0200

    add version field to flags -- removed again, truncated flags to 8 bit for 
consistency with later sections
---
 draft-schanzen-r5n.xml | 12 ++----------
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 1a0dbe6..d0e809d 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -972,9 +972,9 @@ BEGIN
         <section anchor="route_flags">
           <name>Flags</name>
           <t>
-            Flags is a 16-bit vector representing binary options.
+            Flags is an 8-bit vector representing binary options.
             Each flag is represented by a bit in the field starting from 0 as
-            the rightmost bit to 15 as the leftmost bit.
+            the rightmost bit to 7 as the leftmost bit.
           </t>
          <dl>
           <dt>0: DemultiplexEverywhere</dt>
@@ -1009,14 +1009,6 @@ BEGIN
            If non-zero bits are received, implementations <bcp14>MUST</bcp14>
            preserve these bits when forwarding messages.
           </dd>
-          <dt>8-15: Version</dt>
-          <dd>
-            These bits are used to encode the R<sup>5</sup>N DHT protocol
-           version. They <bcp14>MUST</bcp14> be set to 0. Future revisions
-           of the protocol <bcp14>MAY</bcp14> change the message format.
-           It is envisioned that other cryptographic primitives 
<bcp14>MAY</bcp14>
-           be introduced into the network protocol in the future via this 
mechanism.
-          </dd>
         </dl>
       </section>
       <section anchor="p2p_pathelement">

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.