In relation to this topic, please see ICANN Org’s initial feedback to the draft process for handling a community gTLD change request: https://www.icann.org/en/system/files/correspondence/weinstein-to-schwartz-2.... Best regards, Marika From: <council-bounces@gnso.icann.org> on behalf of "James M. Bladel" <jbladel@godaddy.com> Date: Friday, September 8, 2017 at 08:22 To: Donna Austin <Donna.Austin@team.neustar>, "council@gnso.icann.org" <council@gnso.icann.org> Cc: "'craig@ftld.com'" <craig@ftld.com>, "heather@ftld.com" <heather@ftld.com> Subject: Re: [council] Agenda Item for discussion during 20 September 2017 Council call Thank you, Donna. Council Colleagues – there is quite a bit of info here, so please take a moment to review before our call on 20 SEP. And if you can give Phil/Donna a heads up on any questions you intend to ask during the meeting, I’m sure they would be grateful for any opportunity to prep their response. Thanks, J. ------------------ James Bladel GNSO Chair From: <council-bounces@gnso.icann.org> on behalf of GNSO Council List <council@gnso.icann.org> Reply-To: "Austin, Donna" <Donna.Austin@team.neustar> Date: Thursday, September 7, 2017 at 17:57 To: GNSO Council List <council@gnso.icann.org> Cc: "'craig@ftld.com'" <craig@ftld.com>, "heather@ftld.com" <heather@ftld.com> Subject: [council] Agenda Item for discussion during 20 September 2017 Council call 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/ [ftld.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ftld.com_policies_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5-OhY1fBnz7f0cI0OLs7w2GTX9ksJUMfosafgM9qfiA&s=pY8aDwyJCeBawhlilB3uN0N4VGLZyuKlED3saeEaluU&e=>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