Consumer Watchdog slams “outrageous” Google and Amazon keyword gTLD bids

Consumer Watchdog, a California-based consumer rights advocacy group, has attacked Google and Amazon’s new gTLD applications in a letter to an influential senator.
The organization has asked Sen. Jay Rockefeller, chair of the Senate Commerce, Science and Transportation Committee, to “thwart” the “outrageous” plans for single-registrant dictionary-word gTLDs.
Google and Amazon have separately applied for dozens of gTLDs — such as .music, .blog and .book — that they would exclusively use to market their own products and services.
Consumer Watchdog said in its letter (pdf):

If these applications are granted, large parts of the Internet would be privatized. It is one thing to own a domain associated with your brand, but it is a huge problem to take control of generic strings. Both Google and Amazon are already dominant players on the Internet. Allowing them further control by buying generic domain strings would threaten the free and open Internet that consumers rely upon. Consumer Watchdog urges you to do all that you can to thwart these outrageous efforts and ensure that the Internet continues its vibrant growth while serving the interests of all of its users.

As we reported yesterday, a number of domain name industry participants are planning to complain to ICANN about these applications on pretty much the same grounds.

Industry objection forming to Google and Amazon’s keyword gTLD land grab

Members of the domain name industry, led by Michele Neylon of Blacknight, plan to complain to ICANN about dozens of single-registrant new gTLD applications filed by Google and Amazon.
The signatories of a new letter are bothered by plans by these companies and others to hold dictionary word gTLDs for their own exclusive use, not allowing regular internet users to register domains.
While the letter does not call out applicants by name, it specifically mentions .blog, .music and .cloud as examples of potentially objectionable single-registrant gTLDs.
Google has applied for .blog and .cloud for its own use, among many others. Amazon has done the same for .cloud and .music and dozens of others. All three are heavily contested.
The letter is so far signed by 13 people, many of whom work for registrars. It states in part:

generic words used in a generic way belong to all people. It is inherently in the public interest to allow access to generic new gTLDs to the whole of the Internet Community, e.g., .BLOG, .MUSIC, .CLOUD. Allowing everyone to register and use second level domain names of these powerful, generic TLDs is exactly what we envisioned the New gTLD Program would do. In contrast, to allow individual Registry Operators to segregate and close-off common words for which they do not possess intellectual property rights in effect allows them to circumvent nation-states’ entrenched legal processes for obtaining legitimate and recognized trademark protections.

The ICANN Applicant Guidebook gives certain special privileges to single-registrant gTLDs.
In its discretion, ICANN can release such registries from the Code of Conduct, which obliges them to treat all accredited registrars on a non-discriminatory basis.
The condition for this exception is that “all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for its own exclusive use”.
The measure was designed to capture dot-brand gTLDs such as .google and .amazon, where only the registry itself controls the second-level domain names.
But Google seems to want to benefit from the exception to the Code of Conduct while still offering second-level domains for use by its customers, at least in some applications.
In its .blog application, for example, it states:

Charleston Road Registry [the applying Google subsidiary] intends to apply for an exemption to ICANN’s Registry Operator Code of Conduct and operate the proposed gTLD with Google as the sole registrar and registrant. The proposed gTLD will specifically align with Blogger, an existing Google product, and will provide users with improved capabilities that meet their diverse needs.
The specialization goal of the proposed gTLD is to provide a dedicated second-level domain space for the management of a userʹs Blogger account.

However, the same application also states:

The mission of the proposed gTLD is to provide a dedicated domain space in which users can publish blogs. All registered domains in the .blog gTLD will automatically be delegated to Google DNS servers, which will in turn provide authoritative DNS responses pointing to the Google Blogger service. The mission of the proposed gTLD is to simplify the Blogger user experience. Users will be able to publish content on a unique .blog domain (e.g., myname.blog) which will serve as a short and memorable URL for a particular Blogger account.

“Google want .blog to be only for Blogspot users, which is insane,” Neylon told DI. “No one company should have control of a generic name space like that.”
“The new TLD project spent thousands of hours working on protecting IP rights, and then you get big companies blatantly abusing the system,” he said.
It’s not at all clear whether Google’s plan for .blog is a permitted use case. Does Google’s plan for .blog and other gTLDs mean third parties will be “controlling” and/or “using” .blog domains?
Or is its plan more akin to a dot-brand offering its customers vanity URLs, such as kevin.barclays or john.citi?
I err to the former interpretation.
When a new gTLD applicant asked ICANN for clarity on this matter last December, ICANN’s response was:

