ICANN U-turns on appeals loophole after community revolt
ICANN has backtracked and substantially pared down a proposal that could have weakened its accountability mechanisms after most of the community said they didn’t like it.
The Org has published for public comment a proposed amendment to its bylaws that will exclude its new Grant Program from the Request for Reconsideration and Independent Review Process mechanisms.
The amendment would specifically exclude claims “relating to decisions to approve or not approve an application to the ICANN Grant Program” from both procedures.
An earlier proposal would have created a new procedure to enable ICANN to also exclude other programs from accountability in future, if certain conditions were met.
But the community largely reacted with revulsion to that proposal, saying they could not support something so overly broad, forcing ICANN to narrow it down to the Grant Program only. ICANN needs the support of its sovereign Empowered Community if it wants to amend its fundamental bylaws.
The $220 million Grant Program is seeking to distribute ICANN’s new gTLD auction funds to worthy causes, but there was a fear the cash could be siphoned off by lawyers if unsuccessful grant applicants were allowed to trigger the accountability mechanisms.
The revised language is likely to be much more palatable to the community, based on previous comments.
The public comment period is open until September 16.
GNSO mulls lawyering up over auction fund dispute
The GNSO Council has started discussing bringing in the lawyers over ICANN’s recent handling of issues related to its $200+ million auction fund and Grant Program.
The Council today raised the possibility of deploying the never-before-used Community Independent Review Process, which would involve every major community group ganging up on ICANN’s board in a protracted quasi-judicial bunfight.
Ironically, the beef concerns the way ICANN is trying to stop people invoking its accountability mechanisms, including the IRP, to challenge decisions it makes under its Grant Program, which hopes to distribute $10 million to worthy causes this year.
ICANN policy is that nobody should be able to challenge grant decisions, because that would mean funneling the available funds into the pockets of worthless lawyers, rather than worthy causes. But how it proposes to achieve that goal is in dispute.
The original community recommendation was for a bylaws amendment that specified that the Grant Program was out-of-bounds for IRP and Request for Reconsideration claims, and the board initially agreed, before changing its mind and instead plumping for a clause in the program’s terms that prevents grant applicants appealing adverse decisions.
After community pushback, the board said it would also propose a bylaws amendment, but many believe the amendment it came up with goes way too far and risks making it far too easy for ICANN to wriggle out of its accountability obligations in future.
Leading the fight against the board is the GNSO’s Intellectual Property Constituency, which filed a Request for Reconsideration in November, asking ICANN to reverse its decision to “contract around” its accountability promises and scale back its over-broad bylaws amendment.
But the RfR was thrown out, with the Board Accountability Mechanisms Committee ruling that the IPC had failed to say how it had been specifically harmed by the board’s actions, accusing the constituency of merely “speculating” about possible future harms.
GNSO Councillor Susan Payne, today expressed the IPC’s disappointment with BAMC’s decision on the Council’s monthly conference call.
“We think that’s wrong,” she said. “If you purport to change a fundamental bylaw by using a process that cuts out the GNSO and effectively therefore also its constituencies and stakeholder groups then clearly there’s a harm there.”
She also noted the financial expense of challenging the board’s decisions.
“Constituencies or stakeholder groups will have real difficulty in withstanding the ICANN machine,” Payne said. “It’s a really expensive process to to challenge these kind of decisions. We asked if other constituencies and stakeholder groups would be able to join the IPC in bringing that RfR and no one had the finances to do it.”
The IPC has joined ICANN in a Cooperative Engagement Process — a kind of informal discussion that is often a precursor to an IRP filing — but Payne raised the possibility of ICANN’s Empowered Community filing its own IRP.
Under ICANN’s bylaws, the EC has the special ability to bring a Community IRP and ICANN has to pay for it. It’s never been used before, and it doesn’t look to me like the complex conditions required to trigger it are close to having been met.
The IPC had broad support in principle from the other Councillors speaking in today’s meeting, but some urged caution due to ICANN’s past behavior when the lawyers are called in.
“Once you get into the IRP process, ICANN buckles down, hands it off to their outside counsel, and you really get a nasty litigation fight,” said Jeff Neuman, a liaison on the Council. “You’re talking about years of litigation, outside counsel, and no progress”.
Fellow council member Thomas Rickert of the ISPs constituency suggested looking for a law firm that would handle the IRP on a no-win-no-fee basis before committing further.
While it seems a Community IRP may be unrealistic for now, the fact that it’s even being discussed shows how seriously the GNSO is taking this apparent power grab by ICANN’s board and lawyers.
Community revolts over ICANN’s auction proceeds power grab
Parts of the ICANN community have revolted over ICANN’s move to make it easier to turn off the mechanisms used to appeal its decisions.
Both registries and registrars, along with their usual opponents in the business and intellectual property communities, have told the Org that a proposal to change its foundational bylaws are overly broad and creates new powers to diminish ICANN’s accountability.
Meanwhile, the Intellectual Property Constituency seems to have escalated its beef with ICANN related to the proposals, entering into a Cooperative Engagement Process with ICANN. CEP is usually, but not always, a precursor to an expensive, quasi-judicial Independent Review Process case.
The row relates to the Grant Program, which launched a month ago and will see ICANN hand out $217 million it gained from auctioning registry contracts during the 2012 new gTLD program application round.
The rules of the program were developed by the Cross-Community Working Group on New gTLD Auction Proceeds.
The CCWG was afraid that ICANN might wind up frittering away most of the money on legal fees unless unsuccessful grant applicants, and third parties, were banned from appealing grant decisions they didn’t like. So its Recommendation 7 proposed a bylaws amendment that would prevent the Independent Review Process and Request for Reconsideration process from being used with reference to the Grant Program.
What ICANN came up with instead is a bylaws amendment that could be applied not only to the Grant Program, but also potentially to any future activities.
Specifically, ICANN’s proposed amendment gives future CCWGs, assuming they have sufficient community representation, the ability to recommend exceptions to the accountability mechanisms, which ICANN could then accept without having the amend the bylaws every time.
But almost every constituency that has filed an opinion on the proposals so far thinks ICANN has gone too far.
The IPC said says ICANN’s proposal is “unacceptably broad and exceeds what is necessary to give effect to Recommendation 7” adding:
The IPC is also concerned that making such a broad Bylaws amendment could have the consequence of normalizing the idea of removing access to accountability mechanisms, rather than this being an exceptional event. This is not something that should be encouraged.
The Registries Stakeholder Group said the proposal “creates an alternative path for amending the Bylaws that contradicts the existing amendment processes”
“The Accountability Mechanisms are foundational to ICANN’s legitimacy. Access to Accountability Mechanisms should be prevented only in rare circumstances with the clear support of the Empowered Community,” it added.
The Registrar Stakeholder Group concurred, writing:
Robust Accountability Mechanisms are a lynchpin of ICANN’s broader accountability structure. They should only be disallowed, if ever, in very specific circumstances, and as a result of the full bylaw amendment process. The proposed bylaws amendment vests CCWGs with the power to disallow Accountability Mechanisms which we believe is inappropriate.
Several commenters pointed out that CCWGs are less formal ICANN policy-making structure, with fewer checks and balances than regular Policy Development Processes.
The only dissenting view came from the At-Large Advisory Committee, which said it “strongly supports” ICANN’s proposed amendment, writing:
Although any limitation in accountability is potentially onerous, the ALAC is comfortable that the three conditions proposed in the amendment only allow such limitations in situations where a more specific Bylaw limitation would also be approved by the Empowered Community.
In a related development, the IPC has taken the highly unusual move of entering CEP with ICANN, suggesting it is on the IRP path.
The IPC had filed a Request for Reconsideration late last year, at a time when it appeared that ICANN had outright rejected Recommendation 7 (having previously approved it), but ICANN’s board threw it out mostly on the grounds that the IPC could not show it had been harmed, which the IPC found curious.
If the IPC were to go to IRP, it would be unprecedented. The mechanism has only ever been used by companies defending their commercial interests, never by one of ICANN’s own community groups on a matter of principle.
ICANN opens $217 million Grant Program
Ten million bucks of ICANN’s money is up for grabs, starting today.
The Org has opened the application window for the first stage of its Grant Program, which it hopes to eventually see hand out over the $217 million that it raised auctioning off contested gTLDs during the 2012 new gTLD program application round.
In this first phase, up to $10 million will be distributed, in tranches of between $50,000 and $500,000, to projects that align in some way with ICANN’s technical and internet governance missions.
Only registered non-profits are allowed to apply.
The application window is open until May 24, and ICANN expects its board of directors to make its final decision in December, before grant contracts are signed early next year.
Successful applicants are expected to begin their funded projects, which should last no more than two years, within 60 days of receiving the money, so presumably the cash will start actually making a difference about a year from now.
In a blog post, ICANN CEO Sally Costeron urged readers to spread word of the program on social media, specifically naming Facebook, Instagram, LinkedIn, Twitter, and WeChat, which appears to be a platform used primarily in China.
With ICANN occupying a rarefied, occasionally incestuous corner of the internet, there’s obviously a risk of the perception that the money will be doled out primarily to community insiders, but the rules ban anyone who was involved in crafting the program’s rules from participating.
The rules also ban applicants from using ICANN’s accountability mechanisms, such as the Independent Review Process, to challenge adverse grant decisions, and ICANN wants to change its bylaws to also ban third-party non-applicants from using IRP to appeal decisions they don’t like.
Details on the Grant Program can be found here.
DNS Women barred from ICANN funding?
A networking group set up to support women in the domain name industry, especially in the developing world, may be banned from applying for ICANN funding under rules published earlier this week.
Concerns have been raised that DNS Women may be excluded from the $10 million in non-profit Grant Program funding ICANN is making available this year because its CEO participated in the program’s community rule-making process.
ICANN’s rules, written by Org staff based on the recommendations of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP), ban anyone from applying for grants — set at between $50,000 and $500,000 — if they have potential conflicts of interest.
Participation in the CCWG-AP is listed as one such conflict:
No person that participated as a member (including temporary member appointments) of the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP) is eligible to apply for or be included within funded proposal activities as principals, advisors, or in other roles. Grants may not be awarded to businesses and organizations owned in whole or in part by the CCWG-AP members or their family members. Grant funding may not be used to pay compensation to CCWG-AP members or their family members.
DNS Women is currently led by Vanda Scartezini, who was a member of CCWG-AP representing the At-Large Advisory Committee. She’s written to ICANN to express surprise to find herself suddenly unable to apply for funding. ICANN has responded with a pointer to the CCWG-AP’s recommendations, where the language closely mirrors that found in the new application rules as implemented.
But if Scartezini has shot herself in the foot, she may not be alone. According to the CCWG-AP’s final report, there may have been almost enough foot-shooting to create a Paralympic football team.
Of the 22 people who participated as full members of the group — and would be therefore barred from financially benefiting from grants — 10 people answered “yes” or “maybe” when asked to disclose whether they or their employer expected to apply for funding (almost all, including Scartezini, were “maybes”).
The $10 million tranche available this year comes from a $217 million fund ICANN raised auctioning off contested gTLDs following the 2012 application round.
$10 million of ICANN cash up for grabs
ICANN has officially launched its Grant Program, making $10 million available to not-for-profit projects this year.
The Org expects to start accepting applications for between $50,000 and $500,000 between March 25 and May 24 and start handing out the cash early next year.
It’s the first phase of a program that currently sees ICANN sitting on a distributable cash pile of $217 million that it raised by auctioning off contested new gTLD registry contracts under the 2012 gTLD application round.
The money is only available to registered charities that in some way support ICANN’s mission in terms of developing internet interoperability or capacity building.
Organizations worldwide will be able to apply, but it seems unlikely anyone from a country currently subject to US government sanctions will be successful. Conflicted organizations — such as those led by somebody involved with the program — are also barred.
Applications for grants will be assessed by ICANN staff, a yet-to-be-named Independent Application Assessment Panel comprising “a diverse collective of subject matter experts”, and ultimately the ICANN board of directors.
More information and the application form can be found here.
ICANN accused of power grab over $271 million auction fund
ICANN has acted outside of its powers by ignoring community policy recommendations and leaving its $271 million gTLD auction windfall open to being frittered away on lawyers, according to community members.
The Intellectual Property Constituency of the GNSO has filed a formal Request for Reconsideration over a board resolution passed at ICANN 78 last month in Hamburg, and other constituencies may add their names to it shortly.
The row concerns the huge cash pile ICANN was left sitting on following the auction of 17 new gTLD contracts between 2014 and 2016, which raised $240 million (as of July, around $271 million after investment returns and ICANN helping itself to a portion to fund its operations reserve).
It was decided that the money should be used to fund a grant program for worthy causes, with organizations able to apply for up to $500,000 during discrete rounds, the first of which is due to open next year with a $10 million pot. Around $220 million is believed to be earmarked for the grant program over its lifetime.
But the Cross Community Working Group for Auction Proceeds (CCWG-AP) that came up with the rules of the program was concerned that unsuccessful applicants, or others chagrined by ICANN’s grant allocations, might challenge decisions using ICANN’s accountability mechanisms.
This would cause money earmarked for worthy causes to be spaffed away on lawyers, which the CCWG-AP wanted to avoid, so it recommended that ICANN modify its fundamental bylaws to exclude the grant program from mechanisms such as the Independent Review Process, which usually incurs high six-figure or seven-figure legal fees.
ICANN seemed to accept this recommendation — formally approving it in June last year — until ICANN 78, when the board approved a surprise U-turn on this so-called Recommendation 7.
The board said it was changing its mind because it had found “alternative ways” to achieve the same objective, “including ways that do not require modification to ICANN’s core Bylaws on accountability”. The resolution stated:
As a result, the Board is updating its action on Recommendation 7 to reflect that ICANN org should implement this Recommendation 7 directly through the use of applicant terms and conditions rather than through a change to ICANN’s Fundamental Bylaws.
This left some community members — and at least one ICANN director — scratching their heads. Sure, you might be able to ban grant applicants from using the IRP in the program’s terms and conditions, but that wouldn’t stop third parties such as an applicant’s competitors from filing an IRP and causing legal spaffery.
The board was well aware of these concerns when it passed the resolution last month. Directors pointed out in Hamburg that ICANN is still pursuing the bylaws amendment route, but has removed it as a dependency for the first grant round going ahead.
This left some community members nonplussed — it wasn’t clear whether ICANN planned to go ahead with the program ignoring community recommendations, or not. The reassuring words of directors didn’t seem to tally with the language of the resolution.
So the IPC took the initiative and unironically invoked an accountability mechanism — the RfR — to get ICANN to change its mind again. I gather the request was filed as a precaution within the 30-day filing window due to the lack of clarity on ICANN’s direction.
The RfR states:
the impetus behind the Bylaws change was to prevent anyone from challenging grant decisions, including challenges from parties not in contractual privity with ICANN. The Board’s hasty solution would only prevent contracting grant applicants from challenging decisions; it would not in any way affect challenges by anyone else – including anyone who wished to challenge the award of a grant. The grant program could be tied in knots by disgruntled parties, competitive organizations or anyone else who wished to delay or prevent ICANN from carrying out any decision to grant funds. This is exactly what the CCWG-AP sought to prevent
The IPC says that by bypassing the bylaws amendment process, which involves community consent, the ICANN board is basically giving itself the unilateral right to turn off its bylaws-mandated accountability mechanisms when it sees fit. A power grab.
It wants the Hamburg resolution reversed.
Discussing the RfR a few days before it was filed, other members of the GNSO Council suggested that their constituencies might sign on as fellow complainants if and when it is amended.
RfRs are handled by ICANN’s Board Accountability Mechanisms Committee, which does not currently have a publicly scheduled upcoming meeting.
Recent Comments