Turkey blocks Google DNS in Twitter crackdown

The Turkish government has reportedly blocked access to Google’s public DNS service from with its borders, as part of its recently instituted censorship of Twitter.
According to local reports, the IP addresses 8.8.8.8 and 8.8.4.4 — Google’s public DNS servers — were banned after they became widely used to circumnavigate blocks on Twitter’s domain names.
Turkish prime minister Recep Tayyip Erdogan last week vowed to “wipe out” Twitter, after the company refused to take down tweets criticizing his government over corruption allegations ahead of an election next week.
Twitter is encouraging Turkish users to use SMS to send tweets instead. Many Turks are also turning to VPNs to evade this bizarre piece of Draconian censorship.

First ICANN gTLD auction slated for June 4

ICANN has published a preliminary schedule for its first new gTLD contention set auctions, which would see the first batch hit the block on June 4 this year.
The plan is now to sell off roughly 20 strings every month, with the last lot going under the hammer in March 2015, a full year from now.
Each contention set, of which there are 233, has been allocated to a batch, ordered by the applicants with the best position in the prioritization queue governing all aspects of the new gTLD program.
But each batch is filled with sets that have either already been resolved or which are currently “ineligible” for auction for one reason or another.
Ineligible contention sets are those that include an application that has, for example, an outstanding change request or a piece of unresolved Governmental Advisory Committee advice.
For example, the 12 applications for .app are scheduled for a July auction, but none of them are going anywhere until the GAC advice against the string goes away.
Naturally enough, ICANN says it’s a preliminary schedule that is subject to a lot of change.
Applicants in contention sets may nevertheless draw comfort from the fact that these auctions finally seem to have firm dates. The auctions were originally slated to start this month.

Community gTLD applicants flunk on “nexus”

The first four Community Priority Evaluation results are in, and all four applicants flunked by failing to prove a “nexus” between the new gTLD string and the community they purport to represent.
No applicant score more than 11 points of the 14 necessary to pass. A total of 16 points are available.
Winning a CPE automatically wins a contention set — all the other applicants for the same new gTLD must withdraw — so it’s a deliberately difficult test.
The scoring mechanism has been debated for years. Scoring 14 points unless the gTLD string exactly matches the name of your organization has always struck me as an almost impossible task.
The first four results appear to substantiate this view. Nobody scored more than 0 on the “nexus” requirement, for which 4 points are available.
The four CPE applicants were: Starting Dot (.immo), Taxi Pay (.taxi), Tennis Australia (.tennis) and the Canadian Real Estate Association (.mls). All four were told:

The string does not identify or match the name of the community, nor is it a well-known short-form or abbreviation of the community.

In some cases, the evaluation panel used evidence from the applicant’s own applicant to show that the string “over-reaches” the community the applicant purported to represent.

The application for .Taxi defines a core community of taxi companies and drivers, as well as peripheral industries and entities.
…
While the string identifies the name of the core community members (i.e. taxis), it does not match or identify the peripheral industries and entities that are included in the definition of the community

In other cases, the panel just used basic common sense. For example, Tennis Australia was told:

Tennis refers to the sport and the global community of people/groups associated with it, and therefore does not refer specifically to the Tennis Australia community.

Starting Dot (.immo) and Taxi Pay (.taxi) both also scored 0 on the “Community Establishment” criteria where, again, 4 points were available.
In that part of the CPE, the applicants have to show that their community is clearly delineated, organized, and long-standing.
In both cases, the panel found that the communities were too eclectic, too disorganized and too young — neither existed before the new gTLD program kicked off in September 2007.
It’s not looking promising for any of the 14 CPE applicants listed by ICANN here. I’ll give $50 to a charity of the applicant’s choosing if any of them scores more than 14 points.

Donuts plays the genericide card in showdown with Belgian government over .spa

Donuts has asked ICANN to approved its .spa new gTLD application over the objections of the Belgian government, saying the town of Spa no longer has exclusive rights to the string.
As we reported at the weekend, Spa is asking Donuts and rival applicant Asia Spa and Wellness Promotion Council for an up to 25% cut of profits from .spa, as well as the right to help manage the TLD at the registry’s expense.
ASWPC has agreed to these terms, but Donuts has not. It says it offered Spa extra protections for sensitive names, but does not want to hand over any managerial control or profit.
Yesterday, Donuts wrote to ICANN (pdf) to say that “spa” is now so generic that no interest would be served by ICANN enforcing the city’s demands. Here’s the meat of it:

