commit 112cb457e64f6b118c9ee01523d5ae8e6919d064
parent 7e54cdeb9cdd673b474d20493b204bc0d9b395bf
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sun, 7 Aug 2022 17:53:36 +0200
spice up ambiguity
Diffstat:
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -2772,11 +2772,21 @@ NICK: john (Supplemental)
<section anchor="namespace_ambiguity">
<name>Namespace Ambiguity</name>
<t>
- Some GNS names are indistinguishable from DNS names in their
+ Technically, the GNS protocol can be used to resolve names in the
+ namespace of the global DNS.
+ However, this would require the respective governance bodies and
+ stakeholders to standardize the use of GNS for this particular use
+ case and publish their zones accordingly.
+ </t>
+ <t>
+ However, this capability means that by definition GNS names may be
+ indistinguishable from DNS names in their
respective common display format <xref target="RFC8499"/> or
- other special-use domain names <xref target="RFC6761"/>.
- Given such a name it is ambiguous which name system should be used
- by an application in order to resolve it.
+ other special-use domain names <xref target="RFC6761"/> given
+ a local GNS start zone configuration that maps suffixes from the
+ global DNS to GNS zones.
+ For applications, it is then ambiguous which name system should be
+ used in order to resolve a given name.
This poses a risk when trying to resolve a name through DNS when
it is actually a GNS name.
In such a case, the GNS name is likely to be leaked as part of the DNS
