<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 name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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;}
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;
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;}
@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 style='text-autospace:none'><span style='font-size:11.0pt'>Dear GNSO Councilors,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>Following the discussion at the GNSO Council meeting on 12 May on the draft revised ICANN Bylaws and the IANA Transition, staff conducted a detailed review and analysis of the final revised ICANN Bylaws with respect to GNSO obligations. This analysis, attached for your reference as a table (in Word and PDF), could provide guidance on where new GNSO operating procedures may be necessary, where it appears that existing procedures may apply, and where no action is necessary. Please note, however, that the attached table is subject to further updates pending final checks against the Bylaws.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>This analysis also could help guide a discussion at the Monday, 27 June GNSO meeting in Helsinki and for planning possible next steps. These steps could include approval of a follow-up mechanism, such as a Drafting Team that could work with staff to fully identify all the new or additional rights and responsibilities that the GNSO has, and develop new or modified procedures (as necessary) to fully implement the revised Bylaws.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>As noted in the attached analysis the revised ICANN Bylaws contain a number of new provisions that may require the GNSO Council and community to develop additional mechanisms to address certain new obligations and allow for the GNSO’s effective participation in the Empowered Community that is to be created as a result of the IANA stewardship transition, as well as to ensure continuity of GNSO processes in other matters. In the attached table, the staff analysis grouped the obligations as follows:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>1.</span><span style='font-size:11.0pt;font-family:"Times New Roman"'> </span><span style='font-size:11.0pt'>Obligations of the GNSO as a Decisional Participant of the Empowered Community;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>2.</span><span style='font-size:11.0pt;font-family:"Times New Roman"'> </span><span style='font-size:11.0pt'>Engagement in the new Customer Standing Committee; and<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>3.</span><span style='font-size:11.0pt;font-family:"Times New Roman"'> </span><span style='font-size:11.0pt'>New or existing procedures relating to voting thresholds.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>The details concerning how the Empowered Community exercises its powers in all the areas where these powers apply are contained in Annex D Empowered Community Mechanisms of the revised Bylaws. This Annex provides step-by-step descriptions of these mechanisms. Because of the complexity of Annex D, staff is conducting a separate analysis of the Annex in order to determine whether possible new GNSO procedures may apply and whether they can be grouped according to type of obligation or procedure.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>We look forward to your consideration of this analysis and any assistance we can provide for the subsequent discussion, as well as for planning next steps.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>Kind regards,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'>Julie<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Julie Hedlund, Policy Director</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></body></html>