While the City of Spa maintains a historical link to the word “spa”, that word long ago evolved as a globally recognized generic term by people who have never even heard of the city of its origin. The public interest served by making that term available to a global community of spa users far outweighs any risk of confusion with the city of the same name. And for those names that may cause confusion, Donuts has provided a rigorous series of additional protections and controls.
The City of Spa gave the word “spa” to the world many centuries ago, and the world has done a great deal with it. Just as attorneys for the City of Spa don’t fly around the world handing cease-­and-desist notices to resort operators and hot-­tub manufacturers, we do not believe it is appropriate for them to overrun ICANN procedure to try to exert control over how that term is used in the Internet’s global addressing system.

I’m going to raise my hand to say that I’d never heard of Spa before this particular controversy arose, and I expect that goes for most of the people reading this article. Donuts surely has a point.
But that’s not to say Spa doesn’t have a point too. There are plenty of governments that managed to squeeze concessions out of applicants for gTLDs matching place names in their territories, with little complaint from applicants; it’s just that the line was drawn at capital cities, something which Spa is not.
Donuts urges ICANN to give no weight to the Spa-ASWPC deal and to move both applications forward to the next stage of the process — contention resolution.
We may see some progress at the ICANN meeting in Singapore next week, when ICANN will surely press the Governmental Advisory Committee for further advice on this string.

Full TMCH database published by registry?

DotBerlin seems to have published the full list of trademarks and other strings protected by the Trademark Clearinghouse.
The list, published openly on nic.berlin as the .berlin new gTLD went through its sunrise period, contains 49,989 .berlin domain names that the registry says are protected.
Neither the TMCH nor DotBerlin have yet responded to a request for comment, so I can’t be 100% certain it’s the TMCH list, but it certainly appears to be. You can judge for yourself here (pdf).
UPDATE: DotBerlin told DI that it is “not the full list but part of a registry-reserved names list” that was published “accidentally” and has now been removed from its web site.
The DotBerlin web site calls the list “MarkenSchutzEngel-Domains” which I believe translates to something like “Trademark Guardian Angel Domains”.
While the TMCH says it has 26,802 listed marks, the document published by DotBerlin seems to also include thousands of strings that are protected under the “Trademark +50” rule.
That allows companies that have won UDRP complaints to have those domains’ second-level strings added to their TMCH records. I see plenty of UDRP’d domains on this list.
The list also seems to include hundreds, possibly thousands, of variant strings that put hyphens between different words. For example, Santander appears to have registered:

a-bank-for-your-ideas
a-bank-for-yourideas
a-bank-foryour-ideas
a-bank-foryourideas
a-bankfor-your-ideas
a-bankfor-yourideas
a-bankforyour-ideas
a-bankforyourideas

I spotted dozens of examples of this, which is permitted under ICANN’s TMCH rules.
There are 2,462 internationalized domain names on the list.
I gather that the full TMCH list today is over 50,000 strings, a little larger than the DotBerlin document.
I took the liberty of comparing the list to a dictionary of 110,000 English words and found 1,941 matches. Strings such as “fish”, “vision”, “open”, “jump” and “mothers” are all protected.
A listing in the TMCH means you get the right to buy a domain matching your mark during new gTLD sunrise periods. Anyone else trying to register a matching name will also generate a Trademark Claims notice.
According to some registries I’ve spoken to today, the TMCH forbids the publication of the full database under the contract that all new gTLD registries must sign.
I’ve no idea whether the publication of a list of .berlin names means that DotBerlin broke its contract.
While the TMCH rules were being developed, trademark owners were adamant that the full database should not be published and should not be easily reverse engineered.
They were worried that to publish the list would reveal their trademark enforcement strategies, which may leave them open to abuse.
(Hat tip to Bart Mortelmans of bNamed.net for the link.)

Panel doesn’t consider TLD in the first-ever new gTLD UDRP case

