commit 8d8134fb7d41748bca8510055ba7f56fdc64017f
parent 117a47e3463ce91effc96be16a8e6a16ad88006c
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Mon, 7 Mar 2022 17:30:19 +0100
-minor
Diffstat:
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -19,6 +19,7 @@
<!ENTITY RFC6895 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6895.xml">
<!ENTITY RFC6979 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6979.xml">
<!ENTITY RFC7363 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7363.xml">
+<!ENTITY RFC7706 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7706.xml">
<!ENTITY RFC7748 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml">
<!ENTITY RFC8032 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml">
<!ENTITY RFC8126 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml">
@@ -156,9 +157,9 @@
This is an important distinguishing factor from the Domain Name System
where root zone governance is centralized at the Internet Corporation
for Assigned Names and Numbers (ICANN).
- In DNS terminology, GNS roughly follows the idea of a locally
- authoritative root zone deployment, with the difference that it is not
- expected that all deployments use the same local root zone,
+ In DNS terminology, GNS roughly follows the idea of a local
+ root zone deployment (see <xref target="RFC7706"/>), with the difference that it is not
+ expected that all deployments use the same root zone,
and that users can easily delegate control of arbitrary domain names to
arbitrary zones.
</t>
@@ -2681,6 +2682,7 @@ Purpose | Name | References | Comment
&RFC6234;
&RFC6895;
&RFC6979;
+ &RFC7706;
&RFC7748;
&RFC8032;
&RFC8126;
