Thursday , August 11 2022

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.

The post ICANN lists the reasons I probably won’t be going to ICANN 74 first appeared on Domain Incite.

About Kevin Murphy

Check Also

Buyer “phasing out” domain “bought for $2.2 million”

The domain name coupons.com, which was acquired for a reported $2.2 million over two decades …

Leave a Reply

Your email address will not be published.