commit 0be9ad6aad91b027588cec257085d56540db4d56
parent f95fe19f7a37225f111703d2cddfe680aeb3638d
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 8 Feb 2022 22:09:12 +0100
fix punycode
Diffstat:
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -1465,8 +1465,8 @@ S-Decrypt(zk,label,expiration,ciphertext):
</dl>
<t>
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" />. <!-- punycode or IDNA? -->
+ in a DNS request they must first be converted to an IDNA punycode
+ representation <xref target="RFC5891" />.
</t>
</section>
</section>
@@ -1516,7 +1516,7 @@ S-Decrypt(zk,label,expiration,ciphertext):
</dl>
<t>
NOTE: If an application uses a LEHO value in an HTTP request header
- (e.g. "Host:" header) it must be converted to a punycode representation
+ (e.g. "Host:" header) it must be converted to an IDNA punycode representation
<xref target="RFC5891" />.
</t>
</section>
@@ -2078,7 +2078,7 @@ example.com = zk2
This may in turn trigger a GNS name resolution process depending
on the system configuration.
In case resolution continues in DNS, the name MUST first be
- converted to a punycode representation <xref target="RFC5890" />.
+ converted to an IDNA punycode representation <xref target="RFC5891" />.
</t>
<t>
In order to prevent infinite loops, the resolver MUST
@@ -2099,8 +2099,8 @@ example.com = zk2
<t>
Otherwise, it is expected that the resolver first resolves the
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.
+ The DNS name may have to be converted to an IDNA punycode
+ representation <xref target="RFC5891" /> for resolution in DNS.
GNS2DNS records MAY
contain numeric IPv4 or IPv6 addresses, allowing the resolver to
skip this step.
