ICANN lists the reasons I probably won’t be going to ICANN 74

“Don’t blame us if you die!”

That’s one of the messages coming out of ICANN, which has confirmed that it’s returning to in-person meetings for ICANN 74 this June.

The “hybrid” four-day meeting in The Hague is going ahead, but under strict Covid-19 mitigation rules that seem a bit too annoying for this particular potential attendee.

If you want to get in the venue, you’ll need to show proof of a full course of WHO-approved vaccinations, wear a face mask, stay an appropriate distance away from your peers, and subject yourself to a temperature check and “health screening” every time you walk through the door.

You’ll be issued a wrist-band on first entry that you have to keep visible at all times. If you lose it, you’ll have to re-verify your vaccination status.

As somebody who got irritated by even the metal detectors as pre-Covid ICANN meetings, this all seems a bit too much of a hassle for me, despite The Hague being pretty much right on my doorstep. I probably won’t go, at least not for the full four days.

There will be no on-site registration, and you’ll have to register your attendance online five days in advance of the meeting, which begins June 13.

ICANN’s also asking attendees to sign away their rights, and their children’s rights, to sue if they get sick, even if they catch the virus from general counsel John Jeffrey walking up and sneezing a Covid payload directly into their eyes.

As spotted by Michele Neylon, the registration process for ICANN 74 contains an extensive, obligatory waiver that contains the following text:

Participation in the Event includes possible exposure to and illness from infectious diseases including but not limited to COVID-19. While particular rules and personal discipline may reduce this risk, the risk of serious illness and death exists. I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19, even if arising from the negligence or fault of ICANN. I understand that, unless otherwise confirmed in writing by ICANN, if I am suggested or required to take diagnostic tests, seek medical treatment, extend my stay due to quarantine or illness, or otherwise change travel arrangements, I am responsible for making such arrangements and all costs incurred. I understand that ICANN recommends that I obtain appropriate insurance to cover these risks.

…

I hereby knowingly assume all risks, and covenant not to sue any employees, board members, agents, executives, contractors or volunteers of ICANN or its affiliate for any expense, loss, damage, personal injury, including loss of life, illness, including but not limited to COVID-19, disability, property damage, or property theft or actions of any kind that I may hereafter suffer or sustain before, during, or after the Event, unless said expense, loss, damage, personal injury, including loss of life, illness, disability, property damage or property theft or actions of any kind is caused by the sole, gross negligence of ICANN or its affiliate. This Liability Waiver and Release is specifically binding upon my heirs and assigns and is knowingly given.

I agree to indemnify and hold ICANN and its affiliate harmless from and against any claims, suits, causes of action, loss, liability, damage or costs, including court cost and attorneys’ fees, and fees to enforce this Agreement, that ICANN may incur arising from my involvement in the Event.

This kind of waiver is par for the course with ICANN. Just ask any new gTLD applicant. ICANN really, really doesn’t like being sued.

ICANN has outlined its health-and-safety measures, which may change, here. The waiver can be read during the registration process.

1 Comment Tagged: coronavirus, covid-19, ICANN, icann 74, pandemic, the hague

A public apology for my April Fool’s blog post

Earlier today, I published a lighthearted April Fool Day’s blog post concerning the fictional invasion of Los Angeles by a chthonic demon entity, accidentally summoned by a DNSSEC misconfiguration at an ICANN ceremony.

In the course of the post, I made multiple references to “enslavement” and “madness”, and as a result I’ve received a substantial number of complaints both privately and on social media about my choice of language.

Having considered these complaints, I’d like to publicly acknowledge that slavery and mental health are not laughing matters and should not be the subject of jokes, or even referred to in jokes, under any circumstances.

Please accept my sincerest apologies for these oversights. I shall endeavor to be more sensitive in my choice of words in future.

I am a work in progress.

8 Comments Tagged: april 1

ICANN accidentally summons Lesser Old One in DNSSEC snafu

Southern California has come under the control of timeless demonic entities, plunging the Greater Los Angeles Area into a thousand years of darkness and torment, after a DNSSEC misconfiguration led to ICANN accidentally summoning a Lesser Old One into the mortal realm.

“I can confirm that there was an RRSIG glitch during the ceremony to sign the root zone ZSK for 2022Q2 and introduce HSM6W at our secure facility in El Segundo, California, today,” an ICANN spokesperson said.

“A downstream KSK misconfiguration was inadvertently introduced into the IMRS, resulting in a cascading Trust Anchor collapse across the entire constellation,” he said.

