lsd0001

commit e4bc2bac415cf2c9b8c9c0fa3d04c2460459a2dc
parent 8c58a3a83d30508e5093966ec72603dd0f7d6275
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue,  1 Feb 2022 20:47:54 +0100

editorializing, '+' is NOT a TLD by any sane definition

Diffstat:
M
draft-schanzen-gns.xml
 | 
13
+++++++------

1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1320,8 +1320,8 @@ NONCE := HKDF-Expand (PRK_n, label, 128 / 8)
            The DNS server to use. May be an IPv4 address in dotted-decimal
            form or an IPv6 address in colon-hexadecimal form or a DNS name.
            It may also be a relative GNS name ending with a
-           "+" top-level domain.
-           The implementation MUST check the string syntactically for a
+           "+" as the rightmost label.
+           The implementation MUST check the string syntactically for
            an IP address in the respective notation before checking for a
            relative GNS name.
            If all three checks fail, the name MUST be treated as a DNS name.
@@ -1329,8 +1329,8 @@ NONCE := HKDF-Expand (PRK_n, label, 128 / 8)
          </dd>
        </dl>
        <t>
-         NOTE: If an application uses names from GNS2DNS records in a DNS request
-         they must first be converted to a punycode representation
+         NOTE: If an application uses DNS names obtained from GNS2DNS records
+         in a DNS request they must first be converted to a punycode representation
          <xref target="RFC5890" />.
        </t>
    </section>
@@ -1341,7 +1341,7 @@ NONCE := HKDF-Expand (PRK_n, label, 128 / 8)
        <name>Auxiliary Records</name>
        <t>
          This section defines the initial set of auxiliary GNS record types. Any
-         implementation MUST be able to process the specified record types
+         implementation SHOULD be able to process the specified record types
          according to <xref target="record_processing"/>.
        </t>
      <section anchor="gnsrecords_leho" numbered="true" toc="default">
@@ -1357,7 +1357,8 @@ NONCE := HKDF-Expand (PRK_n, label, 128 / 8)
          The most common use case is HTTP virtual hosting, where a DNS name must
          be supplied in the HTTP "Host"-header.
          Using a GNS name for the "Host"-header may not work as
-         it may not be globally unique.
+         it may not be globally unique. Furthermore, even if uniqueness is
+         not an issue, the legacy service might not even be aware of GNS.
 
          A LEHO resource record is expected to be found together in a single
          resource record with an IPv4 or IPv6 address.