Use XXX domain prefix as a replacement for WWW at the start of URLs, not as a new TLD

[Bruce <bruce@xxxxxxxxxxxx>]

ICANN should advocate using XXX as a replacement for WWW as a domain
prefix, not as a new TLD. For example, the hypothetical adult site
EXAMPLE.COM company can host their adult content at
http://XXX.EXAMPLE.COM instead of at http://WWW.EXAMPLE.COM. This
addresses a number of concerns:
(1) It is unlikely that companies that already have established
non-.XXX domain names will drop them and there is no way to force them
to do it as there is no single country that governs the internet. Why
should they change what's already working for them? So adding a new
TLD is merely a revenue enhancement for ICANN: any XXX domains that
are registered are likely to be new TLDs not replacements for existing
ones.

(2) The XXX domain prefix enables companies that have both adult and
non-adult content to host the adult content at WWW and their adult
content at XXX. For example, a general information site might that
have some adult content, a movie site might have information about
adult and non-adult movies or a blog hosting company might allow both
adult and non-adult oriented blogs.

(3) The XXX domain prefix is more likely to be adopted since the XXX
domain prefix requires little more than creating a CNAME record.
Companies do not have to abandon their current domain addresses to
move to the XXX domain prefix. They can easily place an entry page on
WWW with no adult content that links to the XXX site.

(4) This, in turn, will make it easier for blocking software. They can
easily block all URLs that contain XXX domain prefixes or link to XXX
domain prefixes.

(5) The XXX domain prefix avoids companies needing to pre-emptively
reserve the XXX version of their domain names as would be required for
an XXX TLD. With the XXX domain prefix, companies already own all
their subordinate domains.

(6) There is no work to do to implement this proposal other than
advocating it. In fact, web sites can do this today with no action by
ICANN. However, if ICANN should decide to advocate the XXX domain
prefix, it will speed adoption.

In short, ICANN should not create an XXX TLD since it will serve no
useful purpose. Instead, they should advocate using XXX as a domain
prefix instead of WWW.