commit cd00a41b26073023c75f3f6830ba2a20ba964c32
parent c3b8fac8cabaa7a5be121c909ea22da9f5ddbf0a
Author: Christian Grothoff <christian@grothoff.org>
Date: Fri, 30 Jun 2023 18:57:37 +0200
add more structure to overview
Diffstat:
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -351,6 +351,13 @@
</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.
Instead, names are either global and not human-readable or not globally
@@ -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>
