June 2017 - council - lists.icann.org

FW: CSC Report performance PTI May 2017
by James Gannon 19 Jun '17

19 Jun '17

Councillors, On behalf of the CSC please find attached the CSC report for May 2017, there have been no substantial changes from the previous reports. AS ICANN 59 is a Policy Forum the CSC will not be holding any dedicated sessions however myself and other CSC members will be present in Johannesburg and I welcome any of you to contact me to speak about the work of the CSC or any related matters. I look forward to seeing you all in South Africa next week, James Gannon GNSO (Non-RySG) Liaison to the Customer Standing Committee From: icann-csc-bounces(a)icann.org [mailto:icann-csc-bounces@icann.org] On Behalf Of Bart Boswinkel Sent: 16 June 2017 14:41 To: soac-infoalert(a)icann.org Cc: ICANN-CSC(a)icann.org Subject: [ICANN-CSC] CSC Report performance PTI May 2017 Dear all, On behalf of the chair of the CSC (Byron Holland), please find included his monthly message to the community and the latest CSC report on the PTI performance May 2017 Kind regards, Bart Boswinkel Dear Community Members, As chair of the Customer Standing Committee I am pleased to provide you with our monthly report on the performance of Public Technical Identifiers (PTI) over May 2017. You will see that the CSC has concluded that, overall, PTI’s performance in May 2017 was “Satisfactory”, in that they met the agreed service agreement for 98.6 % of the defined metrics. The two, missed service level are subject to a CSC recommendation. In summary: on the evidence to date, the CSC has not identified a persistent problem and no further action is needed. The CSC was informed that PTI has not received a complaint in May 2017. The May 2017 PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports/201705[iana.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_performan…> In addition to its review of the PTI report, the CSC has reviewed the PTI survey to its customers (formerly known as the IANA survey) and together with PTI looked at ways to increase the level of feed-back from its customers in the naming community. The processes to the change the agreed Service Level Expectations were further discussed as well. The CSC has regular meetings: Every month at or around the 15th. The CSC report on the PTI performance is send out shortly after each meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce . Any comments on our reporting to you is welcome. The CSC was formed effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found athttps://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Kind regards, Byron Holland Chair CSC

3 2

FW: [SOAC-Leaders] ICANN59 Policy Report
by James M. Bladel 19 Jun '17

19 Jun '17

Councilors, in case you missed this. Thanks— J. From: <soac-leaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Monday, June 19, 2017 at 9:00 Subject: [SOAC-Leaders] ICANN59 Policy Report [cid:image001.png@01D2E8ED.1EA97180] The ICANN Policy Development Support Team is pleased to announce the publication of its Pre-ICANN59 Policy Report, in preparation for the upcoming Policy Forum in Johannesburg, South Africa. Download the report here: http://go.icann.org/preicann59policyreport[go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_preicann59…> The purpose of this Pre-ICANN59 Policy Report is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. David A. Olive Senior Vice President Policy Development Support Managing Director ICANN Regional Office –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Motion: Confirmation of process and criteria for selection of GNSO representative to the Empowered Community Administration
by Johan Helsingius 18 Jun '17

18 Jun '17

Here is the proposed motion for the Consent Agenda for our meeting on June 28 - item 3.1 – Confirmation of leadership for the GNSO Standing Selection Committee (SSC). Julf

2 1

Reminder: Document and Motion deadline Sunday, 18 June 2017 at 23:59 UTC for the GNSO Council Meeting 28 June 2017 at 11:00 UTC
by Nathalie Peregrine 17 Jun '17

17 Jun '17

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. SUNDAY, 18 June 2017 at 23:59 UTC) of the GNSO Council Meeting on 28 June 2017 at 11:00 UTC. (13:00 local time) Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/KgXfAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Proposed Final Agenda GNSO Council Meeting 28 June 2017 at 11:00 UTC
by Nathalie Peregrine 16 Jun '17

16 Jun '17

