<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
Interestingly, that language would be considered ridiculously unenforceable, here in the US but apparently is normal, under Dutch law
<div><br>
</div>
<div id="ms-outlook-mobile-signature" dir="auto">Jonathan Zuck<br>
Executive Director<br>
Innovators Network Foundation<br>
<a href="http://www.InnovatorsNetwork.org" target="_blank">www.InnovatorsNetwork.org</a><br>
Main: +1 (202) 827-7594<br>
Direct: +1 (202) 420-7483<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> At-Large <at-large-bounces@atlarge-lists.icann.org> on behalf of Holly Raiche via At-Large <at-large@atlarge-lists.icann.org><br>
<b>Sent:</b> Wednesday, April 27, 2022 4:47:25 PM<br>
<b>To:</b> Greg Shatan [ALAC] <gregshatanalac@gmail.com><br>
<b>Cc:</b> At Large <at-large@atlarge-lists.icann.org><br>
<b>Subject:</b> Re: [At-Large] info on waiver to attend ICANN74I</font>
<div> </div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">Thanks Greg
<div class=""><br class="">
</div>
<div class="">And I agree with the IPC - it is extraordinary that ICANN would seek such a waiver. This should absolutely be on the table for discussion and someone from ICANN Org should explain why they are taking such an extraordinary step as seeking to legally
deny all responsibility for ANY negligence on their part that could impact on attendees (even if totally unrelated to COVID). I’d rather attend by zoom than run the risk of being injured through negligence on the part of ICANN and have no legal avenue of
recovery. I’d be much happier if the last phrase (<i class="">even if arising from the negligence or fault</i>) were omitted. It is that phrase that goes beyond what could be reasonably expected, given COVID. This is particularly true for ALAC, given that
many, if not most, of the ALAC attendees would need to pay for any injury incurred - regardless of whether ICANN was negligent. </div>
<div class=""><br class="">
</div>
<div class="">Holly<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 28, 2022, at 7:32 AM, Greg Shatan [ALAC] via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" class="">at-large@atlarge-lists.icann.org</a>> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div dir="auto" class="">As an additional data point, I will note that the IPC, which is chock full of American lawyers, was up in arms about this and held a special meeting just to discuss the waiver. (I did not attend as I’ve stepped back from IPC while on
the ALAC.) My understanding of the ultimate conclusion of that meeting was to live with the waiver and not try to fight it. I’ll need to see what the reasoning is. But I assume that if IPC thought it was worth making a stink about, they would have done so.
This should not dissuade us from discussing the waiver — it’s just worth knowing.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Greg</div>
<div class=""><br class="">
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Wed, Apr 27, 2022 at 4:54 PM Antony Van Couvering via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" class="">at-large@atlarge-lists.icann.org</a>> wrote:<br class="">
</div>
<blockquote class="x_gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div class="" style="word-wrap:break-word; line-break:after-white-space">We are litigious, certainly, but it is requirements like these that make us so.
<div class=""><br class="">
</div>
<div class="">Suspicious minds might wonder if one of the staff or directors has a known STD and a rampant libido and ICANN legal is worried about being held responsible for a syphilis outbreak. </div>
<div class=""><br class="">
</div>
<div class="">Or whether speaking in acronyms and boring everyone in near proximity about the progress of their working group is an infectious disease that ICANN is worried about being blamed for. </div>
<div class=""><br class="">
</div>
<div class="">The possibilities are endless...</div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 27, 2022, at 1:40 PM, Salanieta T. Tamanikaiwaimaro via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank" class="">at-large@atlarge-lists.icann.org</a>> wrote:</div>
<br class="">
<div class="">
<div dir="ltr" class="">The important thing to note is that the US is a litigious nation and it is within ICANN's purview to create waiver forms for its events otherwise it would not be able to host a physical event. For those who don't like it, they can participate
virtually or wear immunity suits.....lol</div>
<br class="">
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Wed, Apr 27, 2022 at 9:33 PM Roberto Gaetano via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank" class="">at-large@atlarge-lists.icann.org</a>> wrote:<br class="">
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class="">Thanks Marita.
<div class="">One sentence - among others - is particularly puzzling to me:</div>
<blockquote class="" style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div class="">
<div title="Page 2" class="">
<div class="" style="background-color:rgb(255,255,255)">
<div class="">
<div class="">
<p class=""><span class="" style="font-size:12pt; font-family:ArialMT"><i class="">I knowingly and freely assume all risks related to illness and infectious diseases, including but not limited to COVID-19,
<b class="">even if arising from the negligence or fault of ICANN</b> </i></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class="">This means to me that I acknowledge that ICANN has the right to be negligent. I have to confess that sometimes in the past I have thought that this was ICANN’s approach, but it is the first time that I see it in writing.</div>
<div class=""><br class="">
</div>
<div class="">I wonder whether this is a sort of friendly advice to participate online and avoid showing up in person in the Hague.</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class="">Roberto</div>
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 27.04.2022, at 22:09, Marita Moll via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank" class="">at-large@atlarge-lists.icann.org</a>> wrote:</div>
<br class="">
<div class="">
<div class="">
<p class="" style="margin:0px 0px 10px; padding:0px; line-height:1.7em">Dear colleagues. If you are planning to attend ICANN74, please note that you will be required to sign a very broadly worded waiver that goes well beyond any issues related to the pandemic.
You can read the waiver here: <a href="https://www.internetnews.me/wp-content/uploads/2022/04/ICANN-waiver.pdf" target="_blank" class="">
https://www.internetnews.me/wp-content/uploads/2022/04/ICANN-waiver.pdf</a><br class="">
</p>
<p class="">Several registrars have asked that this requirement be dropped <a href="https://domainincite.com/27793-icanns-covid-19-waiver-formally-appealed" target="_blank" class="">
https://domainincite.com/27793-icanns-covid-19-waiver-formally-appealed</a>. <br class="">
</p>
<p class="">Michele Neylon, Managing Director of Blacknight Solutions, seeking legal advice on behalf of himself and staff, was advised that neither he nor his staff should sign a waiver granting ICANN blanket exclusion of liability.
<a href="https://blacknight.blog/wp-content/uploads/2022/04/blacknight-ICANN-April-2022-Hague-waiver.pdf" target="_blank" class="">
<font color="#000080" class=""><span lang="zxx" class=""><u class="">https://blacknight.blog/wp-content/uploads/2022/04/blacknight-ICANN-April-2022-Hague-waiver.pdf</u></span></font></a> .</p>
<p class="">It is an unsettling way to begin what was looking like a new beginning after so many hours at virtual public meetings. I have attended more public meetings in my life than I could ever count, and have never been asked to sign such an extensive
waiver. I would be interested to know if others have ever encountered this.</p>
<p class="">Marita Moll, ALAC rep. for NARALO<br class="">
</p>
<p class=""><br class="">
</p>
<p class="" style="margin-bottom:0cm"><br class="">
</p>
<p class="" style="margin-bottom:0cm"><br class="">
</p>
</div>
_______________________________________________<br class="">
At-Large mailing list<br class="">
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" class="">At-Large@atlarge-lists.icann.org</a><br class="">
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank" class="">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br class="">
<br class="">
At-Large Official Site: <a href="http://atlarge.icann.org/" target="_blank" class="">
http://atlarge.icann.org</a><br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing,
setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
At-Large mailing list<br class="">
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" class="">At-Large@atlarge-lists.icann.org</a><br class="">
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer" target="_blank" class="">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br class="">
<br class="">
At-Large Official Site: <a href="http://atlarge.icann.org/" rel="noreferrer" target="_blank" class="">
http://atlarge.icann.org</a><br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including
unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote>
</div>
<br clear="all" class="">
<div class=""><br class="">
</div>
-- <br class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">"<span class="" style="background-color:transparent; font-family:Georgia; font-size:1.575em; color:rgb(61,61,61)">The entrance of Your words gives light;</span></div>
<div class="" style="margin:0px 0px 0px 36pt; padding:0px; border:0px; outline:0px; font-size:1em; vertical-align:baseline; line-height:34px; color:rgb(61,61,61); font-family:"Source Sans Pro",sans-serif">
<span class="" style="margin:0px; padding:0px; border:0px; outline:0px; font-size:1.575em; vertical-align:baseline; background:transparent; font-family:Georgia">It gives understanding to the </span><span class="" style="margin:0px; padding:0px; border:0px; outline:0px; font-size:1.575em; vertical-align:baseline; background:transparent; font-family:Georgia">simple".<br class="">
</span></div>
<div class="" style="margin:0px 0px 0px 36pt; padding:0px; border:0px; outline:0px; font-size:1em; vertical-align:baseline; line-height:34px; color:rgb(61,61,61); font-family:"Source Sans Pro",sans-serif">
<span class="" style="margin:0px; padding:0px; border:0px; outline:0px; font-size:1.575em; vertical-align:baseline; background:transparent; font-family:Georgia">Psalms 119:130</span></div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
At-Large mailing list<br class="">
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" class="">At-Large@atlarge-lists.icann.org</a><br class="">
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank" class="">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br class="">
<br class="">
At-Large Official Site: <a href="http://atlarge.icann.org/" target="_blank" class="">
http://atlarge.icann.org</a><br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing,
setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
At-Large mailing list<br class="">
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" class="">At-Large@atlarge-lists.icann.org</a><br class="">
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer" target="_blank" class="">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br class="">
<br class="">
At-Large Official Site: <a href="http://atlarge.icann.org/" rel="noreferrer" target="_blank" class="">
http://atlarge.icann.org</a><br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including
unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote>
</div>
</div>
_______________________________________________<br class="">
At-Large mailing list<br class="">
<a href="mailto:At-Large@atlarge-lists.icann.org" class="">At-Large@atlarge-lists.icann.org</a><br class="">
https://atlarge-lists.icann.org/mailman/listinfo/at-large<br class="">
<br class="">
At-Large Official Site: http://atlarge.icann.org<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>