<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Poppins SemiBold";
panose-1:0 0 7 0 0 0 0 0 0 0;}
@font-face
{font-family:"Poppins Light";
panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
{font-family:"Helvetica Neue";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:26031623;
mso-list-template-ids:-1278159908;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1995257407;
mso-list-type:hybrid;
mso-list-template-ids:-1898021604 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’d like to echo Paul’s concerns, which I share, and his suggestion that Council ask the Board to pause for further discussion. I note that this is on the agenda for a Special Board Meeting tomorrow.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">If staff can be instructed to disapply the IRP and RfR by contract, rather than the community going through the formal process to approve a targeted Bylaws change, that sets a concerning precedent.
Furthermore:<o:p></o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span style="mso-fareast-language:EN-US">Doesn’t this place Org in a position where the Bylaws allow for these accountability mechanisms to apply, but a staff action purports to contravene
the Bylaws, which itself could be challenged?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l1 level1 lfo3"><span style="mso-fareast-language:EN-US">I also share the concern that Anne has raised that while this might catch the applicant who agrees to the terms, it would not cover a third
party who had not signed on to the terms and who might seek to challenge a Grant award to someone else.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">It seems that the CCWG considered how best to handle disapplying these accountability mechanisms and concluded that a Bylaws change was the right way forward. Seeking to shortcut this by using the
T&Cs appears to be an unsatisfactory alternative. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Susan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Poppins SemiBold"">Susan Payne
<br>
</span><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">Head of Legal Policy
</span><span style="font-size:9.0pt;font-family:"Poppins SemiBold""><br>
Com Laude<br>
</span><strong><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">T</span></strong><span style="font-size:9.0pt;font-family:"Poppins Light""> +44 (0) 20 7421 8250<br>
<strong><span style="font-family:"Poppins Light";color:#950734">Ext</span></strong> 255</span><span style="font-size:9.0pt;font-family:"Poppins SemiBold""><br>
<br>
</span><a href="https://comlaude.com/"><span style="font-size:9.0pt;font-family:"Poppins SemiBold";text-decoration:none"><img border="0" width="60" height="82" style="width:.625in;height:.8541in" id="Picture_x0020_1" src="cid:image001.png@01D9BFEA.9E26DDA0"></span></a><br>
<br>
<em><span style="font-family:"Calibri",sans-serif">We are pleased to launch our </span>
</em><a href="https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0"><i>new YouTube channel</i></a><img border="0" width="1" height="1" style="width:.0138in;height:.0138in" id="_x0000_i1025" src="https://t-uk.xink.io/Tracking/Impression/UxsAAGVfAADw_RQA0"><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>Paul McGrady via council<br>
<b>Sent:</b> Friday, July 21, 2023 9:19 PM<br>
<b>To:</b> council@gnso.icann.org<br>
<b>Cc:</b> gnso-secs@icann.org<br>
<b>Subject:</b> [council] Fwd: Message from Tripti Sinha to Former CCWG-AP Members<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I have reservations about this. While a narrowly tailored amendment to the Bylaws would have resulted in a carve out of the Accountability Mechanisms related solely to the grant program which would not be easily replicated
for other programs and issues, instructing Staff to do this <b><u>in a contract</u></b> sets a very worrying precedent and opens the door for other future instances where Staff could be instructed to use contracts and/or the renewals of contracts to carve
out the accountability mechanisms, making them a de facto nullity and undoing the work of the Accountability CCWG.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I think the Council should ask the Board to hold on this and engage in a community dialogue prior to taking further action. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Paul<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">On Thu, Jul 20, 2023 at 6:24 AM Wendy Profit <</span><a href="mailto:wendy.profit@icann.org" target="_blank"><span lang="EN-US">wendy.profit@icann.org</span></a><span lang="EN-US">> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i><span lang="EN-US" style="font-family:"Helvetica Neue",serif">Sending on behalf of ICANN Board Chair, Tripti Sinha…</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i><span lang="EN-US" style="font-family:"Helvetica Neue",serif"> </span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i><span lang="EN-US" style="font-family:"Helvetica Neue",serif"> </span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Dear Former CCWG-AP Members, (in bcc)<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">In follow up to the update email from Xavier Calvez, I am writing to you as Chair of the ICANN Board to update you on the Board’s discussions at its workshop
during ICANN77. During this workshop, the ICANN Board discussed with ICANN org how to best implement Recommendation #7 of the Final Report.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">As a reminder, part of Recommendation #7 stated that ICANN’s existing accountability mechanisms – the Independent Review Process (IRP) or the Reconsideration
Process – could not be used to challenge decisions made by the Independent Applications Assessment Panel on individual applications within the Grant Program. To allow this would add unnecessary complexity to the program. Additionally, the total available funding
for the program could also be depleted by the cost of such challenges. The CCWG-AP (and the Board as well, as indicated in our June 2022 action on the CCWG-AP’s Final Report) assumed that the best way to restrict the use of ICANN’s accountability mechanisms
in this way would be to amend the ICANN Bylaws to create a “carve-out.” This would therefore require a Fundamental Bylaws Amendment.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">After exploring this issue more in-depth, I am happy to share with you that the Board and ICANN org identified a path that both upholds the CCWG-AP’s recommendation
that individual application decisions should not be challenged through ICANN’s accountability mechanisms, while also keeping ICANN’s accountability mechanisms unchanged within the Bylaws. The Board is planning to take action on this later this month; however,
I wanted to provide you with a preview. The Board will direct ICANN org to use the contractual terms and conditions required to apply for the Grant Program to obtain applicant agreement that they cannot use ICANN’s accountability mechanisms to challenge any
individual decision taken on their application within the ICANN Grant Program. This remains in line with the CCWG-AP’s recommendation regarding the accountability mechanisms as well as the intention to lower complexity and protect the total amount of proceeds
available for applicants. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">When the CCWG-AP made Recommendation #7, it also provided guidance that providing limited opportunity for review of decisions within the Grant Program might also
introduce complexity, and encouraged ICANN to not make such opportunities available. However, when considering the inability for applicants to use ICANN’s accountability mechanisms for individual decisions, the ICANN Board will also ask ICANN org to explore
whether there are appropriate interim opportunities within the evaluation process for applicants to ask for a limited procedural review. The Board hopes this will enhance ICANN’s accountability to applicants, while following best practices within grant making
programs.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">We are happy to have identified a path forward that preserves the CCWG-AP’s recommendation and enhances accountability to applicants and the wider Internet community.
The Bylaws are important to us, and we are confident that we can keep up ICANN’s accountability, as set up, while at the same time limiting the ability to challenge for individual selection decisions.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">The Board is following ICANN org’s implementation closely and looks forward to seeing this program launch next year. Thank you again for your time and efforts
that went into envisioning this exciting program. The establishment of the ICANN Grant Program is a testament to your commitment to the work of the CCWG-AP and is an excellent representation of the multistakeholder model in action.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Kind Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Tripti Sinha<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Chair, ICANN Board of Directors<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-family:"Helvetica Neue",serif"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt" id="footer">
<p class="MsoNormal" style="background:#FFEB9C"><span lang="EN-US" style="color:black">This email originated from outside the firm. Please use caution.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</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>
</body>
</html>