Dear councilors, Please find the Proposed Final Agenda for the GNSO Council Meeting on 28 June 2017 at 11:00 UTC (13:00 local time). Additional necessary information will be added upon receipt and an updated version circulated at that moment. Proposed Final Agenda for GNSO Council Meeting of 28 June 2017 in Johannesburg Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/KAXfAw This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 11:00 UTC: http://tinyurl.com/yafc4np6 04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Istanbul; 21:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/jnb59-ballroom2-en.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the meeting of the GNSO Council on 20 April 2017, posted on 8 May 2017. Minutes of the meeting of the GNSO Council on 18 May 2017, posted on 5 June 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (5 mins) 3.1 – Confirmation of leadership for the GNSO Standing Selection Committee (SSC) On 15 March 2017, the GNSO Council adopted the charter for the GNSO Standing Selection Committee (SSC), which was established on an interim basis to, upon request from the GNSO Council, select candidates for ICANN structures, such as review teams and related to the Empowered Community. The SSC has selected Susan Kawaguchi as its Chair and Johan Helsingius and Maxim Alzoba as Vice-Chairs. Here, the Council will confirm this leadership structure. Item 4: COUNCIL VOTE – Process and criteria for selection of the GNSO representative to the Empowered Community Administration (15 minutes) The GNSO, as a Decisional Participant in the Empowered Community, is required to deliver annually a written certification from its Chair or Vice-Chairs to the ICANN Secretary designating the individual who shall represent the Decisional Participant on the EC Administration. On 29 September 2016, the GNSO Council resolved that James Bladel, GNSO Chair, will represent the GNSO and serve as the interim representative to the Empowered Community Administration. Further, on 15 March 2017, the Council resolved that the GNSO Standing Selection Committee (SSC) would be tasked to develop the criteria and processes for the selection of the GNSO representative to the Empowered Community Administration. The Council has considered the proposed selection process as developed and shared by the SSC. Here, the Council will vote on whether or not to approve the proposed selection process and criteria. 4.1 – Presentation of motion (TBD) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Initiation of a Drafting Team to Consider Changing the Name of the GNSO (10 minutes) Some in the community have noted that as domain name are available globally, the term “generic” has certain meanings to different parts of the ICANN community, that the usage of “generic” to describe a .brand is potentially confusing, and among other reasons, that it might make sense to substitute the word “Generic” for “Global” in Generic Names Supporting Organization. To consider this change, the GNSO Council believes that a narrowly scoped Drafting Team should be formed to determine whether a change of this nature is recommended and if so, develop a proposed implementation plan to effectuate that change. Here, the Council will vote on whether to initiate a Drafting Team to consider changing the name of the GNSO. 5.1 – Presentation of motion (https://community.icann.org/x/KgXfAw) (Paul McGrady) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL DISCUSSION – Updated Charter for the Cross Community Working Group on Internet Governance (20 minutes) At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a motion conditioning the future participation of the GNSO as a Chartering Organization of the CCWG on Internet Governance (CCWG-IG) upon a comprehensive review of the group’s Charter by the CCWG-IG, in accordance with the Framework of Uniform Principles for CCWGs that had been adopted recently by the ccNSO and GNSO Councils (http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendation…). In its resolution, the GNSO Council had noted that the CCWG-IG’s future work is expected to be subject to a clear work plan, with regular updates and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was to report on its findings, which report may include a revised charter, and the CCWG-IG was to also consider whether it will be preferable to reconstitute the group under a new structure (https://gnso.icann.org/en/council/resolutions - 20161107-3<https://gnso.icann.org/en/council/resolutions#20161107-3>). The CCWG-IG provided a written report on its 2016 activity and a draft revised Charter for the GNSO Council’s consideration on 10th March 2017 (http://mm.icann.org/pipermail/council/2017-March/019816.html). At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its joint meeting with the ccNSO Council on 13 March 2017, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group’s reports. At the GNSO Council’s call on 18 May 2017, the Council continued its discussion of the topic. Here the Council will continue its discussion on the CCWG-IG’s revised charter and consider the GNSO’s participation as a Chartering Organization of this CCWG. 6.1 – Update on current status (GNSO Council chairs) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION – Proposed Fundamental Bylaw Changes (15 minutes) On 23 May 2017, the ICANN organization sent a notice<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> to the Empowered Community (EC) that the ICANN Board has approved<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> amendments to ICANN’s Fundamental Bylaws to move the Board Governance Committee’s reconsideration responsibilities to another Board Committee. This notice triggered the Bylaws-mandated process according to which the EC is to consider whether to approve the amendments before they can go into effect. On 27 June 2017 at ICANN59, the first Community Forum under the revised ICANN Bylaws will be held to discuss the proposal, and the EC will be coming together to exercise one of the EC's new powers under the revised ICANN Bylaws. Here, the Council will discuss the proposed Fundamental Bylaw change and plan for next steps. 7.1 – Update on current status (GNSO Council chairs) 7.2 – Council Discussion 7.3 – Next Steps Item 8: COUNCIL DISCUSSION – Cross Community Working Group on the Use of Country and Territory Names (15 minutes) On 26 March 2014, the GNSO Council resolved to approve the charter for the Cross Community Working Group on the Use of Country and Territory Names (CWG-UCTN). The purpose of the CWG-UCTN was to assess the feasibility of developing a harmonized framework for the use of country and territory names that could be applicable across the respective Supporting Organizations and Advisory Committees. On 24 February, the CWG-UCTN published its Interim Report for public comment. While the CWG-UCTN considered two and three-character country codes, it was determined that consensus was not feasible; the group did not consider full country and territory names. The CWG-UCTN therefore recommended that the CWG be closed, that policy efforts within the community should be consolidated, and that future work must be fully inclusive of the community. As a Chartering Organization, the GNSO is expected to consider the CWG-UCTN’s Final Report [LINK TO BE PROVIDED] and determine next steps. Here, the Council will discuss the Final Report and its recommendations and consider next steps. 8.1 – Update on current status (Heather Forrest) 8.2 – Council discussion 8.3 – Next steps Item 9. UPDATE – Initiation of the GNSO’s Section 16 Process for Amending Approved GNSO Policy Recommendations Relating to Certain Red Cross Movement Names (15 minutes) At ICANN58 in Copenhagen in March 2017, representatives from the GNSO (including the GNSO Council chairs) and the GAC held a dialogue, facilitated by former Board member Bruce Tonkin, to discuss possible ways of reconciling inconsistent GAC advice and GNSO policy recommendations relating to National Society names of the Red Cross Movement and the two names of the international components of the Movement (http://sched.co/9xr2). Following that discussion, the ICANN Board passed a resolution requesting that the GNSO Council initiate the process outlined in Section 16 of the GNSO’s Policy Development Process (PDP) Manual, which sets forth the requisite steps for amending policy recommendations that have been approved by the GNSO Council but not yet approved by the ICANN Board (https://www.icann.org/resources/board-material/prelim-report-2017-03-16-en#…). The Board’s request was limited to the 190 Red Cross National Society names, the two international movement names and a limited defined set of their variants. The Council initiated electronic voting on the Board’s request on 3 May 2017, with the motion to initiate the policy amendment process passing<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-07may17-en.…> successfully. Here the Council will receive an update on the progress of the original PDP Working Group, reconvened for this purpose in accordance with Section 16, regarding the policy amendment process. 9.1 – Update on current status (Thomas Rickert) 9.2 – Next Steps Item 10: ANY OTHER BUSINESS (15 minutes) 10.1 – Update on Review Teams * Registration Directory Service (RDS) Review Team: The GNSO’s four (4) Primary nominees, Erika Mann, Stephanie Perrin, Susan Kawaguchi, and Volker Greimann, were selected to serve on this RDS Review Team. The RDS Review Team has held its first meeting and a brief update will be provided on the work to date. * Second Security, Stability, and Resiliency Review Team (SSR2): The SSR2 Review Team has been meeting since early March of 2017 and here, an update will be provided on the team’s latest work. 10.2 – Open Microphone ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 11:00 UTC Local time between October and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-7 04:00 San José, Costa Rica UTC-6 05:00 Iowa City, USA (CST) UTC-5 06:00 New York/Washington DC, USA (EST) UTC-4 07:00 Buenos Aires, Argentina (ART) UTC-3 08:00 Rio de Janeiro, Brazil (BRST) UTC-3 08:00 London, United Kingdom (GMT) UTC+1 12:00 Bonn, Germany (CET) UTC+2 13:00 Cairo, Egypt, (EET) UTC+2 13:00 Istanbul, Turkey (TRT) UTC+3 14:00 Singapore (SGT) UTC +8 19:00 Tokyo, Japan (JST) UTC+9 20:00 Sydney/Hobart, Australia (AEDT) UTC+11 21:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2017, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and http://tinyurl.com/yafc4np6 Thank you. With kind regards, Nathalie Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Motion for JoBurg Meeting
by icannlists 16 Jun '17

