ICANN Officially Approves .jobs and .travel TLD's

EyeMyke writes "As reported on News.com, ICANN has approved the .jobs and .travel domains, and is pending decision on .asia, .mail, .tel, and .xxx. One has to ask 'Will these new domains actually prove useful, or is ICANN just avoiding the real issues confronting them in regards to regulating domain registration?'" We've covered both of these domains before, but it would seem they are even more-approved now, or at least the process is important enough to warrant an official announcement from ICANN.

Comments

I can't believe they added .jobs

[Anonymous Coward]

Why does steve.jobs need a whole TLD? That man sure has an ego!

Re:I can't believe they added .jobs

[Anonymous Coward]

Don't worry - .nojobs is coming out shortly, they are just looking for somewhere to outsource it to.

Names

[DarkHelmet]

I for one can't wait until they approve .xxx. Here are a list of names I would snag up, both xxx and otherwise.

1. whitehouse.xxx (It would of course refer to clinton as president... it HAS to)
2. britneyspears.xxx (Imagine the hits you could get to a site like this)
3. g.mail (nuff said)
4. euthan.asia
5. steve.jobs
6. michaeljackson.xxx (Because I want the FBI at my door)

Not enough

[ites]

TLDs should not be restricted in this way. It creates an artificial shortage which simply acts as a tax. Is there any technical reason why TLDs cannot be created by anyone with the capability?

Re:Not enough

[way2trivial]

and indeed, research public dns servers some time.

you'll find there are MANY alternate tld schemes, including one which was using .biz- and that got destroyed by icann..

http://support.open-rsc.org/.servers/
You can freely use any of these servers instead of your ISP's nameservers if you want to be able to see ALL the domain names on the net, not just the ones in the US Government controlled nameservers. You will, of course be able to see all the "old" domain names like .com, but you'll also be able to see all the ORSC new top level domains, too. If you need instructions on how to use these please see
for one example.

I'm thinking...

[ImaLamer]

blow.jobs
hand.jobs
head.jobs


Wait, let me get my credit card number.

.xxx is potentially bad news.

[\\]

I don't really understand the point of a .xxx tld. You can usually tell from a domain name if you should be loading the url or not, it isn't like everything will be forced to use .xxx once the new tld exists.. unless..

If the point of .xxx is to force adult web sites into using it, how long until adult sites are sued into the ground for using other tlds? What if I'm running a french or italian language site with occasional boobies on it on a .com tld, would some tool force me onto a .xxx? Or even a .uk site?

Blarg. .xxx is perhaps more stupid than the entire artificial tld scarcity bit.

Re:.xxx is potentially bad news.

[ImaLamer]

If the point of .xxx is to force adult web sites into using it, how long until adult sites are sued into the ground for using other tlds? What if I'm running a french or italian language site with occasional boobies on it on a .com tld, would some tool force me onto a .xxx? Or even a .uk site?

Maybe the first step is to just create the xxx domain.

What I'd do (if I was ICANN or whomever):

* Create the xxx tld and then take a select bunch of dictionary words and sell them to pr0n friendly bandwidth/hosting providers.
* Make them the official registratrs for "free.xxx", "anal.xxx" or whatever.
* This creates more imaginative and available pr0n namespace (pr0n is always going to be number one)
* Allow ISP's or OS vendors to block xxx domain
* Stop accepting pr0n sites for .com, .net, .org, (and .edu and .mil)
** Don't get into censorship, unspoken agreement.
* Allow pr0n marketing on other tld's...
** Direct community of pr0n content producers to use the xxx tld when the content is obscene
** Example: playboy.tv is a site about the channel, but it doesn't have nude content. When you want nude you click into xxx tld, unless your parents blocked it.
** Example (2): Playboy.com is a portal to all xxx tlds but contains magazine content; all images are hosted on a xxx tld.
* Only send form letters to .com owners when enough people vote for it or something...

I think we can solve the "censorship" problem a lot easier that way. Make it transparent to content producers who want to go wild and they will adopt it fast, and that is all it takes. Build the porn, they will come (no pun intended).

Some say this approach will cause it to become USENET 2010, but I say that depends on content producers. If they want to create pointy.boobies.bobs.image.xxx let them - but they will learn right away that won't work.

Re:.xxx is potentially bad news.

[houghi]

You can usually tell from a domain name if you should be loading the url or not

whitehouse.org
nice-tits.org

Both not really the sites you might expect

It's not a dupe!

[CHESTER COPPERPOT]

"We've covered both of these domains before, but it would seem they are even more-approved now"

Whoah, back off people he's just applied a +4 magical dupe shield. Now we can't use our 4th level 'Cry of dupe' scroll.

Can we have a .dot, too while you're at it?

[Anonymous Coward]

It would greatly improve slashdot's domain.

http://slashdot.dot sounds great. Like morse code or something.

Re:Are these really useful?

[Anonymous Coward]

I don't know, but I think we ought to add some extra TLDs to make things clear: .spware .scam .ripoff

etc.

And for ICANN, .kerching

No no no

[Anonymous Coward]

What we REALLY need is a .blog and force them all onto it so we can exclude them from search results.

Plus it'd be really easy for goverments to censor them all in one fell swoop! :)

TLDs should be optional

[tehshen]

It's always annoyed me how companies must register two or three domains, to pull in the users that only know .com. If you are a .org (like Slashdot) it's best to register a .com as well, so lost visitors get to your site that way as well; if you're a .co.uk (like the BBC) you also need a .com for the same reason. It shows that the TLD idea wasn't thought through, or was designed to make people register many domains, generating loads of money (not best for the end-user).

Citing monster.com as an example again: it is a jobs site, so it should get a .jobs domain. But not many people have heard of .jobs, so it has to get a .com as well. But why do we need these - what's wrong with 'http://monster' by itself? It should go to the main monster jobs page. If I wanted country-specific sites, I would go to the monster.co.uk or monster.de subdivisions. Categorising things by their status just confuses things.

I shouldn't care whether the site I want is a network, a company, or a non-profit organisation; usually I just want to get to the site.

At this point...

[brainnolo]

At this point the tld does not make any sense anymore. Sites are (were) classified in 2 big categories:

- By language (.it, .de, .au, .uk, etc..)
- By kind (and assumed language was english (.org, .com, .net, .edu)

The first category is ok and works well. But then we come to the second. Having these 4 original category: .com, .org, .net identified Commercial sites, Organization sites (usually non-profit), .net i really never understood and .edu represent educational institues. So the .info was missing (but is largely unused) and they added it. Now .travel, .jobs etc are just confusing. How do i distinguish a travel agency from a informational site on travels from the TLD if they have the same TLD? This put in the same category completely different sites. I really thing the travel agency should be .com and the info site should be .info. Also .biz for me is a misterious entity because it could be interpreted as .com.

So why can't people just use the 2nd level domain to describe who they are? The TLD is already composed of enough entries to distinguish the category.

Slashdot should be .info in my mind. Or .dupes, but that is another story.