“This unfortunately led to the opening of a transdimensional portal to the Lost City of R’lyeh and the manifestation of an entity our initial analysis indicates may be Baoht Z’uqqa-Mogg, High Commander of the Armies of the Damned and celestial envoy for the mighty Cthulhu,” he added.

“And for some reason Facebook is down in Denver; we’re looking into that too,” the spokesperson said.

ICANN’s Seven Secret DNSSEC Key Holders were observed fleeing from the data center where the signing ceremony had been taking place, casting aside their cowls and robes and clawing at their eyes and skin, according to local reports.

They were pursued by a wailing, forty-foot-tall scorpion-faced lizard monster, emerging from a blinding disc of purple hellfire and bent on subjugating the human race to millennia of torment, local TV station Fox Action 5 Shooty Shooty Bang Bang News reported from the scene, shortly before its news chopper was plucked from the sky by a blistered tentacle and tossed into Z’uqqa-Mogg’s slavering, beak-like mandibles.

The entity was then seen slamming its cloven hoof into the ground and performing an obscene incantation, opening a rift through which poured a horde of bloodthirsty, crab-headed minions that proceeded to swarm through the streets of LA, devouring all in their path.

“This is the one thing we hoped would not happen,” the ICANN spokesperson admitted.

In response to the crisis, which has so far resulted in the deaths of millions and the enslavement into madness of half the US west coast, ICANN’s Security and Stability Advisory Committee has formed an ad-hoc working group to devise possible strategies to banish the Old One to its cthonic netherworld.

It’s planning to deliver an initial draft of its report no later than September 2023, after which its work will be opened to the Whatever’s-Left-Of-The-Public Comment process.

1 Comment Tagged: april 1

ICANN “volunteers” want to get paid for sitting through pandemic Zoom calls

It’s often said that ICANN policy-making has become so complex, long-winded and thankless that it’s becoming harder and harder to attract and retain community volunteers, and now some of those community members are calling on ICANN to open its wallet to sweeten the deal.

ICANN could provide volunteers, particularly those who have participated heavily in remote meetings during pandemic travel restrictions, with monetary stipends or free business trips to future ICANN meetings, the At-Large Advisory Committee has said.

In a letter (pdf), ALAC chair Maureen Hilyard, along with members Marita Moll and Joanna Kulesza, ask that ICANN starts measuring the contribution of its volunteers and compensate them according to their work.

“There is a need to recognize and reward the efforts of volunteers who kept the public face of the institution going through 7 virtual public meetings,” they wrote.

“The pandemic ultimately exposed the limited efficiency of the existing volunteer system within the ICANN community. It is clear that the system of incentives currently in effect needs to be adjusted to address challenges of the post-pandemic reality,” the letter says.

ICANN’s thrice-yearly public meetings have been held over Zoom since the start of 2020 due to the coronavirus pandemic. Many community members have not sat in the same room as their peers for over two years.

ICANN 72 last October had the lowest turnout since records began, though this bounced back a little at ICANN 73.

ALAC’s suggestions for incentivizing its members include extending the term of leadership appointments to enable some face-time at future meetings, paying for “one or two trips to future ICANN meetings” and “a retroactive honoraria for those who would have been funded travellers during the period of virtual meetings, considering the fact that they were still incurring costs re: internet connection, electricity, food, etc”

An “honorarium” is a cash payment for services rendered on a voluntary basis. Basically, ALAC seems to be asking for travel expenses that were not incurred to be reimbursed retroactively regardless.

ICANN already has a program for reimbursing community members, such as those on metered connections, who incur extra connectivity charges during ICANN meetings, but it has regardless saved millions of dollars on funded travel since the pandemic started.

The letter goes on to say “volunteer work by definition is work without pay or compensation” but that “forms of monetary or in-kind compensation are possible”. These could include stipends, “symbolic gifts” and reimbursements.

Before you start getting outraged about the potential for high-priced IP lawyers and well-paid registry VPs putting their hands in ICANN’s pocket, ALAC is asking ICANN to distinguish between genuine volunteers and those who are paid for, or get a direct business benefit from, participating in community work.

ALAC defines volunteers as “individuals who commit time and effort to the work of ICANN with no personal connection to the domain name industry and who pay their own costs of participation, engagement and commitment to this work”.

That’s a rare thing in some segments of the community, but more common in the At-Large community.

Many of the issues raised in the letter were also discussed at the ALAC’s session with the ICANN board earlier this month.

2 Comments Tagged: .travel, alac, burnout, ICANN, icann 73

War fails to stop .ua domains selling

