<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<span lang="EN-US">How would the words "</span><span lang="EN-US">significant
issues" be interpreted and by whom? (From this piece of text
below "</span><span lang="EN-US"><span
style="font-family:"Arial","sans-serif";color:black;background:lime"
lang="EN-US">Notice is based on one or more significant issues
that were specifically raised in the applicable public comment
period(s)"<br>
<br>
</span></span>
<div class="moz-cite-prefix">Thanks.<br>
<br>
On 5/4/2016 4:46 PM, Mathieu Weill wrote:<br>
</div>
<blockquote cite="mid:5448e687.000005d8.00000080@cygnos" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:8.0pt;
margin-left:36.0pt;
line-height:105%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
p.e84b2592-57c5-40c7-995f-eb5ab116926e, li.e84b2592-57c5-40c7-995f-eb5ab116926e, div.e84b2592-57c5-40c7-995f-eb5ab116926e
{mso-style-name:e84b2592-57c5-40c7-995f-eb5ab116926e;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.balloontextchar
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Dear
Colleagues, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Paragraph
14 of Annex 4 of our supplemental report states : <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">A community decision to reject a budget or a
plan after it has been approved by the ICANN<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">Board will be based on perceived inconsistency
with the purpose, Mission and role set out in<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-family:"Helvetica","sans-serif""
lang="EN-US">ICANN’s Articles and Bylaws; the global public
interest; </span><span
style="font-family:"Arial","sans-serif""
lang="EN-US">the needs of ICANN stakeholders;<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-family:"Arial","sans-serif""
lang="EN-US">financial stability, or other matters of
concern to the community. <b>The veto could only concern<o:p></o:p></b></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span
style="font-family:"Arial","sans-serif""
lang="EN-US">issues that had been raised in the public
consultations conducted before the Board approved the<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-family:"Arial","sans-serif"">budget
or plan.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">(emphasis
added) <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">I
believe our lawyers have been diligent in ensuring this
requirement is taken into account. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Mathieu<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Kavouss Arasteh [<a class="moz-txt-link-freetext" href="mailto:kavouss.arasteh@gmail.com">mailto:kavouss.arasteh@gmail.com</a>] <br>
<b>Envoyé :</b> mercredi 4 mai 2016 15:25<br>
<b>À :</b> Mathieu Weill<br>
<b>Cc :</b>
<a class="moz-txt-link-rfc2396E" href="mailto:accountability-cross-community@icann.org"><accountability-cross-community@icann.org></a><br>
<b>Objet :</b> Re: [CCWG-ACCT] TR: Rationale Requirement
in Annex D, Section 2.2(c)(i)(A)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Did we specifically agreed in CCWG the
need for a)" rationale" <br>
And b) indoor the conditions that such rationale is based on
"one or more significant issues raised during the public
comment"?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">May you refresh our mind by citing the
corresponding paragraph in CCWG REC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Moreover, if such issue is not raised
during the public comment no action could be taken to reject
..,.,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Is this is not intended to reduce ,
diminish or make it impossible for any entity to proceed
with a petition in that regard?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">May you further clarify the matter<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kavouss<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 4 May 2016, at 08:43, Mathieu Weill <<a
moz-do-not-send="true"
href="mailto:mathieu.weill@afnic.fr"><a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a></a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">Dear Colleagues, </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">As a follow up from the call yesterday,
please find below a note from our lawyers regarding one
of the points we discussed. This is related to the
requirement to provide rationale when initiating a
community power escalation process. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">Mathieu</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"
lang="EN-US"> </span></b><o:p></o:p></p>
</div>
<div class="MsoNormal" style="text-align:center"
align="center"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif"" lang="EN-US">
<hr align="center" size="2" width="100%"></span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> Grapsas, Rebecca<br>
<b>Sent:</b> Tuesday, May 03, 2016 05:24:00 PM<br>
<b>To:</b> Gregory, Holly<br>
<b>Subject:</b> Rationale Requirement in Annex D,
Section 2.2(c)(i)(A)</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear Co-Chairs,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">On today’s CCWG
call, a concern was raised regarding the requirement
to provide “specific rationales” in Annex D, Section
2.2(c)(i)(A) (pasted below). As discussed below,
this provision is consistent with the CCWG Proposal.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
lang="EN-US">As I noted in the chat during today’s
call, the general requirement for the Petitioning
Decisional Participant to provide a rationale for
the rejection petition (i.e., the first part of (A),
highlighted in yellow) was included to reflect Annex
2, Paragraph 32 (first bullet, first sub-bullet)),
which provides that “Within 24 hours of a petition
being approved, the petitioning Decisional
Participant will: Circulate a detailed rationale for
proposing to use the Community Power to all
Decisional Participants. Any SO or AC may contribute
preliminary thoughts or questions in writing via a
specific publicly archived email list set up for
this specific issue….”</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
lang="EN-US">The language in (A) highlighted in
green was included to reflect Annex 4, Paragraphs 12
and 14:</span><o:p></o:p></p>
<p class="MsoListParagraph"
style="text-indent:-18.0pt;text-autospace:none"><span
style="font-family:Symbol" lang="EN-US">·</span><span
style="font-size:7.0pt;line-height:105%;font-family:"Times
New Roman","serif"" lang="EN-US">
</span><span lang="EN-US">Paragraph 12: “The
CCWG-Accountability has determined that a separate
petition would be required for each budget or
strategic/operating plan being challenged. A budget
or strategic/operating plan could only be challenged
if there are significant issue(s) brought up in the
engagement process that were not addressed prior to
approval.”</span><o:p></o:p></p>
<p class="MsoListParagraph"
style="text-indent:-18.0pt;text-autospace:none"><span
style="font-family:Symbol" lang="EN-US">·</span><span
style="font-size:7.0pt;line-height:105%;font-family:"Times
New Roman","serif"" lang="EN-US">
</span><span lang="EN-US">Paragraph 14: “A community
decision to reject a budget or a plan after it has
been approved by the ICANN Board will be based on
perceived inconsistency with the purpose, Mission
and role set out in ICANN’s Articles and Bylaws; the
global public interest; the needs of ICANN
stakeholders; financial stability, or other matters
of concern to the community. The veto could only
concern issues that had been raised in the public
consultations conducted before the Board approved
the budget or plan.”</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Given that a
budget or plan can only be rejected based on
“perceived inconsistency with the purpose, Mission
and role set out in ICANN’s Articles and Bylaws; the
global public interest; the needs of ICANN
stakeholders; financial stability, or other matters
of concern to the community”, the Bylaw was drafted
to limit the ability to escalate rejection of a
budget or plan to situations where the rationale
includes one or more of those specified items.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif";color:black"
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span lang="EN-US">Annex D,
Section 2.2(c)(i)(A):</span></u></b><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif";color:black"
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-family:"Arial","sans-serif";color:black"
lang="EN-US">(c) A Decisional Participant that has
received a Rejection Action Petition shall either
accept or reject such Rejection Action Petition;
provided that a Decisional Participant may only
accept such Rejection Action Petition if it was
received by such Decisional Participant during the
Rejection Action Petition Period. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-family:"Arial","sans-serif";color:black"
lang="EN-US">(i) If, in accordance with the
requirements of Section 2.2(c) of this Annex D, a
Decisional Participant accepts a Rejection Action
Petition during the Rejection Action Petition
Period, the Decisional Participant shall promptly
provide to the EC Administration, the other
Decisional Participants and the Secretary written
notice (“Rejection Action Petition Notice”) of such
acceptance (such Decisional Participant, the
“Rejection Action Petitioning Decisional
Participant”), and ICANN shall promptly post such
Rejection Action Petition Notice on the Website. The
Rejection Action Petition Notice shall also include:
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span
style="font-family:"Arial","sans-serif";color:black;background:yellow"
lang="EN-US">(A) the rationale upon which rejection
of the Rejection Action is sought. </span><span
style="font-family:"Arial","sans-serif";color:black;background:lime"
lang="EN-US">Where the Rejection Action Petition
Notice relates to an ICANN Budget, an IANA Budget,
an Operating Plan or a Strategic Plan, the Rejection
Action Petition Notice shall not be valid and shall
not be accepted by the EC Administration unless the
rationale set forth in the Rejection Action Petition
Notice is based on one or more significant issues
that were specifically raised in the applicable
public comment period(s) relating to perceived
inconsistencies with the Mission, purpose and role
set forth in ICANN’s Articles of Incorporation and
Bylaws, the global public interest, the needs of
ICANN’s stakeholders, financial stability, or other
matter of concern to the community;</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Annex D, Section
2.2(c)(i)(A) as included in the April 20 draft of
the Bylaws is consistent with the CCWG Proposal.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Holly</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US">HOLLY</span></b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US"> <b>J. GREGORY</b></span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:#1F497D"
lang="EN-US"><br>
</span><span
style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US">Partner and Co-Chair<br>
Corporate Governance & Executive Compensation
Practice Group</span><o:p></o:p></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US">Sidley Austin LLP</span></b><span
style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US"><br>
787 Seventh Avenue<br>
New York, NY 10019<br>
+1 212 839 5853</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:#1F497D"
lang="EN-US"><br>
</span><span
style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"
lang="EN-US"><a moz-do-not-send="true"
href="mailto:holly.gregory@sidley.com"
title="Click to send email to Gregory, Holly">holly.gregory@sidley.com</a></span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif";color:#1F497D"
lang="EN-US"><br>
<a moz-do-not-send="true"
href="http://www.sidley.com/"
title="www.sidley.com"><span
style="font-size:9.0pt;font-family:"Arial","sans-serif"">www.sidley.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Times New
Roman","serif"" lang="EN-US"> </span><o:p></o:p></p>
</div>
</div>
<p class="e84b2592-57c5-40c7-995f-eb5ab116926e"><span
lang="EN-US"> </span><o:p></o:p></p>
<p><span lang="EN-US">****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain
information that is privileged or confidential.<br>
If you are not the intended recipient, please delete the
e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************</span><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif"">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears | Director, Global Internet Policy & Human Rights Project
Center for Democracy & Technology | cdt.org
E: <a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a> | T: +44.771.247.2987
</pre>
</body>
</html>