DotConnectAfrica still barking mad after IRP win

DotConnectAfrica thinks it is going to get the .africa gTLD, following its successful Independent Review Process case against ICANN.
In a press release today, the company hailed last week’s ruling as a “resounding victory”.
DCA CEO Sophia Bekele is quoted as saying:

Going forward, we now expect ICANN to accept the binding IRP outcome, refrain from any further plans to delegate .Africa to the ZA Central Registry who should now be removed immediately from the new gTLD program; and cooperate fully with DCA Trust to ensure that the IRP Panel ruling is implemented so that .Africa can be delegated to DotConnectAfrica Trust

That’s right, Bekele reckons the IRP win means ICANN has to kick rival .africa applicant ZACR — which has already signed a Registry Agreement for the string — out of the new gTLD program.
Needless to say, it doesn’t.
The IRP panel refused DCA’s demands that ZACR be kicked out, and by ruling against DCA on a number of other counts, it essentially signed its application’s death warrant.
Bekele goes on to make three startling assertions about the case that have little to no basis in the IRP panel’s ruling:

During the IRP, DotConnectAfrica Trust clearly established three major findings: that ZA Central Registry lacked any valid endorsements for the .Africa string that it applied for; and that the purported Governmental Advisory Committee Objection Advice against our .Africa application was not by consensus; and that the ICANN Board had seriously erred in accepting the GAC Advice. The truth has prevailed and we are absolutely happy with the IRP Panel decision.

“I also give thanks to God for helping to correct this act of victimization that was committed against DCA Trust,” she added.
I’m not making that up. She really said that.
In Bekele’s opinion, DCA “established” three major findings, but “alleged” would be a better word. The IRP panel largely disagreed with or ignored the claims.
First, there’s nothing in the IRP’s decision that shows ZACR “lacked any valid endorsement” for its .africa bid.
ZACR has the unambiguous support of the African Union and says on its web site it has backing from 78% of African nations. The IRP declaration doesn’t even mention these endorsements, let alone question them.
Second, the IRP panel does not say that the GAC’s advice against DCA’s application lacked consensus. It says it lacked fairness and transparency, but did not dispute that it had consensus.
Third, the IRP did not conclude that ICANN should not have accepted that GAC advice, just that it should have carried it a bit more due diligence.
Finally, there’s nothing in the IRP’s declaration that gives DCA a chance of winning the .africa gTLD. In fact, the panel specifically decided not to give DCA that chance.
The closest the panel came to addressing any of DCA’s myriad accusations of ICANN wrongdoing is described in its ruling:

DCA Trust has criticized ICANN for its various actions and decisions throughout this IRP and ICANN has responded to each of these criticisms in detail. However, the Panel, having carefully considered these criticisms and decided that the above is dispositive of this IRP, it does not find it necessary to determine who was right, to what extent and for what reasons in respect to the other criticisms and other alleged shortcomings of the ICANN Board identified by DCA Trust.

So what happens to .africa now?
ICANN’s board of directors will discuss the IRP declaration at its next meeting, July 28, so we don’t yet know for certain how things will proceed.
However, some things seem safe bets.
The IRP panel suggested that ICANN should continue to refrain from delegating .africa, which has been on hold since May 2014, to ZACR. I think it likely that ICANN will follow this recommendation.
It also seems possible that ICANN may decide to reconsider (that is, consider again, rather than necessarily overturn) its decision to accept the GAC’s consensus objection to DCA’s .africa bid.
The panel’s key criticism of ICANN was that it failed to seek a rationale from the GAC for its objection. So ICANN may decide to seek such a rationale before reconsidering the advice.
The panel also told ICANN that DCA’s application, which had been rejected, should re-enter the application process.
Assuming ICANN accepts this recommendation (and I think it will, given the political climate), the first step would to be for DCA to finish its Initial Evaluation. ICANN rejected the DCA bid, based on GAC advice, before the IE panels finalized their evaluation DCA’s application.
Part of the IE process is the Geographic Names Review, which determines whether a string is “geographic” under ICANN’s definition and whether the applicant has the necessary support — 60% of national governments in .africa’s case — to be allowed to proceed.
DCA does not have this support, and it knows that this means its application is on life support.
It had asked the IRP panel to rule that ICANN should either give it 18 months to try to gather support, or to rule that it already has the support, essentially trying to lawyer itself into a position where it had a shot of winning .africa.
But the panel rejected both of these demands.
While DCA seems to have given up trying to convince people that its 2009 letter of support from the AU is still valid, it still holds that a 2008 letter from the executive secretary of the United Nations Economic Commission for Africa shows the requisite 60% support.
I don’t know whether this letter was ever formally withdrawn, but UNECA is today listed as a ZACR supporter.
However, even if the Geographic Names Panel ruled that DCA had passed its 60% threshold, the application would still fail the geographic review.
The rules state that “there may be no more than one written statement of objection” from an affected government, and DCA received GAC Early Warnings from 16 national governments as well as the AU itself.
No matter what DCA says in its press releases now, its application is still doomed.