“Exclusive use” has its common meaning. The domain name must be exclusively used by the Registry Operator, and no unaffiliated (using the definition of “Affiliate” in the Registry Agreement) third-party may have control over the registration or use of the domain name.

Neylon said he plans to send the letter to ICANN management, board and new gTLD program Independent Objector next week. There’s no target number of signatures.

ICANN plans meeting on URS amid calls for RFP

ICANN wants to try to put the unresolved issues surrounding the Uniform Rapid Suspension system to bed and is planning a meeting in a couple of weeks time to solicit community input.
According to an email from chief of strategy Kurt Pritz to the GNSO Council and At-Large Advisory Committee, ICANN plans to hold a webinar, with a possible face-to-face option, in about two weeks.
The aim is to sort out the problems with URS, which was originally conceived as a faster, cheaper version of UDRP for clear-cut cases of cybersquatting that don’t require much thought to decide.
It’s currently neither fast enough for the trademark lobby’s liking, nor as cheap as ICANN had hoped.
ICANN had targeted a $300 to $500 fee to file URS complaints, but following conversations with the World Intellectual Property Organization and National Arbitration Forum it realized that the true cost was likely to be as much as triple that amount, more in line with UDRP fees.
The higher than expected costs are largely due to the additional registrant protections that were negotiated into the URS procedure over the last few years, which complicate matters.
At a session at the ICANN meeting in Prague this June, community members tried to figure out ways to make URS cheaper without compromising these protections.
Pritz’s email suggested that some of these ideas might work, but others might run counter to established policy.
Many parties on both side of the fence are coming to the realization that unless URS is in place, new gTLD registries that are contractually obliged to abide by it may not be able to launch.
Yesterday, at Melbourne IT’s summit on trademark protection in Washington DC, there were some calls for ICANN to just issue a request for proposals and see which provider offers the best price.
There are plenty of UDRP lawyers/panelists who believe URS cases can easily be handled in 15 minutes at $200, assuming most of the process is automated and the complaints are kept to a word limit.

ICANN sets deadline to sort out Olympic shambles

ICANN’s board of directors has set itself a deadline to come to a decision on special new gTLD protections for the International Olympic Committee and Red Cross.
It’s looking rather like the IOC, Red Cross and Red Crescent are going to get more of the concessions they’ve been asking for for the last few years, including protection at the second level.
In a resolution passed last week, the ICANN board urged the Generic Names Supporting Organization to make recommendations before January 31 next year, and indicated that it would take matters into its own hands if GNSO consensus cannot be found.

Resolved, the Board thanks the GNSO for its continued attention and ongoing work on this topic, and requests that the GNSO continue its work on a policy recommendation on second-level protections for the IOC and Red Cross/Red Crescent names on an expedited basis.
Resolved (NG2012.09.13.01), if it is not possible to conclude the policy work prior to 31 January 2013, the Board requests that the GNSO Council advise the Board by no later than that date if it is aware of any reason, such as concerns with the global public interest or the security or stability of the DNS, that the Board should take into account in making its decision about whether to include second level protections for the IOC and Red Cross/Red Crescent names

The GNSO has a working group looking at the problem, which is currently deciding whether to recommend starting a formal Policy Development Process.
Given that new gTLDs are expected to start launching in less than a year, and given that PDPs take forever to wrap up, if they ever do, it’s also trying to decide whether to recommend that the IOC/RC/RC marks should be protected in the interim.
Exact matches of the Olympic and Red Cross names, as well as a limited number of translations, would be “reserved” or otherwise removed from sale by each new gTLD registry.
The ICANN board appears to be leaning towards granting these interim protections. In last week’s resolution, it stated:

the Board favors a conservative approach, that restrictions on second-level registration can be lifted at a later time, but restrictions cannot be applied retroactively after domain names are registered.

The IOC/RC/RC debate has been going on since June 2011, when the ICANN board gave the organizations temporary top-level protection in new gTLDs and then passed the hot potato to the GNSO.
The GNSO working group tasked with sorting through the resulting policy mess was subsequently hindered by procedural posturing and acrimony at the Council level and an unreceptive board.
There’s a parallel argument going on at the moment with intergovernmental organizations demanding the same or greater protection, too. Expect IGOs to react with further (mock?) outrage if the IOC/RC/RC get special treatment.
Recently unredacted ICANN board briefing documents reignited the IGO debate last week.

Registries propose PKI-based new gTLD sunrises

