[GNUnet-SVN] [lsd0001] branch master updated: fix padding

[gnunet]

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new bf2ead7  fix padding
     new fd37205  Merge branch 'master' of ssh://gnunet.org/lsd0001
bf2ead7 is described below

commit bf2ead7076a2cb86fede4c75a782ed589fc81dd8
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Oct 4 11:20:53 2019 +0200

    fix padding
---
 draft-schanzen-gns.xml | 30 ++++++++++++++----------------
 1 file changed, 14 insertions(+), 16 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 3330f54..33972e1 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -112,11 +112,7 @@
      |           FLAGS       |        DATA           /
      +-----+-----+-----+-----+                       /
      /                                               /
-     /                       +-----+-----+-----+-----+
-     /                       |      PADDING          /
-     +-----+-----+-----+-----+                       /
-     |                                               |
-     +-----+-----+-----+-----+-----+-----+-----+-----+
+     /                                               /
      ]]></artwork>
     <!--        <postamble>which is a very simple example.</postamble>-->
    </figure>
@@ -130,10 +126,7 @@
     </dd>
     <dt>DATA SIZE</dt>
     <dd>
-      The size of the DATA field in bytes and in network byte order including
-      padding. The padding MUST ensure that the size of the resource record
-      is a power of two. The only excption is the PKEY record type, which is
-      never padded.
+      The size of the DATA field in bytes and in network byte order.
     </dd>
     <dt>TYPE</dt>
     <dd>
@@ -153,11 +146,6 @@
      The resource record data payload. The contents are defined by the
      respective type of the resource record.
    </dd>
-   <dt>PADDING</dt>
-   <dd>
-     The padding MUST contain the 0 value in all octets. Not applicable for
-     PKEY records.
-   </dd>
  </dl>
  <t>
    Flags indicate metadata surrounding the resource record. A flag
@@ -586,8 +574,10 @@
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |           FLAGS       |        DATA           /
           +-----+-----+-----+-----+                       /
-          /                                               /
-          /                                               /
+          /                       +-----------------------/
+          /                       |                       /
+          +-----------------------+                       /
+          /                     PADDING                   /
           /                                               /
           ]]></artwork>
         <!--        <postamble>which is a very simple example.</postamble>-->
@@ -599,6 +589,14 @@
           A 32-bit value containing the number of resource records which are
           following in network byte order.
         </dd>
+        <dt>PADDING</dt>
+        <dd>
+          The padding MUST contain the 0 value in all octets. Not applicable 
for
+          PKEY records.
+          The padding MUST ensure that the size of the RDATA is a power of two.
+          The only excption is the PKEY record type, which is never padded.
+        </dd>
+
       </dl>
       <t>
         is followed by a set of resource records with the respective

-- 
To stop receiving notification emails like this one, please contact
address@hidden.