Latest news of the domain name industry

Recent Posts

Government anger over two-letter domains

Kevin Murphy, March 16, 2017, Domain Policy

ICANN’s Governmental Advisory Committee has clashed with its board of directors over the lack of protections for two-letter domain names that match country codes.

The board has now formally been urged to reconsider its policy to allow registries to sell these names, after angry comments and threats from some GAC members.

Governments from Brazil, Iran, China and the European Union are among at least 10 angered that the names are either not adequately protected or only available for exorbitant prices,

The debate got very heated at ICANN 58 here in Copenhagen on Wednesday morning, during a public session between the GAC and the board, with Iran’s outspoken GAC rep, Kavous Arasteh, almost yelling at Chris Disspain, the board’s point man on the topic.

Arasteh even threatened to take his concerns, if not addressed, to the International Telecommunications Union when it convenes for a plenipotentiary next year.

“Your position is not acceptable. Rejected categorically,” he said.

“The multistakeholder process was not easily accepted by many countries. Still people have difficulty with that,” he said. “We have a plenipotentiary coming in 2018, and we will raise the issue if the matter is not resolved… It is not always commercial, government also has some powers, and we exercise our powers.”

Invoking the ITU is a way to turn a relatively trivial disagreement into an existential threat to ICANN, a typical negotiating tactic of governments that don’t get what they want from ICANN.

The relatively trivial disagreement in this case is ICANN’s decision to allow gTLD registries to release all previously reserved two-letter strings.

In November, ICANN approved a policy that released all two-letter strings on the proviso that registrants have to assert that they will not pass themselves off as affiliated with the countries concerned.

Registries also were given a duty to investigate — but not necessarily act upon — governmental complaints about confusion.

ICANN thinks that this policy is perfectly compliant with the GAC’s latest official advice, supplied following the Helsinki meeting last June, which asked ICANN to:

urge the relevant Registry or the Registrar to engage with the relevant GAC members when a risk is identified in order to come to an agreement on how to manage it or to have a third-party assessment of the situation if the name is already registered.

Disspain patiently pointed out during Wednesday’s session that governments have no legal rights to their ccTLD strings at the second level, and that most of the complaining governments don’t even protect two-letter strings in their own ccTLDs.

But some GAC reps disagreed.

China stated (via the official interpreter): “We believe the board doesn’t have the right or the mandate to decide whether GAC members have the right over two-character domain names.”

While no government spoke in favor of the ICANN policy on Wednesday, the complaining governments do appear to be in a minority of the GAC.

Despite this, they seem to have been effective in swaying fellow committee members to issue some stern new advice. The Copenhagen communique, published last night (pdf), reads:

a. The GAC advises the ICANN Board to:

I. Take into account the serious concerns expressed by some GAC Members as contained in previous GAC Advice

II. Engage with concerned governments by the next ICANN meeting to resolve those concerns.

III. Immediately explore measures to find a satisfactory solution of the matter to meet the concerns of these countries before being further aggravated.

IV. Provide clarification of the decision-making process and of the rationale for the November 2016 resolution, particularly in regard to consideration of the GAC advice, timing and level of support for this resolution.

ICANN is being compelled to retroactively revisit a policy that was issued in compliance with previous GAC advice, it seems.

The next ICANN meeting is being held in Johannesburg in June, so the clock is ticking.

Two-letter domains are valuable properties even in new gTLDs. With each expected to sell for thousands, two-letter names are likely to be a multimillion dollar windfall for even moderately sized portfolio registries.

In rare public session, ICANN approves sexual harassment policy

Kevin Murphy, March 11, 2017, Domain Policy

ICANN’s board of directors this afternoon approved an anti-harassment policy designed to protect community members from unwanted sexual attention.

It’s the policy inspired by the now infamous Cheesesandwichgate incident at the Marrakech meeting a year ago.

But general counsel John Jeffrey noted that there have been multiple similar complaints to the Ombudsman over the last year or so, possibly as a result of increased awareness that such complaints are possible.

While the text of the resolution has not yet been published, I believe it’s approving a lightly modified version of the policy draft outlined here.

That draft sought to ban activities such as “sexually suggestive touching” and “lewd jokes” at ICANN meetings. A laundry list of characteristics (such as race, gender, disability) were also given special protection.

What’s possibly more interesting than the new policy itself is the manner in which the policy was approved.

It was the first time in goodness knows how many years — definitely over 10, and I’m tempted to say over 15, but nobody seems to know for sure — that the ICANN board has deliberated on a resolution in public.

By “in public” I mean the 30-minute session was live-streamed via Adobe Connect from an undisclosed location somewhere at ICANN 58, here in Copenhagen. An in-person live audience was not possible for logistical reasons, I’m told.

Apart from the first few years of ICANN’s existence, its public board meetings have usually been rubber-stamping sessions at the end of the week-long meeting, based on discussions that had gone on behind closed doors days earlier.

So today’s session was a significant attempt to increase transparency that is likely to be welcomed by many.

Unfortunately, its existence could have been communicated better.

For the first 15 minutes, there were no more than 19 people in the Adobe room, and I believe I may have been the only one who was not ICANN staff or board.

After I tweeted about it, another 10 or so people showed up to listen.

Given that increased board transparency is something many sections of the community have been clamoring for for years, one might have expected a bigger turnout.

While the meeting had been prominently announced, it was not listed on the official ICANN 58 schedule, so had failed to make it onto the to-do lists of any of the iCal slaves pottering around the venue.

