ICANN slashes millions from its budget

ICANN has cut $5 million from its annual budget, warning the community that difficult decisions have to be made amid a slowing domain name market.
Staff and community members will all be affected by the cuts, whether in the form of less generous pay raises or fewer travel opportunities.
Cuts have also been proposed to international outreach, tech support, contractual compliance and translation services.
The organization at the weekend published for comment its proposed budget for fiscal 2019. That’s the year that begins July 1, 2018.
It would see ICANN spend $138 million, $5 million less than it expects to spend in fiscal 2018.
Four of the five top-line areas ICANN reports expenses will be cut for a total of $12 million in savings, while one of them — personnel — is going up by $7.3 million.
This rounds out to a $5 million cut to the total FY19 ICANN budget. Here’s the breakdown:

• Personnel costs going up from $69.5 million to $76.8 million, up $7.3 million.
• Travel and meetings costs are to go down from $17.8 million to $15.6 million, a $2.2 million saving.
• Professional services costs will go down from $27.7 million to $23.4 million, a $4.3 million saving.
• Administration and capital costs will go down from $22.5 million to $17.8 million, a $4.7 million saving.
• The contingency budget is going down from $5.3 million to $4.5 million, a $800,000 saving.

Personnel costs are going up due to a combination of new hires and pay rises, but the average annual pay rise will be halved from 4% to 2%, saving $1.3 million, ICANN documentation states.
Headcount is expected to level out at about 425, up from the current 400, by the end of FY19.
The travel budget is going down due to a combination of cuts to services provided at the three annual meetings and the number of people ICANN reimburses for going to them.
The Fellows program — sometimes criticized for giving people what look like free vacations for little measurable return — is seeing the biggest headcount cut here. ICANN will only pay for 30 Fellows to go its meetings in FY19, half the level of FY18. The Next Gen program, a similar outreach program for yoof participants, goes down to 15 people from 20.
The Governmental Advisory Committee will get its number of funded seats reduced by 10 to 40. The ALAC and the ccNSO also each lose a few seats. Other constituencies are unaffected.
At the meetings themselves, translation is to be scaled back to be provided on an as-requested basis, rather than automatically translating everything into all six UN languages. Key sessions will continue to have live interpretation.
Outside of the three main meetings, ICANN is pulling back on plans to expand its irregular “capacity building” workshops in “under-served” areas of the world.
It’s also slashing the “additional budget request” budget by 50%.
In terms of compliance, a proposed Technical Compliance Monitoring system that was going to be built this year — a way to make sure gTLD registries and registrars are stable and secure — appears to be at risk of being deprioritized.
ICANN said it “will develop an implementation plan in due time, depending on the RFP results and, if needed, work with the Board to identify necessary resources and funds to support implementation of the project.”
The documents published today are now open for public comment until March 8.
The cuts I’ve reported here can be found from page 19 of this document (pdf).
The reason for the cutbacks is that ICANN’s revenue isn’t growing as fast as it once did, due to the slower than expected growth of the domain name industry in general. I’ll get to that a later article.

ICANNWiki could be first victim of budget cutbacks