New gTLD program thrown into chaos as ICANN loses .africa case

ICANN has been opened up to a world of hurt after an independent panel of judges ruled that the organization broke its own bylaws when it kicked DotConnectAfrica’s .africa bid out of the new gTLD program.
The what-the-fuck ruling cuts to the very heart of how ICANN deals with advice from its Governmental Advisory Committee, which comes out of the case looking like a loose canon with far too much power to sway the ICANN board.
Witness testimony published in the panel’s opinion sheds humiliating light on the GAC’s self-defeating habit of supplying ICANN with deliberately vague advice, a practice described by its former chair under oath as “creative ambiguity”.
The ruling does not, however, give DCA a serious shot at winning the .africa gTLD, which has already been contracted to rival ZA Central Registry. More delay is, however, inevitable.
The Independent Review Panel said:

the Panel is of the unanimous view that certain actions and inactions of the ICANN Board (as described below) with respect to the application of DCA Trust relating to the .AFRICA gTLD were inconsistent with the Articles of Incorporation and Bylaws of ICANN.

It also unanimously ruled that ICANN should un-reject DCA’s application and allow it to continue through the application process and that ICANN should bear the full $600,000+ cost of the IRP, not including DCA’s legal fees.
It’s an important ruling, especially coming as ICANN seeks to extricate itself from US government oversight, because it implicitly calls on ICANN’s board to treat GAC advice with much less deference.
What’s the backstory?
DCA and ZACR have competing applications for .africa, which is a protected geographic string.
Under new gTLD program rules, only an applicant with support from over 60% of African national governments can be approved. ZACR’s support far exceeds this threshold, whereas DCA enjoys little to no government support at all.
The ICANN board’s New gTLD Program Committee rejected the DCA bid in June 2013, before its Initial Evaluation (which includes the Geographic Names Review) had been completed, based on the GAC’s April 2013 Beijing communique advice.
That advice invoked the GAC’s controversial (and vaguely worded) powers to recommend against approval of any application for any reason, as enshrined in the Applicant Guidebook.
A subsequent Request for Reconsideration (IRP lite) filed by DCA was rejected by ICANN’s Board Governance Committee.
An IRP is the last avenue community members have to challenge ICANN’s actions or inaction without resorting to the courts.
DCA filed its IRP complaint in October 2013 and amended it in January 2014, claiming ICANN broke its own bylaws by rejecting the DCA application based on GAC advice.
Despite the IRP, ICANN went ahead and signed a Registry Agreement with rival ZACR in the May and was just days away from delegating .africa when the IRP panel ordered the process frozen.
The case dragged on, partly because one of the original three-person panel died and had to be replaced, the delay causing much consternation among African GAC members.
What did the IRP panel finally rule?
Yesterday’s ruling avoided deciding on or even commenting on any of DCA’s crazy conspiracy theories, instead limiting itself to the question of whether ICANN’s board and committees acted with bylaws-mandated transparency, fairness and neutrality.
It found that the GAC itself did not act according to these principles when it issued its Beijing advice against DCA.
It found that ICANN did not “conduct adequate diligence” when it accepted the advice, nor did the BGC or NGPC when they were processing the RfR.

