commit 2dd7cd9bc660ef1097bfd519ae5225450534d6a5
parent 4444fc2981abbd5c4e3f9b725828dd19af8fb385
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sat, 19 Feb 2022 13:14:30 +0100
fix
Diffstat:
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -209,8 +209,9 @@
example according to <xref target="Unicode-UTS46"/>.
Zone administrators MAY disallow certain labels that may be easily
confused with other labels through registration policies.
- The apex label, label separator and the extension label are reserved
- and MUST NOT be used.
+ The apex label, label separator and the extension label have
+ special purposes in the resolution protocol which are defined
+ in the rest of the document.
</dd>
<dt>Apex Label</dt>
<dd>
@@ -223,12 +224,12 @@
</dd>
<dt>Extension Label</dt>
<dd>
- If a name ends with the label U+002B ("+" without the quotes),
+ If a name ends with the extension label U+002B ("+" without the quotes),
the rest of the name MUST be
interpreted relative to the current zone in the resolution process.
- The primary use for this is in redirection records
- <xref target="gnsrecords_redirect"/> where the redirection should
- happen relative to the authoritative zone.
+ The primary use for this is in redirections where the redirection
+ target is defined relative to the authoritative zone of the redirection
+ record (<xref target="gnsrecords_redirect"/>).
</dd>
<dt>Label Separator</dt>
<dd>