Neustar and ARI Registry Services have come up with an alternative to ICANN’s proposed new gTLDs sunrise period process, based on a secure Public Key Infrastructure.
The concept was outlined in a draft paper published today, following an intensive two-day tête-à-tête between domain companies and Trademark Clearinghouse providers IBM and Deloitte last month.
It’s presented as an alternative to the implementation model proposed by ICANN, which would use unique codes and was criticized for being inflexible to the needs of new gTLD registries.
The PKI-based alternative from Neustar and ARI would remove some of the cost and complexity for registries, but may create additional file-management headaches for trademark owners.
Under the ICANN model, which IBM and Deloitte are already developing, each trademark owner would receive a unique code for each of their registered trademarks and each registry would be given the list of codes.
If a trademark owner wanted a Sunrise registration, it would submit the relevant code to their chosen registrar, which would forward it to the registry for validation against the list.
One of the drawbacks of this method is that registries don’t get to see any of the underlying trademark data, making it difficult to restrict Sunrise registrations to certain geographic regions or certain classes of trademark.
If, for example, .london wanted to restrict Sunrise eligibility to UK-registered trademarks, it would have no easy way of doing so using the proposed ICANN model.
But IP interests participating in the development of the Trademark Clearinghouse have been adamant that they don’t want registries and registrars getting bulk access to their trademark data.
They’re worried about creating new classes of scams and have competitive concerns about revealing their portfolio of trademarks.
Frankly, they don’t trust registries/rars not to misuse the data.
(The irony that some of the fiercest advocates of Whois accuracy are so concerned about corporate privacy has not been lost on many participants in the TMCH implementation process.)
The newly proposed PKI model would also protect trademark owners’ privacy, albeit to a lesser extent, while giving registries visibility into the underlying trademark data.
The PKI system is rather like SSL. It used public/private key pairs to digitally sign and verify trademark data.
Companies would submit trademark data to the Clearinghouse, which would validate it. The TMCH would then sign the data with its private key and send it back to the trademark owner.
If a company wished to participate in a Sunrise, it would have to upload the signed data — most likely, a file — to its registrar. The registrar or registry could then verify the signature using the TMCH’s public key.
Because the data would be signed, but not encrypted, registrars/ries would be able to check that the trademark is valid and also get to see the trademark data itself.
This may not present a privacy concern for trademark owners because their data is only exposed to registries and registrars for the marks they plan to register as domains, rather than in bulk.
Registries would be able to make sure the trademark fits within their Sunrise eligibility policy, and would be able to include some trademark data in the Whois, if that’s part of their model.
It would require more file management work by trademark owners, but it would not require a unique code for each gTLD that they plan to defensively register in.
The Neustar/ARI proposal suggests that brand-protection registrars may be able to streamline this for their clients by enabling the bulk upload of trademark Zip files.
The overall PKI concept strikes me as more elegant than the ICANN model, particularly because it’s real-time rather than using batch downloads, and it does not require the TMCH to have 100% availability.
ICANN is understandably worried that about the potentially disastrous consequences for the new gTLD program if it creates a TMCH that sits in the critical registration path and it goes down.
The PKI proposal for Sunrise avoids this problem, as registries and registrars only need a stored copy of the TMCH’s public key in order to do real-time validation.
Using PKI for the Trademark Claims service — the second obligatory rights protection mechanism for new gTLD launches — is a much trickier problem if ICANN is to stick to its design goals, however.
ARI and Neustar plan to publish their Trademark Claims proposal later this week. For now, you can read the Sunrise proposal in PDF format here.

What the hell happened to Go Daddy last night?

Thousands — possibly millions — of Go Daddy customers suffered a four-hour outage last night, during a suspected distributed denial of service attack.
The company has not yet revealed the cause of the downtime, which started at 1725 UTC last night, but it bears many of the signs of DDoS against the company’s DNS servers.
During the incident, godaddy.com was inaccessible. DI hosts with Go Daddy; domainincite.com and secureserver.net, the domain Go Daddy uses to provide its email services, were both down.
The company issued the following statement:

At 10:25 am PT, GoDaddy.com and associated customer services experienced intermittent outages. Services began to be restored for the bulk of affected customers at 2:43 pm PT. At no time was any sensitive customer information, such as credit card data, passwords or names and addresses, compromised. We will provide an additional update within the next 24 hours. We want to thank our customers for their patience and support.