The first new gTLD domain name has been lost to a UDRP complaint.
The famous German bike maker Canyon Bicycles won canyon.bike from a registrant who said he’d bought the name — and others — in order to protect the company from cybersquatters.
The panelist in the case, WIPO’s Andrew Lothian, declined to consider the fact that the TLD was related to Canyon’s business in making his decision. Finding confusing similarity, he wrote:

The Panel finds that, given the advent of multiple new gTLD domain names, panels may determine that it is appropriate to include consideration of the top-level suffix of a domain name for the purpose of the assessment of identity or similarity in a given case, and indeed that there is nothing in the wording of the Policy that would preclude such an approach. However, the Panel considers that it is not necessary to do so in the present case.

Canyon had argued that the fact that it’s a .bike domain reinforced the similarity between the domain and the mark, but it’s longstanding WIPO policy that the TLD is irrelevant when determining confusing similarity.
The domain was registered under Whois privacy but, when it was lifted, Canyon looked the registrant up on social media and discovered he was very familiar with the world of bikes.
The registrant told WIPO that he’s registered Canyon’s mark “with the best of intentions”.
Apparently, he’s registered more than one famous brand in a new gTLD in the belief that the existence of the program was not wildly known, in order to transfer the domains to the mark holders.
He claimed “that many companies have been content with his actions” according to the decision.
But the fact that he’d asked for money from Canyon was — of course — enough for Lothan to find bad faith.
He also chose to use the fact that the registrant had made no attempt to remove the default Go Daddy parking page — which the registrar monetizes with PPC — as further evidence of bad faith.
The domain is to be transferred.

Roundup: industry reaction to US giving up IANA role

Members of the domain name industry and ICANN community reacted generally positively to the news Friday night that the US will step aside from its central role in ICANN oversight.
Several companies, organizations and individuals issued early statements in response. We present a summary of those to hit the wires so far here.
First, the so-called I* organizations (IETF, IAB, RIRs, ccTLD ROs, ISOC, and W3C), which manage the internet’s various technical functions and standards, issued a joint statement via ICANN:

Our organizations are committed to open and transparent multi-stakeholder processes. We are also committed to further strengthening our processes and agreements related to the IANA functions, and to building on the existing organizations and their roles. The Internet technical community is strong enough to continue its role, while assuming the stewardship function as it transitions from the US Government.

The Domain Name Association’s executive director Kurt Pritz said this:

The DNA welcomes a deliberate, thoughtful process, inclusive of all stakeholder views to determine the future of the IANA function. As our members are some of the most widely recognized customers of IANA, we will be playing an active role in the process moving forward. The US government performs admirably in this role and it is important that any new oversight mechanism perform as reliably and consistently, and in a manner that prevents the Internet from onerous regulations and/or content controls.

New gTLD portfolio applicant Donuts said:

The IANA function is very important to Internet stability, and Donuts supports the multistakeholder approach to managing this vital resource. As the largest applicant for new top-level domains, we look forward to providing a constructive contribution in this multi-stakeholder discussion. It’s critical that any new mechanisms for IANA oversight ensure not only stability and accountability but also uphold the vital public sector role in promoting Internet innovation and openness.

Lisa Hook, CEO of back-end registry provider Neustar, said in a press release:

We share the US government’s view that the time has come for ICANN to convene global stakeholders to develop the policies, procedures, and accountability framework needed to transition ultimate responsibility for the IANA functions, and we look forward to participating in that process.

Back-end and portfolio applicant Afilias said in its own press release:

We endorse the statements of the NTIA and the organizations noted above [the I*s] with respect to the maturation of these organizations and processes, and we are committed to continuing to contribute to the stewardship of the Internet as part of a globally inclusive, open and transparent multi-stakeholder community.

Michele Neylon, CEO of domain name registrar Blacknight Solutions said:

This is an incredibly historic and important day for Internet governance. As a member of the International governance and infrastructure communities I applaud this move away from a single government to a regulating body that represents the interests of the global community. However, the real challenge now lies ahead in identifying and implementing a strong, diverse community to oversee these crucial organizations.

Milton Mueller, the principal academic behind the Internet Governance Project blogged:

IGP has been leading the call for the US government to be consistent about its non-governmental approach to Internet governance since 2005. Naturally, we were gratified to see the Commerce Department finally come around to that position. Far from “giving up” something or “losing control,” the U.S. is sure to find that its policy has gained strength. We have just made it a lot harder for opponents of a free and open Internet to pretend that what they are really against is an Internet dominated by one hegemonic state.