In light of the clear “Transparency” obligation provisions found in ICANN’s Bylaws, the Panel would have expected the ICANN Board to, at a minimum, investigate the matter further before rejecting DCA Trust’s application.

ICANN did not do that, the panel decided, so it broke its bylaws.

both the actions and inactions of the Board with respect to the application of DCA Trust relating to the .AFRICA gTLD were not procedures designed to insure the fairness required… and are therefore inconsistent with the Articles of Incorporation and Bylaws of ICANN.

Does this mean DCA gets .africa?
No. The IRP panel ruled that DCA’s application must re-enter the application process, presumably at the point it exited it.
DCA’s application never had a final Initial Evaluation result issued. If it were to re-enter IE today, it would certainly be failed by the Geographic Names Panel because it lacks the requisite support of 60% of African governments.
DCA wanted the panel to rule that it should have 18 months to try to secure the needed support, but the panel refused to do so.
The application is still as good as dead, but ICANN will need to go through the motions to actually bury it.
In the meantime, ZACR’s delayed delegation of .africa is to remain on hold.
How embarrassing is this for the GAC?
Hugely. Verbal testimony from Heather Dryden, who was GAC chair at the time of the Beijing meeting, highlights what I’ve been saying for years: GAC advice is regularly so vaguely written as to be useless, inconsistent, or even harmful.
Dryden told the panel at one point: “In our business, we talk about creative ambiguity. We leave things unclear so we don’t have conflict.”
The IRP panel took a dim view of Dryden’s testimony, writing that she “acknowledged during the hearing, the GAC did not act with transparency or in a manner designed to insure fairness.”
The ruling quotes large chunks of text from the hearing, during which Dryden was grilled about the GAC’s rationale for issuing a consensus recommendation against DCA.
Dryden responded by essentially saying that the GAC did not discuss a rationale, and that there was “deference” to the governments proposing consensus objections in that regard.

ARBITRATOR KESSEDJIAN: So, basically, you’re telling us that the GAC takes a decision to object to an applicant, and no reasons, no rationale, no discussion of the concepts that are in the rules?
[DRYDEN]: I’m telling you the GAC did not provide a rationale. And that was not a requirement for issuing a GAC —
HONORABLE JUDGE CAHILL: But you also want to check to see if the countries are following the right — following the rules, if there are reasons for rejecting this or it falls within the three things that my colleague’s talking about.
[DRYDEN]: The practice among governments is that governments can express their view, whatever it may be. And so there’s a deference to that. That’s certainly the case here as well.

This and other quoted sections of the hearing depict the GAC as a body that deliberately avoids substantive discussions and deliberately provides unclear advice to ICANN, in order to avoid offending its members.
Does this mean all GAC advice on new gTLDs is open to appeal now?
Maybe. There are numerous instances of the ICANN board accepting GAC advice without demanding an explanation from the GAC.
At a bare minimum, the applicant for .gcc, which was rejected in the same breath as .africa, now seems to have a case to appeal the decision. The applicant for .thai is in a very similar situation.
Amazon’s lawyers will no doubt also be poring over yesterday’s decision closely; its .amazon bid was also killed off by GAC advice.
But in the case of .amazon, it would be hard to argue it was a .africa-style summary execution. ICANN took extensive advice and delayed its decision for a long time before killing off that application.
The ruling essentially calls the part of the Applicant Guidebook that gives the GAC its strong advisory powers over new gTLD applications into question.
Literally hundreds of new gTLD applications were affected by the Beijing communique.
Anything else of note?
Yes.
First, large parts of the decision have been redacted. The redactions mostly appear to relate to sensitive documents disclosed between the parties (reading between the lines, I think some of them related to DCA’s purported support from a certain African government) that the panel ruled should remain private last September.
Second, the decision inexplicably quotes the ICANN bylaws text “MISSION AND CORE VALUES” as “MISSION AND CORE (Council of Registrars) VALUES”, in what appears to be a weird search-and-replace error by an unknown party. CORE (Council of Registrars) is of course a registry back-end provider with apparently no involvement in .africa whatsoever.
Third, it seems I’ve been elected Pope. I hereby select “Dave” as my Papal name and will commence my program of donating all Church assets to the poor forthwith.