The session itself came across to me as a genuine discussion — not stage-managed or rehearsed as some had feared.

Directors raised issues such as the possible increased workload on the Ombudsman, the fact that the current Ombudsman (or Ombudsperson, as some directors referred to him) is male, and the availability of female staff members to receive “sensitive” complaints.

Today’s open session is part of a “pilot” and is due to be followed up on Sunday with another, which will discuss ICANN’s fiscal 2018 operating plan and budget.

Again, turning up to watch in person will not be possible, but the 90-minute session will be streamed live at 0745 UTC here.

The first in the pilot program, which even I missed, was in Brussels in September.

Schneider quits as chair of GAC

Kevin Murphy, March 11, 2017, Domain Policy

ICANN’s Governmental Advisory Committee is looking for a new chair.

Incumbent Thomas Schneider intends to leave the role before his current two-year term expires, he told GAC members assembled here at the ICANN 58 public meeting in Copenhagen this afternoon.

Schneider said that his boss at the Swiss government agency at which he works recently retired and that he has been appointed his successor.

From April, he’ll become vice director of the Federal Office of Communication, responsible for international affairs, he said.

The increased workload, including organizing the next Internet Governance Forum in Geneva, means he will no longer be able to devote his time to chairing the GAC, he said.

Schneider’s first two-year term as GAC chair started at the beginning of 2015. He was reelected to the position for a second term last November.

His replacement will be elected at the ICANN 60 meeting in Abu Dhabi this coming October, at which point Schneider will hand over the reins.

Papac named ICANN’s first complaints officer

Kevin Murphy, March 10, 2017, Domain Policy

ICANN has named its first-ever complaints officer.

It’s Krista Papac, a long-time domain industry participant who’s been working for ICANN, most recently as director of registry services and engagement, since 2013.

She’s previously worked for the registries Verisign, ARI (now part of Neustar) and data escrow agent Iron Mountain.

Her job will be to “provide a centralized mechanism to track complaints received about the ICANN organization” and is “an additional way for the ICANN organization to be accountable for and transparent about its performance”.

Her input will come largely from existing accountability mechanisms — the Ombudsman, Requests for Reconsideration, the Independent Review Process, and the contractual compliance department.

She’ll report to general counsel John Jeffrey.

The hire, and the reporting line, has already proved somewhat controversial.

Domain investor trade group the Internet Commerce Association today said that it was skeptical that a complaints officer reporting to the general counsel could be effective.

ICA added in a blog post that, while it has no beef with Papac, it had concerns that an insider had been hired into the role.

How can any individual who has worked for years within ICANN’s [Global Domains Division] be expected to cast prior experience and relationships aside to thoroughly and dispassionately investigate a complaint brought against GDD actions generally, or those of a specific member of the GDD staff?

Papac’s new role follows Jamie Hedlund’s internal move from head of government relations to VP of contractual compliance and consumer safeguards, in January.

How .com became a restricted TLD

Verisign has been given approval to start restricting who can and cannot register .com and .net domain names in various countries.

Customers of Chinese registrars are the first to be affected by the change to the registry’s back-end system, which was made last year.

ICANN last week gave Verisign a “free to deploy” notice for a new “Verification Code Extension” system that enables the company to stop domains registered via selected registrars from resolving unless the registrant’s identity has been verified and the name is not on China’s banned list.

It appears to be the system Verisign deployed in order to receive its Chinese government license to operate in China.

Under Verification Code Extension, Verisign uses ICANN records to identify which registrars are based in countries that have governmental restrictions. I believe China is currently the only affected country.

Those registrars are able to register domains normally, but Verisign will prevent the names from resolving (placing them in serverHold status and keeping them out of the zone file) unless the registration is accompanied by a verification code.

These codes are distributed to the affected registrars by at least two verification service providers. Verisign, in response to DI questions, declined to name them.

Under its “free to deploy” agreement with ICANN (pdf), Verisign is unable to offer verification services itself. It must use third parties.

The company added the functionality to its .com and .net registry as an option in February 2016, according to ICANN records. It seems to have been implemented last July.

A Verisign spokesperson said the company “has implemented” the system.

The Verification Code Extension — technically, it’s an extension to the EPP protocol pretty much all registries use — was outlined in a Registry Services Evaluation Process request (pdf) last May, and approved by ICANN not long after.

Verisign was approved to operate in China last August in the first wave of gTLD registries to obtain government licenses.

Under Chinese regulations, domain names registered in TLDs not approved by the government may not resolve. Registrars are obliged to verify the identities of their registrants and names containing certain sensitive terms are not permitted.

Other gTLDs, including .vip, .club, .xyz .site and .shop have been granted approval over the last few months.

Some have chosen to work with registration gateway providers in China to comply with the local rules.

Apart from XYZ.com and Verisign, no registry has sought ICANN approval for their particular implementation of Chinese law.

Because Chinese influence over ICANN is a politically sensitive issue right now, it should be pointed out that the Verification Code Extension is not something that ICANN came up with in response to Chinese demands.

Rather, it’s something Verisign came up with in response to Chinese market realities. ICANN has merely rubber-stamped a service requested by Verisign.

This, in other words, is a case of China flexing market muscle, not political muscle. Verisign, like many other gTLD registries, is over-exposed to the Chinese market.

It should also be pointed out for avoidance of doubt that the Chinese restrictions do not apply to customers of non-Chinese registrars.

However, it appears that Verisign now has a mechanism baked into its .com and .net registries that would make it much easier to implement .com restrictions that other governments might choose to put into their own legislation in future.