Latest news of the domain name industry

Recent Posts

Go Daddy objects to numeric .tel domains

Kevin Murphy, November 19, 2010, Domain Registries

Go Daddy has objected to Telnic’s plan to start selling numeric .tel domain names, saying that it, among other things, “smells a lot like gaming”.

Telnic applied to ICANN last month to revise its registry contract to enable it to start selling domains containing numbers and hyphens.

I speculated a month ago that the International Telecommunications Union might object to the proposal, for reasons I explained in some depth.

(Briefly, Telnic won the .tel sponsored TLD partly because it promised for years not to enable domains that could look like phone numbers.)

But the ITU had nothing to say, at least in terms of the ICANN public comment period.

Go Daddy’s Tim Ruiz did object last Saturday on related grounds, telling ICANN:

We believe that this request cannot be granted without requiring the rebidding of the .tel sTLD itself. It is unfair to other applicants and potential applicants to allow an sTLD to change its purpose after the fact.

Since community, purpose, and use were such important aspects of the sTLD allocation decisions it seems inappropriate, fundamentally unfair, and even smells a lot like gaming, to allow an sTLD to change those aspects without an opportunity for others to bid competitively.

In response to Ruiz’s letter, Telnic chief executive Khashayar Mahdavi wrote to ICANN:

The restriction on all-numeric strings has nothing to do with the nature of .tel and was instead a measure put in place to address initial concerns about potential conflicts with ENUM… We believe time and the growing understanding of the .tel technology have proven such a conflict does not exist.

ENUM is a protocol for addressing voice services using the DNS. It uses dots between each individual digit of a phone number, which would be specifically disallowed under Telnic’s plans.

Mahdavi also expressed confusion as to why Go Daddy bothered to object – it is not currently a registry, it does not carry .tel domains and it will presumably not be affected by the relaxation of the .tel rules.

Is it possible the registrar is taking a principled stance?

Ruiz also noted:

We believe that certain other recent requests under the guise of the RSEP [Registry Services Evaluation Process] by sTLDs were also likely inappropriate for similar reasons

He didn’t specify which sTLDs he was talking about. Without wishing to put words into his mouth, I can think of at least one that fits the description.

The Telnic proposal has already passed ICANN’s staff evaluation. I expect it could come before the board next month at its Cartagena meeting.

In separate news, Telnic’s less-controversial proposal to start selling one and two-character .tel domains has now passed its ICANN evaluation (pdf).

Native American domain gives .jobs critics ammo

Kevin Murphy, October 22, 2010, Domain Registries

The coalition of companies opposed to the expansion of the .jobs top-level domain seems to think it has found a ‘gotcha’ in the recent registration of nativeamerican.jobs.

The domain leads to a site listing jobs that are identified, for whatever reason, as being particularly suitable for Native Americans. It’s based on an earlier site at ndianjobs.com

The .jobs TLD was originally intended to allow human resources departments to list their corporate job openings using only their own company name or brand in the domain.

The .JOBS Charter Compliance Coalition, made up of a number of jobs portals including Monster.com, now points to nativeamerican.jobs as an example of .jobs registry Employ Media breaking its charter commitments.

The Coalition wrote to ICANN yesterday in support of its effort to get ICANN to overturn its recent decision on .jobs liberalization.

In August, ICANN told the registry that it could start accepting non-company-name .jobs registrations through a “phased allocation process” that involves an RFP and possibly auctions.

But the Coalition contends that the amended registry contract does not allow Employ Media to break its Charter commitment to restrict registrations to purely human resources registrants.

It could not be clearer that Employ Media is using the Board’s approval of the Phased Allocation Program to transform the fundamental nature of the .JOBS sponsored top level domain from a site for employers to link directly with job seekers to a generic employment services theme park – in clear violation of the .JOBS charter, and without the smallest consideration of third party rights.

These “third-party rights” include the owner of nativeamericanjobs.com, who presumably did not have the chance to register the contested domain.

It’s not clear whether the Coalition statement is entirely correct, however.

Judging from Whois records, the domain nativeamerican.jobs was registered in May, prior to ICANN’s board approving the .jobs registry contract changes.

It was certainly registered prior to the closure of the initial RFP stage of Employ Media’s phased allocation program.

The Coalition has a Reconsideration Request pending. ICANN earlier this week asked Employ Media to respond to 13 questions about its plans.

ICANN asks .jobs registry to explain itself

Kevin Murphy, October 20, 2010, Domain Registries

ICANN has asked .jobs registry manager Employ Media to clarify its plan to lift restrictions on who can register names in its top-level domain.

The ICANN board committee which handles Reconsideration Requests – essentially ICANN’s first-stop appeals court – has sent the registry a list of 13 questions (pdf), apparently distilled from a much longer list (pdf) supplied by the .JOBS Charter Compliance Coalition.

Employ Media wants to be able to start allocating premium generic .jobs domain names to companies via an RFP process and possibly auctions, dropping the rule which states that only companyname.jobs domains are permitted in the TLD.

