<div dir="ltr">Hi Scott,<div><br></div><div>The Covenant is in Module 6 to the Applicant Guidebook, which is the applicant contract -- attached for convenience. </div><div><br></div><div>Attached also is ICANN's demurrer brief in the litigation that I referenced. We have a court hearing on that on May 30. </div><div><br></div><div>Best,</div><div>Mike<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div style="font-family:arial;font-size:small"><span><br><div dir="ltr" style="margin-left:0pt" align="left"><table style="border:none;border-collapse:collapse"><colgroup><col width="203"><col width="86"><col width="335"></colgroup><tbody><tr style="height:20.25pt"><td rowspan="4" style="border-right:0.75pt solid rgb(0,133,61);vertical-align:middle;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.38;text-align:center;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:159px;height:95px"><img alt="Logo" src="https://lh4.googleusercontent.com/S_Oxvn9Vep0rF8IVyiOnDwA4LymtHrWirggIxlsU26JihhEYDv5A5D03ZY0k_npND2t8xfiWCdTM5NTO_LSZMksjO_UlJm5IAP3FEi5cw96AwIPgVzvoOfHIux_qNA26n5UuxvQZ" width="159" height="95" style="margin-left:0px;margin-top:0px"></span></span></p></td><td colspan="2" style="border-left:0.75pt solid rgb(0,133,61);vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.38;margin-left:3.6pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:12pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">Mike Rodenbaugh</span></p></td></tr><tr style="height:18pt"><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.38;margin-left:3.6pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">address:</span></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.53;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">548 Market Street, Box 55819</span></p><p dir="ltr" style="line-height:1.53;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">San Francisco, CA 94104</span></p></td></tr><tr style="height:12.75pt"><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.38;margin-left:3.6pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">email:</span></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.53;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="mailto:mike@rodenbaugh.com" target="_blank">mike@rodenbaugh.com</a></span></p></td></tr><tr style="height:24pt"><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.38;margin-left:3.6pt;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,133,61);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">phone:</span></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.53;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9.5pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">+1 (415) 738-8087</span></p></td></tr></tbody></table></div></span></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 18, 2023 at 1:25 PM Scott Austin <<a href="mailto:saustin@vlplawgroup.com">saustin@vlplawgroup.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-8009780577811869700">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_-8009780577811869700WordSection1">
<p class="MsoNormal">Susan:<u></u><u></u></p>
<p class="MsoNormal">I also would like another link to the document with access approved and would like to address the ambiguity in the word “capacity” as it is used in this context.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Assuming Mike is correct regarding the covenant not to sue, please identify where it is found in ICANN documents we can read, and will that covenant be something we need to consider down the road or is it beyond our remit.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
<p class="MsoNormal">Scott<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><i><span style="color:red">Please click on a link below to calendar a 15, 30, or 60 minute call with me:<u></u><u></u></span></i></b></p>
<p class="MsoNormal"> <a href="http://calendly.com/saustin2/15min" target="_blank"><span style="color:rgb(5,99,193)">a 15-minute call</span></a>
<a href="http://calendly.com/saustin2/30min" target="_blank"><span style="color:rgb(5,99,193)">a 30-minute call</span></a>
<a href="http://calendly.com/saustin2/60min" target="_blank"><span style="color:rgb(5,99,193)">a 60-minute call</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(31,73,125)"><img border="0" width="129" height="51" style="width: 1.3402in; height: 0.5347in;" id="m_-8009780577811869700Picture_x0020_13" src="cid:1882dc743d14cff311"><img border="0" width="40" height="53" style="width: 0.4166in; height: 0.5486in;" id="m_-8009780577811869700Picture_x0020_14" src="cid:1882dc743d15b006a2" alt="IntellectualPropertyLaw 100">
</span></b><a href="http://www.avvo.com/attorneys/33308-fl-scott-austin-1261914.html" target="_blank"><b><span style="color:rgb(31,73,125);text-decoration:none"><img border="0" width="151" height="36" style="width: 1.5694in; height: 0.375in;" id="m_-8009780577811869700Picture_x0020_15" src="cid:1882dc743d16917eb3" alt="microbadge[1]"></span></b></a> <u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(91,155,213)">Scott R. Austin | Board Certified Intellectual Property Attorney | VLP Law Group LLP<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><u><span style="color:rgb(46,116,181)">101 NE Third Avenue, Suite 1500, Fort Lauderdale, FL 33301<u></u><u></u></span></u></b></p>
<p class="MsoNormal"><b><span style="color:rgb(91,155,213)">Phone: (954) 204-3744 | Fax: (954) 320-0233 |</span></b>
<a href="mailto:SAustin@VLPLawGroup.com" target="_blank"><span style="color:rgb(5,99,193)">SAustin@VLPLawGroup.com</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>> <b>On Behalf Of </b>
Mike Rodenbaugh via IOT<br>
<b>Sent:</b> Wednesday, May 17, 2023 10:14 PM<br>
<b>To:</b> Susan Payne <<a href="mailto:susan.payne@comlaude.com" target="_blank">susan.payne@comlaude.com</a>><br>
<b>Cc:</b> <a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a><br>
<b>Subject:</b> Re: [IOT] IRP-IOT Panelist Selection Update<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi Susan, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I don't have quarrel with any of this except that the point #1 is simply incorrect based on actual IRP cases to date. In fact, almost all of them arise from the NewTLD Program, where ICANN imposed a purported Covenant Not to Sue on all
applicants. And ICANN has vigorously litigated the validity of that Covenant when it has been challenged, including in a pending lawsuit I am handling. In other words,, ICANN tries to force all TLD applicants to the IRP rather than court. I imagine they
intend to try to maintain that Covenant and that position as to future gTLD applications also. And we should expect, based on past history, that the vast majority of disputes with ICANN will arise from future applications.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">But I think you can just erase that point from your summary, and everything else still makes sense to me.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Can you send around the link to the Google Doc again please, for a final review by the group as you suggest?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thank you,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Mike<br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr style="height:20.25pt">
<td rowspan="4" style="border-top:none;border-bottom:none;border-left:none;border-right:1pt solid rgb(0,133,61);padding:5pt;height:20.25pt;overflow:hidden">
<p align="center" style="margin:0in;text-align:center"><span style="font-family:Arial,sans-serif;color:black;border:1pt none windowtext;padding:0in"><img border="0" width="159" height="95" style="width: 1.6527in; height: 0.993in;" id="m_-8009780577811869700_x0000_i1038" src="https://lh4.googleusercontent.com/S_Oxvn9Vep0rF8IVyiOnDwA4LymtHrWirggIxlsU26JihhEYDv5A5D03ZY0k_npND2t8xfiWCdTM5NTO_LSZMksjO_UlJm5IAP3FEi5cw96AwIPgVzvoOfHIux_qNA26n5UuxvQZ" alt="Logo"></span><u></u><u></u></p>
</td>
<td colspan="2" valign="top" style="border:none;padding:5pt;height:20.25pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:12pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">Mike Rodenbaugh</span></b><u></u><u></u></p>
</td>
</tr>
<tr style="height:0.25in">
<td valign="top" style="padding:5pt;height:0.25in;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">address:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:0.25in;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">548 Market Street, Box 55819</span><span style="color:black"><u></u><u></u></span></p>
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">San Francisco, CA 94104</span><u></u><u></u></p>
</td>
</tr>
<tr style="height:12.75pt">
<td valign="top" style="padding:5pt;height:12.75pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">email:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:12.75pt;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black"><a href="mailto:mike@rodenbaugh.com" target="_blank">mike@rodenbaugh.com</a></span><u></u><u></u></p>
</td>
</tr>
<tr style="height:24pt">
<td valign="top" style="padding:5pt;height:24pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">phone:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:24pt;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">+1 (415) 738-8087</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, May 18, 2023 at 12:52 AM Susan Payne <<a href="mailto:susan.payne@comlaude.com" target="_blank">susan.payne@comlaude.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Hi all<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Thanks to Malcolm, Mike and Kavouss for their recent comments.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-GB">Lack of requisite skill/experience</span></b><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">During our call last week we again discussed the strawperson on IRP Panel selection, and again largely focussed on the situation where the Standing Panel might
lack “<span style="color:rgb(51,51,51);background:white">the requisite diversity of skill and experience needed for the particular IRP proceeding” (para 3 in the Strawperson), as envisaged in the Bylaws Section 4.3(k)(ii). </span>If you were unable to join the call
I encourage you to listen to the recording or review the transcript. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Based on the input from participants on the call, I would say that most are opposed to building a system for considering claims by either of the IRP parties that
the Standing Panel lacks <span style="color:rgb(51,51,51);background:white">the requisite diversity of skill and experience needed for the particular IRP proceeding (and thus seeking to select panelist(s) from
</span>outside of the Standing Panel). Instead, the majority of participants on the call seemed to favour that any consideration of lack of Standing Panel capacity, whether in terms of panelist availability or requisite panelist diversity of skill/experience
for a particular case, should be a matter for the Standing Panel alone. Points made included:<u></u><u></u></span></p>
<ol start="1" type="1">
<li class="MsoNormal">
<span lang="EN-GB">In many (but not all) cases, a claimant who is not satisfied with the Standing Panel is not bound to use the IRP, but can take their claim elsewhere, such as to Court;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">The issue is not about panelist expertise in a particular subject matter, but whether they have the capacity, skill and experience to hear and determine disputes.
<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">If you go to court you do not get to select your judge, and judges routinely hear cases outside of the area of their subject-matter expertise – their role is as an impartial neutral, able to weigh the evidence and form a sound judgment, and
to manage the case with efficiency, lack of delay, etc. The same is the case for an IRP panelist<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">If the IRP Panel requires specific subject-matter expertise, there is provision to allow for the appointment of expert(s)<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">This situation should arise very rarely, therefore, and it is matter for the Standing Panel to manage rather than building a complex process for adjudicating such concerns raised by parties.<u></u><u></u></span></li></ol>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Since a number of our members were unable to join the call, could you please share further views on this before our next call. If there is in fact support for
building a process to handle skill and experience concerns raised by parties, please provide your concrete suggestions for how to address this in our Rule 3.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-GB">Other provisions in the Rule 3 Strawperson</span></b><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I don’t see any suggestions in the Google Doc regarding the rest of the Strawperson. This has been out for review and input now for a few weeks. We need to make
progress, and it’s our joint responsibility to develop solutions. There were comments expressed on our last call that the process for where the Standing Panel lacks capacity (i.e. is too busy) presupposes that there would be
<u>no</u> IRP Panellists drawn from the Standing Panel, whereas it might be that there simply isn’t capacity to find 3 Panelists. If this is a concern, or there are any other concerns with the Rule 3 text, please make concrete proposals by 1700 UTC on Monday
so that we all have some opportunity to review before our call on Tuesday. Absent this I will be assuming there are no objections to the rest of the text (aside for the skill/experience issue referred to above).<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Susan<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins SemiBold"">Susan Payne
<br>
</span><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">Head of Legal Policy
</span><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins SemiBold""><br>
Com Laude<br>
</span><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">T</span></b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light""> +44 (0) 20 7421 8250<br>
<b><span style="color:rgb(149,7,52)">Ext</span></b> 255</span><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins SemiBold""><br>
<br>
</span><a href="https://comlaude.com/" target="_blank"><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins SemiBold";text-decoration:none"><img border="0" width="40" height="55" style="width: 0.4166in; height: 0.5763in;" id="m_-8009780577811869700m_-8209744118714542298Picture_x0020_10" src="cid:1882dc743d17745b44"></span></a><span lang="EN-GB"><br>
<br>
<i>We are pleased to launch our <a href="https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0" target="_blank">
new YouTube channel</a></i></span><span lang="EN-GB"><img border="0" width="1" height="1" style="width: 0.0069in; height: 0.0069in;" id="m_-8009780577811869700_x0000_i1036" src="https://t-uk.xink.io/Tracking/Impression/UxsAAGVfAADw_RQA0" alt="."></span><span lang="EN-GB"><u></u><u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>>
<b>On Behalf Of </b>Kavouss Arasteh via IOT<br>
<b>Sent:</b> Thursday, May 11, 2023 2:22 PM<br>
<b>To:</b> Mike Rodenbaugh <<a href="mailto:mike@rodenbaugh.com" target="_blank">mike@rodenbaugh.com</a>><br>
<b>Cc:</b> <a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a><br>
<b>Subject:</b> Re: [IOT] IRP-IOT Panelist Selection Update<span lang="EN-GB"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">Dear Susan, <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">Dear Allé, Thank you very much for the new text.It is far better than that proposed by the Secretariat .<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">However, I have COMMENT on the following <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Quote<u></u><u></u></span></p>
</div>
<div>
<ul style="margin-top:0in" type="disc">
<li class="m_-8009780577811869700m-8209744118714542298m-6708160936308384402msolistparagraph" style="margin-top:0in;margin-bottom:0in">
<i><span lang="EN-GB" style="color:blue">A party can raise a concern that there is a lack of the requisite diversity of skill and experience in the Standing Panel for the particular case, which they would do at the time of IRP Panelist selection, i.e. before
the 3-person IRP Panel is appointed. </span></i><span lang="EN-GB"><u></u><u></u></span></li><li class="m_-8009780577811869700m-8209744118714542298m-6708160936308384402msolistparagraph" style="margin-top:0in;margin-bottom:0in">
<i><span lang="EN-GB" style="color:blue">Where raised by a party, an Emergency Panelist will be appointed to from within the Standing Panel to make the determination, unless and until the Standing Panel has set their own procedure for handling such a situation.</span></i><span lang="EN-GB"><u></u><u></u></span></li></ul>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:black">Unquote</span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="color:red">In both of these two circumstances there should be a clweat and specified justification, valid and convicing reasons </span></b><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:black">Regards</span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:black">Kavouss </span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">On Wed, May 10, 2023 at 10:33 PM Mike Rodenbaugh via IOT <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>> wrote:<u></u><u></u></span></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<div>
<p class="MsoNormal"><span lang="EN-GB">I echo Malcolm's sentiment that the role of the Emergency Panelist should be narrowly and precisely defined in our end product.<br clear="all">
<u></u><u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12pt;font-family:Arial,sans-serif"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<table border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr style="height:20.25pt">
<td rowspan="4" style="border-top:none;border-bottom:none;border-left:none;border-right:1pt solid rgb(0,133,61);padding:5pt;height:20.25pt;overflow:hidden">
<p align="center" style="margin:0in;text-align:center"><span style="font-family:Arial,sans-serif;color:black;border:1pt none windowtext;padding:0in"><img border="0" width="159" height="95" style="width: 1.6527in; height: 0.993in;" id="m_-8009780577811869700_x0000_i1035" src="https://lh4.googleusercontent.com/S_Oxvn9Vep0rF8IVyiOnDwA4LymtHrWirggIxlsU26JihhEYDv5A5D03ZY0k_npND2t8xfiWCdTM5NTO_LSZMksjO_UlJm5IAP3FEi5cw96AwIPgVzvoOfHIux_qNA26n5UuxvQZ" alt="Logo"></span><u></u><u></u></p>
</td>
<td colspan="2" valign="top" style="padding:5pt;height:20.25pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:12pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">Mike Rodenbaugh</span></b><u></u><u></u></p>
</td>
</tr>
<tr style="height:0.25in">
<td valign="top" style="padding:5pt;height:0.25in;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">address:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:0.25in;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">548 Market Street, Box 55819</span><span style="color:black"><u></u><u></u></span></p>
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">San Francisco, CA 94104</span><u></u><u></u></p>
</td>
</tr>
<tr style="height:12.75pt">
<td valign="top" style="padding:5pt;height:12.75pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">email:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:12.75pt;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black"><a href="mailto:mike@rodenbaugh.com" target="_blank">mike@rodenbaugh.com</a></span><u></u><u></u></p>
</td>
</tr>
<tr style="height:24pt">
<td valign="top" style="padding:5pt;height:24pt;overflow:hidden">
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.05in">
<b><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:rgb(0,133,61)">phone:</span></b><u></u><u></u></p>
</td>
<td valign="top" style="padding:5pt;height:24pt;overflow:hidden">
<p style="margin:0in"><span style="font-size:9.5pt;font-family:Arial,sans-serif;color:black">+1 (415) 738-8087</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">On Wed, May 10, 2023 at 3:36 AM Malcolm Hutty via IOT <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>> wrote:<u></u><u></u></span></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Dear all,
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">My apologies for my absence last night without prior notice.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I don’t have anything much to add to what I hope was a useful discussion on Susan’s straw man. For my part it seems a good suggestion, subject to any points that
may have been raised in my absence.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">However, I would add one word of caution on finer detail for when it comes to implementing this. Susan’s proposal includes the following statement:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">“The Emergency Panelist role will be expanded to allow Emergency Panelists to make determinations on procedural matters such as this.”<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">While I have no objection to the proposal, the Emergency Panelist is intended as an exceptional position, with a narrowly defined role. The three member panel
should be the norm. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I would not want the elaboration of more responsibilities for the Emergency Panelist such as this to create a sense that the role was defined only by example,
rather than exhaustively, and that therefore the Emergency Panelist could acquire more powers over time not previously contemplated because each addition seemed somewhat similar to those that came before, so as to erode the use of the three member panel.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Kind Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Malcolm.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">--
<u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="color:rgb(112,48,160)"> Malcolm Hutty | Director, Legal and Policy</span></b><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">T: +44 7789 987 023 |
<a href="http://www.linx.net" target="_blank">
<span style="color:rgb(5,99,193)">www.linx.net</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><img border="0" width="156" height="60" style="width: 1.625in; height: 0.625in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_8" src="cid:1882dc743d1855d355"></span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="color:rgb(112,48,160)">London Internet Exchange Ltd (LINX)</span></b><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.5pt;font-family:"Segoe UI",sans-serif">c/o WeWork, 12 Moorgate, London EC2R 6DA</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Registered in England No. 3137929 at Trinity Court, Trinity Street, Peterborough PE1 1DA<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>>
<b>On Behalf Of </b>Susan Payne via IOT<br>
<b>Sent:</b> Tuesday, May 9, 2023 3:00 PM<br>
<b>To:</b> <a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a><br>
<b>Subject:</b> [IOT] IRP-IOT Panelist Selection Update<span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Hi all<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">During our last call, we spent our time largely focussed on the situation where the Standing Panel might lack “<span style="color:rgb(51,51,51);background:white">the
requisite diversity of skill and experience needed for the particular IRP proceeding”, as envisaged in the Bylaws Section 4.3(k)(ii). Frm that discussion, I think the key points raised were as follows:</span><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:rgb(51,51,51);background:white"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-GB">Any rules we set should be light-touch. Need to allow the panel to have some procedural freedom, which has worked will to date;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">The Standing Panel concept is an important one under the Bylaws, so any exception to this should be narrow and exceptional;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">There is a need to clarify the mechanism to address the situation where the Standing Panel lacks the diversity of skill and experience. Whilst many felt that this decision needs to rest with the Standing Panel (or its Chair), there was also
support for finding a balance, since the parties may, in practice want to raise this as a concern;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">Care is needed not to invite actions/decisions from the full Standing Panel which might then have the effect of excluding them all from subsequently acting on the case;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">The Bylaws also allow for an IRP Panel to seek expert input;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">A determination on whether there is a lack of the requisite diversity of skill and expertise could be made by:<u></u><u></u></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal">
<span lang="EN-GB">Full Standing Panel (risk that all are then conflicted from serving on the IRP Panel for the substantive dispute)<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">Chair of the Standing Panel (risk that the Chair then is excluded from serving on the IRP Panel in such cases)<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">Emergency Panelist (likely requires some expansion of this role; currently only seems to cover interim relief)<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">Allow the Standing Panel to set their own process<u></u><u></u></span></li></ul>
</ul>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Proposed way forward:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-GB">The Standing Panel may, of its own volition and acting through the Chair of the Standing Panel, conclude that it lacks the
<span style="color:rgb(51,51,51);background:white">requisite diversity of skill and experience in the Standing Panel for a particular case. They would need to identify the proposed path forward, for example that both parties select an IRP Panelist from the Standing
Panel and then the third IRP Panelist is selected from outside the Standing Panel, or that all IRP Panelists are selected from Outside the Standing Panel</span><u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">A party can raise a concern that there is a lack of the <span style="color:rgb(51,51,51);background:white">
requisite diversity of skill and experience in the Standing Panel for the particular case, which they would do at the time of IRP Panelist selection, i.e. before the 3-person IRP Panel is appointed.
</span><u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">Where raised by a party, an Emergency Panelist will be appointed to from within the Standing Panel to make the determination, unless and until the Standing Panel has set their own procedure for handling such a situation.<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-GB">The Emergency Panelist role will be expanded to allow Emergency Panelists to make determinations on procedural matters such as this. The expectation is that Standing Panelists will take it in turns to serve as n Emergency Panelist, but this
will be a matter of Standing Panel procedure for the Standing Panel to decide.<u></u><u></u></span></li></ul>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I have not amended the draft strawperson to reflect this, but would propose to do so after our call if there is support from the group.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins SemiBold"">Susan Payne
<br>
</span><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">Head of Legal Policy
<br>
<br>
</span><a href="https://comlaude.com/" target="_blank"><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><img border="0" width="133" height="32" style="width: 1.3888in; height: 0.3333in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072_x005f_x0000_i1039" src="cid:1882dc743d19374b66"></span></a><span lang="EN-GB" style="font-size:9pt"><br>
<br>
</span><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light"">28-30 Little Russell Street,<br>
London WC1A 2HN, UK<br>
<b><span style="color:rgb(149,7,52)">T</span></b> +44 (0) 20 7421 8250<br>
<b><span style="color:rgb(149,7,52)">Ext</span></b> 255</span><span lang="EN-GB" style="font-size:9pt"><br>
<br>
</span><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light""><a href="http://comlaude.com/" target="_blank"><span style="color:rgb(149,7,52)">comlaude.com</span></a></span></b><span lang="EN-GB"><br>
<br>
<i>We are pleased to launch our <a href="https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADw_RQA0" target="_blank">
new YouTube channel</a></i><br>
<br>
</span><a href="https://www.linkedin.com/company/com-laude" target="_blank"><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><img border="0" width="17" height="17" style="width: 0.1736in; height: 0.1736in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_2" src="cid:1882dc743d1a18c377"></span></b></a><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light""> </span></b><a href="https://twitter.com/comlaude?lang=en" target="_blank"><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><img border="0" width="17" height="17" style="width: 0.1736in; height: 0.1736in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_3" src="cid:1882dc743d1afa3b88"></span></b></a><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light""> </span></b><a href="https://www.facebook.com/ComLaude/" target="_blank"><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><img border="0" width="17" height="17" style="width: 0.1736in; height: 0.1736in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_4" src="cid:1882dc743d1bdbb399"></span></b></a><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light""> </span></b><a href="https://www.youtube.com/@comlaude" target="_blank"><b><span lang="EN-GB" style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><img border="0" width="17" height="17" style="width: 0.1736in; height: 0.1736in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_5" src="cid:1882dc743d11f3c04fa"></span></b></a><span lang="EN-GB"><br>
<br>
<img border="0" width="67" height="67" style="width: 0.7013in; height: 0.7013in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_6" src="cid:1882dc743d2201c188b"><span style="border:1pt solid windowtext;padding:0in"><img border="0" width="1" height="1" style="width: 0.0069in; height: 0.0069in;" id="m_-8009780577811869700m_-8209744118714542298m_2524858489791316066m_-6075149667044422072Picture_x0020_1" src="cid:1882dc743d220fd909c" alt="Image removed by sender. ."></span><u></u><u></u></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-GB">
<hr size="1" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-GB">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other
than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the
“Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not
made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group
includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company
number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland;
Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered
in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For
further information see <a href="https://comlaude.com/" target="_blank">
www.comlaude.com</a> <u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB">_______________________________________________<br>
IOT mailing list<br>
<a href="mailto:IOT@icann.org" target="_blank">IOT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iot" target="_blank">https://mm.icann.org/mailman/listinfo/iot</a><br>
<br>
_______________________________________________<br>
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">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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.<u></u><u></u></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-GB">_______________________________________________<br>
IOT mailing list<br>
<a href="mailto:IOT@icann.org" target="_blank">IOT@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iot" target="_blank">https://mm.icann.org/mailman/listinfo/iot</a><br>
<br>
_______________________________________________<br>
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">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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.<u></u><u></u></span></p>
</blockquote>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-GB">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span lang="EN-GB">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this
message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for
viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities.
The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered
in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell
Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation
incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office
at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see
<a href="https://comlaude.com/" target="_blank">
www.comlaude.com</a> <u></u><u></u></span></p>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<font face="Arial" color="Gray" size="1"><br>
This message contains information which may be confidential and legally privileged. Unless you are the addressee, you may not use, copy or disclose to anyone this message or any information contained in the message. If you have received this message in error,
please send me an email and delete this message. Any tax advice provided by VLP is for your use only and cannot be used to avoid tax penalties or for promotional or marketing purposes.<br>
</font>
</div>
</div></blockquote></div>