<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:large">All,</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Firstly, happy new year to all.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Second, please find the agenda for the January 10, 2023, 18:00 UTC plenary call below.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Third, please find below a copy of Susan's Straw Person email from January 4th.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Agenda:</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large"><ol start="1" type="1" style="margin-bottom:0cm;font-size:small;margin-top:0cm"><li class="m_-857451422517872622MsoListParagraph" style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">Review agenda and updates to SOIs<u></u><u></u></li><li class="m_-857451422517872622MsoListParagraph" style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">Review action items:<u></u><u></u></li><ol start="1" type="a" style="margin-bottom:0cm;margin-top:0cm"><li class="m_-857451422517872622MsoListParagraph" style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">Sam to provide information on costs awards from pre-Transition (2016) IRPs, which may assist with this discussion<u></u><u></u></li></ol><li class="m_-857451422517872622MsoListParagraph" style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">Discussion of Straw Man proposal<u></u><u></u></li><li class="m_-857451422517872622MsoListParagraph" style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">Next call - to be confirmed</li></ol></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 4, 2023 at 12:43 PM Susan Payne <<a href="mailto:susan.payne@comlaude.com">susan.payne@comlaude.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="msg9027943361584356551">
<div lang="EN-GB" style="overflow-wrap: break-word;">
<div class="m_9027943361584356551WordSection1">
<p class="MsoNormal"><span>Hi all<u></u><u></u></span></p>
<p class="MsoNormal"><span>I hope that those of you who celebrated have had an enjoyable and relaxing holiday season.
<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Following on from the email exchange and subsequent discussion on our call last month, I have put together what I hope can be the basis for resolving the initiation-related issues we have been discussing.
As always, the views of group members do range across the spectrum, on topics such as the initiation fee, and so the attached is an effort at finding a compromise that we can hopefully all live with.
<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>This is a strawperson, and so is open to further discussion and revision, but we have now spent some time discussing initiation and, I believe, the various views have been well-aired. I would like
us to wrap up our discussion on this after the next call if at all possible. With that in mind, please do share any feedback in advance of next Tuesday’s call.
<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Susan<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Poppins SemiBold"">Susan Payne
<br>
</span><span style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">Head of Legal Policy
</span><span style="font-size:9pt;font-family:"Poppins SemiBold""><br>
Com Laude<br>
</span><b><span style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">T</span></b><span 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 style="font-size:9pt;font-family:"Poppins SemiBold""><br>
<br>
</span><a href="https://comlaude.com/" target="_blank"><span style="font-size:9pt;font-family:"Poppins SemiBold";text-decoration:none"><img border="0" width="60" height="82" style="width: 0.625in; height: 0.8541in;" id="m_9027943361584356551_x0000_i1033" src="cid:18597c401fc5b16b24"></span></a><span><u></u><u></u></span></p>
</div>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> 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> 06 December 2022 17:19<br>
<b>To:</b> Flip Petillion <fpetillion@petillion.law>; McAuley, David <dmcauley@Verisign.com>; <a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>; <a href="mailto:Malcolm@linx.net" target="_blank">Malcolm@linx.net</a>; <a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a><br>
<b>Subject:</b> Re: [IOT] IRP-IOT action items/next steps on Initiation<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span>Malcolm, David, Mike and Flip<u></u><u></u></span></p>
<p class="MsoNormal"><span>Thanks so much for your thoughtful comments. I hope that those of us who can make today’s call can continue with this fruitful discussion and hopefully near or reach a possible compromise. It seems
to me we may be able to build something based loosely on Mike’s proposal as a starting point.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Regarding the thoughts on a loser pays element to the costs and expenses of the IRP, I do appreciate and tend to share those views. Coming from a UK law background, it is entirely the norm (certainly
in litigation) for a successful party to recover their costs from the loser, subject to an assessment of reasonableness of the figures and a judicial discretion to alter that norm based on the behaviour of the winning party. Nevertheless, I do not think that
we have the scope to follow that approach here, whether for non-commercial Claimants only or for all Claimants, since we must work within the terms of the Bylaws. Bylaws 4.3(r) could be clearer in other regards, but I don’t believe there is disagreement over
the intent that parties should bear their own legal costs except where the losing party’s defence or claim is deemed by the panel to be frivolous or abusive:<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:36pt">ICANN<span style="font-size:12pt;font-family:Helvetica,sans-serif;color:rgb(51,51,51);background:white"> shall bear all the administrative costs of maintaining the IRP mechanism, including compensation of Standing
Panel members. Except as otherwise provided in Section 4.3(e)(ii), <span style="background:yellow">
each party to an IRP proceeding shall bear its own legal expenses</span>, except that </span>ICANN<span style="font-size:12pt;font-family:Helvetica,sans-serif;color:rgb(51,51,51);background:white"> shall bear all costs associated with a Community IRP, including
the costs of all legal counsel and technical experts. <span style="background:yellow">
Nevertheless, except with respect to a Community IRP, the IRP Panel may shift and provide for the losing party to pay administrative costs and/or fees of the prevailing party in the event it identifies the losing party's Claim or defense as frivolous or abusive.</span></span><span><u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Obviously I am open to discussing this is that is not an agreed understanding. I will note however, that this was the understanding of the IRP panel in .WEB. I did previously include a link to
the .WEB decision, which I found to be very helpful, but for convenience on today’s call, I have pulled out a few key paragraphs from that decision into the attached document.
<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9pt;font-family:"Poppins SemiBold"">Susan Payne
<br>
</span><span style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">Head of Legal Policy
</span><span style="font-size:9pt;font-family:"Poppins SemiBold""><br>
Com Laude<br>
</span><b><span style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">T</span></b><span 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 style="font-size:9pt;font-family:"Poppins SemiBold""><br>
<br>
</span><a href="https://comlaude.com/" target="_blank"><span style="font-size:9pt;font-family:"Poppins SemiBold";text-decoration:none"><img border="0" width="60" height="82" style="width: 0.625in; height: 0.8541in;" id="m_9027943361584356551_x0000_i1032" src="cid:18597c401fc7745b41"></span></a><span><u></u><u></u></span></p>
</div>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>>
<b>On Behalf Of </b>Flip Petillion via IOT<br>
<b>Sent:</b> 06 December 2022 14:27<br>
<b>To:</b> McAuley, David <<a href="mailto:dmcauley@Verisign.com" target="_blank">dmcauley@Verisign.com</a>>;
<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>; <a href="mailto:Malcolm@linx.net" target="_blank">
Malcolm@linx.net</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 action items/next steps on Initiation<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">All:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Here are some thoughts. Apologies, but I don't have time to prepare a more detailed overview.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">I believe it is worth reminding the CCWG-Accountability Recommendation on accessibility and costs:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"><img border="0" width="697" height="150" style="width: 7.2569in; height: 1.5625in;" id="m_9027943361584356551Picture_x0020_3" src="cid:18597c401fc8546ed2" alt="Text
Description automatically generated"></span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">With respect to the loser pays/fee shifting, I see no basis to distinguish between non-profits and for-profits.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">The way that cost the loser pays/fee shifting has been transposed into Articles 4(3)(e)(ii) and 4(3)(r) of the Bylaws seems unbalanced and in contradiction with the stated purposes of the IRP (Article
4(3)(a) of the Bylaws).</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Article 4(3)(e)(ii) provides that, in certain circumstances (i.e., non good faith participation to CEP), the IRP Panel shall award to ICANN all reasonable fees and costs incurred by ICANN, including
legal fees. </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">There is no such provision for a reimbursement of all reasonable fees and costs incurred by a Claimant. Yet the IRP is a system to ensure ICANN’s compliance. As a result, ICANN is the main beneficiary
of IRP rulings. Without a balanced cost shifting model, the system risks to install unwarranted burdens for Claimants who risk paying the bill for enhancing ICANN’s accountability.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Article 4(3)(r) <i>in fine</i> provides for possible fee shifting in the event of frivolous or abusive claims or defenses. To date, there is no cost shifting case law. That could be because the burden
of Article 4(3)(r) is too high. </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">In international arbitration, the principle of <i>costs follow the event</i> is well accepted (with fairness adjustments). The requirement of frivolous or abusive claims or defenses seems at odds with
this principle and with the stated purposes of an IRP. According to these stated purposes, IRPs are aimed at securing the “accessible, transparent, efficient, consistent, coherent, and just resolution of Disputes” and to lead to final resolutions “consistent
with international arbitration norms”. Deviating from the <i>costs follow the event </i>principle to ICANN’s benefit risks making IRPs less accessible, less just, and not consistent with international arbitration norms.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">In my experience, adherence to the <i>costs follow the event </i>principle has never incentivized a commercial entity to engage in imprudent management or in making intemperate legal expenses. Efficiency
as to time and costs is an important driver in international arbitration, which always forms part of the decision-making matrix. Even when an arbitral tribunal decides to shift costs, it will have no scruples about rejecting the reimbursement of excessive
or unnecessary legal costs.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Instead of trying to re-invent the wheel, I would make a plea of confirming ourselves to well-established norms of international arbitration and adapting where necessary to serve the stated purposes
of an IRP. In my view, the stated purpose of making IRPs accessible favours adherence to the <i>costs follow the event </i>principle, provided Claimants are offered some protection in line with the stated purpose of IRPs to ensure ICANN’s accountability to
the global Internet community and Claimants.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I’ll try to join you in the call tonight.<br>
<br>
Best<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Flip<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black">Flip Petillion<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"><a href="mailto:fpetillion@petillion.law" target="_blank"><span style="color:windowtext;text-decoration:none">fpetillion@petillion.law</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">+32484652653<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"><a href="http://www.petillion.law" target="_blank"><span style="color:black;text-decoration:none">www.petillion.law</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><a href="https://www.petillion.law/" target="_blank"><span style="color:black;text-decoration:none"><img border="0" width="191" height="43" style="width: 1.9861in; height: 0.4444in;" id="m_9027943361584356551Picture_x0020_1" src="cid:18597c401fc9374b63" alt="id:image001.png@01D3691D.DA7539C0"></span></a><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="X-NONE" style="font-family:"Gill Sans MT Pro Light";color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Gill Sans MT Pro Light";color:black"> </span><span style="font-size:10pt;font-family:"Gill Sans MT Pro Light";color:black">Attorneys – Advocaten – Avocats</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12pt;color:black">IOT <<a href="mailto:iot-bounces@icann.org" target="_blank">iot-bounces@icann.org</a>> on behalf of "McAuley, David via IOT" <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>><br>
<b>Reply to: </b>"McAuley, David" <<a href="mailto:dmcauley@Verisign.com" target="_blank">dmcauley@Verisign.com</a>><br>
<b>Date: </b>Tuesday, 6 December 2022 at 12:46<br>
<b>To: </b>"<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>" <<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>>, "<a href="mailto:Malcolm@linx.net" target="_blank">Malcolm@linx.net</a>" <<a href="mailto:Malcolm@linx.net" target="_blank">Malcolm@linx.net</a>><br>
<b>Cc: </b>"<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>" <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>><br>
<b>Subject: </b>Re: [IOT] IRP-IOT action items/next steps on Initiation<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Thank you, Malcolm and Mike.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I agree with how Mike approaches these matters, subject to these further comments:<u></u><u></u></span></p>
<p class="m_9027943361584356551MsoListParagraphCxSpFirst"><span lang="EN-US"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="m_9027943361584356551MsoListParagraphCxSpMiddle" style="margin-left:0cm">
<span lang="EN-US">Needy claimants should be able to bring IRPs and I encourage ICANN to pay special heed to Bylaw 4.3(y) regarding meaningful participation by those who might otherwise be excluded.
<u></u><u></u></span></li></ol>
<p class="m_9027943361584356551MsoListParagraphCxSpMiddle"><span lang="EN-US"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="m_9027943361584356551MsoListParagraphCxSpMiddle" style="margin-left:0cm">
<span lang="EN-US">I agree that costs and fees are best handled by the panel and Mike’s guardrails of fairness and equity seem right, as does note of having rules that conform with international arbitration norms.
<u></u><u></u></span></li></ol>
<p class="m_9027943361584356551MsoListParagraphCxSpMiddle"><span lang="EN-US"><u></u> <u></u></span></p>
<ol style="margin-top:0cm" start="3" type="1">
<li class="m_9027943361584356551MsoListParagraphCxSpLast" style="margin-left:0cm">
<span lang="EN-US">I am not convinced that non-commercial claimants should be able to capture all of their costs if they prevail unless ICANN was frivolous in its defense. Parties who are able typically shoulder their own costs and this helps ensure that the
costs incurred remain subject to prudent management. <u></u><u></u></span></li></ol>
<p class="MsoNormal"><span lang="EN-US">Sorry I will not be able to attend today.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Best wishes,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">David<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">David McAuley<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Policy Director<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Verisign, Inc.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><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 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Mike Silber <<a href="mailto:silber.mike@gmail.com" target="_blank">silber.mike@gmail.com</a>>
<br>
<b>Sent:</b> Tuesday, December 6, 2022 6:22 AM<br>
<b>To:</b> Malcolm Hutty <<a href="mailto:Malcolm@linx.net" target="_blank">Malcolm@linx.net</a>><br>
<b>Cc:</b> McAuley, David <<a href="mailto:dmcauley@Verisign.com" target="_blank">dmcauley@Verisign.com</a>>;
<a href="mailto:susan.payne@comlaude.com" target="_blank">susan.payne@comlaude.com</a>; <a href="mailto:iot@icann.org" target="_blank">
iot@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] Re: [IOT] IRP-IOT action items/next steps on Initiation<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<table border="0" cellspacing="3" cellpadding="0" width="1185" style="width:888.75pt;background:rgb(245,236,206)">
<tbody>
<tr>
<td width="1175" style="width:881.25pt;padding:0.75pt">
<p><strong><span style="font-family:Calibri,sans-serif;color:rgb(153,51,0)">Caution:</span></strong><span style="color:rgb(153,51,0)"> </span><span style="color:black">This email originated from outside the organization. Do not click links or open attachments unless
you recognize the sender and know the content is safe. </span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US">Hi Malcom<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I think you make several excellent points below. At the same time I think you are ascribing certain intent to some of David’s statements that may be unwarranted. Rather than responding in-line [to avoid picking nits]
or speaking for David [as he can respond if he feels it is required] I will top post.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">My personal view [recognising that i have been observing in the background and may not be totally current]:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-US">a party intending to use the IRP (“applicant”) should pay a filing fee. The filing fee should be a first gate to limit trivial or vexatious use of the process, but not so onerous to prevent use of the process. Deserving [needy] applicants
should be entitled to seek a waiver of the fee from the panel;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">a successful applicant should be entitled to have the filing fee refunded;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">the question of costs and fees is best dealt with by the panel having regard to fairness and equity with the IRP process giving some limited guidance which could be:<u></u><u></u></span></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal">
<span lang="EN-US">commercial applicants should pay their own costs [they will presumably get commercial benefit from a positive outcome] and only be entitled to a refund of those costs if ICANN’s opposition is frivolous or vexatious;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">non-commercial applicants must apply to the panel for their costs to be met, which may be granted in whole or in part;<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">ICANN pays its own costs and is only able to claim back costs from an (i) unsuccessful;
<b>and</b> (ii) frivolous or vexatious applicant [an applicant who is unsuccessful but not frivolous or vexatious should nt be act risk of a claim for ICANN’s costs];<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">ICANN should pay all the panel / IRP process costs [except for the initial filing fee] and is only entitled to claim a refund of costs if a finding is made that the claim is frivolous or vexatious; and<u></u><u></u></span></li><li class="MsoNormal">
<span lang="EN-US">a party’s costs include both internal, legal and administrative costs [courier, translation etc] and should follow the above process.<u></u><u></u></span></li></ul>
</ul>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Mike<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US"><u></u> <u></u></span></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On 5 Dec 2022, at 18:32, Malcolm Hutty via IOT <<a href="mailto:iot@icann.org" target="_blank">iot@icann.org</a>> wrote:<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear all,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">David wrote:<u></u><u></u></span></p>
</div>
<div style="margin-left:36pt">
<p class="MsoNormal"><span lang="EN-US">Presumably, a prevailing party will make a claim for such costs or fees, the losing party will have an opportunity to challenge the claim, and we should trust the panel to make an appropriate ruling. I believe that here
too they should act consistent with international arbitration norms (see also Bylaw 4.3(a)(viii)).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I think this notion that a prevailing party will have to claim for costs and fees, while typical for litigation in a court of law, is a big part of what the IRP was intended to avoid.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The idea was that ICANN would have an independent review process that claimants could access to resolve disputes. Nothing in the bylaws authorises ICANN (or its provider) to condition access this process on payment of
fees, just as there is no suggestion that you have to pay to file a Request for Reconsideration or to use the services of the Ombudsman.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Moreover, in David’s formulation, if a Claimant loses, then they’re not the prevailing party and would not be able to claim for costs and fees. This is quite different to the bylaws requirement that ICANN pays the costs
of the IRP, with them only being shifted when the claim was frivolous or vexatious.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">David asserts that the bylaws language requiring ICANN to pay the costs of the IRP mechanism only applies to some intangible costs that form a ‘mechanism’ that somehow exclude the actual operation of that mechanism. I
find that distinction artificial, a construct invented to support charging the Claimant, but without foundation in the bylaws.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">We should always look to the Bylaws themselves to understand what is required.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">David’s assertion that the ‘IRP mechanism’ and the process of hearing a dispute are distinct is actually contradicted directly by the bylaws themselves: Bylaw 4.3(r) states quite explicitly that the fees of the panellists
who hear the dispute are included in the definition of administrative costs. Yet these fees are incontrovertibly the cost of hearing one individual dispute. So any possible suggestion that the costs of hearing the dispute are outside the definition of “administrative
costs” is directly excluded by the clear language of 4.3(r).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">This notion of an IRP mechanism as being something other than the process of hearing disputes arises only because we keep using shorthand: we talk of “the IRP” and forget what the IRP actuall is. We need to look back
to the bylaws definition of the IRP to see what the “IRP” really means.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Bylaws Article 4.3 (a) begins as follows:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12pt;font-family:Helvetica,sans-serif;color:rgb(51,51,51);background:white">“ In addition to the reconsideration process described in <u>Section 4.2</u>, </span><span lang="EN-US">ICANN</span><span lang="EN-US" style="font-size:12pt;font-family:Helvetica,sans-serif;color:rgb(51,51,51);background:white"> shall
have a separate process for independent third-party review of Disputes (defined in <u>Section 4.3(b)(iii)</u>) alleged by a Claimant (as defined in <u>Section 4.3(b)(i)</u>) to be within the scope of the Independent Review Process ("<strong><span style="font-family:Helvetica,sans-serif">IRP</span></strong>").
The IRP is intended to hear and resolve Disputes for the following purposes ("<strong><span style="font-family:Helvetica,sans-serif">Purposes of the IRP</span></strong>"): […]”</span><span lang="EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">This is where IRP is defined: it is a defined term. It refers to “a separate process for independent third-party review of Disputes”. Accordingly when 4.3(r) speaks of ICANN paying for the ‘IRP mechanism’, it is referring
to “the process for independent third-party review of Disputes”. The mechanism *<b>is</b>* the process: there is nothing else.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Bylaw 4.3(r) requires ICANN to pay for the process of those Disputes being reviewed. That is what ‘IRP mechanism’ means. Which is entirely consistent with everything else that is said in the Bylaws, including the Purposes.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Kind Regards,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Malcolm.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">--<span class="m_9027943361584356551apple-converted-space"> </span><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="color:rgb(112,48,160)"> Malcolm Hutty | Executive Director, Legal and Policy</span></b><span lang="EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">T: +44 7789 987 023 |<span class="m_9027943361584356551apple-converted-space"> </span><a href="http://secure-web.cisco.com/1gXx9xbCru0oZFI-I6cKHfFRzZEJ-IRIPzx0q-EjM2gMoAdTyFo_FX-O6lwVvRquI9YLJrCdQnSszD5STY3x1BoGInoPNWMOLYZJzOUfglxuuDMmUe2qejkTskCGtyUNyozbxhdc3itm1saMNr9-wXhcN4fjFKWSGBJpvyIe9wrsADkmLcpPC35AiYV1lMaKBYAgH0yxoA2W7hZ9ppxPDLvcOViSKGwUq6AQNxcSlf9EjZpWPBZbhLcig2JXbKWNZDIcgxRxCsEnrINITeiHSI3qRZdBFC8UgD9reu76GKaU/http%3A%2F%2Fwww.linx.net%2F" target="_blank"><span style="color:rgb(5,99,193)">www.linx.net</span></a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><image006.png><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="color:rgb(112,48,160)">London Internet Exchange Ltd (LINX)</span></b><span lang="EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">c/o WeWork, 2 Minster Court, Mincing Lane London EC3R 7BB<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Registered in England No. 3137929 at Trinity Court, Trinity Street, Peterborough PE1 1DA<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<div>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span class="m_9027943361584356551apple-converted-space"><span lang="EN-US"> </span></span><span lang="EN-US">IOT <<a href="mailto:iot-bounces@icann.org" target="_blank"><span style="color:rgb(5,99,193)">iot-bounces@icann.org</span></a>><span class="m_9027943361584356551apple-converted-space"> </span><b>On
Behalf Of<span class="m_9027943361584356551apple-converted-space"> </span></b>McAuley, David via IOT<br>
<b>Sent:</b><span class="m_9027943361584356551apple-converted-space"> </span>05 December 2022 13:28<br>
<b>To:</b><span class="m_9027943361584356551apple-converted-space"> </span><a href="mailto:susan.payne@comlaude.com" target="_blank"><span style="color:rgb(5,99,193)">susan.payne@comlaude.com</span></a>;<span class="m_9027943361584356551apple-converted-space"> </span><a href="mailto:iot@icann.org" target="_blank"><span style="color:rgb(5,99,193)">iot@icann.org</span></a><br>
<b>Subject:</b><span class="m_9027943361584356551apple-converted-space"> </span>Re: [IOT] IRP-IOT action items/next steps on Initiation<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Thank you, Susan.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">My thoughts are below since I need to send apologies for the meeting tomorrow. There is a conflicting meeting for the Community Representatives Group to nominate members of the IRP Standing Panel that I must attend.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">With respect to the issue of filing-fee costs, Bylaw 4.3(r) indicates that ICANN will bear the administrative costs of maintaining the IRP<span class="m_9027943361584356551apple-converted-space"> </span><u>mechanism</u>. In my opinion that
does not include a complainant’s filing fee, which instead should be set (probably by ICDR) so as to conform to international arbitration norms (Bylaw 4.3(n)(i) and (ii)). Whatever is set as an initiation fee should not act as an unreasonable bar to filing
complaints, I think, as that would probably not conform to such norms.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">On other costs that might routinely apply, I think that we should ensure that a clear and easily findable link to the schedule of applicable fees on the ICDR website be available. It should not take the labors of Hercules
to find these fees.<span class="m_9027943361584356551apple-converted-space"> </span><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">As for any other administrative costs and/or fees that might be shifted under Bylaw 4.3(r), I appreciate the thought you put into this as manifest in the google doc. But I tend to think it better not to try to anticipate/imagine
such costs. Here, I think the principle in the bylaw is ok as written.<span class="m_9027943361584356551apple-converted-space"> </span><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Presumably, a prevailing party will make a claim for such costs or fees, the losing party will have an opportunity to challenge the claim, and we should trust the panel to make an appropriate ruling. I believe that here
too they should act consistent with international arbitration norms (see also Bylaw 4.3(a)(viii)).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best wishes,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">David<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">David McAuley<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Policy Director<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Verisign, Inc.<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<div>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span class="m_9027943361584356551apple-converted-space"><span lang="EN-US"> </span></span><span lang="EN-US">IOT <<a href="mailto:iot-bounces@icann.org" target="_blank"><span style="color:rgb(5,99,193)">iot-bounces@icann.org</span></a>><span class="m_9027943361584356551apple-converted-space"> </span><b>On
Behalf Of<span class="m_9027943361584356551apple-converted-space"> </span></b>Susan Payne via IOT<br>
<b>Sent:</b><span class="m_9027943361584356551apple-converted-space"> </span>Friday, December 2, 2022 5:01 PM<br>
<b>To:</b><span class="m_9027943361584356551apple-converted-space"> </span><a href="mailto:iot@icann.org" target="_blank"><span style="color:rgb(5,99,193)">iot@icann.org</span></a><br>
<b>Subject:</b><span class="m_9027943361584356551apple-converted-space"> </span>[EXTERNAL] [IOT] IRP-IOT action items/next steps on Initiation<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<table border="0" cellspacing="3" cellpadding="0" width="1185" style="width:888.75pt;background:rgb(245,236,206)">
<tbody>
<tr>
<td width="1175" style="width:881.25pt;padding:0.75pt">
<p class="MsoNormal"><strong><span style="font-family:Calibri,sans-serif;color:rgb(153,51,0)">Caution:</span></strong><span style="color:rgb(153,51,0)"> </span><span style="color:black">This email originated
from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. </span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi all<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">On our last call, our discussion on initiation we pent much of our time focussed on the allocation of costs and fees, with reference to the language of Bylaws 4.3(r). As a result of this, we had one action item for Sam,
but also a task for all of us to try to give clarity for potential claimants on the costs they will be responsible for. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">We also captured a useful suggestion to use flashes to indicate an updated section (as the UN do), with respect to the planned improvements to the IRP website area which have been anticipated for some time now.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-US">Action items from our previous call</span></b><span lang="EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Sam to provide information on costs awards from pre-Transition (2016) IRPs, which may assist with this discussion<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-US">Action for us all</span></b><span lang="EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Irrespective of where we come out on the narrow issue of the IRP filing fee, Kavouss raised a point on our last call which I think resonated with most of the group. Participants and potential participants of an IRP need
to know what costs they will be responsible for. This is directly relevant to initiation because potential Claimants to an IRP should be aware of what they are committing to when they make the decision to proceed. If Bylaws 4.3(r) is ambiguous – which, based
on our discussions, does seem to be the case – then we must give them this clarity. Even if we cannot be exhaustive as to all possible costs, we should be able to identify sufficient examples to serve as a guide for participants on what types of costs will
fall to them. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Below is a link to a Google Doc where I have started to capture types of costs that would likely be incurred in an IRP, and tried to identify who bears these costs, currently. In order to make a start on this, I went
back to the .WEB decision since this is a case decided under the new Bylaws and where there were some costs orders made, and I have included a footnote to explain where the costs addressed in that decision seem to give us some guidance. As a result, for a
few items I have indicated both that the Claimant initially paid and that this was later ordered to be reimbursed by ICANN. Indeed, the Claimant’s filing fee, which we have been discussing at length, does appear to have been reimbursed in the .WEB case.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><a href="https://docs.google.com/document/d/1AUMSllaxG_9SicIEVoq4eHwzHn95D8rNPqjwIECNLvI/edit?usp=sharing" target="_blank"><span style="color:rgb(5,99,193)">https://docs.google.com/document/d/1AUMSllaxG_9SicIEVoq4eHwzHn95D8rNPqjwIECNLvI/edit?usp=sharing</span></a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I am putting this forward to get the ball rolling. I am sure that there will be other costs/fees that I have not thought about, and I hope that others in the group will add to this, particularly those who are practitioners.
I would also welcome input from IOT members who disagree with my characterisation of any of these items. I am not a practitioner so may inadvertently have mischaracterised something. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9pt;font-family:"Poppins SemiBold"">Susan Payne<span class="m_9027943361584356551apple-converted-space"> </span><br>
</span><span lang="EN-US" style="font-size:9pt;font-family:"Poppins Light";color:rgb(149,7,52)">Head of Legal Policy<span class="m_9027943361584356551apple-converted-space"> </span><br>
<br>
</span><span lang="EN-US"><a href="https://secure-web.cisco.com/1_fqZwmD0LVUqv3bkbwC1oQie03MVXTMWHEHycrK_PG0ShzCIGzF_fBnDG9FjHcMDJN4tlr-YaWC22UStf69G24qky6m33hkrg8UFyxmHu083UmSChJqxoVaftc-peBFVUXLq9IuI2a6LbqCnig1Ok7zRLWrxAdo5oB1VxYGKOCfxtJjmpHi5szn42EkVleM7OvIZstWxrm3gJ7OXAL4GZT1nYmPa5qZEdSBPPGU_3d2ghm7fVJu7M_3UQFARqsSOv2sT1puZvoZp9KrUEedYpZOlcATRfp3eQCoI8TO6fhs/https%3A%2F%2Fcomlaude.com%2F" target="_blank"><span style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><image007.png></span></a></span><span lang="EN-US" style="font-size:9pt"><br>
<br>
</span><span lang="EN-US" 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><span class="m_9027943361584356551apple-converted-space"> </span>+44 (0) 20 7421 8250<br>
<b><span style="color:rgb(149,7,52)">Ext</span></b><span class="m_9027943361584356551apple-converted-space"> </span>255</span><span lang="EN-US" style="font-size:9pt"><br>
<br>
</span><b><span lang="EN-US" style="font-size:9pt;font-family:"Poppins Light""><a href="http://secure-web.cisco.com/1o1hQd12d0SDcx6mbPBYv7xox-vKEiIzN7LER0ZKvGXvRIQn7WlewJP9Lv9uaFFpI4bgTDbXIzHWBu2ZpbvGuTS9EprsKKIVV0X5StfrmGthUSAvmELHgqFH394kLaYwROaX6Q7S7qj4nQ6hGR1w07pae4328uMK08Py3xhQZCT9K-VCprhE8IndFnz9eOd9U0R_sC3eTocOSKHi_hqYdJt6NoW63cxfavggeAGbbszfnlZ9cvaVZq3ly87-gFXe4JsybYBCTd-4Srx1iKokwmWjvZBA1czgRkWgFCvIjyyY/http%3A%2F%2Fcomlaude.com" target="_blank"><span style="color:rgb(149,7,52)">comlaude.com</span></a></span></b><span lang="EN-US"><br>
<br>
<a href="https://www.linkedin.com/company/com-laude" target="_blank"><b><span style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><image008.png></span></b></a></span><b><span lang="EN-US" style="font-size:9pt;font-family:"Poppins Light""> </span></b><span lang="EN-US"><a href="https://secure-web.cisco.com/1ZeiC_pAMsTw0Kc0K383TCPjqjtkiut1kbAMTKQKv7mQY6KE_h1XmPQhhfHyegNg6C8JP8c_amE229wdPgaoapV_3NjEt5f0u1bNU5efDx2ZuSwnL1THPAgkGzAIN8UxwjUM7swLtEAWdXR9d5Ba3EhiP3lgcEXvErqYVeZXxs5lgy6YYZRsTWf8E-c7bHYV2k-o4aohWwLPwj6opX0yVZD0Z-406ASTW1_VzobZKHaIhBCycUK3fVuKsDR-C0YDzLBlFBRAHoydlXK6XNqJcwqni64pKrgVgeVPh9cyQ4dM/https%3A%2F%2Ftwitter.com%2Fcomlaude%3Flang%3Den" target="_blank"><b><span style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><image009.png></span></b></a></span><b><span lang="EN-US" style="font-size:9pt;font-family:"Poppins Light""> </span></b><span lang="EN-US"><a href="https://www.facebook.com/ComLaude/" target="_blank"><b><span style="font-size:9pt;font-family:"Poppins Light";text-decoration:none"><image010.png></span></b></a><br>
<br>
<image011.png><u></u><u></u></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="1" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><span lang="EN-US">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<span class="m_9027943361584356551apple-converted-space"> </span><a href="https://secure-web.cisco.com/1fAS9w-NRUWTvfqlrwf9dqUaqT8nWymC_MP4NWXVwcfSqc1MsM7EOHuk4KBciMJ2ypcKZizxMVR5nJDnBt6CDGWMp9v4RWnyGgEJaQpRX9muHdjWic17n6fklslPhtD6zGkWT4IiC1QGBgBqJMfp45A6v1_dZTBn2iFgozcf9aERaQRFdT0Fpg7z_2gXXfG2lpLecgMkxzDxVgiWp4mEfAfkzv65CWBSYMQT0wkIb2SKCZlpvvR0a4Kp1igDf_O3euH0_0t_OWTXoLiXTfIeT8FzlvGfPc9ksMiZGXCtGVfM/https%3A%2F%2Fcomlaude.com" target="_blank"><span style="color:rgb(5,99,193)">www.comlaude.com</span></a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:ArialMT">_______________________________________________<br>
IOT mailing list<br>
</span><span lang="EN-US"><a href="mailto:IOT@icann.org" target="_blank"><span style="font-size:10.5pt;font-family:ArialMT;color:rgb(5,99,193)">IOT@icann.org</span></a></span><span lang="EN-US" style="font-size:10.5pt;font-family:ArialMT"><br>
</span><span lang="EN-US"><a href="https://secure-web.cisco.com/1KjqmW97zUTf_JLJEJi_kP_lYtqBoBIujjP6lvvjozhNjcoPOePHnjAKeZGYCQd2NjcmKwvxidxqC-0PSD-8LF8baevV7XurEcoaNY-aGWKX9L4BCIiFuKBq8GBs_OK-kQfTGOqHsHuS0VqFlnt9hIgDZ13509budukkn-MeQHwVrAIVnKeItWAuuZ8shpfKFehA_AArU0mDiv4LxM6up4NX8-_RL3zoPo0SeJBbVNwxmlLxhByJOvyo-VyVFfmcHq25AJjc9AO-BpmG95zKKepgfI8rQ9gbpRwKStlSbVW8/https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fiot" target="_blank"><span style="font-size:10.5pt;font-family:ArialMT;color:rgb(5,99,193)">https://mm.icann.org/mailman/listinfo/iot</span></a></span><span lang="EN-US" style="font-size:10.5pt;font-family:ArialMT"><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 (</span><span lang="EN-US"><a href="https://secure-web.cisco.com/1DKf0Y48xPy5viVE2hcGYEK2zrU82NwCZGq9tk3JzBOXSmCTzGdnhLBywiWALvPthGcyRYTwgMoEfhYacfJoAJn2xiWQgxmnvFG1Md7A2ZlLZvxatRhrX7SUmXLGjBOaECPgispnttMY62Th6DiAxloz2js3zJjtBxc2Kyx7bRGFCX32Fecjxm7xs26OGzXHpGIZA5SvDrBnzpCVMlsJAyTxwp2LqdOc2_c3xMF4nEiOzipKtgHntQMcDIH7e7tFrJUZhfAVdVLJ-cPy6T02tKsMdfzHXxYMW6QPQji_W0Do/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Fpolicy" target="_blank"><span style="font-size:10.5pt;font-family:ArialMT;color:rgb(5,99,193)">https://www.icann.org/privacy/policy</span></a></span><span lang="EN-US" style="font-size:10.5pt;font-family:ArialMT">)
and the website Terms of Service (</span><span lang="EN-US"><a href="https://secure-web.cisco.com/1zVi745PSEg05F7Kp2GoY1nZUld0DGDVO-m0_Pu9-Sjyj4jYGYCmQIn5iLwtr0tkX_BMubxXfwOK93tWGD-EQHU8YV05L44OvEhWBsOviUO0W3ApTkRPVyNTKPMSS7ItlZlDog4rGMEc64F2zWqR0U5ZHMjv_ZsNbnoY0FY29IRWZH6tIOhsOtjnzynmMRSV4zDAezJuC87xHxiOQ-V92etL619x3Ym7sPAt63kuNRIGHiJwhAdI7IodB-DJZ51Q4EFD54QBMnlJJxMkB-n_NQi_V4RaygQXPCI0g2uaVYa8/https%3A%2F%2Fwww.icann.org%2Fprivacy%2Ftos" target="_blank"><span style="font-size:10.5pt;font-family:ArialMT;color:rgb(5,99,193)">https://www.icann.org/privacy/tos</span></a></span><span lang="EN-US" style="font-size:10.5pt;font-family:ArialMT">).
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.</span><span lang="EN-US"><u></u><u></u></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal">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></p>
</div>
<hr>
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>
</div>
</div></blockquote></div></div>