gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: reorder


From: gnunet
Subject: [lsd0001] branch master updated: reorder
Date: Mon, 17 Feb 2020 21:04:19 +0100

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 89214a0  reorder
89214a0 is described below

commit 89214a08261ae9d9c94b569e866bdfe78d7caa83
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Mon Feb 17 21:00:23 2020 +0100

    reorder
---
 draft-schanzen-gns.html | 27 +++++++++++++--------------
 draft-schanzen-gns.txt  | 10 +++++-----
 draft-schanzen-gns.xml  |  8 +++-----
 3 files changed, 21 insertions(+), 24 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index fa6fb07..2578bf5 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -2499,7 +2499,9 @@ table {
 <p id="section-7-17">
          The final revocation data object consists of a signature over the
          public of the zone which is revoked, the zone key itself and the just
-         calculated proof-of-work:<a href="#section-7-17" 
class="pilcrow">¶</a></p>
+         calculated proof-of-work.
+         The resulting block is then published and disseminated. The concrete
+         dissemination and publication methods are out of scope of this 
document.<a href="#section-7-17" class="pilcrow">¶</a></p>
 <div id="figure_revocationdata">
 <figure id="figure-20">
         <div class="artwork art-text alignLeft" id="section-7-18.1">
@@ -2549,15 +2551,12 @@ table {
 </dd>
 </dl>
 <p id="section-7-21">
-         The resulting block may now be published and disseminated. The 
concrete
-         dissemination and publication methods are out of scope of this 
document.<a href="#section-7-21" class="pilcrow">¶</a></p>
-<p id="section-7-22">
          The signature over the public key covers a 32 bit pseuso header
          conceptually prefixed to the public key. The pseudo header includes
-         the key length and signature purpose:<a href="#section-7-22" 
class="pilcrow">¶</a></p>
+         the key length and signature purpose:<a href="#section-7-21" 
class="pilcrow">¶</a></p>
 <div id="figure_pkeywithpseudo">
 <figure id="figure-21">
-        <div class="artwork art-text alignLeft" id="section-7-23.1">
+        <div class="artwork art-text alignLeft" id="section-7-22.1">
 <pre>
            0     8     16    24    32    40    48    56
            +-----+-----+-----+-----+-----+-----+-----+-----+
@@ -2572,17 +2571,17 @@ table {
 </div>
 <figcaption><a href="#figure-21" class="selfRef">Figure 
21</a></figcaption></figure>
 </div>
-<p id="section-7-24">where:<a href="#section-7-24" class="pilcrow">¶</a></p>
-<dl class="dlParallel" id="section-7-25">
-        <dt id="section-7-25.1">SIZE</dt>
-<dd id="section-7-25.2">
+<p id="section-7-23">where:<a href="#section-7-23" class="pilcrow">¶</a></p>
+<dl class="dlParallel" id="section-7-24">
+        <dt id="section-7-24.1">SIZE</dt>
+<dd id="section-7-24.2">
            A 32-bit value containing the length of the signed data in bytes
-           (36 bytes) in network byte order.<a href="#section-7-25.2" 
class="pilcrow">¶</a>
+           (36 bytes) in network byte order.<a href="#section-7-24.2" 
class="pilcrow">¶</a>
 </dd>
-<dt id="section-7-25.3">PURPOSE</dt>
-<dd id="section-7-25.4">
+<dt id="section-7-24.3">PURPOSE</dt>
+<dd id="section-7-24.4">
            A 32-bit signature purpose flag. This field MUST be 3 (in network
-           byte order).<a href="#section-7-25.4" class="pilcrow">¶</a>
+           byte order).<a href="#section-7-24.4" class="pilcrow">¶</a>
 </dd>
 </dl>
 </section>
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index dc3dbf3..3d48dc7 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -1180,7 +1180,9 @@ Internet-Draft             The GNU Name System            
 November 2019
 
    The final revocation data object consists of a signature over the
    public of the zone which is revoked, the zone key itself and the just
-   calculated proof-of-work:
+   calculated proof-of-work.  The resulting block is then published and
+   disseminated.  The concrete dissemination and publication methods are
+   out of scope of this document.
 
               0     8     16    24    32    40    48    56
               +-----+-----+-----+-----+-----+-----+-----+-----+
@@ -1216,10 +1218,6 @@ Internet-Draft             The GNU Name System           
  November 2019
 
    POW  The value of the proof of work.
 
-   The resulting block may now be published and disseminated.  The
-   concrete dissemination and publication methods are out of scope of
-   this document.
-
    The signature over the public key covers a 32 bit pseuso header
    conceptually prefixed to the public key.  The pseudo header includes
    the key length and signature purpose:
@@ -1229,6 +1227,8 @@ Internet-Draft             The GNU Name System            
 November 2019
 
 
 
+
+
 Schanzenbach, et al.       Expires 13 May 2020                 [Page 22]
 
 Internet-Draft             The GNU Name System             November 2019
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 1a92248..19f4d4b 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -1240,7 +1240,9 @@
        <t>
          The final revocation data object consists of a signature over the
          public of the zone which is revoked, the zone key itself and the just
-         calculated proof-of-work:
+         calculated proof-of-work.
+         The resulting block is then published and disseminated. The concrete
+         dissemination and publication methods are out of scope of this 
document.
        </t>
        <figure anchor="figure_revocationdata">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -1286,10 +1288,6 @@
            The value of the proof of work.
          </dd>
        </dl>
-       <t>
-         The resulting block may now be published and disseminated. The 
concrete
-         dissemination and publication methods are out of scope of this 
document.
-       </t>
        <t>
          The signature over the public key covers a 32 bit pseuso header
          conceptually prefixed to the public key. The pseudo header includes

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]