<story><title>Giving every IPv6 address a name</title><url>https://has-a.name</url></story><parent_chain><item><author>gregmac</author><text>Also don&amp;#x27;t use for anything real, because you should not be teaching users that &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; is the proper, trusted domain for your service. Because it was supposed to be &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; and I just tricked &lt;i&gt;you&lt;/i&gt;.</text></item><item><author>robbya</author><text>This is cool, but keep in mind that the operator can also get SSL certs for your site (they just point the domain somewhere else and use Lets Encrypt or similar to get a certificate). So from a security perspective, you are putting a ton of trust if you use this for anything real.</text></item></parent_chain><comment><author>jandrese</author><text>The fundamental problem with this whole scheme is that it is still just trying to memorize the entire IP address.  The point of a name is to make it something that feels natural for actual people.&lt;p&gt;Maybe it would make more sense to choose the 65,536 most common English words (or whatever language you want) and break the address up into 8 words to form a crazy looking phrase.  This is still difficult to memorize but not as bad as just stuffing 128 bits of hex down your throat.  You could even allow for the collapsing 0s by making entry 0 be &amp;quot;and&amp;quot; and adding a bit of logic that does the collapse.&lt;p&gt;For fun I wrote a tiny script that does this and tried it with their example domain:&lt;p&gt;1234:5678:9abc:def0:1234:5678:9abc:def0 -&amp;gt; balcony gaining pawn toothill balcony gaining pawn toothill&lt;p&gt;Or Google&amp;#x27;s address from that page:&lt;p&gt;2a00:1450:4009:811::200e -&amp;gt; chinker bauchle dorter amor and bromidic&lt;p&gt;So maybe this wasn&amp;#x27;t the best idea, but at least they&amp;#x27;re a bit more amusing than the hex noise in the article.&lt;p&gt;Anyway, if anybody else wants to play around with it I have a tiny demo:  &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;jubei.ceyah.org&amp;#x2F;cgi-bin&amp;#x2F;ipv6toenglish&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;jubei.ceyah.org&amp;#x2F;cgi-bin&amp;#x2F;ipv6toenglish&lt;/a&gt;</text></comment>
<story><title>Giving every IPv6 address a name</title><url>https://has-a.name</url></story><parent_chain><item><author>gregmac</author><text>Also don&amp;#x27;t use for anything real, because you should not be teaching users that &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; is the proper, trusted domain for your service. Because it was supposed to be &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; and I just tricked &lt;i&gt;you&lt;/i&gt;.</text></item><item><author>robbya</author><text>This is cool, but keep in mind that the operator can also get SSL certs for your site (they just point the domain somewhere else and use Lets Encrypt or similar to get a certificate). So from a security perspective, you are putting a ton of trust if you use this for anything real.</text></item></parent_chain><comment><author>treysis</author><text>Same&amp;#x2F;similar working mechanism is built-in into Windows since Vista:
1234-5678--abcd.ipv6-literal.net
This doesn&amp;#x27;t even need functioning DNS and can work offline (add s&amp;lt;devnumber&amp;gt; for link-local addresses).</text></comment>