ICANN dragged into Gamergate as Whois reform cast as misogynist threat

What do ICANN’s current Whois privacy reform proposals have to do with the “Gamergate” controversy?
Quite a lot, according to the latest group to slam the proposals as an enabler for “doxing… harassment… swatting… stalking… rape and death threats.”
The Online Abuse Prevention Initiative was formed in March by female software developers in the wake of a sexism slash online abuse scandal that continues to divide the video game community.
Led by Randi Harper, OAPI’s first public move was to today write to ICANN to complain about the GNSO Privacy & Proxy Services Accreditation Issues (PPSAI) Working Group Initial Report.
The report, as previously reported, contains a minority opinion that would ban transactional e-commerce sites from using Whois privacy services.
OAPI said today that this posed a risk of “doxing” — the practice of publishing the home address and other personal information about someone with the aim to encourage harassment — and “swatting”, where people call up America’s notoriously trigger-happy cops to report violent crimes at their intended victim’s home address.
Harper, who was one of the targets of the Gamergate movement (Google her for examples of the vitriol) claims to have been a victim of both. The OAPI letter says she “was swatted based on information obtained from the WHOIS record for her domain.”
The letter, which is signed by groups including the Electronic Frontier Foundation, the National Network to End Domestic Violence, the National Council of Women’s Organizations, and dozens of noted digital rights voices, says:

We strongly oppose the Working Group’s proposal, which will physically endanger many domain owners and disproportionately impact those who come from marginalized communities. People perceived to be women, nonwhite, or LGBTQ are often targeted for harassment, and such harassment inflicts significant harm
…
Even the most limited definition of a “website handling online financial transactions for commercial purpose” will encompass a wide population that could be severely harmed by doxing, such as:

• women indie game developers who sell products through their own online stores
• freelance journalists and authors who market their work online
• small business owners who run stores or businesses from their homes
• activists who take donations to fund their work, especially those living under totalitarian regimes
• people who share personal stories online to crowdfund medical procedures

To make things worse, the proposed definition of what constitutes “commercial purpose” could be expanded to include other types of activity such as running ads or posting affiliate links.

The letter does not directly refer to Gamergate, but some of the signatories are its most prominent victims and the allusions are clearly there.
Gamergate is described somewhere in its 9,000-word Wikipedia article as “part of a long-running culture war against efforts to diversify the traditionally male video gaming community, particularly targeting outspoken women.”
At its benign end, it was a movement for stronger ethics in video game journalism. At its malignant end, it involved quite a lot of male gamers sending abuse and violent threats to female players and developers.
The PPSAI report is open for comment until July 7. It has so far attracted over 10,000 emails, most of them rustled up by registrar letter-writing campaigns here and here.

Registrars open floodgate of Whois privacy outrage

A letter-writing campaign orchestrated by the leading domain registrars has resulted in ICANN getting hit with over 8,000 pro-privacy comments in less than a week.
It’s the largest volume of comments received by ICANN on an issue since right-wing Christian activists deluged ICANN with protests about .xxx, back in 2010.
The comments — the vast majority of them unedited template letters — were filed in response to the GNSO Privacy & Proxy Services Accreditation Issues (PPSAI) Working Group Initial Report.
That report attempts to bring privacy and proxy services, currently unregulated by ICANN, under ICANN’s contractual wing.
There are two problematic areas, as far as the registrars are concerned.
The first is the ability of trademark and copyright owners to, under certain circumstances, have the registrant of a privately registered name unmasked.
Upon receiving such a request, privacy services would have 15 days to obtain a response from their customer. They’d then have to make a call as to whether to reveal their contact information to the IP owner or not.
Possibly the most controversial aspect of this is described here:

