ICANN's decision to open the floodgates to hundreds of new generic top-level domains last week is expected to create a land-rush of "dot-brand" internet addresses. To date, fewer than six companies, notably including Canon, Hitachi and Deloitte, have publicly expressed their intention to acquire a branded gTLD. But domain …
Let the horse trading begin...again...
It has happened before - our senior sysadmin has pointed out that we were never meant to be .uk, but .gb - which would exclude the Northern Irish part, so we got .uk from the Ukraine - hence the less logical .ua that they have.
When are we going to see .co.usa instead of .com, one wonders.
.us already exists and is the correct geographical tld for the USA
We were already using UK
as the top of the JANET naming system before DNS came in.
I'm looking forward...
... the .facepalm, .bullshit and other .brainless
I'm applying for...
.knobhead and will run websites with profiles of all our MPs.
If I'm successful expect to www.davidcameron.knobhead and www.nickclegg.knobhead first to go live.
Wouldn't you be better off applying for .isaknobhead?
Now you're just increasing my costs, I'll have to get both now ;-)
These knobheads are turning out to be quite expensive now (ah, how online mimicks the real world).
So, it was "marketed" / promoted on the basis of companies being able to claim .brand type domains ("http://enjoy.coke/" was mentioned somewhere, if memory isn't playing tricks on me), but many of the largest and/or most important companies won't be able to use it.
Proof that one's worst enemy is normally oneself, I guess.
Oh, and why would the fact that the Slovenes use "Rim" as their word for "Rome" have the slightest bearing on whether a Canadian firm called (ok, abbreviated as) RIM can register that word as its gTLD? Reducing the relevance of that is that from a marketing point of view they'd be better off registering .blackberry anyway...
"the slightest bearing on whether a Canadian firm..."
On account of the internet being global, chief. The baseline rules were laid down in order to limit the amount of international irritation the stupid new domains would inevitably cause. The line has to be drawn somewhere.
Incidentally, do you think it is really such a bad thing that sovereignty is still considered important, even next to multibillion dollar corporate behemoths?
Why do I get the feeling you would not have raised this point if the name (well, acronym) of the Canadian berry-botherers was "ROME"? Would you, I wonder, have argued that there was no reason for .rome to be thus protected? (Apologies if you don't suffer from anglocentric bias; most native anglophone do.)
The thing about this approach, though, is I bet there must be a few collisions. Perhaps, for example, the Magyar name for Kuala Lumpur is "Wales"? Who wins then?
I'm looking forward to...
I'm also looking forward to .hpee
Should that not be .haitchpee?
Actually it would be
NATO phonetics for the win.
.aitchpee - spot on
.threefat ladies for 888
.armandaleg for ARM (these TLDs ain't cheap, you know)
.cheerio for Tata
and of course -
.RIP for RIM
"The $83 billion company could well be forced to seek the consent of Tata, a city of just 15,000 inhabitants, before it would be able to secure the .tata address."
... or they could just buy it.
Just goes to show ...
Great TaTa's are born, not made.
I can understand that a city name would be reserved, but I would expect the reserved names to be based on it's native names. The Italian name for Rome should be protected, bu why would the Slovenian name be protected. If the USA called Rome "Roomey", would that deserve protection too?
So you think rome shoud not be protected but roma should?
Yes - exactly. If the city of Roma want to buy Rome then they can apply but if we have to protect the name of every city in every language then there isn't going to be much left.
You obviously have to draw the line somewhere, and I think (as much as I hate to admit it) ICANN are probably right here. I am all for using the local name for places, but I wonder how many people actually know the local names for more than about 1% of the planet. Not many people would recognise 'Москва' as Moscow, for example, and I would guess that's probably one of the better known ones.
When you say not many, are you including the 142 million Russians nationals or not?
So according to your logic (and ICANN's), we should reserve Moscow in every language known to man, and then repeat for every city in the world?
Well, you don't need to repeat for every city in the world because the vast majority of cities only have one name - ie they either didn't exist 'back in the day', or weren't well known enough to be given a non-local name by other nationalities.
For places which do have non-local names given to them, yes those names should be reserved. What should really happen is when the city of Roma decides to register .roma, they should automatically get .rome, .рим, .rom, etc pointing to the same servers.
Ultimately it may turn out to be a non-issue, but ICANN are playing it safe by preventing ne'er-do-wells from hijacking translated names and scamming people through them.
I'm not entirely sure I agree with that decision, but I can see why they're doing it.
And a certain brand of peanuts
shares its name with the ccTLD of North Korea.
North Korea's ccTLD is 'Planters'? Who knew!
Is this a variant on "you are what you eat" ?
It's got the bananas, fruitcake and crackers in the pocket.
I take it that .ramsbottom is out of the question?
...has pointed out that ".arm" is short for ".am"
So when advertising new jobs at RIM they won't be able to use "jobs.rim"?
I'm gutted :(
Not to worry - I doubt they'll be advertising new jobs any time soon...
Houses of Parliament?
I may work in IT, but HP still always means the sauce.