ICANN is mulling whether to cut funding to ICANNWiki, the independent community encyclopedia, as part of its efforts to rein in spending.
There’s $100,000 at stake, more than half of the Oregon-based non-profit’s annual budget.
Ray King, the gTLD registry CEO who founded ICANNWiki in 2005, told DI today that ICANN has been providing funding for the last three years.
“While no decision has been made yet, there is a possibility that ICANN will not continue it,” he said in an email.
“We’ve poured our hearts and minds into this project for many years so this would be disappointing to say the least,” he said. “We believe in our mission and that it is in the community’s interest for this support to continue”.
An ICANN spokesperson said: “At this time, while it is highly unlikely that ICANN will be renewing its contract with ICANNWiki, we have not come to a final determination.”
ICANNWiki currently carries about 6,000 volunteer-edited articles covering many aspects of the ICANN community and the domain name industry in general.
It’s perhaps most recognizable for the frequently shared caricatures of community members it produces, such as this handsome devil, and the playing card decks handed out as freebies at ICANN meetings.
According to a letter (pdf) sent to ICANN earlier this month, ICANNWiki receives cash contributions of $161,000 a year, $61,000 of which comes from 10 corporate sponsors.
ICANNWiki estimates the 2,200 hours per year of volunteer work it benefits from is worth about $66,500. It says it has in-kind contributions worth about $40,000 from other companies.
It puts the value of its “reference services” at $339,959 a year.
That’s based on estimated visits to its site of 182,774 in 2017 (not including visits from its editors and staff) and a value per visit of $1.86 (based on an unrelated ROI calculation Texas Public Libraries used to justify its own existence earlier this year).
The ICANN $100,000 contribution is at risk now due to the organization’s plan to cut back on spending in the face of revenues that are coming in lower than expected due to a weak domain name market.
CEO Goran Marby said yesterday that its fiscal 2018 is currently running a million dollars short. Coupled with a perceived need to add an extra $80 million to its reserve budget, ICANN is looking for areas to cut costs.
ICANNWiki funding may be the low-hanging fruit in this endeavor; while it’s no doubt valuable (I probably use it two or three times per week on average), it’s perhaps not straightforward to quantify that value.
Even if the funding is cut, I would not expect ICANNWiki the web site to disappear, given the level of corporate sponsorship and in-kind services it receives and the low overheads suggested by its modest traffic numbers, but perhaps its growth and outreach ambitions would be curtailed.
UPDATE: This post was updated at 2307 UTC with a quote from ICANN.

ICANN, with $143 million budget, running out of cash

ICANN is to tighten its belt over the coming year as lower than expected revenue from domain name registrations has caused a budget shortfall and dwindling reserves.
The organization is $1 million short so far in its fiscal 2018, which CEO Goran Marby says is forcing him to look at making cuts to staffing costs, travel expenses, and community-requested projects.
Meanwhile, chair Cherine Chalaby says the board of directors is worried that ICANN’s reserve fund is $80 million shy of where it ideally should be.
Both men outlined their priorities in separate end-of-year blog posts this week.
It does not yet appear that anyone’s job is on the line.
Marby indicated that headcount would be reduced through attrition — sometimes not replacing staff who leave — rather than lay-offs.
“The reality is, ICANN has a significant budget but not an infinite budget. We need to make some changes, and can’t do everything we are asked,” he wrote, before explaining some areas where “efficiencies” could be found.

For example, when someone leaves ICANN org, we are taking a close look at the vacancy, the team’s needs and other people’s availability and skills before deciding if we are going to fill the role. We are also looking at our staff travel practices for ICANN meetings and other ICANN org commitments, reviewing our language services support levels and offering, and trying to consolidate our collateral and the volume of reports. We are looking at what projects we could delay or stop

Some might say that this renewed focus on how ICANN manages its money is overdue. The organization has bloated fast over the last several years, as over 1,200 new gTLD registries became contracted parties and interest in ICANN’s work grew globally.
In its financial year ending June 2012, it budgeted for revenue of $69.7 million and expenses of $67 million.
For FY2017, which ended this June, it was up to revenue of $132.4 million and expenses of $126.5 million.
Over the same period, headcount swelled from 158 full-time equivalents to 365. That was anticipated to grow to 413 by next June.
For the financial year ending next June, ICANN had budgeted for $142.8 million revenue, growing from $135.9 million, but Marby said in his blog post today that it might actually be flat instead.
As much as 64% of ICANN’s revenue is driven by transaction volumes — registrations, renewals and transfers — in gTLDs. In the quarter to September, revenue was $1 million behind plan due to lower than expected transactions, Marby said.
The message is to expect cuts, possibly to projects you care about.
Adding complexity, the ICANN board has decided following public consultation at 12 months funding is the appropriate amount ICANN should be keeping in reserve — so it can continue to function for a year should its contracted parties all abruptly decide not to pay their dues.
Unfortunately, as Chalaby outlined in his post today, this reserve pool is currently at about $60 million — just five months’ worth — so the organization is going to have to figure out how to replenish it.
Building up reserves to the tune of an extra $80 million is likely to put more pressure on the regular annual budget, leeching cash from other projects.
Chalaby said that the board will discuss its options at its February 2018 workshop.
Marby, meanwhile, said that a new budget will be out for public comment in mid-January.

Anger as ICANN splashes out $160,000 on travel

