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.xml22
1 files changed, 6 insertions, 16 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 787302e..b3128a0 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -30,6 +30,7 @@
<!ENTITY RFC8324 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8324.xml">
<!ENTITY RFC8499 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8499.xml">
<!ENTITY RFC9106 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.9106.xml">
+<!ENTITY I-D.ietf-dnsop-alt-tld PUBLIC '' "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dnsop-alt-tld.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
@@ -230,7 +231,7 @@
A GNS name may be indistinguishable from a DNS name and care must
be taken by applications and implementors when handling GNS names
(see <xref target="namespace_ambiguity"/>). In the spirit of
- <xref target="draft-ietf-dnsop-alt-tld"/>, this draft uses the suffix
+ <xref target="I-D.ietf-dnsop-alt-tld"/>, this draft uses the suffix
".gns.alt" in examples and reserves it in the GANA ".alt Subdomains"
registry <xref target="GANA"/>.
</dd>
@@ -2822,10 +2823,10 @@ NICK: john (Supplemental)
<t>
The user or system administrator <bcp14>MAY</bcp14> configure one or
more unique suffixes for all suffix-to-zone mappings in the spirit
- of <xref target="draft-ietf-dnsop-alt-tld"/>.
+ of <xref target="I-D.ietf-dnsop-alt-tld"/>.
For this purpose, this draft creates a <xref target="GANA"/> registry
for subdomains under
- the special-use top-level domain ".alt" <xref target="draft-ietf-dnsop-alt-tld"/>
+ the special-use top-level domain ".alt" <xref target="I-D.ietf-dnsop-alt-tld"/>
in <xref target="gana"/>, and within it registers the subdomain ".gns.alt" for use with GNS in particular.
The use of the suffix ".gns.alt" in local suffix-to-zone mappings is
recommended in order to address the issues raised in
@@ -2920,7 +2921,7 @@ Number | Name | Contact | References | Comment
Each entry has the following format:
</t>
<ul>
- <li>Subdomain: The name of the subdomain (in UTF-8).</li>
+ <li>Label: The label of the subdomain (in DNS LDH format as defined in Section 2.3.1 of <xref target="RFC5890"/>).</li>
<li>Comment: Optionally, a brief English text describing the purpose of
the subdomain (in UTF-8)</li>
<li>Contact: Optionally, the contact information of a person to contact for
@@ -3145,18 +3146,7 @@ gns | (*) | [This.I-D] | The .alt subdomain for GNS.
&RFC8806;
&RFC6761;
&RFC8244;
-
- <!-- &RFC3912;-->
- <reference anchor="draft-ietf-dnsop-alt-tld" target="https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/">
- <front>
- <title>The ALT Special Use Top Level Domain </title>
- <author initials="W." surname="Kumari" fullname="Warren Kumari">
- </author>
- <author initials="P." surname="Hoffman" fullname="Paul Hoffman">
- </author>
- <date year="2019" month="March"/>
- </front>
- </reference>
+ &I-D.ietf-dnsop-alt-tld;
<reference anchor="Tor224" target="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt#n2135">
<front>