Jobs boards slam plan to open up .jobs

Providers of online jobs boards have started to complain to ICANN about plans by registry manager Employ Media to liberalize the .jobs sponsored top-level domain.
It’s rare that an ICANN public comment period attracts a decent amount of comment from outside the usual suspects, but this controversial proposal seems to be heading that way.
Employ Media wants to amend its registry contract to remove the restriction that limits .jobs registrations to the corporate name of employers, a key component of its original commitments.
This has naturally enough stirred debate in the HR community, which now appears to have divided itself into two camps – employers for the changes and jobs boards strongly against.
Several HR professionals with large companies including IBM, BT and Intercontinental Hotels have already filed brief messages with ICANN in support of the .jobs proposal.
Now, the counterargument is being made by a few operators of employer-independent jobs boards, including CollegeRecruiter.com and SalesGravy.com.
The Employ Media proposal would allow it to fulfil its deal with the DirectEmployers Association, which plans to lease thousands of geographic and industry domains.
The DEA plan would essentially be a single jobs site with thousands of domains acting as entry points to vertical listings. Want a job in Chicago? Type in chicago.jobs.
Importantly – and this may explain why HR folk like it – the site would be ad-supported and free for employers to list their openings.
Naturally, existing listings sites see this as an unacceptable competitive threat.
Steve Rothberg, CEO of CollegeRecruiter.com, said in his comment that Employ Media “went out of its way” to avoid getting feedback from existing jobs sites.
The results of an Employ Media survey submitted as part of its application to ICANN make that point pretty clearly.
Todd Goldstein, founder of AccountingJobsToday.com, observed in his comment that the proposal would dilute Employ Media’s original commitment to be “a place for employers” and accused the registry of trying to “route around” its promises to ICANN.

Employ Media asks ICANN for a .jobs landrush

The company behind the .jobs sponsored top-level domain wants to loosen the shackles of sponsorship by vastly liberalizing its namespace.
Employ Media has applied (pdf) to ICANN to get rid of the current restrictions on .jobs domain ownership and open hundreds of thousands of strings to the highest bidder.
The registry wants to amend its contract with ICANN to cut the text that limits .jobs domains to the exact match or abbreviation of a company name, and add:

Domain registrations are permitted for other types of names (e.g., occupational and certain geographic identifiers) in addition to the “company name” designation.

Employ Media is basically asking for the right to open the floodgates to a complete relaunch of the .jobs TLD with very few restrictions on who can register and what strings they can register.
Phase One of the relaunch would be an RFP “to invite interested parties to propose specific plans for registration, use and promotion of domains that are not their company name”.
It sounds a little like the current .co Founders Program, or the marketing initiatives Afilias and Neustar asked for to supplement the auction of their single-character domains.
In practice, I expect that this first phase is when the DirectEmployers Association would expect to grab hundreds of thousands of .jobs domains under its universe.jobs business plan, in which it intends to offer job listings tailored to “city, state, geographic region, country, occupation [and] skill”.
Phase Two would see your basic landrush auction of any premium domains left over.
Phase three would be “A first-come, first-served real-time release of any domains not registered through the RFP or auction processes.”
While I have no strong views on the merits of this particular proposal, I do think that the application and ICANN’s response to it could wind up setting the template for how to operate a bait-and-switch in ICANN’s forthcoming round of new TLD applications.
If you say you want to do one thing with your TLD, and later decide you could make more money doing another, how much will ground will ICANN give when it comes to renegotiating your contract? It will be interesting to find out.
Reactions so far from the HR community have not been positive.
Steven Rothberg of CollegeRecruiter.com wrote that the process by which Employ Media’s sponsor, the Society for Human Resource Management, approved the new proposal “stunk”.
“The only winner here is Employ Media,” he wrote.
Comments posted at ERE.net, which has been on top of this story from the beginning, express what could be easily described as outrage over Employ Media’s plans.
The comment posted by Ted Daywalt of VetJobs.com is especially worth a read.
The Employ Media proposal has been submitted under ICANN’s Registry Services Evaluation Process, which allows comments to be submitted.

.jobs seeks comment on dictionary domains

The sponsor organization behind the restricted .jobs domain is soliciting comment on a plan to substantially liberalize the TLD, allowing generic and two-letter registrations.
The Society For Human Resource Management has published a very brief survey, asking HR folk what they think the pros and cons to the plan might be.
The .jobs domain is run by Employ Media. It’s currently restricted to companyname.jobs registrations, and as such has been predictably unsuccessful.
Now Employ Media wants to branch out into geographical and generic domains. As I reported last month, it looks like it’s trying to remove essentially all of its significant registration restrictions.
The attempt at a policy shift follows a deal made with DirectEmployers Association to monetize geographic domains that raised eyebrows at ICANN late last year.
ERE.net has more here.

.jobs aiming to become a gTLD by the back door?

Employ Media, the company behind the sponsored TLD .jobs, looks like it’s making a play to become a significantly more open gTLD.
The company has proposed a substantial relaxation of its registration policies, based on what may be a loophole in its ICANN registry contract.
Currently, the .jobs namespace is one of the most restrictive TLDs. Only company names can be registered, and registrants have to be approved HR professionals at those companies.
As you might imagine, it’s been phenomenally unsuccessful from a business point of view, with only about 15,000 domains registered since it went live five years ago.
Employ Media now wants to be able to register “non-companyname” domains, and is to apply to its sponsorship body, the Society for Human Resource Management, for permission.
At least, that’s what it looks like. The documents posted over at policy.jobs are pretty opaque.
Indeed, as ERE.net points out, the “proposed amendment” to its charter reads more like a claim that no amendment is required.
The company appears to be pursuing a business model whereby it could auction off (continue reading)