From 4d803b49b0ae0af9d92c34e53cc1d79810df02c2 Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Wed, 22 Nov 2023 15:58:27 -0500
Subject: [PATCH] Naming: Add section on .alt
---
i2p2www/pages/site/docs/naming.html | 33 +++++++++++++++++++++++------
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/i2p2www/pages/site/docs/naming.html b/i2p2www/pages/site/docs/naming.html
index c081e14f..3f3a3863 100644
--- a/i2p2www/pages/site/docs/naming.html
+++ b/i2p2www/pages/site/docs/naming.html
@@ -168,18 +168,39 @@ Otherwise, it forwards the request to a configured HTTP outproxy.
Thus, in practice, all HTTP (I2P Site) hostnames must end in the pseudo-Top Level Domain '.i2p'.
{%- endtrans %}</p>
-<p>{% trans i2ptld='https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/',
-rfc6761='http://tools.ietf.org/html/rfc6761' -%}
-We have <a href="{{ i2ptld }}">applied to reserve the .i2p TLD</a>
-following the procedures specified in <a href="{{ rfc6761 }}">RFC 6761</a>.
-{%- endtrans %}</p>
-
<p>{% trans -%}
If the router fails to resolve the hostname, the HTTP proxy returns
an error page to the user with links to several "jump" services.
See below for details.
{%- endtrans %}</p>
+
+<h2 id="alt">.i2p.alt Domain</h2>
+We previously <a href="https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/">applied to reserve the .i2p TLD</a>
+following the procedures specified in <a href="https://www.rfc-editor.org/rfc/rfc6761.html">RFC 6761</a>.
+However, this application and all others were rejected, and RFC 6761 was declared a "mistake".
+</p>
+<p>
+After many years of work by the GNUnet team and others, the .alt domain was reserved as a special-use TLD
+in <a href="https://www.rfc-editor.org/rfc/rfc9476.html">RFC 9476</a> as of late 2023.
+While there are no official registrars sanctioned by IANA, we have registered the .i2p.alt domain
+with the primary unofficial registrar <a href="https://gana.gnunet.org/dot-alt/dot_alt.html">GANA</a>.
+This does not prevent others from using the domain, but it should help discourage it.
+</p>
+<p>
+One benefit to the .alt domain is that, in theory, DNS resolvers will not forward .alt requests
+once they update to comply with RFC 9476, and that will prevent DNS leaks.
+For compatibility with .i2p.alt hostnames, I2P software and services should be updated to handle
+these hostnames by stripping off the .alt TLD.
+These updates are scheduled for the first half of 2024.
+</p>
+<p>
+At this time, there are no plans to make .i2p.alt the preferred form for display and interchange of I2P hostnames.
+This is a topic for further research and discussion.
+</p>
+
+
+
<h2 id="addressbook">{% trans %}Address Book{% endtrans %}</h2>
<h3>{% trans %}Incoming Subscriptions and Merging{% endtrans %}</h3>
--
GitLab