Number of subsidized gTLD bidders far lower than thought
A huge number of organizations that started applying to ICANN for subsidized new gTLD applications have apparently pulled out of the program, judging by newly released stats.
As of September 19, 42 would-be applicants had joined the Applicant Support Program, with ICANN stats published yesterday revealing that 30 have been removed compared to last month’s stats because they are “deemed inactive, with 90 or more days of inactivity.”
Last month, there were over 70 reported applicants.
To date, only three have received provisional approval and of those only one has fully progressed through the system. Only one has formally withdrawn from the process.
ASP promises applicants — only non-profits and/or charities so far, though small businesses from the developing world can apply too — 75% to 85% off the expected $227,000 application fee when the next application opens in Q2 next year.
ICANN has faced some criticisms from governments at the lack of applicants so far from under-serviced regions such as South America.
Sixteen new gTLD bids could face the firing squad
ICANN’s board of directors has an unusually bumper crop of non-trivial resolutions on its agenda for next week, including the fate of the .ly TLD, new anti-harassment rules, and killing off as many as 16 applications from the 2012 new gTLD application round.
Of the nine items on the agenda, published overnight, four stand out as noteworthy:
Termination Procedure for Remaining 2012 Round Applications that were not Successful
With ICANN spooling up to start accepting new gTLD applications in the second quarter next year, it appears to be ready to clear the decks of the last application round by killing off lingering applications.
While details of the proposed procedure are not yet available, it could apply to as many as 15 applications that are currently marked as “Will Not Proceed” or other failure states in ICANN’s application database.
Perhaps the most obviously affected application is Nameshop’s bid for .idn, which was rejected because the string matches a protected country-code for Indonesia. ICANN has been begging Nameshop to withdraw its application for many years, but the requests have fallen on deaf ears.
If ICANN’s search engine is to be believed, major companies such as Tata (.tata, blocked on geographic grounds) and L’Oréal (.salon, lost at last-resort auction to Identity Digital) still have failed, unwithdrawn applications.
Applications for contested, legally challenged, as-yet-undelegated gTLDs, including .web and .hotel, are also apparently still live in the system.
Transfer of the .LY (Libya) top-level domain to the General Authority of Communications and Informatics
Libya’s .ly ccTLD is notable because it’s somewhat popular as a domain hack for words that end in “ly”. It’s been delegated to Libyan state-owned General Post and Telecommunication Company for 20 years.
While the transition from GPTC to GACI, the government regulator, may just be a formality, there’s an added wrinkle that Libya, tormented by civil unrest since the fall of dictator Muammar Gaddafi in 2011, currently has two governments and GACI is reportedly aligned with just one of them.
Community Anti-Harassment Policy and Retirement of Board Working Group on Anti-Harassment
ICANN has been sitting on this one for longer than expected. The Org proposed revisions to its Community Anti-Harassment Policy a year ago and quickly putting them to public comment, but there’s been scant movement on the issue since January.
The proposed changes would further regulate personal and professional interactions between ICANN community members.
Some commenters complained that the changes do not go far enough, suggesting that situations where no offence was intended and none was taken should also be disciplinary infractions.
Others said that the changes would have a chilling effect and fail to sufficiently take into account cultural differences among ICANN’s global community.
The proposals came shortly after the latest in a series of sexual harassment lawsuits against the Org was revealed. That suit was settled after ICANN failed to get it thrown out of court.
Some relevant developments over the last eight months include the appointment of a new Ombuds and CEO, allegations (denied by ICANN) that it retaliated against friends of the latest harassment plaintiff by firing them, and ICANN’s capitulation to the Trump administration by easing itself away from public commitments to diversity, inclusion and equity.
Sixteen more orgs vie for cheap gTLDs, but…
Africa and Latin America are still under-represented in applications for ICANN’s new gTLD Applicant Support Program, according to the latest stats.
The program now has a whopping 76 organizations at some stage of the application process, which is 31 more than ICANN originally budgeted for. That’s up from 60 a month ago.
The program offers successful applicants a discount of 75% to 85% off the expected $227,000 application fee, among other perks such as access to pro bono service providers.
But the geographic breakdown shows that, as of the August 19 compilation date, only one more applicant hails from Africa and there’s only one more from Latin America and the Caribbean, compared to a month earlier.
Two influential ICANN advisory committees, including the governments, told ICANN earlier this month that they are “deeply concerned” that the ASP doesn’t seem to be reaching potential applicants in these two regions.
Hardly any applications have actually been submitted to be formally evaluated yet. There are 37 open applications that have yet to even submit the names of their organizations. Another 36 have done so, but not yet completed the application form.
I wonder if the top-line count may include a certain number of tire-kickers. The barriers to starting an application are pretty low, requiring just an account on the ICANN web site and a one-time password app on your phone.
Only three applications so far have been conditionally approved — one from Europe and two from Asia-Pacific — and three others from Asia-Pac have submitted their applications for review.
Of the 37 that have opened an application, the geographic region of 19 is still not known, so it’s possible the regional mix could change a lot as applications are actually submitted.
The program is open to charities and other non-profits, with participation from commercial entities limited to small businesses based in poorer regions.
Governments say new gTLD program “credibility” at stake
ICANN’s Governmental Advisory Committee is “deeply concerned” about the credibility of the new gTLD program’s Next Round, after a scheme to broaden the geographic spread of applicants has started to look like a failure.
The GAC and ALAC are calling for ICANN to address urgently what is seen as flaws in its Applicant Support Program, which offers deep discounts on application fees to small businesses in non-developed countries and to non-profit applicants.
GAC chair Nicolas Caballero and ALAC chair Jonathan Zuck said governments are “deeply concerned about the program’s current trajectory, particularly given the limited time remaining in the application window and the disproportionately low representation from underserved regions”.
ICANN said last week that it has approved the first three ASP applicants. One applicant is from Europe and two are from the Asia-Pacific region.
The latest monthly stats, dated July 23, show that only five applications were classified as “Submitted & in Review”, while 25 were “Initiated” and 26 were “In Draft”. By geography, 10 potential applications come from Africa, 16 from Asia-Pacific, four from Europe, 19 from North America and just two from Latin America.
Caballero and Zuck wrote (pdf):
we also identified a geographic imbalance from ICANN’s data… despite seven months of outreach, potential applications from North America (33%) vastly outnumber those from the LAC region (3%), raising questions about the inclusivity of the program.
…
we really think that the ASP is not merely a procedural requirement but a cornerstone of the Next Round’s credibility. At minimum, failure to address its structural challenges risks perpetuating the dominance of well-resourced entities, undermining ICANN’s multistakeholder principles. We kindly request the Board to treat this matter with the urgency it demands
They want ICANN to conduct a fast review of why the geographic balance is tilted towards North America at the expense of Latin America, Asia and Africa.
As I’ve previously noted, the North America region by ICANN’s definition is small. It doesn’t even include Mexico. Small businesses from the USA and Canada don’t qualify for the ASP and the only other places in the region are US island territories such as Puerto Rico and Guam.
The GAC and ALAC want to know whether the low uptake elsewhere is due to ICANN’s lack of local outreach, complexities in the application process, or costs. Why are draft applications not being submitted?
With the clock ticking down to the November 19 closure of the application window, The August 15 letter calls for ICANN to figure out what’s going wrong and let it know by August 22 — this coming Friday.
Even if it wasn’t August, and we weren’t talking about ICANN, that’s a pretty tight deadline.
AI experts replace Chapman on ICANN board
ICANN’s Nominating Committee has announced its annual picks for the Org’s board of directors, with two new fresh faces, both of whom have notable AI policy experience, joining.
Constance Bommelaer de Leusse and Raúl Echeberría, respectively French and Uruguayan internet policy experts, are the newcomers. Australian former regulator Chris Chapman is leaving after just one three-year term.
Echeberría is perhaps the more-familiar name, having been involved with ICANN since its early days. He’s a founder and former long-time CEO of LACNIC, and has held roles in ISOC, WSIS, and the IGF. He’s also former chair of ICANN’s Number Resource Organization.
De Leusse is a French academic, raised in the US, currently employed by the Sciences Po and Ecole normale supérieure (ENS-PLS) universities in Paris. She is a former ISOC VP.
Both have AI policy experience. Echeberría earlier this year sat on the steering committee of the AI Action Summit, hosted in Paris by President Macron, while de Leusse works for the AI & Society Institute at ENS-PLS.
On social media, de Leusse describes herself as a winemaker, which may or may not prove interesting.
NomCom also reappointed Sajid Rahman for a second three-year term. One of the two new appointees replaces former board chair Maarten Botterman, who is term-limited after nine years’ service. The other replaces Chapman.
In terms of geographic balance, it means a director from the Asia-Pacific region has been replaced by one from Latin America. I don’t believe this causes any significant issues in terms of limiting other groups’ election options.
NomCom, which also selected seven other people for non-board roles, said 37% of its candidates were from Africa, with 25% from Asia-Pac, 16% from Latin America, and 8% from Europe.
Only 2% were from North America, perhaps due to the fact that NomCom was unable to pick anyone from that region for a directorship due to its geographic diversity quotas.
NomCom said that 27% of its candidates were female, 73% male, which is broadly in line with previous years and historical stats for general ICANN participation.
The new appointees take their seats at the conclusion of ICANN’s AGM in October.
Golding challenges McCarthy for Nominet board seat
Nominet has revealed the names of just two candidates who are standing in its non-executive director election this year.
Rob Golding of Astutium is on the ballot again, this time challenging incumbent Kieren McCarthy, who is standing for re-election for a second three-year term.
Golding stood last year and came a very close third place when there were two seats available. McCarthy won his seat in 2022 with a more comfortable margin, but only after a second round of voting.
Voting this year opens September 26 and the winner would take his seat in October at Nominet’s AGM.
Three applicants qualify for cheapo gTLDs
Three organizations have been given ICANN’s approval to apply for new gTLDs next year at a deeply discounted rate.
All three are non-profit or nongovernmental organizations, ICANN said. Two come from the Asia-Pacific region and one comes from Europe.
The identities of the applicants have not and will not be disclosed — to publish their names would likely tip the applicants’ hands in terms of what strings they intend to apply for, inviting competition.
The Applicant Support Program offers non-profit entities worldwide or small businesses in non-developed nations a discount of 75% to 85% on the base $227,000 application fee, along with a selection of other benefits.
As of today, there are 45 active applications, ICANN said. Seven come from Africa, 14 from Asia-Pac, five from Europe, two from Latin America, and 12 from North America. Another five haven’t said where they’re based yet.
According to July 23 stats, only five applications — three of which presumably have now been approved — had been fully submitted and were in review.
In the 2012 round, there were only three ASP applications and only one, from the company that now runs .kids, was successful in obtaining the discount.
The window for ASP applications closes in November.
Blockchain crisis looming for new gTLD next round
New gTLD applicants could face more of a threat from blockchain-based alternative naming systems next year than perhaps they first thought.
ICANN is coming under pressure to give additional rights to the owners of top-level strings that act like TLDs on blockchains, potentially adding friction — and six figures of extra costs — to applications for matching strings.
In the recently closed public comment period on the current draft Applicant Guidebook, two blockchain naming firms focused on the risk posed from name collisions should a gTLD get delegated that matches a blockchain TLD.
More importantly, ICANN’s influential Security and Stability Advisory Committee expressed the same views.
Alexander Urbelis, general counsel and CISO of Ethereum Name Service, said in his comments that many operators of alt-TLDs will apply for their DNS matches in next year’s application round, adding:
ICANN should consider that a new gTLD, for which an identical string already exists in an alternative name space, should be considered a compromised asset, and that delegating such gTLDs may subject ICANN, and applicants, to substantial liability. In addition to the technical issues posed by name collision, such delegations could also result in consumer confusion, difficulties with resolving queries (particularly as access to alternative names is increasingly integrated into mainstream web browsers), security risks, and broken authentication systems
Shifting gears, Urbelis then goes on to espouse the exactly opposite view to what you might expect from an operator of a blockchain naming system:
We urge ICANN to ensure that operators of strings in alternative names spaces are not given preferential treatment in the upcoming new gTLD application round, either deliberately or inadvertently. Such operators should not be rewarded for choosing to operate outside of ICANN governance and policies, particularly when the results of such preferential treatment could be so devastating for the stability of the DNS, as well as consumer trust in the new gTLD program and the DNS itself.
However, he concludes that alt-TLDs should be considered during the application process, specifically when ICANN’s evaluators conduct the String Similarity Evaluation.
we note that the string similarity evaluation does not appear to account for strings that may exist in alternative name spaces that are not under ICANN governance. Given the proliferation of such strings and alternative name spaces in recent years, ICANN should not ignore their existence by considering string similarity within only the ICANN-governed DNS, particularly due to the technical issues outlined above in connection with name collision.
Currently, this evaluation stage only looks at similarity to existing TLDs, some strings blocked by policy, and other applied-for strings.
If Urbelis’ advice were taken on board, an application for .clown, for example, could find itself ruled similar to alt-TLD .down, which is on the Handshake naming system and available at some registrars.
ENS runs .eth as a blockchain TLD. While the company claims over 1.6 million names registered there, .eth can never make it to the consensus DNS because ETH is the protected three-letter code for Ethiopia and therefore blocked by a Guidebook policy that is pretty much locked-in.
Unstoppable Domains, which markets dozens of alt-TLDs, focused on name collisions in its brief comment to ICANN, seeking extra clarity in how the collision assessors will decide whether a string is “high risk”.
The current AGB says evaluators will look at both quantitative data — measurements of traffic for non-existent TLDs to the root servers for example — and unspecified “qualitative” factors. Unstoppable’s head of operations Michael Campagnolo wrote:
If ICANN wants to help applicants to assess their risk pre-application submission, examples and sources of qualitative evidence should be described and made available to applicants prior to, and in a reasonable amount of time before the opening of the application window, similar to the quantitative information.
The subtext here, it appears, is that Unstoppable wants to know if non-DNS qualitative factors, such as the existence of an alt-TLD matching an applied-for string, will be taken into account.
That’s a good question, and as the AGB currently stands it appears to be up to the Technical Review Team that will conduct the name collision evaluation on each application.
The Name Collision Analysis Project working group, which came up with most of the current name collision rules, seemed to have mostly ignored alt-TLDs in its work due to difficulty and timing.
Unstoppable points out that applicants with strings deemed at high risk of collisions could incur extra fees of $100,000 to $150,000, on top of the $227,000 standard application fee, so the extra clarity on the rules could avoid applicants having to reach deeper into their pockets.
While ICANN is adept at ignoring or merely paying lip service to self-serving public comments filed by commercial entities, it is bound by its bylaws to take the advice of its Advisory Committees seriously.
Comments filed by the 17-member SSAC will carry more weight, and SSAC is warning that collisions between DNS and non-DNS naming systems could raise security risks, promote instability, and create user confusion.
SSAC’s SAC130 (pdf) — formal Advisory Committee advice — makes four recommendations related to name collisions. One is:
The AGB should explicitly state that the TRT is allowed to include evaluating potential collisions with known, widely used alternative naming systems and other external sources, as these can create foreseeable security and stability risks for DNS users.
If ICANN adopts the SSAC recommendations, it seems the TRT will be encumbered with the heavy burden of figuring out how, when and why an alt-TLD and an applied-for gTLD create risks so unacceptable that the applied-for string should be blocked.
Another question that has been raised in recent weeks is whether alt-TLD operators should be able to use mechanisms such as Community Priority Evaluation and Community Objection to secure their TLDs or disrupt other applications.
Could Unstoppable, for example, claim that its cohort of .wallet alt-TLD registrants constitute a protected “community” and thus get a priority approval?
The company could certainly try, but experts in the policy-making community and ICANN staff seem to think the point-based CPE mechanism is designed in such a way to make such a claim incredibly difficult to back up.
ICANN will consider all of the public comments over the coming weeks and months before making changes, if any, to the AGB.
There are hundreds of thousands of alt-TLDs out there — over 6,000 are even carried by a handful of ICANN-accredited registrars — but it’s not clear how many are actually used.
With that in mind, should ICANN offer additional protections to blockchain-based alt-TLDs, many new gTLD applicants would face the very real risk of additional friction and huge extra costs.
ICANN looking at new bulk reg rules
ICANN seems set to start creating more rules governing DNS abuse, including limits on bulk registrations and more tracking of registrants.
A small team of GNSO volunteers have put together a list (pdf) of dozens of proposed policy change areas, covering everything from registrant data accuracy to pricing to API access to getting ICANN Compliance to be more proactive.
While most of the ideas in the team’s analysis received a broad range of views, it settles on three areas, all related to bulk registration of abusive domains, that it thinks are ripest for further policy work.
The first is “Associated Domain Checks”. The small team think it’s worth looking into whether registrars should have to investigate proactively domains registered by known abusive registrants.
The group also thinks it’s worth looking into better industry information-sharing about domain generation algorithms, which bad actors use to create vast numbers of gibberish names that can be used in spam runs, phishing attacks, or botnets.
Finally, the group thinks rules around API access to registrar platforms should be looked at, given that bulk-registered abusive domains often seem to use APIs to programmatically obtain thousands of throwaway domains in seconds.
The small team thinks a Policy Development Process looking at just these three issues could be completed relatively quickly and the community could address the remaining issues later.
Whether the recommendations go to a PDP is now up to the GNSO Council, which will vote on the matter this Thursday. Assuming the vote passes, which seems likely, ICANN staff would then have to prepare a formal Issue Report, setting out the scope of future work, if any.
A PDP would likely take years to complete.
The three priority topic areas reflect closely the Governmental Advisory Committee advice coming out of June’s ICANN 83 public meeting. Both small team and GAC heavily source ICANN’s INFERMAL research and a recent NetBeacon white paper as their inspirations.
Wine producers worried about new gTLDs
American vintners are worried that someone might steal their protected regional names in the next new gTLD round.
The Napa Valley Vintners has written to ICANN to “express strong opposition to the creation of any generic top-level domain
(gTLDs) that uses our distinctive name.”
The trade association asks that the names of wine-producing areas of the States be added to the Reserved Names List in the new gTLD program’s Applicant Guidebook.
That list currently is limited to the names of intergovernmental organizations, NGOs, and Red Cross/Crescent related entities.
The NVV points out that the names of wine-producing regions are protected by US law — you can’t say your wine comes from Napa unless it was in fact made there.
According to Wikipedia, there are 276 protected American Viticultural Areas in 34 states. More than half are in California.
Some of these names actually have a small degree of protection already, but only accidentally. The string “Napa” would be considered a protected geographic string until the current AGB rules, for example, but only if somebody wanted to run .napa as a city-gTLD.
The issue of protecting wine-related geographic indicators has come up at ICANN before. While it was processing the applications for .wine and .vin in 2014, there was a protracted bust-up in the Governmental Advisory Committee about whether they should go ahead.
Several European governments pressed ICANN to ban or delay .wine, now an Identity Digital gTLD, until promises were made about protecting names like “Champagne” and “Rioja” at the second level.
France in particular got very pissed off, but ultimately objections were dropped after the registry made some kind of deal with the wine-makers.
The NVV letter is cc’d to the federal government’s Alcohol and Tobacco Tax and Trade Bureau, presumably to send the message that the group is not messing about.
The letter (pdf) is addressed to “The Honorable Sally Costerton”, under the apparent assumption that she’s still ICANN’s acting CEO. That hasn’t been true for the last eight months. Also, as lovely as she is, I’m not sure she qualifies for that particular honorific.
Recent Comments