Should representatives of Facebook, Orange, Thomson Reuters, BT and the movie industry have thousands of ICANN dollars spent on their travel to policy meetings?
Angry registrars are saying “no”, after it emerged that ICANN last month spent $80,000 flying 38 community members to LA for a three-day intersessional meeting of the Non-Contracted Parties House.
It spent roughly the same on the 2015 meeting, newly released data shows.
ICANN paid for fewer than 10 registries and registrars — possibly as few as two — to attend the equivalent Global Domains Division Summit last year, a few registrars told DI.
The numbers were released after a Documentary Information Disclosure Policy request by the Registrars Stakeholder Group a month ago, and published on Friday (pdf).
It appears from the DIDP release that every one of the 38 people who showed up in person was reimbursed for their expenses to the tune of, on average, $2,051 each.
The price tag covers flights, hotels, visa costs and a cash per diem allowance that worked out to an average of $265 per person.
ICANN also recorded travel expenses for another two people who ultimately couldn’t make it to the event.
The NCPH is made up of both commercial and non-commercial participants. Many are academics or work for non-profits.
However, representatives of huge corporations such as Facebook and BT also work in the NCPH and let ICANN pick up their expenses for the February meeting.
Lawyers from influential IP-focused trade groups such as the Motion Picture Association of America and International Trademark Association were also happy for ICANN to pay.
One oddity on the list is the CEO of .sucks registry Vox Populi, who is still inexplicably a member of the Business Constituency.
MarkMonitor, a corporate registrar and Thomson Reuters subsidiary that attends the Intellectual Property Constituency, also appears.
Despite $80,000 being a relatively piddling amount in terms of ICANN’s overall budget, members of the Contracted Parties House — registries and registrars — are not happy about this state of affairs as a matter of principle.
ICANN’s budget is, after all, primarily funded by the ICANN fees registries and registrars — ultimately registrants — must pay.
“CPH pays the bills and the non-CPH travels on our dime,” one registrar told DI today.
One RrSG member said only two registrars were reimbursed for their GDD Summit travel last year. Another put the number at five. Another said it was fewer than 10.
In any event, it seems to be far fewer than those in the NCPH letting ICANN pick up the tab.
It’s not entirely clear why the discrepancy exists — it might be just because fewer contracted parties apply for a free ride, rather than evidence of a defect in ICANN expenses policy.
The NCPH intersessional series was designed to give stakeholders “the opportunity, outside of the pressures and schedule strains of an ICANN Public Meeting to discuss longer-range substantial community issues and to collaborate with Senior ICANN Staff on strategic and operational issues that impact the community”, according to ICANN.

ICANN ups new gTLD revenue forecast

ICANN has increased its new gTLD revenue projections for fiscal 2016.
The organization released its draft FY17 budget over the weekend, showing that it expects its revenue from new gTLDs for the 12 months ending June 30, 2016, to come in at $27.3 million.
That’s a 13% increase — an extra $3.1 million — on what it expected when it adopted its FY16 budget last June.
The anticipated extra money comes from registry and registrar transaction fees, spurred no doubt by the crazy speculation in the Chinese market right now.
Registry transaction fees are now expected to be $2.8 million (up from the earlier prediction of $2 million) and $3 million (up from $2.3 million).
The bulk of the new gTLD revenue — $21.5 million — still comes from fixed registry fees, which do not vary with transaction volume.
For fiscal 2017, which starts July 1 this year, ICANN is predicting new gTLD revenue of $41.5 million, a 52% annual growth rate.
The adopted FY16 budget is here. The new proposed FY17 budget is here. Both are PDF files.
The FY17 proposals are open for public comment.

ICANN slashes new gTLD revenues by 57%, forecasts renewals at 25% to 50%