Disclosure cannot be refused solely for lack of any of the following: (i) a court order; (ii) a subpoena; (iii) a pending civil action; or (iv) a UDRP or URS proceeding; nor can refusal to disclose be solely based on the fact that the request is founded on alleged intellectual property infringement in content on a website associated with the domain name.

In other words, the privacy services (in most cases, also the registrar) would be forced make a judgement on whether web site content is illegal, in the absence of a court order, before removing Whois privacy on a domain.
The second problematic area is an “additional statement” on domains used for commercial activity, appended to the PPSAI report, penned by MarkMonitor on behalf of Facebook, LegitScript, DomainTools, IP attorneys Smith, Gambreall & Russell, and itself.
Those companies believe it should be against the rules for anyone who commercially transacts via their web site to use Whois privacy.
Running ads on a blog, say, would be fine. But asking for, for example, credit card details in order to transact would preclude you from using privacy services.
The PPSAI working group didn’t even approach consensus on this topic, and it’s not a formal recommendation in its report.
Regardless, it’s one of the lynchpins of the current registrar letter-writing campaigns.
A page at SaveDomainPrivacy.org — the site backed by dozens of registrars big and small — describes circumstances under which somebody would need privacy even though they engage in e-commerce.
Home-based businesses, shelters for domestic abuse victims that accept donations, and political activists are all offered up as examples.
Visitors to the site are (or were — the site appears to be down right now (UPDATE: it’s back up)) invited to send a comment to ICANN supporting:

The legitimate use of privacy or proxy services to keep personal information private, protect physical safety, and prevent identity theft
The use of privacy services by all, for all legal purposes, regardless of whether the website is “commercial”
That privacy providers should not be forced to reveal my private information without verifiable evidence of wrongdoing

The content of the site was the subject of a sharp disagreement between MarkMonitor and Tucows executives last Saturday during ICANN 53. I’d tell you exactly what was said, but the recording of the relevant part of the GNSO Saturday session has not yet been published by ICANN.
Another site, which seems to be responsible for the majority of the 8,000+ comments received this week, is backed by the registrar NameCheap and the digital civil rights groups the Electronic Frontier Foundation and Fight For The Future.
NameCheap appears to be trying to build on the reputation it started to create for itself when it opposed the Stop Online Piracy Act a few years ago, going to so far as to link the Whois privacy reforms to SOPA on the campaign web site, which says:

Your privacy provider could be forced to publish your contact data in WHOIS or even give it out to anyone who complains about your website, without due process. Why should a small business owner have to publicize her home address just to have a website?
We think your privacy should be protected, regardless of whether your website is personal or commercial, and your confidential info should not be revealed without due process. If you agree, it’s time to tell ICANN.

The EFF’s involvement seems to have grabbed the attention of many reporters in the general tech press, generating dozens of headlines this week.
The public comment period on the PPSAI initial report ends July 7.
If it continues to attract attention, it could wind up being ICANN’s most-subscribed comment period ever.
Do geeks care about privacy more than Christians care about porn? We’ll find out in a week and a half.

Puerto Rico to host ICANN meeting next year

ICANN is to host its first second ever public meeting on a Caribbean island.
The organization’s board of directors yesterday voted in favor of holding ICANN 57 in San Juan, Puerto Rico.
Technically, this fulfills ICANN’s commitment to hold the meeting in North America, even though physically Puerto Rico is in the Caribbean.
The island is one of those oddities in terms of territories in that it inherits its ICANN region from its political overlords.
Puerto Rico is a US territory, which puts it in ICANN’s North American region. The neighboring British Virgin Islands is, according to ICANN, in Europe.
ICANN 57 will be held from October 29 to November 4 2016, at the tail end of Puerto Rico’s hurricane season. It’s the second time ICANN has visited the island, the first since 2007.
There’s no word yet on where ICANN 56, June 2016, will be held. It’s a designated slot for an Latin American/Caribbean host nation.
ICANN 55 will be held in Marrakech next March, ICANN’s board confirmed yesterday, rescheduled from March this year due to the Ebola scare.
Dublin will host ICANN 54 this coming October.

