<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0in;
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{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:8.5in 11.0in;
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Mathieu, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for forwarding this information. I support the approach you have outlined.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I would add, however, that we will also need to help ICANN more accurately predict workload and associated expenses for WS-2, so future budget planning can be more accurate. Speaking personally, I believe the
Board’s concerns around the “impact of project cost on ICANN’s reserves” are legitimate. We should help ICANN’s finance department better understand the future WS2 work plan to help ICANN allocate (or re-allocate) funds and hopefully avoid future overages
and having to draw on reserves. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Mathieu Weill<br>
<b>Sent:</b> Friday, February 05, 2016 4:16 AM<br>
<b>To:</b> 'CCWG-Accountability'<br>
<b>Subject:</b> [CCWG-ACCT] Inputs requested - Budget of the IANA Stewardship Transition<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear colleagues, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This note to report that the co chairs were invited to participate to a Board Finance Committee meeting to discuss the costs of the IANA Stewardship Transition project (overall, not only our group). You can find the notes from the call
attached. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A follow up meeting is planned for Tuesday, February 9th. The purpose of the call is the following (quoting the invite):
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:35.4pt">The Board Chair and members of the Board Finance Committee (BFC) would like to request a call with the Chairs of the SO/AC Chartering Organizations and CCWG/CWG co-chairs to seek their help and collaboration on
how to address key concerns regarding the escalating costs of the current phase of work of the USG IANA Stewardship Transition and Accountability WS1 (thereafter referred to in this document as THE PROJECT) as well as Implementation work as specified in the
CWG Proposal.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In advance of this call, we would like to hear your feedbacks regarding our proposed contribution to this matter.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We believe we could recognize : <o:p></o:p></p>
<p class="MsoNormal">- the value of the advice we are receiving from our two legal firms, which is instrumental to our progress<o:p></o:p></p>
<p class="MsoNormal">- the appreciation from our group of the support we are getting from staff<o:p></o:p></p>
<p class="MsoNormal">- the legitimate concerns from the Board regarding the impact of the project costs on Icann's financial reserves<o:p></o:p></p>
<p class="MsoNormal">- the massive effort undertaken by Icann to support the IANA Stewardship Transition process<o:p></o:p></p>
<p class="MsoNormal">- that there are limited costs that can be attributed to the groups (groups are not responsible for lobbying costs; personnel costs for example), and even some of those costs directly linked to the group are out of the control of the groups
( how many public comments received (costs to analyze them etc)).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We would also suggest to keep our current processes in place as they are until Marrakech, while renewing our group's commitment to act in a financially responsible manner.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We could also offer to include in our Marrakech deliberations a discussion to present to the Board a request for additional funding, to support Bylaw Drafting and Implementation of WS1 on the one side, and to support WS2 on the other side.
This type of request is consistent with our Charter, which states : <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:35.4pt">In addition to the advisors selected by the PEG, the CCWG-Accountability may also identify additional advisors or experts to contribute to its deliberations in a similar manner as the Advisors selected by the
PEG. Should additional costs be involved in obtaining input from additional advisors or experts, prior approval must be obtained from ICANN. Such a request for approval should at a minimum include the rationale for selecting additional advisors or experts
as well as expected costs. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We believe it would also be reasonable if approval of such funds were to be provided in Tranches, so that at the end of each period of, for example, 3 months, our group would have to report on progress and, when appropriate, renew its request
or present a new one. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for sharing your views on list on this. We look forward to your contributions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thomas, Leon & Mathieu<o:p></o:p></p>
<p class="MsoNormal">Co-chairs<o:p></o:p></p>
</div>
</body>
</html>