Ukraine’s ccTLD has maintained what appears to be a healthy level of new registrations, despite the Russian invasion.

The company today reported that between February 24 and March 25, it saw over 3,000 new .ua domain regs, over 2,000 of which were in .com.ua. The ccTLD offers names in a few dozen third-level spaces.

February 24 was the day Russia invaded, and the day Ukraine went into martial law.

“The com.ua domain is mostly used by commercial organizations. Therefore, the presence of registrations shows that Ukrainian business continues to operate under martial law,” Hostmaster wrote (via Google Translate).

.ua had a total of 534,162 domains under all 2LDs today, according to the registry’s web site.

While Hostmaster has not yet published its end-of-month stats for March, it appears that the new adds suggest an improvement on typical monthly performance, or at least business as usual.

The registry has come under denial-of-service attack dozens of times since the war started, but says it has so far continued to operate without interruption.

Comment Tagged: .ua, hostmaster, ukraine, war

Marby pledges low red tape in $1 million Ukraine donation

It’s been three weeks since ICANN promised $1 million to support internet access in Ukraine and CEO Göran Marby says he’s trying to get the money put in to action as efficiently as possible.

Thankfully, the Org doesn’t seem to be resorting to its regular fallback position of creating a time-consuming committee or esoteric process, but there are still some hoops that need to be jumped through.

Marby wrote today:

We made the decision to partner with an organization that is already on the ground in Ukraine providing support that is in alignment with our mission. I believe that contributing to an existing organization is a better option than creating our own tailor-made solution, especially when we do not have expertise in disaster recovery and crisis response work.

ICANN is doing due diligence on “several” organizations to make sure the Org meets “applicable laws, regulations, and ICANN’s fiduciary obligations”, he wrote.

While the money has been committed to help internet access — in line with ICANN’s mission — nothing has been publicly disclosed about what specifically it will be spent on.

One idea floated during ICANN 73 earlier this month was to provide satellite terminals that could be used to work around any infrastructure damage caused by the Russian invasion on the ground.

Marby wrote:

We are working diligently to implement this initiative in a timely manner, doing everything we can to speed the process, while at the same time proceeding in a cautious and responsible way.

He promised an update when the money has been allocated.

Comment Tagged: ICANN, ukraine, war

2LDs boost .au’s growth

Australian ccTLD registry auDA has been reporting registration volumes growing much faster than usual in the days since it started selling .au domains directly at the second level.

The company is currently reporting a grand total of 3,492,366 domains, which is up by almost 78,000 since March 24, when 2LDs went on sale.

Normally, .au rarely grows by more than about 500 domains per day.

Right now and for the next six months, all 2LDs have been reserved for the owners of their exact-match third-level domains, so there’s not the same kind of rush you might expect in a first-come, first-served scenario.

Comment Tagged: .au, 2lds, auda, second-level

With mystery auction winner, .sexy prices go from $25 to $2,500

UNR is increasing the annual price of a .sexy domain from $25 to over $2,000, according to registrars.

The price increase will hit from April 30, according to registrars, but will not affect renewals on domains registered before that date.

French registrar Gandi said its retail price for a .sexy name will increase from $40 to $2,750. That’s after its mark-up. Belgian registrar Bnamed said in January prices were about to get 100 times more expensive.

The current wholesale price for .sexy is believed to be $25 a year. I’m guessing it’s going up to about $2,500, which is a price tag UNR has previously experimented with for its car-related gTLDs.

UNR CEO Frank Schilling has previously defended steep price increases for TLDs that under-perform volume-wise.

.sexy had barely 6,000 names under management at the last count, having peaked at about 28,000 in 2017.

The question is: who’s decided to increase the prices? Did .sexy actually sell when UNR tried to offload its portfolio last year, or is UNR keeping hold of it?

.sexy was among the 23 gTLD contracts UNR said it sold, mostly at auction, about a year ago. But it’s not one of the ones where the buyer has been yet disclosed.

The gTLDs UNR said it sold were: .audio, .blackfriday, .christmas, .click, .country, .diet, .flowers, .game, ,guitars, .help, .hiphop, .hiv, .hosting, .juegos, .link, .llp, .lol, .mom, .photo, .pics, .property, .sexy and .tattoo.

Of those, a new company called Dot Hip Hop bought .hiphop and XYZ.com bought .audio, .christmas, .diet, .flowers, .game, .guitars, .hosting, .lol, .mom and .pics.

ICANN has approved those 11 contract reassignments — after some difficulty — and said that there are six remaining in the approval process.

