Should ICANN Dump The Idea Of Generic Top Level Domains?
from the yes-or-no dept
For years, we've scolded ICANN for its bizarre policies when it came to new top level domains (TLD) (the things like .com, .net, .org, .biz, .info etc.). For the most part, the whole process seemed like a big money grab, where each new TLD was being introduced not because of any need, but because it would generate extra cash. Take, for example, the creation of the .jobs domain. It's designed to be the place where people can go to find job openings for a company. As if it wasn't easy enough to either go to the site directly and look for the "jobs" link, or to do a quick Google search (though, we must admit to an adolescent snicker, when someone recently pointed out that RIM had amazingly signed up for the unfortunately named rim.jobs).On the whole, though, there seemed to be no legitimate reason for dribbling out TLDs in this manner. If the world needed more TLDs, why not open the process up entirely, and let people use whatever TLD made the most sense. Last year, it looked like it was making a step in that direction, by announcing plans to offer such generic TLDs, but at the astronomical price of somewhere between $100,000 and $500,000. So, once again, it was all about the money grab, rather than anything useful.
However, with overwhelming opposition to the idea of super high priced generic TLDs, ICANN has delayed the entire project and some are wondering if ICANN should drop the idea entirely. Personally, it still seems like the real plan should be not to do away with generic TLDs entirely, but to just open up the system, so that any TLD can be used, but that you can register for one at the regular domain price, rather than one that's many orders of magnitude higher.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: generic, icann, top level domains
Reader Comments
Subscribe: RSS
View by: Time | Thread
TLDs
The ICANN proposal is bad on many levels, but a total liberation of the system is neither feasable nor wishable.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
There are already distortions all over the place.
candy.com's recent sale price could easily be justified by the guaranteed #1 ranking it will have in google (saving hundreds of thousands per year in AdWords). .com as default also leads to hundreds of thousands of visits for "free" per month as the word candy typed into the address bar leads to candy.COM
I also don't see how you would administer a free-for-all set of TLDs.
It seems to me that the whole point of a high cost for "registering" a TLD is to make sure an organization is serious about maintaining it. If the idea is to let anyone claim running of a TLD at a similar cost level to registering a domain, that doesn't seem to change the underlying ICANN concept, only to invite chaos.
If the idea is to set up ONE super TLD owner to administer all untaken gTLDs,
and let anyone register for anything in that pool, while that would address one facet of the administration problem, it would overall be worse as among other problems, complete randomness in registrations results in completely meaningless TLDs (say what you will about the others, .org, .edu, and some of the country TLDs still have meaning) leading us straight back to .com again.
[ link to this | view in chronology ]
TLD - have a place...
[ link to this | view in chronology ]
Re: TLD - have a place...
Hell, who would define what "porn" is? Iran or Sweden?
In some places instructional videos on how to check yourself for breast cancer have been called "Porn".
[ link to this | view in chronology ]
Re: TLD - have a place...
Yup, that would be good, then "christian owned" ISPs and bandwidth providers could refuse to provide transit for certain types of data because they don't like it. Imagine what would happen with a .abortion, .naacp, .islam and so many others. Putting everything in neat little boxes is the first step towards blocking the traffic for moral reasons.
Can you imaging all torrent sites on a .torrent domain? you don't think the RIAA and such would have them all blocked out in seconds?
[ link to this | view in chronology ]
Re: TLD - have a place...
But more to the point, if you own a porn site, what incentive do you have to move from your .com or .ru or .job site to .porn? If you already have a thriving business at a well-known address, moving to a relatively unknown TLD isn't going to help you. It's more likely to cost you customers. And who is going to make all of those companies from companies all over the world move their sites? Nobody has the authority to do that.
I used to think like you do, and I'm sure lots of people (politicians especially) still do think that way. But while your solution looks simple on the surface, when you look into the reality of it it's just plainly unworkable.
[ link to this | view in chronology ]
Re: Re: TLD - have a place...
If we stood a chance of stopping bad-players at the source, then you'd think we would see less spam for mycoxafloppin (generic viagra)...
bleh...
[ link to this | view in chronology ]
It is a stupid idea that can end up costing companies tens of thousands of dollars a year having to buy their brandnames out of each of these registry to avoid squatters and other problems.
[ link to this | view in chronology ]
If I could afford thier money grab..
[ link to this | view in chronology ]
Take two:
Walmart.sucks
GW.sucks
work.sucks
yourmom.sucks
M$.sucks
NBA.sucks
I can go on and on.
[ link to this | view in chronology ]
On the whole,"
You followed up rim jobs with on the w(hole).
THAT'S AWESOME!!!!!!!
[ link to this | view in chronology ]
I'm pretty sure...
[ link to this | view in chronology ]
More Ideas of .jobs to register
hand
throat
Dirty
You could probably make some money selling the last one to the discovery channel
[ link to this | view in chronology ]
Beyond the obvious trolling and phishing problems with allowing arbitrary TLDs, I rather doubt that the Internet's DNS infrastructure would handle it well. com. is already unbelievably loaded, and it's fairly surprising that it stays up at all. Adding more entries to the DNS root seems like a bad idea from a technical standpoint.
[ link to this | view in chronology ]
On the other hand, I don't think it would really be the best thing to do. A central regestry that makes TLD decisions is useful. I don't think the current concept is broken, just those implementing it. One thing that has bothered me for some time, is that in the begingin nobody thought that individuals would have their own domain. But many now do. They are not companies, organizations, educational institutions, or anything that is resonably reflected by a normal TLD. Some kind of personal TLD should be created. One that doesn't charge a premium. .NAME and .ME are stupid. They are attempts to do that in a cute way, and are ultimately pretty meaningless terms. Everything has a name, is a name, it's called a domain NAME isn't it. something like .PER for person would be much better.
I guess my point is, i think the rules of the current system are fine, but those working within them are dumb.
[ link to this | view in chronology ]
No friggin way
[ link to this | view in chronology ]
Yippiii
[ link to this | view in chronology ]
It seems like a systems where people register any unicode string as a web address and just dropping TLDs entirely is feasible. It's just that the TLD system is free cash for some and was designed as a free cash cow.
[ link to this | view in chronology ]
TLD TLA never needed.
Also, I don't think any one company should be able to own a URL you can't even trademark. Simple domains like "car" should just bounce back an alphabetical listing of all the domains containing the sub-string "car". This would make the transition easier for some older people, who are more used to yellow pages than google. I understand the technical reasons behind omitting whitespace from URL standards, but they also should have made a rule that typed whitespace in an address bar gets consistently converted to another spacer character, like '-' or '_'. "%20" doesn't make any sense, visually or otherwise.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Unless there is an authority in place to enforce policy with financial penalties, any attempts to use TLDs to categorize sites is bound to fail. Look no further than .NET and its original purpose.
There is still a problem though, that absent some strategy, we have a finite number of 'useful' domain names in a much larger world. Category-based TLDs don't solve this problem. We need a system that accommodates Fred's Pub in Atlanta and Fred's Pub in Chicago. A trivial example but the concept is the same.
Maybe ICANN can solve some real-world problems instead of trying to load their wallets.
[ link to this | view in chronology ]
Get Rid Of TLD Groupings
As someone with a bit of experience looking after DNS registries, I fail to see the usefulness of dividing up domains into grouping at different levels. Look at the gTLDs (.com, .org etc): over 90% of registrations are in .com, so what exactly is the division achieving? It is not conveying any useful information about the meaning of the domain, nor is it fulfilling any technical kind of load-balancing purpose.
Within country-specific TLDs where the country registries impose their own second-level groupings, we see the same sorts of disparities. Thus over 90% of .nz registrations were in .co.nz. Many large countries (e.g. .de, .fr, .ru, .ca) don’t even bother with these second-level groupings, they let anyone register what they like at the second level. Are they causing themselves any problems as a result of this? Doesn’t seem like it.
I don’t see what the technical difference is between letting someone register “name.” as opposed to “name.com”. What is that extra suffix achieving? Nothing, it seems. So why not get rid of it?
[ link to this | view in chronology ]
.com spoiled the marketplace
[ link to this | view in chronology ]