Many of us know that .edu is a restricted domain, some
end-users don't but to them it is immaterial. Nevertheless, there is no squatter.edu,
no cokocola.edu, no triplexxx.edu and no end-user would reasonably expect there to
be. Creating new domains the same way should have a similar effect.It is easily
possible to build into browsers that when one of these domains is accessed a .reg
or (R) or TM also show up in the url or elsewhere in the browser, like the secure
key. I think it is even technically possible that BIND could insert it in the URL
line. It just seems to me that having both .airline and .reg in the domain, as well
as other necessary info, makes it less intuitive and user friendly.
united.com
is preferable to united.airline.reg or united.reg.airline. united.reg doesn't solve
the problem, therefore perhaps united.airline or united.air is the way to go. End-users
would learn to have faith (and/or it could be shown in some fashion) that this and
similar are closed domains, the genuine article.
Now the name space is like one
large white pages with sections for international, edu., military, government. What
is needed is a yellow pages. Co's can keep their existing white pages listing, or
add new ones. Individuals can't get yellow pages listings, but MacDonalds TM can't
have all the McDonalds and MacDonalds removed from the white pages (unless they pass
themselves off as the TM MacDonalds.