commit 5e232aed098240a21b09477003896be4a2b160ae
parent 61e9ecd7996669fd556fd0de76146c7fe069b29e
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sat, 19 Feb 2022 13:43:11 +0100
clarification
Diffstat:
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -196,6 +196,7 @@
as an ordered list of labels.
Names are UTF-8 <xref target="RFC3629" /> strings consisting of the
list of labels concatenated with a label separator.
+ Names are resolved starting from the rightmost label.
GNS does not impose length restrictions on names or labels.
However, applications MAY ensure that name and label lengths are
compatible with DNS and in particular IDNA <xref target="RFC5890"/>.
@@ -1567,8 +1568,8 @@ S-Decrypt(zk,label,expiration,ciphertext):
<section anchor="gnsrecords_box" numbered="true" toc="default">
<name>BOX</name>
<t>
- In GNS, with the notable exception of zTLDs, every "." in a name
- delegates to another zone. Furthermore,
+ In GNS, with the notable exception of zTLDs, every separator label in a
+ name delegates to another zone. Furthermore,
GNS lookups are expected to return all of the required useful
information in one record set. This avoids unnecessary additional
lookups and cryptographically ties together information that belongs
@@ -1964,7 +1965,8 @@ com = (d2,zk2)
Suffix to zone key mappings MUST be configurable through a local
configuration file or database by the user or system administrator.
The suffix MAY consist of multiple GNS labels concatenated with a
- ".". If multiple suffixes match the name to resolve, the longest
+ label separator.
+ If multiple suffixes match the name to resolve, the longest
matching suffix MUST be used. The suffix length of two results
MUST NOT be equal. This indicates a misconfiguration and the
implementation MUST return an error.
@@ -2423,8 +2425,9 @@ NICK: john (Supplemental)
outdated.
It can be expected that the processing of zone revocations and an
initial start zone is provided with a GNS implementation
- ("drop shipping"). Shipping an initial start zone with an entry for
- the root (".") effectively establishes a root zone.
+ ("drop shipping").
+ Shipping an initial start zone configuration effectively establishes
+ a root zone.
Extension and customization of the zone is at the full discretion of
the user.
</t>
