[lsd0001] branch master updated: terminology

[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 26f5022  terminology
26f5022 is described below

commit 26f5022d657dd7af2525cc5bfebe47fd77b301fa
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Tue Jan 18 16:27:07 2022 +0100

    terminology
---
 draft-schanzen-gns.xml | 163 ++++++++++++++++++++++++++++++++-----------------
 1 file changed, 108 insertions(+), 55 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index cf3becc..f1db2a8 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -168,6 +168,63 @@
        </t>
      </section>
    </section>
+   <section>
+     <name>Terminology</name>
+     <dl>
+       <dt>Label</dt>
+       <dd>
+         A GNS label is a label as defined in <xref target="RFC8499"/>.
+         Within this document, labels are always assumed to be strings of
+         UTF-8 characters <xref target="RFC8499"/> in Normalization Form C 
(NFC)
+         <xref target="Unicode-UAX15"/>.
+       </dd>
+       <dt>Name</dt>
+       <dd>
+         A name in GNS is a domain name as defined in  <xref 
target="RFC8499"/>.
+         as an ordered list of labels.
+         The labels in a name are separated using the character "." (dot).
+         Names, like labels, are encoded in UTF-8.
+       </dd>
+       <dt>Top-Level Domain</dt>
+       <dd>
+         A GNS Top-Level Domain is a GNS label and a Top-Level
+         Domain (TLD) as defined in <xref target="RFC8499"/>.
+         With the exception of Zone Top-Level Domains (see below),
+         GNS TLDs are part of the configuration of the local resolver
+         (see <xref target="governance"/>) and may not be globally unique.
+       </dd>
+       <dt>Zone</dt>
+       <dd>
+         A GNS zone contains authoritative information (resource records).
+         A zone is uniquely identified by its ID.
+       </dd>
+       <dt>Zone Type</dt>
+       <dd>
+         The type of a GNS zone determines the format and type of the
+         zone key.
+       </dd>
+       <dt>Zone Owner</dt>
+       <dd>
+         The owner of a GNS zone is the holder of private key corresponding to
+         the respective zone key.
+       </dd>
+       <dt>Zone Top-Level Domain</dt>
+       <dd>
+         A GNS Zone Top-Level Domain (zTLD) is a GNS name and a Top-Level
+         Domain (TLD) as defined in <xref target="RFC8499"/>.
+         It represents a sub-group of all TLDs and encodes the zone type and
+         zone key of a zone.
+         Due to the statistical uniqueness of zone keys, zTLDs are also 
globally unique.
+       </dd>
+       <dt>Resource Record</dt>
+       <dd>
+         A GNS resource record is the information associated with a label in a
+         GNS zone.
+         A GNS resource record contains information as defined by its
+         resource record type or a DNS resource record.
+       </dd>
+     </dl>
+   </section>
    <section anchor="overview" numbered="true" toc="default">
      <name>Overview</name>
      <t>
@@ -179,8 +236,7 @@
        The zone type determines the respectice set of cryptographic functions.
      </t>
      <t>
-       A zone can be populated with mappings from labels
-       (as defined in <xref target="RFC8499"/>, Section 2) to resource records 
by
+       A zone can be populated with mappings from labels to resource records by
        its owner (<xref target="rrecords"/>).
        Labels can be delegated to other zones using delegation records and in
        order to support (legacy) applications as well as facilitate the use
@@ -234,32 +290,27 @@
    <section anchor="zones" numbered="true" toc="default">
      <name>Zones</name>
      <t>
-       A zone in GNS is defined by its zone type and zone ID.
-       Further, each zone can be represented by a Zone Top-Level Domain (zTLD)
-       string.
-       In this section, the zone type, zone ID, zTLD and zone revocation is
-       specified.
+       A zone in GNS is uniquely identified by its zone type and zone key.
+       It can be represented by a Zone Top-Level Domain (zTLD) string.
+     </t>
+     <t>
+       The zone type ztype is the unique zone type of the zone as registered
+       in the GNUnet Assigned Numbers Authority <xref target="GANA" />.
+       The zone type determines which cryptosystem is used for the
+       asymmetric and symmetric key operations of the zone.
+       The zone type is identified by a 32-bit number.
+       It always corresponds to a resource record type number identifying a
+       delegation into a zone of this type.
+     </t>
+     <t>
+       For any zone, d is the private key. zk is the zone key.
+       The specific formats depends on the zone type.
+       The creation of zone keys for the default zone types are specified in
+       <xref target="gnsrecords_delegation"/>.
+       New zone types may be specified in the future, for example if the
+       cryptographic mechanisms used in this document are broken.
+       Any zone type MUST define the following set of cryptographic functions:
      </t>
-     <section anchor="ztype" numbered="true" toc="default">
-       <name>Zone Type</name>
-       <t>
-         The zone type ztype is the unique zone type of the zone as registered
-         in the GNUnet Assigned Numbers Authority <xref target="GANA" />.
-         The zone type determines which cryptosystem is used for the
-         asymmetric and symmetric key operations of the zone.
-         The zone type is identified by a 32-bit number.
-         It always corresponds to a resource record type number identifying a
-         delegation into a zone of this type.
-       </t>
-       <t>
-         For any zone, d is the private key. zk is the zone key.
-         The specific formats depends on the zone type.
-         The creation of zone keys for the default zone types are specified in
-         <xref target="gnsrecords_delegation"/>.
-         New zone types may be specified in the future, for example if the
-         cryptographic mechanisms used in this document are broken.
-         Any zone type MUST define the following set of cryptographic 
functions:
-       </t>
      <dl>
        <dt>Private-KeyGen() -> d</dt>
        <dd>
@@ -312,15 +363,9 @@
          and otherwise "FALSE".
        </dd>
      </dl>
-   </section>
-     <section anchor="zid" numbered="true" toc="default">
-       <name>Zone ID</name>
-
-       <t>The zone ID zid is a unique public identifier of a zone.
-         It consists of the ztype and the zone key zk.
-         The wire format is illustrated in <xref target="figure_zid"/>.
-       </t>
-     <figure anchor="figure_zid">
+     <section anchor="zTLD" numbered="true" toc="default">
+       <name>Zone Top-Level Domain</name>
+       <figure anchor="figure_zid">
        <artwork name="" type="" align="left" alt=""><![CDATA[
 0     8     16    24    32    40    48    56
 +-----+-----+-----+-----+-----+-----+-----+-----+
@@ -330,20 +375,18 @@
 /                                               /
          ]]></artwork>
      </figure>
-     </section>
-     <section anchor="zTLD" numbered="true" toc="default">
-       <name>Zone Top-Level Domain</name>
-
+       <t>The decoded binary representation of the zTLD</t>
        <t>
          The zTLD is the Zone Top-Level Domain.
-         It is a string which encodes the zone key into a domain name.
+         It is a string which encodes the zone type and zone key into a domain 
name.
          The zTLD is used as a globally unique reference to a specific
          namespace in the process of name resolution.
-         To encode the zone key, a zone key label zkl is derived from the zone
-         ID using the Crockford Base32
-         encoding <xref target="CrockfordB32"/> but the letter "U" is decoded 
to
-         the same Base32 value as the letter "V" in order to further increase
-         tolerance for failures in character recognition.
+         To encode the zone key, a zone key label zkl is derived from a
+         concatenation of the zone type and zone key (see <xref 
target="figure_zid"/>)
+         using the Crockford Base32 encoding <xref target="CrockfordB32"/>.
+         In order to further increase tolerance for failures in character
+         recognition, the letter "U" MUST be decoded to the same Base32 value 
as the
+         letter "V".
          The encoding and decoding symbols for Crockford Base32 including this 
modification are defined in
          <xref target="CrockfordB32Encode"/>.
          The functions for encoding and decoding based on this table are called
@@ -394,8 +437,8 @@ Value       Symbol            Symbol
          For the string representation of a zone identifier we define:
        </t>
        <artwork name="" type="" align="left" alt=""><![CDATA[
-zkl := GNSCrockfordEncode(zid)
-zid := GNSCrockfordDecode(zkl)
+zkl := GNSCrockfordEncode(ztype|zkey)
+ztype|zkey := GNSCrockfordDecode(zkl)
     ]]></artwork>
        <t>
          If zkl is less than 63 characters, it can directly be
@@ -403,7 +446,7 @@ zid := GNSCrockfordDecode(zkl)
          If zkl is longer than 63 characters, the
          zTLD is constructed by dividing zkl into smaller labels separated by 
the
          label separator ".".
-         Here, the most significant bytes of the "zid" must be contained
+         Here, the most significant bytes of the "ztype|zkey" concatenation 
must be contained
          in the rightmost label of the resulting string and the least 
significant
          bytes in the leftmost label of the resulting string. This allows the
          resolver to determine the zone type and zkl length from the rightmost 
label.
@@ -602,7 +645,7 @@ zTLD := zkl[126..129].zkl[63..125].zkl[0..62]
            which is revoked and corresponds to the key used in the PoW.
            The signature is created using the Sign() function of
            the cryptosystem of the zone and the private key
-           (see <xref target="ztype" />).
+           (see <xref target="zones" />).
          </dd>
        </dl>
       <t>
@@ -1532,7 +1575,7 @@ q := SHA512 (HDKD-Public(zk, label))
            this field.
            The signature is created using the Sign() function of
            the cryptosystem of the zone and the derived private key
-           "ZKDF-Private(d, label)" (see <xref target="ztype" />).
+           "ZKDF-Private(d, label)" (see <xref target="zones" />).
          </dd>
          <dt>SIZE</dt>
          <dd>
@@ -2333,7 +2376,7 @@ Zone private key (d, little-endian, with ztype prepended):
 e7467aff2d4d06c9
 1bd00c73
 
-Zone identifier (zid):
+Zone identifier (ztype|zkey):
 00010000de93f193
 8df85f1918a35c6d
 d0f3ae70f94692a7
@@ -2451,7 +2494,7 @@ e439e4cd1139a4bf
 cb74318c3abd331a
 488e30f6
 
-Zone identifier (zid):
+Zone identifier (ztype|zkey):
 000100140f833e26
 fed15c9e6c03f31c
 fb724e9ebf6889e9
@@ -2570,7 +2613,7 @@ a56693e07087ad35
 24f8e303931d4ade
 946dc447
 
-Zone identifier (zid):
+Zone identifier (ztype|zkey):
 00010000d06ab6d9
 14e8a8064609b2b3
 cb661c586042adcb
@@ -2706,7 +2749,7 @@ cae1789d
            <date year="2019" month="March"/>
          </front>
        </reference>
-             <reference anchor="XSalsa20" 
target="https://cr.yp.to/snuffle/xsalsa-20110204.pdf";>
+       <reference anchor="XSalsa20" 
target="https://cr.yp.to/snuffle/xsalsa-20110204.pdf";>
          <front>
            <title>Extending the Salsa20 nonce</title>
           <author initials="D." surname="Bernstein" fullname="Daniel 
Bernstein">
@@ -2715,6 +2758,16 @@ cae1789d
            <date year="2011"/>
          </front>
        </reference>
+       <reference anchor="Unicode-UAX15" 
target="http://www.unicode.org/reports/tr15/tr15-31.html";>
+         <front>
+           <title>Unicode Standard Annex #15: Unicode Normalization Forms, 
Revision 31</title>
+          <author fullname="The Unicode Consortium">
+            <organization>University of Illinois at Chicago</organization>
+          </author>
+           <date year="2009" month="September"/>
+         </front>
+       </reference>
+
 
 
              <!--    <reference anchor="ISO20022">

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