Several Go Daddy sites I checked remained accessible from some parts of the world initially, only to disappear later.
Others reported that they were able to load their Go Daddy webmail, but that no new emails were getting through.
This all points to a problem with Go Daddy’s DNS, rather than with its hosting infrastructure. People able to view affected sites were likely using cached copies of DNS records.
Close to 34 million domains use domaincontrol.com, Go Daddy’s primary name server, for their DNS. The company says it has over 10 million customers.
Reportedly, Go Daddy started using Verisign’s DNS for its home page during the event, which would also point to a DNS-based attack.
The outage was so widespread that the words “GoDaddy” and “DNS” quickly became trending topics on Twitter.
The web site downforeveryoneorjustme.com, which does not use Go Daddy, also went down as thousands of people rushed to check whether their web sites were affected.
Some outlets reported that Anonymous, the hacker group, had claimed credit for the attack via an anonymous (small a) Twitter account.
Companies the size of Go Daddy experience DDoS attacks on a daily basis, and they build their infrastructure with sufficient safeguards and redundancies to handle the extra traffic.
This leads me to believe that either yesterday’s attack was either especially enormous, or that somebody screwed up.
The fact that the company has not yet confirmed that external malicious forces were at work is worrying.
Either way it’s embarrassing for Go Daddy, which is applying for three new gTLDs which it plans to self-host.
Several reports have already speculated that the attack could be revenge for one or more of Go Daddy’s recent PR screw-ups.
The company has promised an update later today.

ICANN dragging its feet on new gTLD refunds?

Former new gTLD applicants are having to wait for months to have their deposits refunded by ICANN, according to two companies that withdrew applications before Reveal Day.
One company withdrew four applications and requested a refund on May 7, some weeks before the TLD Application System closed to new applicants, according to the consultancy Sedari.
But the company, a Sedari client, is still waiting for the return of its $20,000 TAS access fee over four months later, according to Sedari.
Another applicant, GJB Partners, filed a complaint with the California Attorney General in July after waiting for over a month for the refund of a $185,000 application fee.
According to the complaint, the application was withdrawn June 6, a week before Reveal Day, after the company had TAS password problems and suspected foul play.
The company eventually received its refund July 11, shortly after filing the AG complaint.
Sedari’s client has yet to received its refunds, according to the company.
Are any other readers experiencing similar problems?

Secret ICANN briefing fuels IGO new gTLDs debate

The Universal Postal Union, newly installed .post registry manager, has launched a withering attack on ICANN for protecting some intergovernmental organizations and not others.
Its salvo follows the release of briefing materials — previously redacted — that ICANN’s board was given when it approved the new gTLD program at the Singapore meeting in June 2011.
The UPU says that the documents show that ICANN engaged in “ex post facto attempts at justifying legally-flawed decisions” when it decided to give extra protection to the Olympics and Red Cross/Red Crescent movements.
As you may recall, these protections were granted by the ICANN board when the program was approved, following lobbying of the Governmental Advisory Committee by both organizations.
In the current round, nobody was allowed to apply for gTLDs such as .redcross or .olympic, or translations in dozens of languages. There are also ongoing talks about extending this protection to the second level.
Some have argued that this would lead to a “slippery slope” that would resurrect the problematic Globally Protected Marks List, something ICANN and the GAC have denied.
They have maintained that the IOC/RC/RC movements are unique — their marks are protected by international treaty and many national laws — and no other groups qualify.
Other IGOs disagree.
Almost 40 IGOs, including the United Nations and International Telecommunications Union, are lobbying for an additional 1,108 strings to be given the same protection as the Olympics.
If they get what they want, four applied-for gTLDs could be rejected outright and dozens of others would be put at risk of failing string similarity reviews.
According to the UPU’s latest letter, ICANN’s newly disclosed rationale for giving only the IOC/RC/RC organizations special privileges was based on a flawed legal analysis:

most of the recommendations contained in documents such as the Unredacted Paper seem to reflect, in an unambiguous way, ex post facto attempts at justifying legally-flawed decisions in order to narrow even further the necessary eligibility “criteria” for protection of certain strings, apparently so that only two organizations would merit receiving such safeguards under the new gTLD process.

In other words, according to the UPU and others, ICANN found itself in a position in June 2011 where it had to throw the GAC a few bones in order to push the new gTLD program out of the door, so it tried to grant the IOC/RC/RC protections in such a way that the floodgates were not opened to other organizations.
You can read the unredacted ICANN briefing materials here. The UPU letter, which deconstructs the document, is here.
It’s worth noting that the Applicant Guidebook already gives IGOs the explicit right to file Legal Rights Objections against new gTLD applications, even if they don’t have trademark protection.

Big brands ask US for published list of known cybersquatters, other stuff