ICANN’s board of directors approved the company’s plan in August, and Employ Media opened its RFP process shortly thereafter. Then the Compliance Coalition filed its Reconsideration Request.

This ad-hoc coalition comprises a number of employment web sites, such as Monster.com, and the Newspapers Association of America, which believe Employ Media’s plans fall outside its remit and could pose a competitive threat.

It’s common knowledge that the registry was planning to allocate a big chunk of premium real estate to the DirectEmployers Association, which wants to run a massive jobs board called universe.jobs, fed traffic by thousands of generic industry or geographic .jobs names.

Essentially, the Coalition’s questions, echoed by the Board Governance Committee, seem to be a roundabout way of asking whether this violates the .JOBS Charter, which limits the registrant base to corporate human resources departments.

Notably, the BGC wants to know when a universe.jobs promotional white paper (pdf) was produced, how much input Employ Media had in it, and whether the ICANN board got to see it before making its decision.

(A bit of a ludicrous question really, given that the BGC is comprised of four ICANN directors)

It also wants to know which purported “independent job site operators” have welcomed the Employ Media plan (a situation reminiscent of the recent unsuccessful calls for ICM Registry to disclose its .xxx supporters.)

The BGC’s Question 9 also strikes me as interesting, given that it does not appear to be inspired directly by the Coalition’s list of questions:

Please state whether Employ Media took any steps to prevent or interfere with any entity or person’s ability to state its position, or provide information, to the Board regarding amendment of the .JOBS Registry Agreement before or during the 5 August 2010 Board meeting.

I’m now beginning to wonder whether we may see a rare reversal of an ICANN board decision based on a Reconsideration Request.

Monster.com slams .jobs plan

Kevin Murphy, September 17, 2010, Domain Registries

Monster.com and the US Chamber of Commerce have ripped into Employ Media’s plans to liberalize the .jobs top-level domain, with Monster calling the plan “anti-competitive”.

Both organizations have over the last two days said they support the ICANN Reconsideration Request I reported on here.

Essentially, they want ICANN’s board to reverse the decision that would allow Employ Media, the .jobs registry, to start leasing thousands of .jobs domains to whichever company offers it the best deal.

Monster said (pdf) this:

The Board has, without proper consideration and deliberation, consented to the privatization and capture of a sponsored top-level domain (“sTLD”) by a single registrant or small group of registrants.

The jobs boards market is pissed that Employ Media has already made it pretty obvious that it plans to lease thousands of premium domains to the DirectEmployers Association.

Monster claims that the ICANN decision to allow the registry to start accepting “non-company-name” registrations violates the original .JOBS Charter, which limited the registrant pool to companies that wanted to advertise their own vacancies at “company.jobs” URLs.

The company says that the move could create “serious consequences for ICANN’s credibility” as it rolls out new TLDs, on the basis that it sets a bad precedent for ostensibly restricted “community” TLDs:

ICANN will be viewed as willing to tolerate sweeping, unauthorized changes to community based TLDs with no regard for the representations made during the application process.

Monster also says that the board’s decision “has broad anti-competitive implications that were not examined by staff”.

The US Chamber of Commerce, which has previously opposed TLD expansion in principle, has also chipped in (pdf) with its opposition, echoing Monster’s thoughts and adding that the proposed .jobs expansion fails to protect IP rights.

Opponents pick holes in .jobs auction plan

Kevin Murphy, September 6, 2010, Domain Registries

A coalition of jobs web sites has accused Employ Media of trying to violate its own charter with its proposal to open up the .jobs namespace to all-comers.

The newly formed .JOBS Charter Compliance Coalition wants ICANN to reverse its approval of the proposal, which would largely liberalize the .jobs domain.

The ad hoc group, made up of dozens of organizations including the International Association of Employment Web Sites, Monster.com and the Newspapers Association of America, wrote:

ICANN is sanctioning a registry operator’s decision to disregard the commitments contained in its charter, which is the fundamental basis upon which the sTLD was awarded.

ICANN approved Employ Media’s “phased allocation program” last month. It allows the company to loosen its previously restrictive policies on who can register domain names and for what purposes.

The first phase of the program, a request for proposals, has already launched. It would assign premium generic .jobs domains to companies willing to offer interesting business partnerships.

It’s seen by some as an obvious smokescreen for Employ Media to hand thousands of domains to the DirectEmployers Association, which plans a huge free jobs portal called Universe.jobs.

The new Coalition is against this plan, and has submitted a paper (pdf) to ICANN claiming to show how the RFP proves Employ Media wants to violate its sponsorship charter.

Its argument seems to boil down to the fact that the charter limits registrations to active human resources professionals, and that the DEA, like members of the Coaltion, does not fall into that strictly defined category.

The document was filed as an addendum to the Coalition’s reconsideration request, which itself was filed with ICANN last month before the Employ Media RFP was published.