That only adds up to 17, meaning there are six more that UNR said it sold but for which it had not, as of a week ago, requested a contract transfer.

But in May last year, UNR “announced gross receipts of more than $40 million USD for its 20+ TLDs”, said there had be 17 participating bidders, and that 10 to 20 had “came away as winners, including six who will be operating TLDs for the first time”.

That leaves with at least five as-yet undisclosed winners from outside the industry, six contract transfers outstanding, and six gTLDs with an unknown status.

Neither UNR nor ICANN have been commenting on the status of pending transfers.

1 Comment Tagged: .sexy, blockchain, bnamed, dot hip hop, ens, ethereum, gandi, ICANN, pricing, uniregistry, unr, xyz.com

Ukraine registry hit by 57 attacks in a week

Ukrainian ccTLD registry Hostmaster today said its infrastructure was hit by 57 distributed denial of service attacks last week.

On its web site, which has continued to function during the now month-long Russian invasion, the company said it recorded the attacks between March 14 and 20, which a top strength of 10Gbps.

“All attacks were extinguished. The infrastructure of the .UA domain worked normally,” the company, usually based in Kyiv, said.

Hostmaster took the initiative in the first days of the war to move much of its infrastructure out-of-country, to protect .ua from physical damage, and to sign up to DDoS protection services.

Comment Tagged: .ua, hostmaster, russia, ukraine, war

ICANN says higher domain prices may be in the public interest

ICANN is trying to get an arbitration case covering the removal of price caps in .org, .biz and .info thrown out because it is registrants, not registrars, that are left shouldering the burden of higher prices.

The argument came in January filings, published this week, in the two-year-old Independent Review Process case being pursued by Namecheap, which is trying to get price caps reinstated on the three gTLDs.

ICANN’s lawyers are saying that the case should be thrown out because Namecheap lacks standing — IRP claimants have to show they are being harmed or are likely to be harmed by ICANN’s actions.

According to ICANN, Namecheap is not being harmed by uncapped domain prices, only its customers are, so the case should be dismissed.

Drawing heavily on an analysis commissioned by ICANN from economist Dennis Carlton, ICANN’s latest IRP submission (pdf) reads:

rational economic theory predicts that if wholesale registry prices increased, Namecheap would pass on any price increases to its customers. Namecheap is one of nearly 2,500 ICANN-accredited registrars that offer domain names to registrants, and one of hundreds of ICANN-accredited registrars that offer domain names specifically in .BIZ, .INFO, and .ORG. Namecheap thus competes against many other registrars that have exactly the same access to same registries, such as .BIZ, .INFO, and .ORG,as does Namecheap, which all pay the same wholesale price for these registry input…

Given the hundreds of registrar competitors (each facing the same registry prices from the .BIZ, .INFO, and .ORG registry operators), economic theory predicts that Namecheap and other such registrars do not have significant market power. Without market power, registrars like Namecheap do not earn supra-competitive margins and cannot absorb higher input costs. As a result, economic theory, as well as common sense, predicts that Namecheap and other competing registrars must pass on higher registry wholesale prices by raising prices to registrants, with little or no resulting harm to Namecheap.

The filing goes on the suggest that higher prices might actually be in the public interest, because ICANN lacks the expertise to set price caps at an appropriate level.

the likely harms of price regulation in these three gTLDs outweigh the likely benefits of price controls. ICANN lacks the expertise to set optimal prices. Without such expertise, the danger is that ICANN could set the wrong price — one that impairs efficient market outcomes — which would ultimately harm registrants rather than protect them…

In short, Namecheap cannot demonstrate that the public interest required ICANN to maintain price control provisions in the .BIZ, .INFO, and .ORG Registry Agreements, especially given that the majority of evidence they cite either pertains to a drastically different DNS or pertains to potential harm to registrants, not registrars.

Interestingly, in almost the same breath, the filing argues that the price of .com domains, which is capped per Verisign’s agreements with ICANN and the US government, acts as an effective deterrent to runaway price increases in other gTLDs.

With its popularity, and relatively-low, regulated price, .COM acts as a check on any registry, including .BIZ, .INFO, and .ORG, that seeks to increase prices above competitive levels.

So, regulating .com prices is good because it indirectly acts as a restraint on other registries’ prices, but regulating those other registries’ prices is bad because ICANN lacks the expertise to regulate prices.

And anyway, it’s only the registrants who get harmed if prices go up.

Got it?

4 Comments Tagged: .biz, .info, .org, ICANN, irp, namecheap