Donuts’ first gTLD sunrise slated for October 29

Donuts has reportedly become the first new gTLD registry to announce its first sunrise periods.
According to BrandShelter, part of the KeyDrive registrar group, nine of Donuts gTLDs will enter sunrise on October 29.
The nine are: .camera, .clothing, .equipment, .guru, .holdings, .lighting, .singles, .ventures and .voyage.
The sunrise periods will last 60 days, BrandShelter said.
I’m seeking confirmation and additional information from Donuts and will provide an update later.
UPDATE: Donuts’ Jon Nevett, in the comments, states that the dates are “estimates”.

Some gTLD applicants welcome ICANN’s clash plan

Some new gTLD applicants, including two of the bigger portfolio applicants, have grudgingly accepted ICANN’s latest name collisions remediation plan as a generally positive development.
ICANN this week scrapped its three-tier categorization of applications, implicitly accepting that it was based on a flawed risk analysis, and instead said new gTLDs can be delegated without delay if the registries promise to block every potentially impacted second-level domain.
You may recall that yesterday dotShabaka Registry said on DI that the plan was a “dog’s breakfast” and criticized ICANN for not taking more account of applicants’ comments.
But others are more positive, if not exactly upbeat, welcoming the opportunity to avoid the six-month delays ICANN’s earlier mitigation plan would have imposed on many strings.
Uniregistry CEO Frank Schilling congratulated ICANN for reframing the debate, in light of Verisign’s ongoing campaign to persuade everyone that name collisions will be hugely risky. He told DI:

There has been a great deal of FUD surrounding name collisions from incumbent registry operators who are trying to negatively shape the utility of the new gTLDs they will be competing against.
I think it was important for ICANN to take control of the conversation in the name of common sense. These types of collisions are ultimately minor in the grand scheme and they occur each and every day in existing namespaces like .com, without the internet melting down.
I think anything that shapes conversation in a way that accelerates the process and sides with common sense is good, I have not yet thought of how this latest change can be gamed to the downside of new G’s.

Uniregistry has 51 remaining new gTLD applications, 20 of which were categorized as “uncalculated risk” and faced considerable delays under ICANN’s original plan.
Schilling’s take was not unique among applicants we talked on and off the record.
Top Level Domain Holdings is involved with 77 current applications as back-end provider — and as applicant in most of them — and also faced “uncalculated” delay on many.
CEO Antony Van Couvering welcomed ICANN’s plan less than warmly and raised questions about the future studies it plans to conduct, criticizing ICANN’s apparent lack of trust in its community:

Basically the move is positive. I characterize it as getting out of jail in exchange for some community service — definitely a trade I’ll make.
On the other hand, the decision betrays ICANN’s basic lack of confidence in its own staff and in the ICANN community. You can see this in the vagueness of the study parameters, because it’s not at all clear what the consultant will be studying or what criteria will be used to make any recommendations — or indeed if anything can be said beyond mere data collection.
But more important, they are hiring an outside consultant when the world’s experts on the subject are all here already, many willing to work for free. ICANN either doesn’t think it can trust its community and/or doesn’t know how to engage them. So they punt on the issue and hire a consultant. It’s a behavior you can see in poorly-run companies anywhere, and it’s discouraging for ICANN’s future.

Similar questions were posed and answered by ICANN’s former new gTLD program supremo Kurt Pritz, in a comment on DI last night. Pritz is now an independent consultant working with new gTLD applicants and others.
He speculated that ICANN’s main concern is not appeasing Verisign and its new allies in the Association of National Advertisers, but rather attempting to head off future governmental interference.
Apparently speaking on his own behalf, Pritz wrote:

The greatest concern is the big loss: some well-spoken individual going to the US Congress or the European Commission and saying, “those lunatics are about to delegate dangerous TLDs, there will be c-o-l-l-i-s-i-o-n-s!!!” All the self-interested parties (acting rationally self-interested) will echo that complaint.
And someone in a governmental role will listen, and the program might be at jeopardy.
So ICANN is taking away all the excuses of those claiming technical risk. By temporarily blocking ALL of the SLDs seen in the day-in-the-life data and by putting into place a process to address new SLD queries that might raise a risk of harm, ICANN is delegating TLDs that are several orders of magnitude safer on this issue than all of the hundreds of TLDs that have already been delegated.

Are you a new gTLD applicant? What do you think? Is ICANN’s plan good news for you?

dotShabaka Diary — Day 16, TMCH testing done

The sixteenth installment of dotShabaka Registry’s journal, charting its progress towards becoming one of the first new gTLDs to go live, written by general manager Yasmin Omer.