16 Jun '17

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.

5 6

Re: [council] Motion for JoBurg Meeting
by Michele Neylon - Blacknight 15 Jun '17

15 Jun '17

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(a)gnso.icann.org> on behalf of icannlists <icannlists(a)winston.com> Date: Thursday 15 June 2017 at 15:20 To: "GNSO Council List (council(a)gnso.icann.org) (council(a)gnso.icann.org)" <council(a)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.

4 3

FW: [soac-chairs] SO/AC Leaders about pre-Joburg Submissions to the Empowered Community
by James M. Bladel 15 Jun '17

15 Jun '17

Councilors, see below. One of the challenges we will face in Johannesburg is an exceptionally tight timeframe for the GNSO to review/approve the changes coming out of the Community Forum. While the subject matter this time around is not very controversial, this might not always hold true for future issues. To participate effectively in the Empowered Community, the GNSO will have to become a bit more “nimble.” I’m looking forward to our discussion in a few weeks. Thanks— j. From: <soac-chairs-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Wednesday, June 14, 2017 at 4:28 Cc: Mary Wong <mary.wong(a)icann.org> Subject: [soac-chairs] SO/AC Leaders about pre-Joburg Submissions to the Empowered Community Dear SO/AC Chairs: As you know, ICANN59 will see the convening of the first-ever Community Forum for the new Empowered Community, as part of the Approval Action process outlined in the revised ICANN Bylaws concerning a proposed amendment to one of ICANN’s Fundamental Bylaws. This note is being sent to remind you and your community groups that, under the revised ICANN Bylaws, any SO or AC “may deliver to the EC Administration in writing its views and questions on the Approval Action prior to the convening of and during the Approval Action Community Forum” (Annex D, Section 1.3(f).) You may wish to note that the ability to provide written views is not limited to the five Decisional Participants that make up the Empowered Community, and all such views received will be posted publicly to the Empowered Community’s Correspondence page on the ICANN website. The Approval Action relates to the Board’s intention to re-designate the responsibility for handling Reconsideration Requests from the Board Governance Committee (BGC) to a new Board committee that will be specifically charged with oversight of ICANN accountability mechanisms, as the Board deems appropriate, with the BGC focusing on core governance activities: https://features.icann.org/proposed-fundamental-bylaws-change-move-board-go…. The Board passed a resolution to this effect on 18 May 2017, and as this proposal will amount to an amendment of a Fundamental Bylaw, this triggered the current Approval Action process through which the Empowered Community can exercise its right to approve a Fundamental Bylaw amendment (see Annex D of the ICANN Bylaws:https://www.icann.org/resources/pages/governance/bylaws-en/#annexD). As the requisite ICANN Secretary notice was sent to the Empowered Community on 23 May 2017, the following timelines apply to this Approval Action process: * Community Forum phase: opened 23 May 2017, closing at 21:59 UTC on 29 June 2017 * Empowered Community decisional phase: opens at 22.00 UTC on 29 June 2017, closes at 06:59 UTC on 21 July 2017 Please see this page for an overview and graphical depiction of the process: https://www.icann.org/en/ec/proposed-fundamentals-bylaws-changes-move-gov-c…. If your respective community groups wish to provide written views on the proposed Fundamental Bylaw amendment, please be sure to send these to the Empowered Community Administration at ecadmin(a)icann.org<mailto:ecadmin@icann.org> before the close of the Community Forum phase. Thank you. Best regards, David Olive Senior Vice President, Policy Development Support ICANN David A. Olive Senior Vice President Policy Development Support Managing Director ICANN Regional Office –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [council] Motion for JoBurg Meeting
by Nathalie Peregrine 15 Jun '17

