On Fri, 12 Jul 2013, Phillip Hallam-Baker wrote:
I notice you are missing .oracle and .exchange and .mail. Is that
because you can't take any more slaps on the back or because you know
too many companies that have servers in their domain that would get
bypassed by your awesome magic three software vendors listed above?
No, I limited it to them only because those three companies can flood the
market with software that makes the decision by force majeur. I don't think the
domains you list have the market
power on the desktop to be a sufficient quorum.
avoiding answering the implicit question about huge collateral damage
when exchange.company.TLD and oracle.company.TLD start resolving to
company external IPs..... Even if just _one_ airline company would
fall into this trap, it would be millions of dollars of damage alone.
Paid for by vanity domains that make turning clearly visible domain names
into a confusion about what's a single word and what's a domain name.
The community has only two choices that make sense, either embrace dotless
domains or deploy DNS rules that simply block all the new ICANN TLDs as
unnecessary rent seeking noise.
We disagree on the the first, and the second one is as relevant as
whether I should add sugar to my morning coffee or not.
The proportion of the Internet user community that is aware of default domain
sufixes at all is very unlikely to be as much as 1%. So if we are going to make
a proper argument on the
grounds of avoiding user confusion we should probably be telling software
providers to stop supporting the local domain prefixes in platforms as a
security risk. The default path on this
machine is probably verizon.net. I find the default domain suffix to be
sufficiently useless that I never bother to set it.
You think that users know and/or can set a default domain suffix?
That programmers twenty years ago knew and/or understood what that even meant
(or you think no one runs 20 year old software?)
That everyone knows about suffix manipulation through their DHCP connections?
And VPN connections?
Apart from that, were you a proponent of the file extension and mime
type wars too? Because as soon as one company takes something like
.profitable as dotless, someone else will claim profitable:// and
all the browsers will just be giant pools of local policy causing
utter confusion and at best will yield a totally unpredictable
user experience for dotless domains. Don't expect a pat on the
shoulder from me in twenty years.
Paul