Tuesday 8 October 2013
We are pleased to report that IBM notified us on Friday 4 October that TMDB testing is complete. The exact wording of the email is:
“I confirm that all tests are ok and have asked to forward your certification request to ICANN.”
We understand that IBM will now send an email notifying ICANN of successful test completion. The process moving forward isn’t entirely clear and we’re hoping to get some answers from ICANN. In the meantime we continue to wait for the delegation process to commence.
We have not had any ‘next step’ communication from ICANN since PDT was completed on 24 August. Further, we have still not received the Welcome Pack, nor have we received the Media Kit.

Read previous and future diary entries here.

First-come, first-served sunrise periods on the cards

New gTLD registries will be able to offer first-come, first-served sunrise periods under a shake-up of the program’s rights protection mechanisms announced a week ago.
The new Trademark Clearinghouse Rights Protection Mechanism Requirements (pdf) contains a number of concessions to registries that may make gTLD launches easier but worry some trademark owners.
But it also contains a concession, I believe unprecedented, to the Intellectual Property Constituency that appears to give it a special veto over launch programs in geographic gTLDs.
Sunrise Periods
Under the old rules, which came about following the controversial “strawman” meetings late last year, new gTLD registries would have to give a 30-day notice period before launching their sunrise periods.
That was to give trademark owners enough time to consider their defensive registration strategies and to register their marks in the Trademark Clearinghouse.
The new rules give registries more flexibility. The 30-day notice requirement is still there, but only for registries that decide to offer a “Start Date” sunrise period as opposed to an “End Date” sunrise.
These are new concepts that require a bit of explanation.
An End Date sunrise is the kind of sunrise we’re already familiar with — the registry collects applications for domains from trademark owners but doesn’t actually allocate them until the end of the period. This may involve an auction when there are multiple applications for the same string.
A Start Date sunrise is a relative rarity — where registrations are actually processed and domains allocated while the sunrise period is still running. First-come, first-served, in other words.
This gives more flexibility to registries in their launch plans. They’ll be able to showcase mark-owning anchor tenants during sunrise, for example.
But it gives less certainty to trademark owners, which in many cases won’t be able to guarantee they’ll get the domain matching their mark no matter how wealthy they are.
Under the new ICANN rules, only registries operating a Start Date Sunrise need to give the 30 days notice. These sunrise periods have to run for a minimum of 30 days.
It seems that registries running End Date Sunrises will be able to give notice the same day they start accepting sunrise applications, but will have to run their sunrise period for at least 60 days.
Launch Programs
There was some criticism of the old RPM rules for potentially limiting registries’ ability to run things such as “Founders Programs”, getting anchor tenants through the door early to help promote their gTLDs.
The old rules said that the registry could allocate up to 100 names to itself, making them essentially exempt from sunrise periods, for promotional purposes.
New gTLD applicants had proposed that this should be expanded to enable these 100 names to go to third parties (ie, “founders”) but ICANN has not yet given this the green light.
In the new rules, the 100 names still must be allocated to the registry itself, but ICANN said it might relax this requirement in future. In the legalese of the Registry Agreement, it said:

Subject to further review and analysis regarding feasibility, implementation and protection of intellectual property rights, if a process for permitting registry operators to Allocate or register some or all of such one hundred (100) domain names (plus their IDN variants, where applicable) (each a “Launch Name”) to third parties prior to or during the Sunrise Period for the purposes of promoting the TLD (a “Qualified Launch Program”) is approved by ICANN, ICANN will prepare an addendum to these TMCH Requirements providing for the implementation of such Qualified Launch Program, which will be automatically incorporated into these TMCH Requirements without any further action of ICANN or any registry operator.

ICANN will also allow registries to request the ability to offer launch programs that diverge from the TMCH RPM rules.
If the launch program requested was detailed in the new gTLD application itself, it would carry a presumption of being approved, unless ICANN “reasonably determines that such requested registration program could contribute to consumer confusion or the infringement of intellectual property rights.”
If the registry had not detailed the program in its application, but ICANN had approved a similar program for another similar registry, there’d be the same presumption of approval.
Together, these provisions seems to give registries a great deal of flexibility in designing launch programs whilst making ICANN the guardian of intellectual property rights.
Geo gTLDs
For officially designated “geographic” gTLDs, it’s a bit more complicated.
Some geographic gTLD applicants had worried about their ability to reserve names for the governments backing their applications before the trademark owners wade in.
How can the .london registry make sure that the Metropolitan Police obtains police.london before the Sting-fronted pop group (or more likely its publisher) snaps up the name at sunrise, for example?
The new rules again punt a firm decision, instead giving the Intellectual Property Constituency, with ICANN oversight, the ability to come up with a list of names or categories of names that geographic registries will be allowed to reserve from their sunrise periods.
It’s very unusual — I can’t think of another example of this happening — for ICANN to hand decision-making power like this to a single constituency of the Generic Names Supporting Organization.
When GNSO Councillors also questioned the move, ICANN VP of DNS industry engagement Cyrus Namazi wrote:

