<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I was scratching my
head over this one too. I sent it to Jeremy and Kathy,
figuring they might be interested. How do you add new members
to a community. when the requestors are the ones figuring out
the process? Seems a bit fishy. How is this not scope
creep? But I know so little about the community gTLDs, will
have to brush up on this stuff before the next council meeting</font></font></p>
<p><font size="+1"><font face="Lucida Grande">SP</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-09-07 20:37, Rafik Dammak
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH5sTh=VoW+Npe6aiOv_t5AxWx5MvMwQAx7o4u=+NEzYcJCRcQ@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_extra">Hi,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I am trying to understand the process
described in the email: so the purpose of the working group is
to make a proposal for changing (or adding to) the
implementation by the AGB on how to handle community gTLD
change request. I am kind of surprised that ICANN (staff in
GDD or the board) to ask the requestors to lead the effort and
going through an ad-hoc process.</div>
<div class="gmail_extra">I am also wondering if the gTLD
subpro WG reviewed anything linked to that for the
community-based gTLD.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Best,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Rafik<br>
<br>
<div class="gmail_quote">2017-09-08 9:29 GMT+09:00 Stephanie
Perrin <span dir="ltr"><<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank" moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div 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="m_8161942023887346155moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table
class="m_8161942023887346155moz-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="m_8161942023887346155moz-txt-link-rfc2396E"
href="mailto:council@gnso.icann.org"
target="_blank" moz-do-not-send="true"><council@gnso.icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT"
nowrap="nowrap">Reply-To: </th>
<td>Austin, Donna <a
class="m_8161942023887346155moz-txt-link-rfc2396E"
href="mailto:Donna.Austin@team.neustar"
target="_blank" moz-do-not-send="true"><Donna.Austin@team.neustar></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT"
nowrap="nowrap">To: </th>
<td><a
class="m_8161942023887346155moz-txt-link-abbreviated"
href="mailto:council@gnso.icann.org"
target="_blank" moz-do-not-send="true">council@gnso.icann.org</a>
<a
class="m_8161942023887346155moz-txt-link-rfc2396E"
href="mailto:council@gnso.icann.org"
target="_blank" moz-do-not-send="true"><council@gnso.icann.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT"
nowrap="nowrap">CC: </th>
<td>'<a
class="m_8161942023887346155moz-txt-link-abbreviated"
href="mailto:craig@ftld.com" target="_blank"
moz-do-not-send="true">craig@ftld.com</a>' <a
class="m_8161942023887346155moz-txt-link-rfc2396E"
href="mailto:craig@ftld.com" target="_blank"
moz-do-not-send="true"><craig@ftld.com></a>,
<a
class="m_8161942023887346155moz-txt-link-abbreviated"
href="mailto:heather@ftld.com"
target="_blank" moz-do-not-send="true">heather@ftld.com</a>
<a
class="m_8161942023887346155moz-txt-link-rfc2396E"
href="mailto:heather@ftld.com"
target="_blank" moz-do-not-send="true"><heather@ftld.com></a></td>
</tr>
</tbody>
</table>
<div>
<div class="h5"> <br>
<br>
<div class="m_8161942023887346155WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">Dear
Councilors</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </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.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></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.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal" style="margin-top:1.6pt"><b><span
style="color:#1f497d">Background</span></b></p>
<p class="MsoNormal"
style="margin-top:.8pt;line-height:12.0pt"> <span
style="color:#1f497d"> </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/"
target="_blank" 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.”</span></p>
<p class="MsoNormal"
style="margin-top:.7pt;line-height:12.0pt"> <span
style="color:#1f497d"> </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.</span></p>
<p class="MsoNormal"
style="margin-right:5.35pt;margin-bottom:0in;margin-left:6.0pt;margin-bottom:.0001pt;line-height:98%"><span
style="color:#1f497d"> </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. </span></p>
<p class="MsoNormal"
style="margin-right:5.35pt;margin-bottom:0in;margin-left:6.0pt;margin-bottom:.0001pt;line-height:98%"><span
style="color:#1f497d"> </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.</span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt"> <span
style="font-size:12.0pt"> </span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt"> <span
style="color:#1f497d">Thanks</span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt"> <span
style="color:#1f497d"> </span></p>
<p class="MsoNormal"
style="margin-top:.5pt;line-height:12.0pt"> <span
style="color:#1f497d">Donna</span></p>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is"
moz-do-not-send="true">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>