lsd0001

commit c9740740f09238e207d10e71d6718acc5f8b9ed6
parent 2be9a4cfe49d292c2af812bcbb3032241f9e29c7
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Sun, 20 Feb 2022 10:35:49 +0100

minor

Diffstat:
M
draft-schanzen-gns.xml
 | 
12
+++---------

1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1881,12 +1881,6 @@ q := SHA-512 (ZKDF-Public(zk, label))
        iteration in the resolution is processed.
      </t>
      <t>
-       GNS resolution of a name must start in a given starting zone indicated using
-       a zone key.
-       Details on how the starting zone may be determined are discussed in
-       <xref target="governance" />.
-     </t>
-     <t>
        The application MAY provide a desired record type to the resolver.
        The desired record type is used to guide processing.
        For example, if a zone delegation record type is requested, the
@@ -1949,9 +1943,9 @@ Example name: www.example.<zTLD>
        <artwork name="" type="" align="left" alt=""><![CDATA[
 Example name: www.example.org
 Local suffix mappings:
-org = zTLD0 (ztype0||zk0)
-example.org = zTLD1 (ztype1||zk1)
-example.com = zTLD2 (ztype2||zk2)
+org = zTLD0 := Base32GNS(ztype0||zk0)
+example.org = zTLD1 := Base32GNS(ztype1||zk1)
+example.com = zTLD2 := Base32GNS(ztype2||zk2)
 ...
 => Start zone: zk1
 => Name to resolve from start zone: www