In response to community input, the TMCH Requirements were revised to allow registry operators the ability to submit applications to conduct launch programs. In response to the large number of Geo TLDs who voiced similar concerns, the IPC publicly stated that it would be willing to work with Geo TLDs to develop mutually acceptable language for Geo TLD launch programs. We viewed this proposal as a way for community members to work collectively to propose to ICANN a possible solution for an issue specifically affecting intellectual property rights-holders and Geo TLDs. Any such proposal will be subject to ICANN’s review and ICANN has expressly stated that any such proposal may be subject to public comment in which other interested community members may participate.

While ICANN is calling the RPM rules “final”, it seems that in reality there’s still a lot of work to be done before new gTLD registries, geo or otherwise, will have a clear picture of what they can and cannot offer at launch.

First gTLD Extended Evaluation results published

ICANN has delivered the first three results of Extended Evaluation for new gTLD applications, all passes.
Dot Registry, which has applied for five corporate-themed gTLDs, flunked its Initial Evaluation on .ltd and .llc back in June on financial grounds, but complained a few days later that ICANN’s evaluators had screwed up.
The company told DI at the time that the two bids used the same Continuing Operation Instrument as applications that had passed IE, and was baffled as to why they failed their financial evaluation.
Both applications have now passed through Extended Evaluation with passing scores, the COI-related score going up from 0 (no COI) to 3 (a perfect score).
Both .ltd and .lcc and still contested, and both also face the uncertainty of Governmental Advisory Committee advice and “uncalculated risk” scores, so the time impact of EE on other applicants is zero.
Also passing through EE this week was Express LLC’s dot-brand bid for .express.
The company had failed on technical grounds in Initial Evaluation, having scored an unacceptable 0 on “Abuse Prevention and Mitigation”. Under EE, this has increased to 2, a pass.
Express is still in contention with Donuts.
This week we also see eight applications, seven of them dot-brands, finally making it through Initial Evaluation: .boehringer, .deloitte, .abbvie, .lamer, .abc, .rogers, .fido and the generic .bar.
The DI PRO Application Tracker and associated tools have now been updated to take account of Extended Evaluation results.

Eleven TLDs get removed from the DNS

ICANN will soon remove 11 experimental internationalized domain name TLDs from the domain name system.
The TLDs, which represent “.test” in nine scripts and 10 languages, were added to the root almost exactly six years ago in preparation for ICANN’s IDN ccTLDs program.
Now that the program is quite mature, with a few dozen IDN ccTLDs live on the internet with no major reported problems, ICANN has decided that the test TLDs are no longer required.
They will be removed from the DNS root zone on October 31, ICANN said.

.pink and two other gTLDs get contracts

ICANN has signed Registry Agreements this week with three new gTLD applicants, covering the strings .wed, .ruhr and .pink.
I would characterize these strings as a generic, a geographic and a post-generic.
regiodot GmbH wants to use .ruhr as a geographic for the Ruhr region of western Germany while Atgron wants to providing marrying couples with .wed for their wedding-related web sites.
Afilias’ .pink belongs to that unusual category of applied-for gTLDs that I’m becoming increasingly interested in: the non-SEO generic.
The vast majority of generic, open gTLDs that have been applied for (mostly by domainer-driven portfolio applicants) in the current round are essentially “keyword” strings — stuff that’s very likely going to prove useful in search engine optimization.
I’m talking here about stuff like .music, .video, .football and .porn. These may prove popular with small business web site owners and domainers.
But there’s another category of generic gTLDs I believe have little SEO value but offer a certain quirky-cool branding opportunity that may prove attractive to regular, non-commercial registrants.
I’d put strings such as .ninja, .bom, .wow, .hot, .love and .pink into this category.
I’m very curious to see how these kinds of strings fare over the next few years, as I suspect we may see many more such applications in future gTLD rounds.

dotShabaka Diary — Day 15, Iran and Name Collisions

The fifteenth installment of dotShabaka Registry’s journal, charting its progress towards becoming one of the first new gTLDs to go live, written by general manager Yasmin Omer.

