summaryrefslogtreecommitdiff
path: root/draft-schanzen-gns.xml
diff options
context:
space:
mode:
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r--draft-schanzen-gns.xml9
1 files changed, 4 insertions, 5 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index a846525..dfea80c 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -217,10 +217,9 @@
<dt>Name</dt>
<dd>
- A name in GNS is a domain name as defined in <xref target="RFC8499"/>
- 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.
+ A name in GNS is a domain name as defined in <xref target="RFC8499"/>:
+ Names are UTF-8 <xref target="RFC3629" /> strings consisting of an
+ ordered 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 <bcp14>MAY</bcp14> ensure that name and label lengths are
@@ -1041,7 +1040,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
the GANA "GNS Record Types" registry (see <xref target="GANA"/>).
Not supporting some zone types will result in resolution failures in case
the respective zone type is encountered.
- This is be a valid choice if some zone delegation record types have been
+ This can be a valid choice if some zone delegation record types have been
determined to be cryptographically insecure.
Zone delegation records <bcp14>MUST NOT</bcp14> be stored and published
under the apex label.