lsd0001

LSD0001: GNU Name System
Log | Files | Refs | README

commit c3b8fac8cabaa7a5be121c909ea22da9f5ddbf0a
parent 6551f86c5aaa044aaa178d86ab78fcd60f5af13e
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri, 30 Jun 2023 18:53:01 +0200

move text on zone masters to more logical spot

Diffstat:
Mdraft-schanzen-gns.xml | 15++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml @@ -436,6 +436,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 delegations recursively as illustrated in <xref target="figure_arch_resolv"/>. @@ -488,13 +496,6 @@ example.000G006K2TJNMD9VTCYRX7BRVV3HAEPS15E6NHDXKPJA1KAJJEG9AFF884 <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. A zone type (ztype) is a unique 32-bit number.