ICANN has dramatically reduced the amount of revenue it expects to see from new gTLDs in its fiscal 2015.
According to a draft 2016 budget published this morning, the organization now reckons it will get just $300,000 from new gTLD registry transaction fees in the year ending June 30, 2015.
That’s down 75% from the $1.2 million predicted by its FY 2015 budget, which was approved in December.
Transaction fees are paid on new registrations, transfers and renewals, but only by gTLDs with over 50,000 billable transactions per year.
Today, only 14 of the 522 delegated new gTLDs have added more than 50,000 names. ICANN says that only 17 registries are currently paying transaction fees.
It’s not only the transaction fees where ICANN has scaled back its expectations, however.
The organization also expects its fixed new gTLD registry fees — the $6,250 each registry must pay per quarter regardless of volume — to come in way below targets.
The new budget anticipates $12.7 million from fixed registry fees in FY15, down 24% from the $16.7 million in its adopted FY15 budget.
This is presumably due to larger than expected numbers of would-be registries either withdrawing or dragging their feet in the path to delegation.
Registrar transaction fees are now anticipated at $1.1 million, compared to $2 million and $3.2 million predicted by the adopted and draft FY15 budgets respectively.
Taking all three revenue sources together, ICANN now expects new gTLDs to contribute just $14.1 million to its fiscal 2015 revenue, down 29% from the $19.8 million forecast in its adopted FY15 budget.
That’s down 57% from the $32.7 million in the original draft budget for the period.
The current budget assumes 15 million new gTLD registrations in the 12-month period, revised down from the 33 million domains predicted in its draft FY15 budget a year ago.
With just a few months left until the end of the fiscal year, there are currently fewer than 4.5 million domains in published new gTLD zone files.
ICANN plainly no longer expects new gTLDs to get anywhere close to 15 million domains.
Renewals expected to be weak, weak, weak
The organization is taking a conservative view about renewals for 2016.
The 2016 budget expects renewals at just 50% for regular gTLDs and 25% for registries — presumably ICANN has .xyz in mind — that gave away domains for free at launch.
That 50% is both ICANN’s “best” and “high” estimate. Its “low” estimate is 35% for non-free domains.
Obviously, 50% is a very low renewal number for any registry (70%+ is the norm). Even شبكة. (.shabaka) told us recently that 55% of its registrants are renewing before their domains expire.
Conversely, 25% may be a very optimistic number for free domains (when Afilias gave away free .info names a decade ago, almost all of them dropped rather than being renewed).
For fiscal 2016, which begins July 1, 2015, ICANN expects new gTLD revenue to be $24.1 million — about a quarter off its original plan for 2015.
That breaks down as $19.9 million from registry fixed fees, $2 million from registry transaction fees, and $2.3 million from registrar transaction fees.
ICANN said it is is assuming that it will start the year with 602 registries and end it with 945.
The proposed FY16 budget, now open for comment, can be found here.
For comparison purposes, the adopted FY15 budget is here (pdf) and the draft FY15 budget is here (pdf).

ICANN board bill tops $2 million

ICANN’s board of directors cost the organization over $2 million in pay and expenses in its fiscal 2014, a document released last night shows.
The total bill for the year ended June 30 was $2,000,609, up 16% on FY13’s $1,721,191 and up 27% on the FY12 figure.
The majority of the expenditure went on travel and other expenses. Just $538,983 went on compensation.
ICANN directors get $35,000 per year basic, plus another $5,000 for each board committee they chair. Board chair Steve Crocker gets $75,000 and accumulated $149,000 in FY2014 expenses.
Six directors chose to receive no compensation whatsoever, though they all racked up travel expenses.
The $2 million total does not include any contribution from CEO Fadi Chehade.
Chehade’s salary was $559,999. He also received $253,826 in bonuses and accumulated expenses totaling $519,421.
FY14 was of course the year in which Chehade and members of the board traveled extensively for outreach related to the IANA stewardship transition process and the NetMundial initiative.

Verisign steps up anti-gTLD campaign with attack on ICANN’s war chest

