commit 597426572f12db2b21a4fcc2c36e0cb14efe9a07
parent 1f02080c7484d60f6a28dc33de2adc73bd48195f
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 10 Nov 2019 21:09:00 +0100
clarify where NICKs can be encountered, fix typo
Diffstat:
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -408,7 +408,8 @@
This is a suggestion to other zones what label to use when creating a
PKEY <xref target="gnsrecords_pkey" /> record containing this zone's
public zone key.
- This record SHOULD only be stored under the empty label "@".
+ This record SHOULD only be stored under the empty label "@" but
+ MAY be returned with record sets under any label.
A NICK DATA entry has the following format:
</t>
<figure anchor="figure_nickrecord">
@@ -430,7 +431,7 @@
<dt>NICKNAME</dt>
<dd>
A UTF-8 string (which is not 0-terminated) representing the preferred
- label of the zone. This string MUST NOT inlcude a "." character.
+ label of the zone. This string MUST NOT include a "." character.
</dd>
</dl>
</section>