The news broke rather late on a Friday night, with an NTIA press release and hastily convened ICANN press conference, after the story was leaked to the Washington Post.
There hasn’t been much time for formal written reactions yet, but I’m sure more will be forthcoming as people get into work on Monday morning.

Belgians do want a piece of Donuts’ new gTLD action

The Belgian government is blocking approval of Donuts’ bid for the new gTLD .spa until the company agrees to hand over up to 25% of its .spa profits to the community of the city of Spa.
It emerged in a letter from Spa published by ICANN this weekend that the city is also demanding a role in managing the TLD at the registry operator’s expense.
The gTLD has been applied for by Donuts and the Asia Spa and Wellness Promotion Council.
Not only does the string .spa match the name of the city, but also the English dictionary word “spa” is actually named after Spa, which has been known for centuries for its “healing” springs.
Despite this, Spa is not a capital city — it has roughly 10,000 inhabitants — so it does not qualify as a protected geographic string under the rules of ICANN’s new gTLD program.
Spa nevertheless wants a role in the TLD’s management, in order to protect the interests of itself and its local community, and wants some of the profits to benefit its local businesses.
According to the letter (pdf) from Spa outside attorney Phillippe Laurent, ASWPC has already signed a memorandum of understanding with the city. That MoU, published with the letter, states:

The turnover generated by the exploitation of the .SPA registry will be used in priority to defray reasonable out-of-pocket expenses incurred by the City as a result of its participation in the SPARC or any other of its activity related to the management and governance of the .SPA extension.
Additionally, 25% of the net profit generated by the domain names registered in the .SPA registry by any Belgian, Dutch, Luxembourgish, French or German person or entity will be earmarks to be contributed towards Internet and spa & wellness activities development in and for the City of Spa and its region, especially as related to the scope of the “.SPA” TLD, to be directed by the City of Spa.

The deal would also see ASWPC reserve 200 .spa domain names (included potential premiums such as poker.spa and golf.spa) for the city to do with as it pleases.
Donuts has refused to sign the MoU, saying it’s inconsistent with the Applicant Guidebook and sets a “bad precedent”. Spa has therefore refused to endorse its application.
The city has its national government on its side. In the April 2013 Beijing communique of the ICANN Governmental Advisory Committee, the GAC listed .spa as one of several bids needing “further consideration”.
This was reiterated in its Durban and Buenos communiques, with the GAC noting that “discussions” between “relevant parties” were “ongoing”.
Essentially, the GAC is delaying .spa from approval while Spa tries to get Donuts to agree to hand over part of its of .spa profits.
There was a somewhat testy exchange at the Buenos Aires meeting in November, after an ICANN director asked the GAC if it was appropriate for a governmental entity to try to get a financial benefit from an applicant.
The Belgian GAC representative responded later that “no money will flow to the city of Spa”, conceding that “a very small part of the profits of the registry will go to the community served by .spa”.
That now seems to be not entirely accurate.
The MoU sees Spa getting reimbursed for its self-imposed cost of inserting itself into the management of the registry, so some money will flow to it. But it will presumably be revenue-neutral to the city.
The issue of the 25% profit cut is a bit ambiguous though.
While the money would not flow directly into city coffers, the city would get the ability to direct how it was spent. Presumably, it could be spent on projects that Spa locals would otherwise look to the city to pay for.
With Donuts and Spa apparently at an impasse, ICANN recently told the GAC that it won’t sign contracts with either applicant, yet, but that it wants “a timeline for final consideration of the string”.
It also wants the GAC to “identify the ‘interested parties’ noted in the GAC advice.”
With Laurent’s letter and the MoU seemingly spelling out exactly what Spa wants and why, perhaps ICANN can move the issue closer to resolution at the Singapore meeting next week.
Is it a shakedown? Is it appropriate behavior for the GAC to hold an application hostage while it tries to obtain financial benefit for its local businesses? Or is Donuts unreasonably trying to exploit a city’s centuries-old cultural heritage for its own economic gain?

US to give up control over ICANN

