commit 334b69b02e5ac642ea4178d99125a00568452191
parent 1e9384f5649de64f3d74f14c36eb7ae3f714ed24
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sun, 20 Feb 2022 09:45:25 +0100
more start zone zTLDs
Diffstat:
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1907,14 +1907,14 @@ q := SHA-512 (ZKDF-Public(zk, label))
</t>
<t>
An implementation MUST first try to interpret the rightmost label of
- the given name as zTLD.
- If the zTLD cannot be decoded or if the decoded zTLD does not indicate
- a supported ztype, the name is treated as a normal name and start zone
- discovery MUST continue.
+ the given name as the beginning of a zTLD (<xref target="zTLD"/>).
+ If the rightmost label cannot be (partially) decoded or if it does not
+ indicate a supported ztype, the name is treated as a normal name and
+ start zone discovery MUST continue.
If a valid ztype can be found in the rightmost label, the
- implementation MUST try to synthesize and decode the start zone key
- according to <xref target="zTLD"/>.
- If the zone key cannot be synthesized or decoded, the resolution of
+ implementation MUST try to synthesize and decode the zTLD to retrieve
+ the start zone key according to <xref target="zTLD"/>.
+ If the zTLD cannot be synthesized or decoded, the resolution of
the name fails and an error is returned to the application.
Otherwise, the zone key MUST be used as the start zone:
</t>
@@ -1924,8 +1924,8 @@ Example name: www.example.<zTLD>
=> Name to resolve from start zone: www.example
]]></artwork>
<t>
- Otherwise, the resolver MUST determine the start zone through other
- means.
+ For names not ending with a zTLD the resolver MUST determine the start
+ zone through other means.
The choice of available start zone(s) is at the sole
discretion of the local system administrator or user.
This property addresses the issue of a single hierarchy with a