Posh Spice takes down porn site

Former Spice Girl Victoria Beckham has used UDRP to take down a porn site bearing her name.
victoria-beckham.biz was owned by a Ukrainian, who had set up a site “at which adult and/or pornographic images and services are offered”, according to the UDRP panelist.
It was pretty much a slam-dunk case.
While not all celebrities own trademarks on their names, Beckham does. The squatter, who registered the name in December 2014, did not even attempt a response.
Based on archived screenshots and Whois records, it looks like victoria-beckham.biz has been around as a rather harmless fan site since about 2006.
It was only after the domain expired late last year and was re-registered did it become a porn site, attracting the attention of Beckham’s lawyers.

ICANN bans closed generic gTLDs, for now

ICANN has slapped a de facto ban on so-called “closed generic” gTLDs, at least for the remaining 2012 round applicants.
The ICANN board’s New gTLD Program Committee passed a resolution Sunday that un-freezes the remaining new gTLD applications that envisage a namespace wholly controlled by the applicant.
The affected strings are .hotels, .dvr and .grocery, which are uncontested, as well as .food, .data and .phone, which are contested by one or two other applicants.
The NGPC said five strings are affected, but the ICANN web site currently shows these six.
The resolution allows the contested strings to head to dispute resolution or auction, but makes it clear that “exclusive generic gTLDs” will not be able to sign a registry contract.
Instead, they will either have to withdraw their applications (receiving a partial refund), drop their exclusivity plans, or have their applications carried over to the second new gTLD round.
The GNSO has been asked to develop a policy on closed generics for the second round, which is still probably years away.
It’s not clear whether other applicants would be able to apply for strings that are carried over, potentially making the close generic applicant fight two contention sets.
The NGPC decision comes over two years after the Governmental Advisory Committee advised that closed generics must serve “a public interest goal” or be rejected.
This weekend’s resolution sidesteps the “public interest” question altogether.

Chehade confirms he’ll be gone before IANA transition is done

ICANN CEO Fadi Chehade has laid out his current best thinking for the timeline of the IANA’s transition from US government oversight, and he’ll be gone well before it’s done.
At the opening ceremony of the ICANN 53 meeting in Buenos Aires today, Chehade described how June 2016 is a likely date for the divorce; three months after his resignation takes effect.
Chehade said:

I asked our community leaders, “Based on your plans and what you’re seeing and what you know today, when could that finish?” The answers that are coming back to us seem to indicate that by ICANN 56, which will be back in Latin America in the middle of 2016, a year from today, the contract with the US Government could come to an end.

He showed a slide that broke the remaining work of the transition into three phases.

Work being carried out within ICANN is not entirely to blame for the length of time the process will take.
The US National Telecommunications and Information Administration needs 60 to 90 days to review the final community-developed transition proposal.
And under forthcoming US legislation, 30 legislative days will be required for the US Congress to review the NTIA’s approval of the plan.
Thirty legislative days, Chehade explained, could mean as many as 60 actual days, depending on the yet-unpublished 2016 Congressional calendar.
He urged the community focus hard on Phase One in his graphic — actually producing a consensus transition plan.
The target for delivery of this is the next ICANN meeting, 54, which will take place in Dublin, Ireland from October 18 to October 22 this year.

ICANN 53 launches with risky Caitlyn Jenner joke

ICANN has risked the ire of community members by kicking off ICANN 53 today with a joke referencing transgender celebrity Bruce/Caitlyn Jenner.
Just moments into his opening address this hour, ICANN chair Steve Crocker worked a joke around before/after photos of the former athlete.
[UPDATE: Crocker has issued an apology. See the bottom of this post.]

This is what Crocker said:

What are we really talking about here? What is this thing we call “the transition”? And why has it captivated the attention of so many?
[Jenner photo appears]
Ahhh, no. That’s not quite the transition that I’m referring to. I’m only referring to the IANA stewardship transition.

Reaction from attendees was mixed.
The joke got laughter from the room.
On Twitter, some were less amused.

