commit 994294bf7206c0807065bbb730a316ca43cf7c68
parent 8c9bed758a54b828682236b19b013b33b56040a0
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 8 Mar 2022 14:21:20 +0100
ambiguity
Diffstat:
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -2553,14 +2553,19 @@ NICK: john (Supplemental)
</t>
<t>
In order to prevent disclosure of queried GNS names it is
- <bcp14>RECOMMENDED</bcp14> that applications try to resolve
- a given name in GNS before any other method in order to honor
- potential suffix-to-zone mappings in GNS by the user.
- If no suffix-to-zone mapping for the name exists, resolution
- <bcp14>MAY</bcp14> continue with other methods such as DNS.
- If a suffix-to-zone mapping exists for the name and the query
- succeeds, fails or returns no results, resolution <bcp14>MUST NOT</bcp14>
- continue by any other means.
+ <bcp14>RECOMMENDED</bcp14> that GNS-aware applications try to resolve
+ a given name in GNS before any other method taking into account
+ potential suffix-to-zone mappings and zTLDs.
+ Suffix-to-zone mappings are expected to be configured by the user or
+ local administrator and as such the resolution in GNS is
+ in line with user expectations even if the name could also be resolved
+ through DNS.
+ If no suffix-to-zone mapping for the name exists and no zTLD is found,
+ resolution <bcp14>MAY</bcp14> continue with other methods such as DNS.
+ If a suffix-to-zone mapping for the name exists or the name ends with
+ a zTLD, it <bcp14>MUST</bcp14> be resolved using GNS and
+ resolution <bcp14>MUST NOT</bcp14> continue by any other means
+ independent of the GNS resolution result.
</t>
<t>
Mechanisms such as the Name Service Switch (NSS) of Unix-like
@@ -2572,8 +2577,8 @@ NICK: john (Supplemental)
<t>
The user or system administrator <bcp14>MAY</bcp14> configure one or
more unique suffixes for all suffix-to-zone mappings.
- In combination with a special-use domain name for GNS or an unreserved
- DNS TLD, this would prevent namespace ambiguity.
+ If this suffix is a special-use domain name for GNS or an unreserved
+ DNS TLD, this prevents namespace ambiguity through local configuration.
</t>
</section>
</section>
