[NCSG-PC] Fwd: [council] Agenda Item for discussion during 20 September 2017 Council call

[Stephanie Perrin]

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

SP


On 2017-09-07 20:37, Rafik Dammak wrote:
> Hi,
>
> 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.
> I am also wondering if the gTLD subpro WG reviewed anything linked to 
> that for the community-based gTLD.
>
> Best,
>
> Rafik
>
> 2017-09-08 9:29 GMT+09:00 Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>>:
>
>     This looks important folks.  ALso requires some homework catching
>     up prior to the briefing.
>
>     cheers Steph
>
>
>
>     -------- Forwarded Message --------
>     Subject: 	[council] Agenda Item for discussion during 20 September
>     2017 Council call
>     Date: 	Thu, 7 Sep 2017 22:57:17 +0000
>     From: 	Austin, Donna via council <council at gnso.icann.org>
>     <mailto:council at gnso.icann.org>
>     Reply-To: 	Austin, Donna <Donna.Austin at team.neustar>
>     <mailto:Donna.Austin at team.neustar>
>     To: 	council at gnso.icann.org <mailto:council at gnso.icann.org>
>     <council at gnso.icann.org> <mailto:council at gnso.icann.org>
>     CC: 	'craig at ftld.com <mailto:craig at ftld.com>' <craig at ftld.com>
>     <mailto:craig at ftld.com>, heather at ftld.com
>     <mailto:heather at ftld.com> <heather at ftld.com>
>     <mailto:heather at ftld.com>
>
>
>
>     Dear Councilors
>
>     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.
>
>     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.
>
>     *Background*
>
>     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 https://www.ftld.com/policies/ 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.”
>
>     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.
>
>     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.
>
>     The working group has also been working closely with ICANN’s GDD team.
>
>     Thanks
>
>     Donna
>
>
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170907/0b83ff7a/attachment.htm>