[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: fix
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: fix |
Date: |
Sat, 19 Feb 2022 13:14:33 +0100 |
This is an automated email from the git hooks/post-receive script.
martin-schanzenbach pushed a commit to branch master
in repository lsd0001.
The following commit(s) were added to refs/heads/master by this push:
new 2dd7cd9 fix
2dd7cd9 is described below
commit 2dd7cd9bc660ef1097bfd519ae5225450534d6a5
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sat Feb 19 13:14:30 2022 +0100
fix
---
draft-schanzen-gns.xml | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index bf05b07..6f7c5b9 100644
--- 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>
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
- [lsd0001] branch master updated: fix, gnunet, 2022/02/01
- [lsd0001] branch master updated: fix, gnunet, 2022/02/01
- [lsd0001] branch master updated: fix, gnunet, 2022/02/03
- [lsd0001] branch master updated: fix, gnunet, 2022/02/03
- [lsd0001] branch master updated: fix, gnunet, 2022/02/06
- [lsd0001] branch master updated: fix, gnunet, 2022/02/12
- [lsd0001] branch master updated: fix,
gnunet <=
- [lsd0001] branch master updated: fix, gnunet, 2022/02/19
- [lsd0001] branch master updated: fix, gnunet, 2022/02/21
- [lsd0001] branch master updated: fix, gnunet, 2022/02/21
- [lsd0001] branch master updated: fix, gnunet, 2022/02/21