15 Jun '17

Dear Paul, The motion has been posted on the Council wiki space: https://community.icann.org/x/KgXfAw Kind regards, Nathalie From: <council-bounces(a)gnso.icann.org> on behalf of icannlists <icannlists(a)winston.com> Date: Thursday, June 15, 2017 at 4:19 PM To: "council(a)gnso.icann.org" <council(a)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.

1 0

Fwd: [RrSG-Members] GoDaddy Status Update
by James M. Bladel 15 Jun '17

15 Jun '17

Councilors, FYI. Thanks - J. -------------- James Bladel GoDaddy ---------- Forwarded message ---------- From: James M. Bladel via RrSG-Members <rrsg-members(a)ICANN-registrars.org> Date: Jun 14, 2017, 20:36 -0500 Cc: James M. Bladel <jbladel(a)godaddy.com> Subject: [RrSG-Members] GoDaddy Status Update Registrar Colleagues - I am pleased to report that the .GODADDY TLD is no longer subject to Specification 13, or, by extension Specification 9. Many thanks to Akram and GDD Staff for helping to expedite this contract change over the past 48 hours. I am truly humbled and grateful for the kind words of support received since yesterday, both privately and here on the list. And in particular, for the support of the ExCom to retain me as an interim appointment. With my eligibility issues now resolved, I'm hopeful that need for a Special Election has been obsoleted by these developments, but I'll defer that decision to Theo and the ExCom. Thanks - J. -------------- James Bladel GoDaddy

3 2