Excuse me @ICANN, is this equality, respect and one world for EVERYONE? Apologise in order #icann53 #notfunny!!!!! pic.twitter.com/Bn2926OlXk

— Aida Mahmutović (@Aidazzles) June 22, 2015

#ICANN53 starts with a joke at the expense of the LGBTQI population. I guess that is better than a prayer. But not a lot.

— avri (@avri) June 22, 2015

Ehhh….what just happened there. Seriously #ICANN, some things one do not joke about.

— Patrik Fältström (@patrikhson) June 22, 2015

Slow start from Crocker here. Apparently ICANN meetings are supposed in Summer and jokes about transgender transition are funny #sheesh

— Adrian Kinderis (@AdrianKinderis) June 22, 2015

Unfortunate & sad that on such a global platform ICANN has used Caitlyn Jenner's image to generate a laugh instead of applauding her courage

— dotgay LLC (@dotgay) June 22, 2015

I’ll be the first to leap to the defense of the joke.
I laughed. I don’t think it was offensive or insulting to Jenner or to trans people in general — it was more a joke about celebrity culture — and I don’t think any offense was intended.
If I had seen it on TV, I wouldn’t have batted an eyelid. I even made a joke about Jenner’s Vanity Fair cover, on Twitter, a couple weeks back.
But a lot of ICANN regulars are more sensitive about this kind of thing. I’ve had conversations with people who believe it was highly inappropriate for CEO Fadi Chehade to congratulate a participant, from the stage during a previous meeting, on her visible pregnancy.
For ICANN’s chairman to make a joke about a transgender person’s transition at the opening ceremony of a major meeting? That’s a misjudgment, in my view.
ICANN, recall, has recently been bombarded with letters from equal rights groups over the decision by the Economist Intelligence Unit to reject a .gay gTLD applicant’s Community Priority Evaluation.
EIU based its decision in large part on the fact that the proposed .gay community included transgender and intersex people, which the EIU said were not encapsulated by the string “gay”.
ICANN has expected standards of behavior for its meetings that cover such things as sexism and homophobia.
UPDATE: Crocker issued the following statement on ICANN’s Facebook account:

I understand that I may have inadvertently offended some during my speech at this morning’s welcome session with a reference to Caitlyn Jenner, which was intended as a salute. It opened up an important dialog that is consistent with our principles.
Please know that I view Caitlyn’s decision to be heroic and brave. I made this reference solely because of the world attention on a transition and it was not intended in any way, shape or form to be a criticism of her heroic decision. I was in no way making light or poking fun at her transition, but rather playing on the world attention on a “transition.” I apologize if my comments were perceived in a different manner than I intended them.
Dr. Stephen Crocker
ICANN Board Chair

Photo credit: James Bladel.

Chehade makes case for insider CEO in frank assessment of failings