Verisign wants ICANN to publish a list of all the reasons it might be sued over the new gTLD program, claiming security and stability risks might be one of them.
In the latest salvo fired in its war against new gTLDs, the company now suggests that the $115 million “risk fund” surplus that ICANN has accumulated is for fending off lawsuits when it breaks the internet.
In a letter (pdf) sent Friday, Verisign asks ICANN to justify the existence of this war chest in light of the fact that it has managed to secure legal indemnities from pretty much everyone involved in the program.
It attempts to link the risk fund to the possible security risks of introducing new gTLDs to the internet, which Verisign has been haranguing ICANN about for the last few months.
“We believe ICANN should be forthcoming about the risks it is shifting and the need for the substantial risk reserve fund, in particular,” the letter, signed by general counsel Richard Goshorn, says.
It’s been well known for a few years that $60,000 of each $185,000 new gTLD application fee was to be allocated to a risk fund created to cover unexpected extra program costs.
The reserve was designed to cover things like underestimating the costs or time needed to evaluate applications, but also, crucially, the lawsuits that ICANN expected but has not yet received.
The cash pile is often to referred to, usually with black humor, as the “legal defense fund”.
Now Verisign seems to be saying that the legal risks are not limited to trademark disputes or the usual antitrust nonsense, but to the security risks ICANN is “transferring” to others.
As we’ve been reporting for the last few months, Verisign has suddenly decided that new gTLDs pose a risk to the internet, largely due to the potential for clashes between newly delegated strings and the unnofficial domains that many organizations already use on their intranets.
For a great discussion on the merits of this argument check out this DI article and comment thread.
With the latest letter, Verisign suggests that ICANN knows it might be sued for messing up corporate intranets, but is keeping that fact quiet.
Referring to a report it issued in March, when its security concerns first emerged, it says:

We believe that ICANN may have established and be maintaining the Risk Reserve in such a high amount in anticipation of significant claims relating to one or more risks identified in the Verisign Report.

If ICANN does get sued on these grounds, the defense cost will effectively have been covered by new gTLD applicants (and therefore their customers, assuming the costs are passed on), Verisign says.
It’s therefore asking for ICANN to disclose the reasons why its risk fund is so big, “in particular, the details regarding what ‘possible litigation’ factored into ICANN’s decisions”.
In other words, Verisign is asking ICANN to publish a list of reasons people might sue it, something I can’t imagine its general counsel agreeing to any time soon.
Is this an effort to shame ICANN into taking its security concerns more seriously, or just more FUD designed to disrupt the new gTLD program and protect its .com dominance?
Opinions, no doubt, will be split.

ICANN’s new gTLD fund at $352.3m

ICANN had $352.3 million in its new gTLD program bank account as of October 13, according to notes from a recent board meeting.
The numbers suggest that ICANN had only spent about $6 million on the program since the application window closed at the end of May.
With 1,930 applications at $186,000 a pop, excluding the seven refunds, ICANN should have grossed about $358 million.
The money is being held in a non-interest-bearing account, partly due to ICANN’s insistence that the program is not an exercise in self-enrichment.
Notes from the October 13 Board Finance Committee meeting also reveal that ICANN plans to revise its 2013 budget to account for the accelerated gTLD timetable.
The current budget was prepared before Digital Archery was scrapped and ICANN expected to process its applications in batches over two years. It now expects one batch lasting one year.

ICANN budgets for 2,000 new gTLDs

ICANN could net $150 million from a 2,000-application new gTLD round.
That’s according to a proposed budget published for comment last night, which for the first time contemplates more than 500 new generic top-level domain applications.
The budget also contains budgets for 500-application and 1,000-application rounds.
But with ICANN revealing this week that it has 1,268 registered users of its TLD Application System, 2,000 applications is beginning to look extremely plausible.
ICANN would receive $368 million in fees from a 2,000-app round, according to the budget, of which an estimated $33 million would be returned in refunds when applicants withdraw.
But the operating cost of the program would only come in at $156 million – slightly cheaper on a per-application basis than a 500-app round due to volume discounts from its contractors.
What happens to the rest of the money?
About $30 million is returned to the ICANN contingency fund to recoup program development costs. A $31 million surplus could be considered “profit” – it’s budgeted as an increase in net assets.
But the majority – $120 million – is budgeted to the amorphous “risk costs” line item.
The risk fund – sometimes flippantly referred to as the legal war chest – was budgeted to cover unanticipated costs such as delays and litigation.
ICANN evidently does not anticipate any economies of scale here. The $120 million in the budget is a simple multiple of the $30 million it said it needed to cover risk in a 500-application round.
It’s quite possible that ICANN won’t even need to dip into the risk fund, or that it might only need to withdraw a small amount, which would leave it sitting on an embarrassingly large wedge of cash.
The organization has yet to decide how its surplus would be deployed, but it’s going to be kept in a separate bank account and accounted for separately.