<html 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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Century Gothic";
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="PT-BR" style="font-family:"Century Gothic"">I agree that 1-4 is to just support.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="PT-BR" style="font-family:"Century Gothic""> We can clearly state that we can not see budget alocated to issue 5 – which I believe there is no hurry for this.<o:p></o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Vanda Scartezini</span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Polo Consultores Associados</span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Av. Paulista 1159, cj 1004</span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">01311-200- Sao Paulo, SP, Brazil</span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Land Line: +55 11 3266.6253</span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Mobile: + 55 11 98181.1464 </span></i></b><span style="font-size:10.5pt;font-family:Calibri;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><i><span style="font-size:10.5pt;font-family:Calibri;color:#009193">Sorry for any typos. </span></i></b><span style="font-size:10.5pt;font-family:"Century Gothic";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="PT-BR" style="font-family:"Century Gothic""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="PT-BR" style="font-family:"Century Gothic""><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black"><alac-bounces@atlarge-lists.icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca><br>
<b>Date: </b>Wednesday, October 5, 2016 at 2:42 PM<br>
<b>To: </b>'ALAC List' <alac@atlarge-lists.icann.org><br>
<b>Subject: </b>[ALAC] Fwd: [CCWG-ACCT] Fwd: FW: Adopted motion<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal">There is an ongoing ALAC consensus call regarding approval of the FY17 CCWG Accountability WS2 budget and process which ends tomorrow. Based on the comments received to date, it will be approved.<br>
<br>
Below is the GNSO Motion approving the budget and process. I thank Sébastien for calling my attention to it. My assumption is that:<span style="font-family:MingLiU"><br>
<br>
</span>- Resolved 1-4 were implied in the proposal, but there is no harm in reiterating them;<span style="font-family:MingLiU"><br>
<br>
</span>- I think that we cannot stop the issue of jurisdiction/organization (Resolved 5) from being discussed, but I would not want to see an explicit funding (as in legal costs) going into this.<br>
<br>
Should we take any action? For example:<br>
<br>
a) Support 1-5 as noted above;<br>
<br>
b) explicitly not support one or more of the points;<br>
<br>
c) be silent;<br>
<br>
d) some other variant?<br>
<br>
Alan<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><b>From:</b> Marika Konings <br>
<b>Sent:</b> Thursday, September 29, 2016 11:33 PM<br>
<b>To:</b> Glen de Saint Géry <<a href="mailto:Glen@icann.org">Glen@icann.org</a>><br>
<b>Subject:</b> Adopted motion<br>
<br>
<b>Motion - GNSO Validation of CCWG-Accountability Budget Request<br>
</b><br>
Made By: James Bladel<br>
Seconded by: Julf Helsingius, Keith Drazek<br>
<br>
WHEREAS,<br>
<br>
1. Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all
the transition costs to date (see <a href="https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf">
https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf</a> ).<br>
<br>
2. The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23
June.<br>
<br>
3. Following review and discussion during ICANN56, the GNSO Council requested a webinar on this topic which was held on 23 August (see transcript at
<a href="https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf">
https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf</a> , recording at
<a href="http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3">
http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3</a> and AC recording at
<a href="https://icann.adobeconnect.com/p8fu99qpt7d/">https://icann.adobeconnect.com/p8fu99qpt7d/</a>).
<br>
<br>
4. The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not likely support revisiting the topic of the jurisdiction of ICANN’s organization in that such exploration would likely require
substantial independent legal advice on alternative jurisdictions and their potential impact on the text and structure of ICANN’s Bylaws.<span style="font-family:MingLiU"><br>
<br>
</span>5. The GNSO Council has discussed and reviewed all the relevant materials.<span style="font-family:MingLiU"><br>
<br>
</span>RESOLVED,<span style="font-family:MingLiU"><br>
<br>
</span>1. The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget, expects the working groups to be restrained and judicious in their use of outside
legal assistance, and believes that the Legal Committee should exercise reasonable and effective controls in evaluating requests for outside legal assistance and should approve them only when deemed essential to assist a working group to fully and objectively
understand and develop a particular course of action for which the group has reached a substantial degree of consensus and requires legal advice on its risks and feasibility.<br>
<br>
2. The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities.<br>
<br>
3. The GNSO Council expects ICANN staff, including its office of General Counsel, to provide the assistance requested by the CCWG and its working groups in an expeditious, comprehensive, and unbiased manner.<br>
<br>
4. The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or requests for additional funding beyond said budget should be recommended by the Legal Committee only when deemed
essential to completion of the CCWG’s work and objectives. .<span style="font-family:MingLiU"><br>
<br>
</span>5. It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, would not likely be supported by this projected budget and, further, that
such inquiry should not be undertaken at this time because the new accountability measures are all premised and dependent on California jurisdiction for their effective operation, and any near-term changes in organizational jurisdiction could be extremely
destabilizing for ICANN and its community.<br>
<br>
6. The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO.<o:p></o:p></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
</body>
</html>