<div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000">tl;dr : I suggest this... Try xx--[whateverword] to avoid most/many future collisions it takes advantage of the IDN blocking dashes at the third and fourth positions and allows for things like xx--vpn or xx--corp or xx--mshome etc which are human readable and won't trigger namespace collisions.</div><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000"><br></div><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000">deeper:</div><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000"><br></div><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000">The random gibberish TLDs that John suggested make sense, but could still cause a future collision, no matter how unlikely. I ran into some instances where there were names I owned that I thought were random gibberish that turned out were highly precious in the Chinese market a couple years back, so it stands to reason that just because we don't currently see a possibility of conflict, the universe seems to provide the potential. I guess even if it is made up, it is still violating ICP-3 and could cause namespace collision in the future.<br><br></div><div class="gmail_default" style="font-family:garamond,serif;font-size:large;color:#000000">We may be kicking a name collision can down the road, though many of us doubt it... I suspect that the wisest course would be to work inside the space restricted from typical use in order to avoid the potential collisions.<br><br>I do have a suggestion.<br><br>If I can 'plus-up' Paul's great suggestion, and synthesize a few of the ideas from the genius on list here, there is a restricted space of null area that exists for IDN whereby names with dashes in the 3rd and 4th positions are restricted. You could, if you avoided xn--, put any other two letters in front of a string then two dashes. <br><br>It also allows for more human readable strings as private space TLDs, like xx--corp or xx--vpn instead of randomness, so in that sense it could be a preferred approach.<br><br>[universe under fingernail stuff beyond this point]<br>As many of us have seen across the years, the ITU or others seeking to introduce geodiversity into the authority of name structure, from time to time. In a conceptual conversation I had with some ... jedi over the years, it was considered wise to stay in the sandbox of the private use space of the ISO 3166 two char prefixes to avoid conflict with national claims and/or compatibility with GACJackassery (not my term, but appropriate).<br><br>This would reduce the likelihood of causing unintentional namespace collision with a future gTLD to not just make up random strings willy nilly. I would suggest x[a-z]-- (but not xn-- so that one avoids IDN collision), to avoid some future use of <iso3166>-- prefix for balkanized national mapping that ITU or someone seeking to do might push on us through law such as TLDs becoming somehow fractionally used geographically in some manner using ccTLD dash dash prefixes (ie. us--com, ru--com, de--com, cn--com being different or affected by some future tech that intervenes in resolution).</div><div class="gmail_extra"><br clear="all"><div><div class="m_-6218382702766912215gmail_signature" data-smartmail="gmail_signature">Jothan Frakes<br><a href="tel:(206)%20355-0230" value="+12063550230" target="_blank">+1.206-355-0230</a> tel<br><a href="tel:(206)%20201-6881" value="+12062016881" target="_blank">+1.206-201-6881</a> fax</div></div>
<br><div class="gmail_quote">On Thu, Sep 7, 2017 at 6:57 PM, Paul Vixie <span dir="ltr"><<a href="mailto:paul@redbarn.org" target="_blank">paul@redbarn.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
John Levine wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
... I would wager<span><br>
quite a lot that none of these TLDs will appear in the root zone in my<br>
lifetime:<br>
<br>
.hcdsjm<br>
.dxozso<br>
.pmlwat<br>
.yoorzf<br>
.usapqm<br>
.miyepz<br>
.tmokxs<br>
.ytnhlv<br>
.nvikrt<br>
.mjjwsj<br>
</span></blockquote>
<br>
i have an even safer wager. put a hyphen in it. say, x-randomstring.<br>
<br>
this is what led us to use .rpz-nsip and similar, in the rpz design.<span class="m_-6218382702766912215HOEnZb"><font color="#888888"><br>
<br>
-- <br>
P Vixie</font></span><div class="m_-6218382702766912215HOEnZb"><div class="m_-6218382702766912215h5"><br>
<br>
______________________________<wbr>_________________<br>
dns-operations mailing list<br>
<a href="mailto:dns-operations@lists.dns-oarc.net" target="_blank">dns-operations@lists.dns-oarc.<wbr>net</a><br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations" rel="noreferrer" target="_blank">https://lists.dns-oarc.net/mai<wbr>lman/listinfo/dns-operations</a><br>
dns-operations mailing list<br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations" rel="noreferrer" target="_blank">https://lists.dns-oarc.net/mai<wbr>lman/listinfo/dns-operations</a><br>
</div></div></blockquote></div><br></div></div>