Thanks Michele. I don’t want to open up the By-laws to just any idea, which is why I drafted the scope so narrowly. As far as the reason goes, I think ICANN needs to use language that conveys meaning that everyone can rely on. New people who hear of generic TLDs and the Generic NSO may not connect that with the GDD and if they do may well wonder why the same community can’t call things the same thing. I know we have a full plate and that there is no hard deadline on this, but if we are going to keep up with the times, we have to talk about it at some point. And, we always have a full plate. Best, Paul From: Michele Neylon - Blacknight [mailto:michele@blacknight.com] Sent: Thursday, June 15, 2017 9:34 AM To: icannlists <icannlists@winston.com>; GNSO Council List (council@gnso.icann.org) (council@gnso.icann.org) <council@gnso.icann.org> Subject: Re: [council] Motion for JoBurg Meeting Paul So you want ICANN to open up the bylaws again? I don’t think changing the words behind the acronym is worth re-opening discussion around the bylaws. I also think the ICANN Community as a whole has enough on its plate without adding to it for something like this. Now if you could present a detailed rationale as to why this is so pressing then I’m sure some people might be willing to consider it, but so far I personally don’t see it. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of icannlists <icannlists@winston.com<mailto:icannlists@winston.com>> Date: Thursday 15 June 2017 at 15:20 To: "GNSO Council List (council@gnso.icann.org<mailto:council@gnso.icann.org>) (council@gnso.icann.org<mailto:council@gnso.icann.org>)" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Motion for JoBurg Meeting Hi All, Below is my motion for consideration when we are together in Johannesburg. Safe travels. Best, Paul WHEREAS, the domain names promulgated by ICANN are available globally and are not sponsored by any particular government (“Global Domains”); WHEREAS, the term “generic” has several meanings within various portions of the ICANN Community; WHEREAS, since the advent of .brand top level domain names, the use of the term “generic” in relationship to Global Domains has become increasingly confusing; WHEREAS, the ICANN Organization has already adjusted its nomenclature and has named the division of the organization dealing with non-ccTLD domain names the “Global Domains Division” Resolved, The GNSO Council requests ICANN staff to issue a call for volunteers to form a Drafting Team to consider a possible change from “Generic Names Supporting Organization” to “Global Names Supporting Organization”, including a proposed implementation plan if such a change is recommended. The scope of the Drafting Team is limited to considering whether or not to change the name of the Generic Names Supporting Organization to the “Global Names Supporting Organization” and to identify changes to the ICANN By-laws, Operating Procedures, and current PDP Charters necessary to effectuate such a renaming, if recommended. The drafting team will not have scope to consider any other changes including, but not limited to, the ICANN By-laws, the GNSO operating procedures, or any current PDP charters. The Drafting Team is expected to publish its proposed recommendations and if applicable proposed implementation plan for public comment prior to submitting it to the GNSO Council for its consideration. The GNSO Council appoints [name] as the Council liaison to the drafting team. ________________________________ The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.