A public, published list of repeat cybersquatters was among the demands that the trademark lobby took to a meeting with the US government in Washington DC yesterday.
The summit, hosted by the Department of Commerce, was the latest stage in the US government’s response to the campaign for more new gTLD rights protection mechanisms kicked off by the Association of National Advertisers a little over a year ago.
About 30 big brand owners, along with several trade associations and campaign groups, took part.
The Internet Commerce Association somehow managed to blag an invitation too, and was the only representative of domain registrants, according to a blog post by ICA counsel Phil Corwin.
The companies, which included tech companies such as Microsoft, Facebook, AOL, Yahoo and eBay and offline brand owners such as Nike, Coca-Cola, Time Warner and News Corp, met in early June to formulate a set of recommendations to take to Commerce.
These recommendations are outlined in an August 29 letter (pdf), a copy of which DI has obtained.
Notably, the companies asked for a published list of “bad actors” who have repeatedly lost Uniform Rapid Suspension cases. The letter states:

Recidivist bad actors should be tracked via a list of common Respondents and that list should be published and publicly available.

However, we understand that this request is a low-priority item, discussed only briefly yesterday, and that Commerce representatives did not immediately embrace it.
The bulk of the discussions related to tweaks trademark owners want to see in the Trademark Claims service — which alerts them and the registrant when somebody tries to register a potentially infringing domain name — and the URS.
The brand owners want Trademark Claims, which new gTLD registries are only obliged to offer for the first 60 days of general availability, extended for a longer period, possibly up to three years.
On the face of it, this is among the most reasonable longstanding demands from the IP crowd, but ICANN has resisted it to date as it’s worried about creating a monopoly in the pre-existing market for trademark monitoring services.
If the Trademark Clearinghouse is alerting you every time somebody registers a domain name with your brand in it, why pay MarkMonitor or Melbourne IT for the same service?
The letter also says that Trademark Claims should cover brand+keyword registrations, and domains containing registered trademarks, rather than just exact matches.
The worrisome aspect of this request is that there’s quite a high risk of false positives due to run-on words, very short trademarks, acronyms and dictionary words.
Non-commercial ICANN stakeholders dislike this due to the possibility of a chilling effect on free speech, while registries and registrars don’t like anything that puts unnecessary obstacles in the registration path.
With URS, the trademark owners want a full loser-pays system, though they acknowledge that it could raise the filing fee, which is something they don’t want.
To keep costs down, they want a lower filing fee for cases where the registrant does not respond and a URS panelist is not appointed, which seems like a reasonable idea.
The idea of ICANN (and, ultimately, registrants) subsidizing URS fees has also been put forward.
Finally, the trademark owners want registries to implement defensive blocking systems with one-time fees, modeled on the Sunrise B process that ICM Registry used with the launch of .xxx.
Some of the ideas — such as lower filing fees for uncontested URS cases — seem fairly reasonable and I can see them gaining traction.
Others, such as the brand+keyword protections, seem harder to implement and less likely to pass through ICANN unchallenged.
So what happens next? According to ICA’s Corwin:

For their part, the hosts of the meeting [Commerce] listened politely but did not to endorse any of the suggestions, although they did commit to follow-up interagency discussions. It was pointed out that some of the proposals have been raised before and went nowhere within ICANN, and questions were raised about what process would be utilized to place them before the broader ICANN community and its Board. It was also indicated that the U.S. would be reluctant to undertake any unilateral communications on these matters to ICANN’s Board.

Given this reluctance, I wouldn’t be surprised to see some of these ideas bubbling up through the Governmental Advisory Committee instead, as ideas from the US trademark lobby are wont to do.
As with every ICANN meeting, expect to see further discussions in Toronto next month.

Seventh new gTLD bid withdrawn

ICANN has now received seven requests to withdraw new gTLD applications, according to documentation published today.
While we learned today that Google and KSB AG are behind four of the junked bids, the identities of the other three are not yet known.
ICANN has said that it will not reveal the withdrawing applications until all the formalities, such as refunds, have been finalized.
The updated stats came in a slide deck (pdf) set to be used in an ICANN webinar scheduled for noon UTC today.
The slides also reveal the aggregate status of applications’ progress through Initial Evaluation.
As you can see from the slide below, over a quarter of applications have had their String Similarity Review already. Just 65 have had their Geographic Names Review, while 127 and 141 have had their technical and financial evaluations respectively.

ICANN also states that there have been 57 requests for changes to applications — up from 49 at the last count — and that so far nobody has filed a formal objection against any bid.