Registry operators for .jobs and .travel get their wishes.
.Jobs and .Travel, two top level domains that probably would have done better if they were released as generic TLDs rather than sponsored, got positive results from ICANN’s board meeting yesterday. At least as far as the registries are concerned.
First, the .jobs registry received permission to effectively open up .jobs. Until now it has been restricted to companies registering just their company name, such as GoDaddy.jobs, for career site purposes.
Now it will be opened up. But don’t expect to be able to go register your favorite generic term in .jobs; the registry has plans to work with out an outside company Direct Employers Association to create thousands (hundreds of thousands?) of job boards on key domains such as city.jobs and vertical.jobs.
Second, .travel registry Tralliance finally got approval to release one and two character .travel domain names. Tralliance made the request in May 2009. Unlike other generic registries that have released these domains, .travel plans to hold some of the domains for itself. This shouldn’t come as a surprise, as a person affiliated with the registry snapped up many of the good generic domain names before .travel was liberalized in the past.
The plan calls for Tralliance to withold 10 domains and then auction some of the others. (Update: This provision for 10 domains was in the original proposal to ICANN, bu apparently was removed later.) But don’t be surprised if it finds a way to siphon off others.
the registry has plans to work with out an outside company Direct Employers Association to create thousands (hundreds of thousands?) of job boards on key domains such as city.jobs and vertical.jobs.
Wasn’t .jobs was setup to be run by an entity providing a service to the worldwide jobs community?
Is the entity now running .jobs now being permitted to compete directly against the same community whose support it elicited and required for its original application?
@ gpmgroup – therein lies the technicality. Apparently it was set up to serve corporations that hire, not headhunters and job boards. So they argued that these job boards will help these corporations hire more people. They don’t care what that means for other job boards/headhunters.
I own a small recruiting firm (8 employees, $1.8 million in revenue) and I can tell you this — we will not be registering a .jobs domain EVER.
With every news TLD or CCLD, .COM’s just become more and more valuable.
http://Steve.JOBS
@Andrew
I wonder if this will be the first nail in the coffin for “generic” new gTLDs?
There has to be serious concerns where a gTLD, even a sponsored gTLD, can be used by a contracted party to secure advantage over other entities looking to compete in the same market place.
The self-management of up to 10 names was removed from the .travel program prior to submission to the board.
@ domains – thanks, I couldn’t find that on ICANN’s web site
“Is the entity now running .jobs now being permitted to compete directly against the same community whose support it elicited and required for its original application?”
Yep.
Jobs.com just increased in value even more!