[lsd0001] branch master updated: add more structure to overview

[gnunet]

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

grothoff pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new cd00a41  add more structure to overview
cd00a41 is described below

commit cd00a41b26073023c75f3f6830ba2a20ba964c32
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 18:57:37 2023 +0200

    add more structure to overview
---
 draft-schanzen-gns.xml | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 8560187..cf58bde 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -350,6 +350,13 @@
            including delegations MUST be verified by the implementation.
          </li>
        </ol>
+       <t>
+         In the remainder of this document, the "implementer" refers to the 
developer building
+         a GNS implementation including the resolver, zone master, and
+         supporting configuration such as start zones (see <xref 
target="governance"/>).
+       </t>
+       <section anchor="names" numbered="true" toc="default">
+       <name>Names and Zones</name>
        <t>
          It follows from the above that GNS does not support names which are
          simultaneously global, secure and human-readable.
@@ -388,6 +395,9 @@ 
example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
          of petnames, GNS defines auxiliary record types in addition to
          supporting existing DNS records.
        </t>
+       </section>
+       <section anchor="publishing" numbered="true" toc="default">
+       <name>Publishing Binding Information</name>
        <t>
          Zone contents are encrypted and signed
          before being published in a remote key-value storage (see <xref 
target="publish"/>)
@@ -443,6 +453,9 @@ 
example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
          configured (see <xref target="resolution"/>) or if the names end with 
a
          zTLD suffix.
        </t>
+       </section>
+       <section anchor="publishing" numbered="true" toc="default">
+       <name>Resolving Names</name>
        <t>
          Applications use the resolver to lookup GNS names.
          Starting from a configurable start zone, names are resolved by 
following zone
@@ -487,11 +500,7 @@ 
example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
                      +---------+                |
            ]]></artwork>
        </figure>
-       <t>
-         In the remainder of this document, the "implementer" refers to the 
developer building
-         a GNS implementation including the resolver, zone master, and
-         supporting configuration such as start zones (see <xref 
target="governance"/>).
-       </t>
+       </section>
    </section>
    <section anchor="zones" numbered="true" toc="default">
      <name>Zones</name>

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