Outgoing ICANN CEO has made a case for his successor to be somebody already intimately familiar with the ICANN community.
His remarks, which stopped short of explicitly recommending an insider take over his position when he leaves next March, came during a frank self-assessment of his shortcomings in the job at ICANN 53 in Buenos Aires yesterday.
“There are many things I could have done better or done differently,” Chehade said before an audience of Generic Names Supporting Organization members.
He freely confessed to jumping headlong into the job before he fully understood ICANN as a community; how it functions and where the real power is supposed to be wielded.
The key example of that, he said, was the creation of some of the rules now in use at the Trademark Clearinghouse.
“I meant well, I intended well, but I broke every process in the system,” he said. “I didn’t know, and I really didn’t realize that I didn’t until later.”
That’s a reference to late 2012, when Chehade convened a series of secretive, invitation-only community meetings that gave the Intellectual Property Constituency yet another chance to have rights protection mechanisms strengthened.
Chehade famously even asked participants to not even live-tweet during the discussions, it was not webcast, and recordings of (some of) the sessions were not published until DI filed a Documentary Information Disclosure Process request.
These “strawman” meetings culminated in the IPC being given the “Trademark+50” mechanism, which allows variations on trademarks to be protected, and the Non-Commercial Users Constituency to claim its voice had been under-represented and largely ignored.
For this reason and others, Chehade now says his successor had better have “very very good preparation and orientation”.
“Spending about seven minutes with the prior CEO before I took this job is not something I recommend,” he said, apparently a reference to time spent with his predecessor, Rod Beckstrom.
“This is a very complex job, and a very layered role, and I had no orientation to speak of,” he said. “If he or she is not someone who knows this community, this person better have a lot of orientation.”
He described how it took him some time to get to grips with the idea that he’s not a CEO in the conventional sense, able to make changes at will and answerable only to the board of directors.
“I am not a CEO,” he said. “There are types of CEO and this is a servant CEO job. Until you get that you keep hitting walls.”
He also described the job as “a politician without a flag” and “community facilitator”.
His biggest regret, he said, was failing to immediately realize that the facilitator function was the most important part of the job.
It took a clash last year about accountability being a key part of the IANA transition for him to realize this, he said.
“I hope you will all contribute in finding a person who will serve you well from day one, not like me, who from day one will arrive understanding all the parts of this,” he said.
Whether he intended it or not, this sounds like Chehade would err towards hiring an ICANN community veteran as his successor.
He said his replacement should be somebody who “knows all the things I learned, hopefully on day one, or on month one. Or on year one, but not three years in.”
It should be noted that Chehade turned down the chance to be a part of the team that will choose his successor.
Chehade’s position appears to diametrically opposed that of his predecessor. During Beckstrom’s tenure as “outgoing” CEO, he explicitly recommended an outsider take over the role.
“I hope that the person who replaces me will be of the highest integrity and has no recent or current commercial or career interests in the domain industry, because ICANN’s fairness, objectivity and independence are of paramount importance to the future of the internet,” Beckstrom said in October 2011.
Beckstrom’s remarks came as ICANN came under intensified scrutiny over perceived conflicts of interest.
Peter Dengate Thrush had recently come to the end of his tenure as ICANN chair, pushing through the (premature?) approval of the new gTLD program in his last few days on the job and joining applicant Minds + Machines just a few weeks later.
Chehade’s remarks yesterday come as ICANN is in a different position.
When he leaves next March, ICANN will either be freshly decoupled from its oversight relationship with the US government, or will be on the verge of it.
It won’t be an easy time for a new CEO to take over, trying to steer the organization under a fresh, untested set of governance principles.
When it comes to “insiders” with intimate knowledge of ICANN, there are a few community members not already on ICANN staff I could imagine pitching themselves for the CEO’s job.
But there’s also the possibility of an internal hire.
Remember, one of Chehade’s first actions upon taking the job was to hire the two other people who had been on the board’s final shortlist — Tarek Kamel and Sally Costerton.
Kamel, once a controversial minister in Mubarak’s Egyptian government, is currently Chehade’s senior advisor for government engagement.
Costerton was London-based EMEA CEO at the public relations agency Hill & Knowlton. Today, she’s the senior advisor for global stakeholder engagement. She maintains a blog about women in leadership positions that some readers might find eye-opening in the ICANN CEO search context.
Both were considered CEO material three years ago, and both now have three years of ICANN experience to put on their job applications (if they choose to file them).
So why is Chehade leaving ICANN? The persistent rumors have him either being offered the job of his dreams elsewhere, or suffering a severe case of ICANN burnout.
But yesterday he left little doubt whether his next job, which it has been confirmed he already has lined up, would be better that his current one.
“[ICANN CEO] is a beautiful job. It is a fantastic job. It is better job that I’ve ever had, or will ever have I think. It is amazing. Lucky is the person who will take my place,” he said.
So, um, why quit?
“The next phase of ICANN requires a different person. Don’t go rehire Fadi. You don’t need another Fadi. I was there for a purpose, for a time,” he said. “I am a classic change agent CEO. I either build things from scratch… or I transform things. ICANN doesn’t need this now.”
Asked to comment on his biggest successes, Chehade deferred, saying his legacy was something to talk about at a different time.