aboutsummaryrefslogtreecommitdiff
path: root/draft-schanzen-gns.xml
diff options
context:
space:
mode:
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r--draft-schanzen-gns.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 333e122..c3e770e 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -263,7 +263,7 @@
263 A GNS TLD can consist of one or more labels. 263 A GNS TLD can consist of one or more labels.
264 Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>), 264 Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>),
265 GNS does not expect all users to use the same global root zone. Instead, 265 GNS does not expect all users to use the same global root zone. Instead,
266 with the exception of Zone Top-Level Domains (see below), 266 with the exception of Zone Top-Level Domains (see <xref target="zTLD"/>),
267 GNS TLDs are typically part of the configuration of the local resolver 267 GNS TLDs are typically part of the configuration of the local resolver
268 (see <xref target="governance"/>), and might thus not be globally unique. 268 (see <xref target="governance"/>), and might thus not be globally unique.
269 </dd> 269 </dd>