Thursday 3 October 2013
At a time when ICANN has hit the ‘pause’ button on the new gTLD program in order to assess the impact of “name collisions” on the security and stability of the DNS, we were surprised to see the ICANN Board approve the delegation of ایران., the IDN ccTLD for the Islamic Republic of Iran. While we understand the many distinctions between a ccTLD and a gTLD, the DNS does not make any such distinction.
As we’ve heard from Paul Mockapetris and John Crain recently in their interviews posted on the ICANN website, name collisions (or, more accurately, NX Domain responses) is not a new phenomenon; they have been evident with the introduction of any TLD and with existing TLDs in the root. Experience has shown that steps have been taken to successfully resolve the issues. We understand that ICANN is concerned that the use of NX Domain responses has the potential to create confusion with the introduction of new TLDs into the DNS.
As a contracted party with ICANN, شبكة. (an IDN gTLD) is unable to be delegated as we wait the outcomes of ICANN’s deliberations on name collisions. We have paid our $185,000 application fee, we have undertaken a very resource intensive exercise to ensure a compliant application, we have passed Initial Evaluation, we have signed a registry agreement with ICANN, we have passed pre-delegation testing and yet we sit and wait.
Our understanding of the IDN ccTLD fast track process is that it is much less rigorous, the application fee is voluntary, there is no requirement to enter into a contract with ICANN, the TLD can develop a launch strategy that is not restricted by ICANN mandated rights protection mechanisms, and any contribution to ICANN’s budget is voluntary. But because this is a ccTLD and not a new gTLD, the Board has seen fit to approve this delegation request at this time despite the serious conversation going on in the community about name collisions.
As we said previously, the DNS does not distinguish between a ccTLD or a gTLD, or for that matter an IDN ccTLD or an IDN gTLD. We would appreciate an explanation as to why we sit and wait for delegation while the IDN ccTLD is approved.

Read previous and future diary entries here.

PIR rebrands, talks up “Facebook-like” new gTLDs

Public Interest Registry is dropping the .org from its primary branding in preparation for the launch of its new gTLDs.
CEO Brian Cute said that branding the registry around .org “made a lot of sense when we were a single product company”, but that the time has come to put the PIR name front and center.
The new logo incorporates “Your”, as a result of focus groups, testing and because Cute says “really reflects to us our commitment to the communities we serve”.
PIR has applied to ICANN for .ngo, for Non-Governmental Organization, along with Latin equivalent .ong and four transliterations of .org in Cyrillic, Hindi and Chinese.
Cute told DI that the plan for .ngo and .ong is to have a space in which, unlike .org, the identities of the registrants have been validated.
There’s going to be a searchable directory, a portal, and a “Facebook-like” service for registrants, he said.
“We’re going to have profile pages, so if a registrant doesn’t want to stand up a full website, there’ll be a Facebook-like profile they can populate,” he said.
It sounds like PIR is thinking about a template-driven approach to getting content on .ngo domains, somewhat similar to how .tel works (though it won’t be mandatory in .ngo) or Employ Media’s .Jobs Universe.
But Cute said neither of those concepts inspired PIR, which is building its profile service from scratch.
It’s an interesting way to market a TLD, and I’m positive that PIR won’t be the only new gTLD applicant to do something along these lines.

TLDH has the end in sight, but no revenue

Top Level Domain Holdings made less than $12,000 in the first half of the year, but says its new gTLD business may start generating revenue in the fourth quarter.
In its interim financial results, published this morning, the company also revealed that it plans to launch its own domain name registrar and, via a partnership, web site building tools.
Revenue for the six months to June 30, which was almost all due to monetization of its second-level domains portfolio, was £7,000 ($11,295), compared to £346,000 ($558,000) a year earlier.
TLDH’s loss for the period grew to £1.8 million ($2.9 million) from £1.5 million ($2.4 million).
But in a lengthy statement chairman Fred Krueger assured investors that he is “confident” that the long process of getting TLDH’s applied-for gTLDs to market is drawing to a close.

Looking forward, I am confident that ICANN will broadly continue to sign contracts in line with the timelines we announced in July 2013, allowing .LONDON potentially to begin its launch and initial marketing as early as the first half of 2014. Given the recent signing of contract between .KIWI and ICANN, we may see our first revenues as a back-end registry operator as early as Q4 2013, and revenue from the sale of domain names from our first wholly-owned new gTLD by Q1 2014.

The company currently has interests in 25 uncontested gTLDs and has applied for 48 more, according to Krueger.
With more private and ICANN new gTLD auctions coming soon, TLDH has cash on hand of £7.4 million ($12 million).
Given the average selling price of a new gTLD is currently $1.3 million, there’s seems to be little chance of TLDH securing its entire portfolio of applied-for strings without additional funding.
Losing private auctions could be a way to generate cash to win more than the nine auctions that its $12 million implies, however.
Krueger also revealed TLDH’s revenue plans beyond its Minds + Machines registry services business.

As we enter into this final phase, we are pursuing other potential revenue-producing ventures by developing our own registrar, and, in cooperation with the website-building company Needly, providing a clean path for users to get a complete online solution – a web presence and email, as well as a domain name.

Krueger is also CEO of Needly, which makes a web content management platform.