lsd0001

commit 681f5e5286177c0eed09acfa1534ae9865aaa703
parent 3881c3a94477a2ef242a3d166462716357c63436
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon,  7 Feb 2022 21:56:09 +0100

punycode; typo

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

1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1392,7 +1392,7 @@ S-Decrypt(zk,label,expiration,ciphertext):
        </figure>
        <t> The REDIRECT DATA Wire Format</t>
        <dl>
-         <dt>NAME</dt>
+         <dt>REDIRECT NAME</dt>
          <dd>
            The name to continue with.
            The value of a redirect record may be a regular name, or a relative
@@ -2024,7 +2024,7 @@ example.com = zk2
          </li>
          <li>
            Case 2:
-           If the filtered record set consists exclusively of a one or more DNS2GNS records
+           If the filtered record set consists exclusively of one or more GNS2DNS records
            resolution continues with DNS.
            Details are described in <xref target="gns2dns_processing" />.
          </li>
@@ -2085,7 +2085,10 @@ example.com = zk2
            </t>
            <t>
              Otherwise, it is expected that the resolver first resolves the
-             IP addresses of the specified DNS name servers. GNS2DNS records MAY
+             IP addresses of the specified DNS name servers.
+             The DNS name may have to be converted to a punycode representation
+             <xref target="RFC5890" /> for resolution in DNS.
+             GNS2DNS records MAY
              contain numeric IPv4 or IPv6 addresses, allowing the resolver to
              skip this step.
              The DNS server names may themselves be names in GNS or DNS.