Portfolio gTLD applicant Donuts has hired Michele Jourdan, who until last week was head of new gTLD communications at ICANN.
She has joined the company as director of sales and marketing, according to her LinkedIn profile.
Applicants and others following the program closely will remember her from the regular update videos published by ICANN.
She worked for ICANN for almost five years, but only in the last year or so started to take a visible front seat role in interactions with community members. I understand she left ICANN a week ago.
Jourdan is not the first ICANN alum Donuts has taken on.
Its CFO is former ICANN CFO Kevin Wilson, and we recently learned that former new gTLD program manager Kurt Pritz has been recruited, non-exclusively, as a consultant.
ICANN’s Ombudsman Chris LaHatte has received complaints about some new gTLD objections that were apparently filed after the submission deadline but are being processed anyway.
Two companies have officially called on LaHatte to tell ICANN that “late complaints should not be received on the basis that the deadlines were well advertised and achievable”.
The issue seems to be that ICANN had set a deadline of 2359 UTC March 13 for objections to be filed, and some of them arrived slightly late.
The delays appear to have been a matter of mere minutes, and blamed on latency caused by heavy email attachments and other technical problems.
According to ICANN, the dispute resolution providers decided to give objectors a five-minute grace period, essentially extending the deadline from 2359 UTC to 0004 UTC the following day.
The recipients of these objections clearly now want to use this technicality to kill off the objections, avoiding the cost of having to defend themselves.
In a set of answers to questions posed verbally in Beijing last month, published last week (pdf), ICANN said:
ICANN is confident that the Dispute Resolution Service Providers are complying with the guidelines in the [Applicant Guidebook].
I don’t know which applications are affected by the issue, but the question at the Beijing public forum was posed by new gTLD consultant Jim Prendergast of the Galway Strategy Group.
He received applause, so I guess he wasn’t the only person in the room with an interest in the subject.
LaHatte, on his blog, is looking for feedback before making his decision.
WellPoint, a major North American health insurance provider, has dropped its application for .anthem, a proposed dot-brand gTLD.
It’s the fifth application to be withdrawn this week and the 64th to be withdrawn overall. The pull-out rate from the original 1,930 applications now stands at roughly 3.3%.
It’s also the second bid to be yanked by WellPoint. It pulled its application for .caremore in December, before even receiving an evaluation prioritization number in The Draw.
Wellpoint, which did not apply for .wellpoint, has no applications remaining in the program.
Anthem is a brand used by WellPoint to provide health insurance, mainly in California.
It’s also the original name of the company, which entered its present incarnation with the merger of WellPoint Health Networks Inc and Anthem Inc in 2004.
The gTLD was to be a straightforward .brand with a Neustar back-end. It was uncontested and had no public comments, objections or Governmental Advisory Committee to stand in its way.
It had a very low priority number, however, and was not due to receive its Initial Evaluation results until the final week of the schedule.
Four new gTLD applications have been withdrawn so far this week, including the first to come from .info operator Afilias.
Afilias has pulled its bid for .mail — the second applicant to do so — due to the number of competitors for the string.
A spokesperson said in an email:
The company felt there were simply too many groups in contention for this domain and we’d rather focus our energy supporting and helping to grow the .POST domain, for which we are the [technical services provider].
There are now five applicants competing for the string, including Google, Amazon and Donuts, but they’re all facing objections from the United States Postal Service and the Universal Postal Union, which runs .post.
Elsewhere this week, Directi has ended its bid for .movie, a contention set with seven other bidders.
The company declined to comment on the reasons for the withdrawal, so we probably can’t entirely rule out some kind of partnership with one or more other applicants.
Today we’ve also seen the withdrawal of applications for .ltd and .inc, both belonging to a Dutch company called C.V. TLDcare. I don’t know much about these guys, other than it used OpenRegistry as its technical partner and that .inc and .ltd were its only two applications.
Interesting fact: not a single “corporate identifier” application (.llp, .corp, .ltd, .inc, .llc) has passed Initial Evaluation yet, but seven applications have been withdrawn.
It’s a controversial category, with many US state attorneys general very unhappy about any of these strings being delegated without safeguards.
The latest four withdrawals bring the total to 63.
The International Organization for Standardization, known as ISO, doesn’t want to have its acronym blocked in new gTLDs by the International Sugar Organization.
ISO has told ICANN in a letter that demands for special favors coming from intergovernmental organizations, via the Governmental Advisory Committee, should be rejected.
Secretary general Rob Steele wrote:
We have very strong concerns with the GAC proposal, and firmly oppose any such block of the acronym “ISO.”
To implement a block on the term “ISO” (requiring its release be permitted by the International Sugar Organization) disregards the longstanding rights and important mission of the International Organization for Standardization. To be frank, this would be unacceptable.
please be assured that the International Organization for Standardization is prepared to take all necessary steps if its well-known short name is blocked on behalf of another organization.
For several months the GAC has argued that IGOs are “objectively different category to other rights holders, warranting special protection from ICANN” in new gTLDs.
Just like the “unique” Olympics and Red Cross were in 2011.
The GAC proposes that that any IGO that qualifies for a .int address (it’s a number in the hundreds) should have its name and acronym blocked by default at the second level in every new gTLD.
But ICANN pointed that this would be unfair on the hundreds (thousands?) of other legitimate uses of those acronyms. It gave several examples.
The GAC in response said that the IGOs would be able to grant consent for their acronyms to be unblocked for use by others, but this opened up a whole other can of implementation worms (as the GAC is wont to do).
ICANN director Chris Disspain of AuDA said in Beijing:
Who at each IGO would make a decision about providing consent? How long would each IGO have to provide consent? Would no reply be equivalent to consent? What criteria would be used to decide whether to give consent or not? Who would draft that criteria? Would the criteria be consistent across all IGOs or would consent simply be granted at the whim of an IGO?
In the GAC’s Beijing communique, it seemed to acknowledge this problem. It said:
The GAC is mindful of outstanding implementation issues and commits to actively working with IGOs, the Board, and ICANN Staff to find a workable and timely way forward.
The GAC insists, however, that no new gTLDs should be allowed to launch until the IGO protections are in place.
Given the amount of other work created for ICANN by the Beijing communique, I suspect that the IGO discussions will focus on implementation detail, rather than the principle.
But the principle is important. IGOs are not typically victims of pernicious cybersquatting. If they deserve special protections, then why don’t trademark owners that are cybersquatted on a daily basis?
ISO standardizes all kinds of stuff in dozens of sectors. In the domain name space, it’s probably best known for providing ICANN with ISO 3166-1 alpha-2, the authoritative list of two-letter strings that may be delegated as ccTLDs.
The International Sugar Organization is very important too, probably, if you’re in the sugar business.
Does it need better brand protection than Microsoft or Marriott or Facebook or Fox? Is anyone going to want to cybersquat the International Sugar Organization, really?
If it does deserve that extra layer of protection, should that right trump the more-famous ISO’s right to register domains matching its own brand?