<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">This looks important
folks. ALso requires some homework catching up prior to the
briefing.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers Steph</font></font><br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>[council] Agenda Item for discussion during 20 September
2017 Council call</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Thu, 7 Sep 2017 22:57:17 +0000</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Austin, Donna via council <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Reply-To:
</th>
<td>Austin, Donna <a class="moz-txt-link-rfc2396E" href="mailto:Donna.Austin@team.neustar"><Donna.Austin@team.neustar></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:council@gnso.icann.org"><council@gnso.icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
<td>'<a class="moz-txt-link-abbreviated" href="mailto:craig@ftld.com">craig@ftld.com</a>' <a class="moz-txt-link-rfc2396E" href="mailto:craig@ftld.com"><craig@ftld.com></a>,
<a class="moz-txt-link-abbreviated" href="mailto:heather@ftld.com">heather@ftld.com</a> <a class="moz-txt-link-rfc2396E" href="mailto:heather@ftld.com"><heather@ftld.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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:11.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;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:31.0pt 67.0pt 14.0pt 66.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1030" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear Councilors<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">Over the past
six months or so a number of community gTLD registry
operators have been developing a Draft Community gTLD Change
Request Process. This has been done under the guidance of
GDD staff and in consultation with the RySG. Attached is a
copy of the draft process for information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Craig Schwartz
from fTLD Registry, and who has been leading this effort,
has requested an opportunity to brief the Council on the
process and this will be done during the 20 September 2017,
Council call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-top:1.6pt"><b><span
style="color:#1F497D">Background<o:p></o:p></span></b></p>
<p class="MsoNormal"
style="margin-top:.8pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-right:5.55pt;line-height:98%"><span
style="color:#1F497D">In September 2016, fTLD submitted a
request to ICANN to amend Specification 12 of our Registry
Agreements for .BANK and .INSURANCE to add another class of
regulated entities to our respective Registrant Eligibility
Policies. fTLD submitted the request after following our
Policy Development Process Policy available at
<a href="https://www.ftld.com/policies/"
moz-do-not-send="true"><span
style="color:#1F497D;text-decoration:none">https://www.ftld.com/policies/
</span></a>and with approval from our Advisory Council and
Board of Directors, which are both comprised solely of
banks, insurance companies and financial services trade
associations. ICANN denied the request in September 2016,
stating in part that they are “not currently in a position
to approve requests to amend community restrictions in
Specification 12 of the New gTLD Registry Agreement.”<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:.7pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-right:5.35pt;line-height:98%"><span
style="color:#1F497D">In follow-up discussions with ICANN
GDD and Legal staff, fTLD was told that ICANN could not
consider the requested changes because there was no
community-developed/supported process to enable them to do
so. There was a procedure discussed in the New gTLD Program
Explanatory Memorandum Discussion Draft: Community gTLD
change request handling, but because it had not been
approved nor was it included in the Applicant Guidebook,
ICANN could not use this as the basis for considering our
request. As a result, ICANN asked fTLD if we would help lead
the way in creating a Community gTLD Change Request process.
fTLD agreed to undertake this effort and formed a working
group comprised of fTLD and several community-based Registry
Operators and New gTLD Applicants to develop a draft
Community gTLD Change Request process.<o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:5.35pt;margin-bottom:0in;margin-left:6.0pt;margin-bottom:.0001pt;line-height:98%"><span
style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-right:5.35pt;line-height:98%"><span
style="color:#1F497D">The working group also sought input
from the RySG on various iterations of the proposal and the
current draft incorporates the feedback provided as a result
of this exercise. <o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:5.35pt;margin-bottom:0in;margin-left:6.0pt;margin-bottom:.0001pt;line-height:98%"><span
style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-right:5.35pt;line-height:98%"><span
style="color:#1F497D">The working group has also been
working closely with ICANN’s GDD team.<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt;mso-line-height-rule:exactly">
<span style="color:#1F497D">Donna<o:p></o:p></span></p>
</div>
</div>
</body>
</html>