In what can only be described as an historic announcement, the United States government tonight said that it will walk away from its control of the DNS root zone.
ICANN CEO Fadi Chehade said during a press conference tonight that the organization has begun a consultation to figure out “accountability mechanisms” that will replace the US role as ICANN’s master.
The news comes in the wake of Edward Snowden’s revelations about US spying, but Chehade and ICANN chair Steve Crocker said that the changes would have been made sooner or later anyway.
So what just happened?
Earlier this evening, the US National Telecommunications and Information Administration announced its “intent to transition key Internet domain name functions to the global multistakeholder community.”
That’s basically referring to the IANA contract, the US government procurement contract under which ICANN has the ability to make changes — essentially by recommendation — to the DNS root zone.
The current version of the contract is due to expire next year, and the hope is that when it does there won’t be any need for a renewal.
Between now and then, the ICANN community (that’s you) is tasked with coming up with something to replace it.
It’s going to be the hottest topic at the ICANN 49 meeting in Singapore, which kicks off a week from now, but it’s expected to be under discussion for much longer than that.
Chehade said during the press conference tonight that the idea is not to create a new oversight body to replace the NTIA. We seem to be talking about “mechanisms” rather than “organizations”.
He also said that the US government has made it plain that any attempt to replace the US with an intergovernmental body (ie, the International Telecommunications Union) will not be considered acceptable.
Whatever oversight mechanism replaces NTIA, it’s going to have to be “multistakeholder” — not just governments.
The root zone is currently controlled under a trilateral relationship between the NTIA, ICANN and Verisign.
Essentially, ICANN says “add this TLD” or “change the name servers for this TLD” and, after the NTIA has approved the change, Verisign implements it on its root zone servers. The other root zone operators take copies and the DNS remains a unique, reliable namespace.
The NTIA has said that it’s going to withdraw from this relationship.
One question that remains is whether Verisign will retain its important role in root zone management.
Chehade appeared slightly (only slightly) evasive on this question tonight, spending some time clarifying that Verisign’s root zone management contract is not the same as its .com contract.
I assume this prevarication was in order to not wipe billions off Verisign’s market cap on Monday, but I didn’t really get a good sense of whether Verisign’s position as a root zone manager was in jeopardy.
My guess is that it is not.
A second question is whether the US stepping away from the IANA function means that the Affirmation of Commitments between the US government and ICANN also has its days numbered.
Apparently it does.
Chehade and ICANN chair Steve Crocker pointed to the ICANN board’s decision a few weeks ago to create a new board committee tasked with exploring ways to rewrite the AoC.
And they said tonight that there’s no plan to retire the AoC. Rather, the idea is to increase the number of parties that are signatories to it.
The AoC, it seems, will be ICANN’s affirmation to the world, not just to the US government.

Common first name lost to URS complaint

The first controversial Uniform Rapid Suspension decision? Probably not.
An self-described “entrepreneur” from Texas has lost control of the domain dana.holdings after a URS complaint filed by Dana Holding, a vehicle component supplier. The domain has been suspended.
It’s the first URS case where the second-level string, in this case “dana”, has a hypothetical multitude of uses not related to the trademark holder’s brand.
The respondent, one Farris Nawas, said in his URS response:

Dana is a common Middle Eastern female name. My family is of Middle Eastern descent. My intention is to establish a holding company in my native country and not in the United States. Upon my registration of the domain name www.Dana.Holdings, I discovered that Dana Holdings is nationally registered in the United states. Out of Courtesy, I approached Dana Limited corporation myself to let them know that I have registered the domain name with the intention of starting my own holding company.

The National Arbitration Forum URS examiner, Darryl Wilson, didn’t buy it
While Nawas was not wrong about Dana being a common first name, I feel I’m on pretty safe ground saying the excuse about starting his own holding company was utter nonsense.
Nawas owns over 200 domains, most of which were registered during the first days of new gTLDs general availability and many of which appear to be cut-and-dried cases of outright cybersquatting.
He was called out by Forbes for registering tommyhilfiger.clothing. I’ve discovered he also owns such as names 4san.ventures and akfen.holdings, among others, which also seem to match company names.
Evidence of a pattern of cybersquatting can be used by URS panels to find bad faith, but that doesn’t seem to have happened in this case.
Rather, Wilson seems to have taken Nawas’ offer to sell the domain to Dana for “an unspecified amount” as evidence that he’s a wrong ‘un. Wilson found his explanation “dubious at best”.