<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
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-family:"Calibri",sans-serif;}
@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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As you may recall, the GNSO Council directed 'ICANN Policy Staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of
the ICANN Bylaws pertaining to the GNSO’ to implement the Bylaws DT recommendations (<a href="https://gnso.icann.org/en/drafts/bylaws-drafting-team-final-report-12oct16-en.pdf">https://gnso.icann.org/en/drafts/bylaws-drafting-team-final-report-12oct16-en.pdf</a>).
In its analysis of the Drafting Team (DT), staff took a minimalist approach by focusing on the minimum changes needed to implement the DT recommendations, recognizing that in certain cases additional work may be desirable to facilitate the GNSO's participation
in the Empowered Community, such as creating templates or fact sheets. These proposed changes to the GNSO Operating Procedures and ICANN Bylaws were published for public comment on 19 June and closed on 10 August (see
<a href="https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en)">
https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en</a>). The staff report of public comments (see attached) will be published on the site shortly. Comments were received from all GNSO Stakeholder Groups and the CSG constituencies.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">In its analysis, Staff notes general support for the proposed changes to the GNSO Operating Procedures and ICANN Bylaws and their consistency with the intent of the Bylaws DT recommendations. Some specific
comments were identified in relation to the GNSO Operating Procedures to which staff has either responded or put forward a proposed way for addressing the comment (see section IV analysis of comments). In addition, the commenters restated their positions with
regards to the role of the GNSO Council along the lines of the positions recorded in the Bylaws DT Final Report.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">It is now up to the GNSO Council to determine what the next steps should be. These could include, for example, adoption of the revised GNSO Operating Procedures and ICANN Bylaws with the minor updates as suggested
in the analysis of comments, further consideration of the comments submitted, and/or consultation with the Bylaws DT. Staff would like to suggest adding this topic to the agenda for the next Council meeting so that you have an opportunity to consider these
or other options that are put forward. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marika <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">Marika Konings<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Email: <a href="mailto:marika.konings@icann.org">
<span style="color:#0563C1">marika.konings@icann.org</span></a> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"> <o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Follow the GNSO via Twitter @ICANN_GNSO<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso"><span style="color:#0563C1">interactive courses</span></a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span style="color:#0563C1">GNSO
Newcomer pages</span></a>. <o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>