[lsd0001] branch master updated: move text on zone masters to more logical spot

[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 c3b8fac  move text on zone masters to more logical spot
c3b8fac is described below

commit c3b8fac8cabaa7a5be121c909ea22da9f5ddbf0a
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 30 18:53:01 2023 +0200

    move text on zone masters to more logical spot
---
 draft-schanzen-gns.xml | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 7bc8883..8560187 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -435,6 +435,14 @@ 
example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
  +---------+          |                 |         +---------+
            ]]></artwork>
        </figure>
+       <t>
+         A zone master implementation <bcp14>SHOULD</bcp14> be provided as
+         part of a GNS implementation to enable users to create and manage 
zones.
+         If this functionality is not implemented, names can still be resolved
+         if zone keys for the initial step in the name resolution have been
+         configured (see <xref target="resolution"/>) or if the names end with 
a
+         zTLD suffix.
+       </t>
        <t>
          Applications use the resolver to lookup GNS names.
          Starting from a configurable start zone, names are resolved by 
following zone
@@ -487,13 +495,6 @@ 
example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884
    </section>
    <section anchor="zones" numbered="true" toc="default">
      <name>Zones</name>
-     <t>
-       A zone master implementation <bcp14>SHOULD</bcp14> enable the zone
-       owners to create and manage zones.
-       If this functionality is not implemented, names can still be resolved
-       if zone keys for the initial step in the name resolution are available
-       (see <xref target="resolution"/>).
-     </t>
      <t>
        A zone in GNS is uniquely identified by its zone type and zone key.
        Each zone can be represented by a Zone Top-Level Domain (zTLD) string.

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