<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="ICANN News Alert">
<meta name="Keywords" content="">
<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]-->
<title>ICANN News Alert</title>
<style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Calibri Light",sans-serif;
color:#2F5496;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
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 style="font-size:11.0pt;font-family:"Calibri",sans-serif">FYI, the staff report of public comments in relation to ICANN’s draft FY18 Operating Plan and Budget has been published (see below). To facilitate your review of the responses
to the Council input received, you will find the relevant excerpts right hereunder.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marika<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GNSO Council Comment #1</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: the GNSO Council notes that many of our comments filed in response to
the Draft FY17 Operating Plan and Budget were not adopted in the Final budget, and that some of these concerns persist in the Draft FY18 budget. This raises broader questions about how ICANN reviews comments received and, if appropriate, responds to the commenter
or amends the draft budget. Given the greater involvement of the Empowered Community in the review of FY18 and future budgets, we reiterate our call for greater transparency in the process of finalizing the draft budget. In particular, ICANN should consider
publishing a detailed analysis of comments received, along with a rationale for those not incorporated in to the Final Budget.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Response</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Staff agrees that providing more information in the published documents might enhance
transparency and accountability to the public interest as well as enable the community to perform its new responsibilities under the new Bylaws. Following the conclusion of the public comment period, ICANN held calls with the community to
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">improve its understanding of the comments received. These calls helped ICANN develop better responses and identify changes to make to the draft plans. The Response to Public
Comment report provides a detailed analysis of comments received, along with a rationale for those not incorporated in to the Final Budget. ICANN uses the comments and other feedback provided on its draft planning documents each year to identify areas of strength
and areas that could be enhanced. These are used to identify specific changes to the next year’s planning process. In the past 3 years, ICANN has organized the public comment responses by associated a response with every comment submitted. While the responses
all attempt to address the comments, the responses may do so by providing additional information as requested, or providing indications of future plans that address the comments received, or providing the rationale as to why a recommended action is not taken.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GNSO Council Comment #2</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: In regards to the chart displayed on page 10 of the draft FY18 budget
showing expenses of FY17 Forecast and FY18 Draft Budget by Function, it might be helpful to also provide a second chart that summarizes the current fiscal year forecast and following fiscal year draft budget at the Goal level (on a page 11) and if possible
by the Portfolio further down in the draft budget where the portfolios are detailed by Goal.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Response</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: We understand that it may be helpful to have the FY17 Forecast and FY18 Draft Budget
at the Goal level and by Portfolio. We publish the FY18 Draft Budget by Project, Goal level and Portfolio. Staff will consider incorporating this change in future Operating Plan and Budget documents.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GNSO Council Comment #3</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Projected growth in resources allocated for global engagement, ranked
third largest by function, continues to raise questions about the value proposition of these expenditures. If ICANN measures the success of this initiative in terms of “...show(ing) a balanced and regional approach to global engagement” and
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“stakeholder participation2 in ICANN by region,” then we request that Staff provide details demonstrating that progress towards these goals is justified by the continued spend
(funding and FTE headcount). For example, are the large quantity of regional stakeholder engagement events and sponsorships at internet related functions still required? And if so, what tangible and meaningful outcomes are derived other than just measuring
the quantity of those events as it pertains to ICANN’s mission such <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">as policy development around the generic names space?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Response</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Funding for Global Stakeholder Engagement did not increase in FY18 but was reduced.
Headcount within GSE was reduced due to transfer of positions to other ICANN functions. Following the review of our service delivery metrics from our mapping exercises in FY17, and gauging needs from ICANN’s regions, GSE had requested additional positions
for FY18 to support technical engagement in EMEA, a position in Istanbul to support local stakeholder engagement, and administrative support in the
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Nairobi and Montevideo offices. GSE has analyzed the delivery of services from ICANN offices and regions to the community, and conducted a mapping exercise to identify gaps
in participation from stakeholder groups in ICANN policy work. The GSE regional team is focused on publishing the tangible and meaningful outcomes of its work. A
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">key aspect of engagement at ICANN is that GSE’s work is largely demand-driven by requests from stakeholder groups in the regions. Regional Organizations request ICANN to
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">participate in engagement events, such as regional and national Internet Governance Forum events, cross-sector initiatives such as Smart Africa and others. The current goal
around measurement in FY18 is to measure this demand, the impacts of our efforts, and continuing to measure the Stakeholder Journey both as it exists today, and how it may exist in the future.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GNSO Council Comment #4</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: The GNSO Council notes with concern that the FYI18 budget, as in prior
years, places a lower priority on resources supporting Policy Development versus other initiatives and programs. In this context, priority is measured by total budget allocation, YoY growth projections, and FTE headcount. We reiterate our position from last
year that supporting policy development and the technical coordination of the Domain Name System are enumerated in ICANN’s Mission and Bylaws.3 The GNSO Council believes that scarcity of Policy Staff and other resources are a challenge to its ability to meet
its objectives. And that as an organization, ICANN is particularly vulnerable to Staff turnover and the loss of institutional knowledge in this area.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Response</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Staffing for the GNSO community is planned to continue at generally previous levels
for FY18 with a couple of professional service positions converting to full time staff. ICANN senior staff work with the Executive and HR teams to engage in succession planning efforts, staff retention and resourcing not only within the Policy Development
Support Team but across all ICANN departments. ICANN Organization is mindful of the critical core Organizational work supported by the Policy Development Support Team. When necessary the Policy Development Support Team has the ability to bring on professional
support services to supplement full time staff on issues of particular expertise that are needed by PDP and other working groups.See also Ref# 96 below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">GNSO Council Comment #5</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: FY18 Projections for new gTLD transaction fees (sec. 3.2 “Funding”) show
a best estimate of approximately 30% growth in funding derived from transaction fees associated with registrations in new gTLDs. Given that this level of growth is also established as the “low estimate,” we strongly encourage ICANN Finance staff to consult
with GNSO contracted parties (and in particular, gTLD registry operators) to ensure that this assumption is supported by their growth projections for the corresponding time frame.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Response</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Many factors are considered in the projection of transaction volumes and resulting fees,
including trends from historical data, recent marketplace developments, and input from industry participants (provided both directly and via public statements/documents). ICANN evaluates and utilizes those various perspectives in developing estimates on future
funding. In addition, the assumptions used for the low/best/high estimates were presented and discussed during the budget ad hoc working group meetings held in Hyderabad and Copenhagen.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black"><soac-leaders-bounces@icann.org> on behalf of David Olive <david.olive@icann.org><br>
<b>Date: </b>Friday, June 2, 2017 at 18:39<br>
<b>To: </b>"soac-leaders@icann.org" <soac-leaders@icann.org><br>
<b>Subject: </b>[SOAC-Leaders] ICANN News Alert -- Staff Report of Public Comments Published - ICANN's Draft FY18 Operating Plan and Budget<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div style="border:solid #CCCCCC 1.0pt;padding:8.0pt 8.0pt 8.0pt 8.0pt">
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=TbLX1s7xCH2cufWHog_CG-nVYVsxKdTF4m6y9SG62NI&s=kHGz-sYb4k3j_9L4F6A4B_c8KZTZxJVsCOnvGkqI5jU&e="><span style="text-decoration:none"><img border="0" width="94" height="94" id="_x0000_i1025" src="https://www.icann.org/sites/default/files/assets/icann-primary-logo-94x94-en.png" alt="CANN"></span>[icann.org]</a>
<o:p></o:p></p>
<h2>News Alert<o:p></o:p></h2>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<span style="font-family:"Arial",sans-serif"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D3-2D2017-2D06-2D02-2Den&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=TbLX1s7xCH2cufWHog_CG-nVYVsxKdTF4m6y9SG62NI&s=0bJrCQ79HHQQUDZtjw3sUJDbFKo9QET_QantYgzk9kI&e=">https://www.icann.org/news/announcement-3-2017-06-02-en[icann.org]</a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="margin-top:15.0pt;text-align:center">
<hr size="2" width="100%" align="center">
</div>
<h2 style="margin-bottom:0in;margin-bottom:.0001pt">Staff Report of Public Comments Published - ICANN's Draft FY18 Operating Plan and Budget<o:p></o:p></h2>
<p style="mso-margin-top-alt:11.25pt;margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt">
2 June 2017<o:p></o:p></p>
<p>On 2 June 2017, ICANN published the Staff Report of Public Comments on ICANN's Draft FY18 Operating Plan and Budget, and an associated update to the Five-Year Operating Plan. These documents were available for community feedback during a public comment period
from 8 March 2017 to 28 April 2017. The documents will be revised to incorporate necessary changes as indicated in the staff report, and will be posted to the public comment page within the next couple weeks.<o:p></o:p></p>
<p>ICANN recognizes and thanks all stakeholders who contributed to the submission of comments during this public comment period. Community and public participation in the planning and budget process of ICANN is a keystone of ICANN's multistakeholder model.<o:p></o:p></p>
<p>ICANN will seek adoption of the proposed FY18 Operating Plan and Budget and updated Five-Year Operating Plan at a board meeting during ICANN 59 in Johannesburg.<o:p></o:p></p>
</div>
</div>
<div style="margin-top:10.5pt;margin-bottom:10.5pt" id="globalfooterNEW1">
<p class="MsoNormal" align="center" style="text-align:center;line-height:12.75pt">
<span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:#777777"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
</body>
</html>