[lsd0001] branch master updated: -figure

[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 e064f8d  -figure
e064f8d is described below

commit e064f8d1eeb3da1375ba804213a0e5a9669e07ab
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Tue Dec 7 12:29:31 2021 +0100

    -figure
---
 draft-schanzen-gns.xml | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 25c545a..7a60f3b 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -224,7 +224,7 @@
      <section anchor="zid" numbered="true" toc="default">
        <name>Zone ID</name>
        <t>
-         The "zid" wire format is illustrated in Figure <xref 
target="figure_zid"/>.
+         The "zid" wire format is illustrated in <xref target="figure_zid"/>.
        </t>
      <figure anchor="figure_zid">
        <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -242,7 +242,7 @@
        the same Base32 value as the letter "V" in order to further increase
        tolerance for failures in character recognition.
        The encoding and decoding symbols for Crockford Base32 including this 
modification are defined in
-       Figure <xref target="CrockfordB32Encode"/>.
+       <xref target="CrockfordB32Encode"/>.
        We assume that the functions for encoding and
        decoding based on this table are called
        "StringEncode(decodedString)" and
@@ -388,7 +388,7 @@ zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
      </t>
      <t>
        A GNS resource record holds the data of a specific record in a zone.
-       The resource record format is defined in Figure <xref 
target="figure_gnsrecord"/>.
+       The resource record format is defined in <xref 
target="figure_gnsrecord"/>.
      </t>
      <figure anchor="figure_gnsrecord">
        <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -442,7 +442,7 @@ zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
      </dl>
      <t>
        Flags indicate metadata surrounding the resource record. A flag
-       value of 0 indicates that all flags are unset. Figure <xref 
target="figure_flag"/>
+       value of 0 indicates that all flags are unset. <xref 
target="figure_flag"/>
        illustrates the flag distribution in the 32-bit flag value of a
        resource record:</t>
      <figure anchor="figure_flag">
@@ -508,7 +508,7 @@ zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
          delegate to.
          A PKEY record MUST be the only record under a label. No other
          records are allowed. The PKEY DATA entry wire format can be found
-         found in Figure <xref target="figure_pkeyrecord"/>.
+         found in <xref target="figure_pkeyrecord"/>.
        </t>
        <figure anchor="figure_pkeyrecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -650,7 +650,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
          The block counter is a 32-bit integer value in network byte order.
          The initialization vector is the expiration time of the
          resource record block in network byte order.
-         The resulting counter ("IV") wire format can be found in Figure
+         The resulting counter ("IV") wire format can be found in 
          <xref target="figure_hkdf_ivs_pkey"/>.
        </t>
        <figure anchor="figure_hkdf_ivs_pkey">
@@ -680,7 +680,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
          delegate to.
          A EDKEY record MUST be the only record under a label. No other
            records are allowed. The EDKEY DATA entry wire format
-         is illustrated in Figure <xref target="figure_edkeyrecord"/>.
+         is illustrated in <xref target="figure_edkeyrecord"/>.
        </t>
        <figure anchor="figure_edkeyrecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -874,7 +874,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
            The nonce is combined with an 8 byte initialization vector.
            The initialization vector is the expiration time of the
            resource record block in network byte order.
-           The resulting counter ("IV") wire format is illustrated in Figure
+           The resulting counter ("IV") wire format is illustrated in 
            <xref target="figure_hkdf_ivs_edkey"/>.
          </t>
          <figure anchor="figure_hkdf_ivs_edkey">
@@ -901,7 +901,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
          The resource record contains a DNS name for the resolver to continue 
with
          in DNS followed by a DNS server. Both names are in the format defined 
in
          <xref target="RFC1034" /> for DNS names.
-           A GNS2DNS DATA entry is illustrated in Figure <xref 
target="figure_gns2dnsrecord"/>.</t>
+           A GNS2DNS DATA entry is illustrated in <xref 
target="figure_gns2dnsrecord"/>.</t>
        <figure anchor="figure_gns2dnsrecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
 0     8     16    24    32    40    48    56
@@ -946,7 +946,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
 
          A LEHO resource record is expected to be found together in a single
          resource record with an IPv4 or IPv6 address.
-         A LEHO DATA entry is illustrated in Figure <xref 
target="figure_lehorecord"/>.</t>
+         A LEHO DATA entry is illustrated in <xref 
target="figure_lehorecord"/>.</t>
        <figure anchor="figure_lehorecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
 0     8     16    24    32    40    48    56
@@ -986,7 +986,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
          returned with record sets under any label as a supplemental record.
          <xref target="nick_processing"/> details how a resolver must process
          supplemental and non-supplemental NICK records.
-         A NICK DATA entry is illustrated in Figure <xref 
target="figure_nickrecord"/>.
+         A NICK DATA entry is illustrated in <xref 
target="figure_nickrecord"/>.
        </t>
        <figure anchor="figure_nickrecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -1025,7 +1025,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
          "example.org" as a BOX record with service (SVC) 443 (https) and 
protocol (PROTO) 6
          (tcp) and record TYPE "TLSA".
          For reference, see also <xref target="RFC2782" />.
-           A BOX DATA entry is illustrated in Figure <xref 
target="figure_boxrecord"/>.
+           A BOX DATA entry is illustrated in <xref 
target="figure_boxrecord"/>.
        </t>
        <figure anchor="figure_boxrecord">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -1068,7 +1068,7 @@ NONCE := HKDF-Expand (PRK_n, label, 32 / 8)
      <section anchor="gnsrecords_vpn" numbered="true" toc="default">
        <name>VPN</name>
        <t>
-           A VPN DATA entry wire format is illustrated in Figure
+           A VPN DATA entry wire format is illustrated in 
          <xref target="figure_vpnrecord"/>.
        </t>
        <figure anchor="figure_vpnrecord">
@@ -1158,7 +1158,7 @@ q := SHA512 (HDKD-Public(zk, label))
          A GNS implementation must publish RRBLOCKs
          in accordance to the properties and recommendations of the underlying
          DHT. This may include a periodic refresh publication.
-         The GNS RRBLOCK wire format is illustrated in Figure
+         The GNS RRBLOCK wire format is illustrated in 
          <xref target="figure_record_block"/>.
        </t>
        <figure anchor="figure_record_block">
@@ -1247,7 +1247,7 @@ q := SHA512 (HDKD-Public(zk, label))
        <t>
          A symmetric encryption scheme is used to encrypt the resource records
          set RDATA into the BDATA field of a GNS RRBLOCK.
-         The wire format of the RDATA is illustrated in Figure
+         The wire format of the RDATA is illustrated in 
          <xref target="figure_rdata"/>.
        </t>
        <figure anchor="figure_rdata">
@@ -1637,7 +1637,7 @@ NICK: john (Supplemental)
          <dt>K</dt><dd>Unused</dd>
        </dl>
        <t>
-         Figure <xref target="figure_revocation"/> illustrates the wire format
+         <xref target="figure_revocation"/> illustrates the wire format
          of the message string "P" on which the PoW is calculated.
        </t>
        <figure anchor="figure_revocation">
@@ -1705,7 +1705,7 @@ NICK: john (Supplemental)
          <dd>A single epoch is fixed at 365 days.</dd>
        </dl>
        <t>
-         The revocation message wire format is illustrated in Figure
+         The revocation message wire format is illustrated in 
          <xref target="figure_revocationdata"/>.
        </t>
        <figure anchor="figure_revocationdata">
@@ -1783,7 +1783,7 @@ NICK: john (Supplemental)
          The signature over the public key covers a 32-bit pseudo header
          conceptually prefixed to the public key. The pseudo header includes
         the key length and signature purpose. The wire format is illustrated
-        in Figure <xref target="figure_revsigwithpseudo"/>.
+        in <xref target="figure_revsigwithpseudo"/>.
        </t>
        <figure anchor="figure_revsigwithpseudo">
          <artwork name="" type="" align="left" alt=""><![CDATA[
@@ -2100,7 +2100,7 @@ example.com = zk2
        <t>
          The registration policy for this sub-registry is "First Come First
          Served", as described in <xref target="RFC8126"/>.
-         GANA is requested to populate this registry as listed in Figure
+         GANA is requested to populate this registry as listed in 
          <xref target="figure_rrtypenums"/>.
        </t>
        <figure anchor="figure_rrtypenums">
@@ -2119,7 +2119,7 @@ Number | Name    | Contact | References | Description
        <t>The GANA Resource Record Registry.</t>
        <t>
          GANA is requested to amend the "GNUnet Signature Purpose" registry
-           as illustrated in Figure <xref target="figure_purposenums"/>.
+           as illustrated in <xref target="figure_purposenums"/>.
        </t>
        <figure anchor="figure_purposenums">
          <artwork name="" type="" align="left" alt=""><![CDATA[

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