October 2017 - council - lists.icann.org

Reminder of outgoing/incoming GNSO Councilors ICANN60
by Nathalie Peregrine Oct. 25, 2017

Oct. 25, 2017

Dear councilors, As you prepare for your travels to ICANN60, here is a reminder of the names of outgoing and incoming GNSO Councilors: Contracted Party House Carlos Gutierrez –NomCom Appointee (Replacing Valerie Tan) Darcy Southwell & Rubens Kuhl (re-elected). Pam Little (Replacing RrSG Councilor James Bladel). Non Contracted Party House Syed Ismail Shah – NomCom Appointee (Replacing Julf Helsingius). Phil Corwin, Tony Harris & Paul McGrady (re-elected). Philippe Fouquart (replacing ISPCP Councilor Wolf-Ulrich Knoben) Ayden Federline (replacing NCSG Councilor Marilia Maciel), Arsene Tungali (replacing NCSG Councilor Stefania Milan), Tatiana Tropina (replacing NCSG Councilor Ed Morris), Martin Pablo Silva Valent (elected for one term) Kind regards, Nathalie Peregrine Nathalie Peregrine Manager, Operations 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

Final Agendas GNSO Council Meeting Part I and II - 1 November 2017 at 13:00 local time
by Nathalie Peregrine Oct. 25, 2017

Oct. 25, 2017

Dear Councilors, Please below find the final agendas GNSO Council Meeting Part I and II - 1 November 2017 at 13:00 local time. They will also be posted shortly on the GNSO Council wiki space<https://community.icann.org/x/1CIhB> and on the GNSO master calendar<https://gnso.icann.org/en/group-activities/calendar#nov>. Final Proposed Agenda 01 November 2017 Part I 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/1iIhB 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: 09:00 UTC: http://tinyurl.com/yaxkzhpl 02:00 Los Angeles; 05:00 Washington; 09:00 London; 12:00 Istanbul; 20:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-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<https://gnso.icann.org/en/meetings/minutes-council-20sep17-en.pdf> of the meeting of the GNSO Council on 20 September 2017, were posted on 9th October 2017 Minutes of the meeting of the GNSO Council on 12 October 2017, will be posted on 3rd November 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 (0 min) None Item 4: COUNCIL VOTE – Appointment of the next GNSO Liaison to the Governmental Advisory Committee (15 minutes) During the discussions of the GAC-GNSO Consultation Group<http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf>, a GNSO liaison to the GAC was proposed as a way to facilitate engagement of the GAC in GNSO policy development activities. On 7 November 2016, the GNSO Council appointed Carlos Raúl Gutiérrez to serve in this role. For the selection of the next GNSO liaison to the GAC, the GNSO Council has delegated the review and selection process to the GNSO Standing Selection Committee (SSC). The SSC reviewed all applications received and achieved full consensus in selecting Julf Helsingius as its preferred candidate. Here, the Council will thank Carlos for his service in support of this role and vote to approve Julf as his successor. 4.1 – Presentation of motion<https://community.icann.org/x/2iIhB> (Susan Kawaguchi) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5: COUNCIL DISCUSSION – Discussion on the Second Security, Stability, and Resiliency (SSR2) Review Team and Registration Directory Service (RDS) Review Team (15 minutes) The ICANN Bylaws call for periodic assessment by community review teams in the areas of: * Accountability and Transparency Review * Security, Stability, and Resiliency Review * Competition, Consumer Trust and Consumer Choice Review * Registration Directory Service Review The GNSO Council has asked that the GNSO representatives to these review teams, including the Security, Stability, and Resiliency Review Team (SSR-2 RT) and the Registration Directory Service Review Team (RDS-RT), provide regular feedback and updates as a group on the discussions taking place in the respective groups, as well as the positions being taken by GNSO representatives individually. There are some concerns within the community about the level of progress and direction of these reviews teams, including from the SSAC<https://www.icann.org/en/system/files/files/sac-098-en.pdf> and the ICANN Board<http://mm.icann.org/pipermail/ssr2-review/2017-October/000631.html> for SSR-2 RT and the ccNSO<https://www.icann.org/en/system/files/correspondence/sataki-to-crocker-15ma…> for the RDS-RT. Here, the Council will discuss some of these concerns and consider how it might be able to provide guidance or assistance to help the review teams better achieve its goals. 5.1 - Presentation of discussion topic (Council Leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION – Update from the GNSO Review Working Group (15 minutes) On 21 July 2016, the GNSO Council adopted<https://gnso.icann.org/en/council/resolutions#201607> the charter<https://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> for the GNSO Review Working Group. The WG was directed to propose an implementation plan to the GNSO Council for approval at the latest by ICANN57. On 15 December 2016, the GNSO Council adopted the proposed implementation plan, directing staff to submit the plan to the ICANN Board for its consideration. On 3 February 2017, the ICANN Board accepted<https://features.icann.org/independent-review-generic-names-supporting-orga…> the GNSO Review Implementation Plan. The GNSO Review Working Group was directed to provide the GNSO Council with regular status updates (at a minimum prior to every ICANN meeting) on the status of implementation. As part of this status update, the GNSO Review Working Group should also identify any questions and/or concerns that may have arisen during the implementation that would require further guidance. Here, the GNSO Review Working Group will provide the GNSO Council with the required update (GNSO2 Review Progress & Implementation Status Report<https://gnso.icann.org/en/drafts/gnso-review-progress-implementation-report…>) 6.1 – Presentation of discussion topic (GNSO Review WG Leadership) 6.2 – Council discussion 6.3 – Next Steps Item 7: COUNCIL DISCUSSION – Discussion with ICANN Finance (15 minutes) The GNSO Council is considering forming a Standing Committee to focus on the ICANN Budget and Operational Plan. While no decision has been made and as the Council continues to deliberate on whether it would like to pursue the establishment of this committee, it may be timely to receive an update from ICANN Finance to help the Council understand the nature and frequency of input that may be needed. In addition, ICANNN Finance would like to provide an update on ICANN’s Reserve Fund (public comment here<https://www.icann.org/public-comments/reserve-fund-2017-10-12-en>) and Long-Term Financial Planning. Here, the Council will receive an update from ICANN Finance and discuss the topics presented. 7.1 - Presentation of discussion topic (ICANN Finance) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Community gTLD Change Request Process (15 minutes) ICANN Organization has received requests, including from fTLD, to amend Specification 12 of their Registry Agreements. ICANN has denied the requests, 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 the request from fTLD and others. As a result, ICANN asked fTLD if it 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’s current draft includes input from the RySG. The working group has also been working closely with ICANN’s GDD team. ICANN has suggested that the GNSO Guidance Process (GGP) might be one path to resolution. fTLD and other impacted parties have concerns about the timeline for a GGP as well as the allocation of community resources to resolve an issue that affects a relatively limited number of Registry Operators. On 11 October, the Council received a letter from Craig Schwartz, intended to provide further clarity about why the issue was brought to the Council. Here, the Council will discuss the topic and determine next steps. 8.1 – Presentation of topic (Council Leadership) 8.2 – Council Discussion 8.3 – Next Steps Item 9: ANY OTHER BUSINESS (15 minutes) 9.1 – Discussion about ICANN Org paper on suggested incremental changes to the ICANN meeting strategy. 9.2 – Discussion about next steps for the revised ICANN Procedure for Handling Whois Conflicts with Privacy Law 9.3 - 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 09:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 02:00 San José, Costa Rica UTC-6 03:00 Iowa City, USA (CDT) UTC-5 04:00 New York/Washington DC, USA (EDT) UTC-4 05:00 Buenos Aires, Argentina (ART) UTC-3 06:00 Rio de Janeiro, Brazil (BRST) UTC-3 07:00 London, United Kingdom (GMT) UTC 09:00 Bonn, Germany (CET) UTC+1 10:00 Cairo, Egypt, (EET) UTC+2 11:00 Istanbul, Turkey (TRT) UTC+3 12:00 Singapore (SGT) UTC+8 17:00 Tokyo, Japan (JST) UTC+9 18:00 Sydney/Hobart, Australia (AEDT) UTC+11 20:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 29 of October 2017, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and http://tinyurl.com/yaxkzhpl Final Proposed Agenda 01 November 2017 Part II 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/1iIhB 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:15 UTC: http://tinyurl.com/y88ff7fb GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-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. Seating of the 2017 / 2018 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest Pam Little – SOI<https://community.icann.org/display/gnsosoi/Pam+Little+SOI> Registrars Stakeholder Group Philippe Fouquart – SOI<https://community.icann.org/display/gnsosoi/Philippe+Fouquart+SOI> Internet Service Providers and Connectivity Providers Arsène Tungali – SOI<https://community.icann.org/pages/viewpage.action?pageId=66087102> Non-Commercial Stakeholder Group Tatiana Tropina – SOI<https://community.icann.org/display/gnsosoi/Tatiana+Tropina+SOI> Non-Commercial Stakeholder Group Martin Pablo Silva Valent – SOI<https://community.icann.org/display/gnsosoi/Martin+Pablo+Silva+Valent+SOI> Non-Commercial Stakeholder Group Ayden Férdeline – SOI<https://community.icann.org/pages/viewpage.action?pageId=56989741> Non-Commercial Stakeholder Group Carlos Raul Gutierrez – SOI<https://community.icann.org/display/gnsosoi/Carlos+Raul+Gutierrez+SOI> Nominating Committee Appointee (CPH) Syed Ismail Shah – SOI<https://community.icann.org/display/gnsosoi/Syed+Ismail+Shah+SOI> Nominating Committee Appointee (NCPH) 1.3 - Review / Amend Agenda Item 2. Election of the Chair (15 mins) One nomination was received for this position, Heather Forrest from the Non-Contracted Parties House. The GNSO held a question & answer session with the candidate on 29 October 2017. Here the GNSO Council will proceed to elect its Chair for 2018-2019, according to the GNSO Operating Procedures (note Section 2.2 of the GNSO Operating Procedures on Officer Elections: Chair and Vice-Chairs (see Appendix 1 below). Item 3: COUNCIL DISCUSSION – Update on the GNSO Council Strategic Planning Session (15 minutes) In January of 2017, the GNSO Council submitted a FY18 additional budget request<https://community.icann.org/download/attachments/64066403/FY18%20-%2023%20-…> to support a 3 day face-to-face strategic planning session in January of 2018. At a high-level, the purpose of the meetings is to allow for focused and dedicated sessions to strategically develop a work plan for the upcoming year. This additional budget request was approved<https://www.icann.org/resources/board-material/resolutions-2017-04-19-en#1.b> by the ICANN Board on 19 April 2017. The GNSO Council Strategic Planning Session is scheduled to take place on January 29–31 2018 at the ICANN office in Los Angeles. Here the Council leadership will provide an update to the Council on preliminary planning steps undertaken to date, including review of a draft agenda. 3.1 Update (Heather Forrest & Donna Austin) 3.2 Council discussion 3.3 Next steps Item 4. Any Other Business (10 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: 1. The GNSO Chair shall be elected by a 60 percent vote of each house. 2. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a current or incoming member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. * All ballots will include the “none of the above” option. In the event that a 60 percent vote of each house selects the “none of the above” option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. * In the case of a tie for the most votes between the two candidates, or between a candidate and “none of above,” a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. * The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and “none of the above.” * In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and “none of the above.” * If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. 3. Each house shall select a Council Vice-Chair from within its respective house. 4. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 5. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 6. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair’s term, the Vice-Chairs will serve as Interim GNSO Co- Chairs to jointly oversee the new Chair election and conduct Council business until a successful election can be held. In the event that one or both Vice-Chairs’ terms ends concurrently with the term of the previous Chair, the procedures described in Section 2.2.1 below shall apply. 7. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: GNSO Council Voting Thresholds (ICANN Bylaws,<https://www.icann.org/resources/pages/governance/bylaws-en/#article11> Article 11, Section 3) (i) Except as otherwise specified in these Bylaws, Annex A, Annex A-1 or Annex A-2 hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: (i) Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. (ii) Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority (as defined in Section 11.3(i)(xix)). (iv) Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. (vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under (iv) or (v) above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. (vii) Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. (viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. (ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, (x) Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xi) Modification of Approved PDP Recommendation: Prior to Final Approval by the Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. (xii) Initiation of an Expedited Policy Development Process ("EPDP"): requires an affirmative vote of a GNSO Supermajority. (xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO Supermajority. (xiv) Approval of EPDP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xv) Approve an EPDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. (xvi) Initiation of a GNSO Guidance Process ("GGP"): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. (xvii) Rejection of Initiation of a GGP Requested by the Board: requires an affirmative vote of a GNSO Supermajority. (xviii) Approval of GGP Recommendations: requires an affirmative vote of a GNSO Supermajority. (xix) A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House. https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf 4.4 Absentee Voting 4.1.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. 1. Initiate a Policy Development Process (PDP); 2. Approve a PDP recommendation; 3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; 4. Fill a Council position open for election. 4.1.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting’s adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.1.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.1.4 Absentee balloting does not affect quorum requirements. Nathalie Peregrine Manager, Operations 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…> Nathalie Peregrine Manager, Operations 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

Community Travel Suport Consultation and Questionnaire
by Nathalie Peregrine Oct. 25, 2017

Oct. 25, 2017

Dear councilors, During the GNSO Council meeting on the 12 October 2017, Patrick Jones and Carlos Reyes, ICANN staff, presented to the Council the community travel support guidelines, and explained the need for community input. Attached to this email, on the last page, is the questionnaire mentioned during the call to be circulated to community members to gather input. The deadline at which to submit responses is the 17 November 2017. Thank you, Kind regards, Nathalie Nathalie Peregrine Manager, Operations 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 1

FW: [So-ac-sg-cleaders] DRAFT REPORT: Meeting Strategy: Incremental Changes for Community Review
by James M. Bladel Oct. 25, 2017

Oct. 25, 2017

Councilors – Apologies for the delay, and you may have already seen this information via your SG/C leadership. Let’s plan to discuss during our meeting in Abu Dhabi as an AOB. Thanks— J. From: <so-ac-sg-cleaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Friday, October 13, 2017 at 17:19 Subject: [So-ac-sg-cleaders] DRAFT REPORT: Meeting Strategy: Incremental Changes for Community Review Dear Community Leaders and Representatives: On 17 August 2017, ICANN.org hosted a call with community leaders and representatives to discuss questions about the criteria for ICANN Meeting venue selection, and potential updates to the current strategy for ICANN Public Meetings, which was approved by the ICANN Board in 2014 (See: https://community.icann.org/display/soaceinputfeedback/Event+Calendar. Community leaders and representatives on the call included: At-Large Advisory Committee (ALAC) and RALO Chairs, Commercial Stakeholder Group (CSG), Country Code Names Supporting Organization (ccNSO), Generic Names Supporting Organization (GNSO), Non-Commercial Stakeholder Group (NCSG), Registrar Stakeholder Group (RrSG), Registry Stakeholder Group (RySG), Root Server System Advisory Committee (RSSAC), and Security and Stability Advisory Committee (SSAC), and the Government Advisory Committee (GAC) . This document summarizes the discussion, and provides a detailed report of proposed incremental changes to the current meeting strategy<https://meetings.icann.org/en/mswgrecommendations-icannfuturemeetingsstrate…>, for the purposes of future consultation with the community. Fundamental changes to the meeting strategy were also discussed, however participants agreed to wait for a more comprehensive review of the current meeting strategy with the community to examine those issues and make informed recommendations for change. ICANN.org will present this paper to community leaders and representatives on 13 October 2017 and solicit feedback from the group at a meeting on 2 November 2017 at 0800 am in Capital Suite 3 at the ICANN60 Annual General Meeting in Abu Dhabi. Following that discussion, community leaders and representatives will determine next steps and whether the proposed incremental changes outlined in this document should go out for consultation with the ICANN community. ICANN.org will await further guidance and direction from the community before amending the current meeting strategy. Best regards and safe travel to those going to Abu Dhabi. Sally, Tanzanica, Nick and David David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

**Updated Highlights of the GNSO Council sessions - ICANN60
by Terri Agnew Oct. 24, 2017

Oct. 24, 2017

Dear all, As a reminder, GNSO Council highlight sessions are as follows: * Sunday, 29 October . 08:30 - 15:00 GNSO Working Session, room: Hall B, Sec. B/C (GNSO) / https://schedule.icann.org/event/CbId/gnso-working-session * Sunday, 29 October * 15:15-16:15 Joint Meeting GAC & GNSO, room: Hall 3 (GAC room) https://schedule.icann.org/event/CbI1/joint-meeting-gac-gnso * Sunday, 29 October 2017 * 19:30 Informal GNSO Council Dinner * Monday, October 30 . 12:15 - 13:30 ccNSO/ GNSO Joint Council meeting, room; Hall B, Sec. B/C (GNSO) / https://schedule.icann.org/event/CbIg/ccnsognso-joint-council-meeting * Tuesday, 31 October . 17:30 - 18:30 GNSO Informal Council Session (closed), room: Capital Suite 03 https://schedule.icann.org/event/CbFI/gnso-informal-council-session-c * Wednesday, 01 November . 13:00 - 15:00 GNSO Council Public Meeting, room: Hall B, Sec. B/C (GNSO) https://schedule.icann.org/event/CbIm/gnso-council-public-meeting * Wednesday, 01 November . 15:15 - 16:00 GNSO Council Open Meeting Part II (admin) room: Hall B, Sec. B/C (GNSO), https://schedule.icann.org/event/CbIn/gnso-council-open-meeting-part-ii-admi n-meeting * Thursday, 02 November . 12:15 - 13:15 GNSO Council Wrap-Up Session room: Hall B, Sec. B/C (GNSO) https://schedule.icann.org/event/CbIu/gnso-wrap-up-session Please remember to add these sessions to your schedules (go to https://schedule.icann.org/ create a profile and add the sessions you're interested in) in order to receive all the updates and/or changes, remote participation is available. Safe travels, With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org <mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy -efforts.htm#newcomers>

1 0

Highlights of the GNSO Council sessions - ICANN60
by Terri Agnew Oct. 24, 2017

Oct. 24, 2017

Dear all, As a reminder, GNSO Council highlight sessions are as follows: * Sunday, 29 October . 08:30 - 15:00 GNSO Working Session, room: Hall B, Sec. B/C (GNSO) / https://schedule.icann.org/event/CbId/gnso-working-session * Sunday, 29 October 2017 * 19:30 Informal GNSO Council Dinner * Tuesday, 31 October . 17:30 - 18:30 GNSO Informal Council Session (closed), room: Capital Suite 03 https://schedule.icann.org/event/CbFI/gnso-informal-council-session-c * Wednesday, 01 November . 13:00 - 15:00 GNSO Council Public Meeting, room: Hall B, Sec. B/C (GNSO) https://schedule.icann.org/event/CbIm/gnso-council-public-meeting * Wednesday, 01 November . 15:15 - 16:00 GNSO Council Open Meeting Part II (admin) room: Hall B, Sec. B/C (GNSO), https://schedule.icann.org/event/CbIn/gnso-council-open-meeting-part-ii-admi n-meeting * Thursday, 02 November . 12:15 - 13:15 GNSO Council Wrap-Up Session room: Hall B, Sec. B/C (GNSO) https://schedule.icann.org/event/CbIu/gnso-wrap-up-session Please remember to add these sessions to your schedules (go to https://schedule.icann.org/ create a profile and add the sessions you're interested in) in order to receive all the updates and/or changes, remote participation is available. Kind regards, With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org <mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy -efforts.htm#newcomers>

1 0

Topic for Discussion at Abu Dhabi
by Michele Neylon - Blacknight Oct. 24, 2017

Oct. 24, 2017

All Apologies if I'm a bit late with this. One of the items that we should discuss if time permits while we are at Abu Dhabi is the whois conflicts with local law, specifically around the triggers. This topic has come up for discussion several times in the past (mild understatement!) and in light of other discussions I believe it is timely for us to look at this again. Bear in mind, however, that this policy and the triggers we are talking about is quite narrow in its focus and remit. They are merely a method to start a discussion between the contracted party and ICANN in order to resolve a conflict. 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

1 0

FW: [So-ac-sg-cleaders] An ICANN Message on the Information Transparency Initiative -Info Session on: Thursday 2 November, 1330-1400 in Hall 3.
by James M. Bladel Oct. 23, 2017

Oct. 23, 2017

Colleagues – Please see below for an announcement & session invitation from David Olive on behalf of the ICANN ITI team. Thank you, J. ------------------ James Bladel GNSO Chair From: <so-ac-sg-cleaders-bounces(a)icann.org> on behalf of David Olive <david.olive(a)icann.org> Date: Sunday, October 22, 2017 at 15:00 Subject: [So-ac-sg-cleaders] An ICANN Message on the Information Transparency Initiative -Info Session on: Thursday 2 November, 1330-1400 in Hall 3. Dear Community Leaders: As you know, the Board recently approved the Information Transparency Initiative (ITI), which is a two-year project to rebuild the technical infrastructure of the way we manage ICANN’s information and content with a first-ever for ICANN dedicated document management system (DMS) to manage our information and a new content management system (CMS) to make that information available. We’ll use this new technical infrastructure to enforce governance of our content through consistent workflows and tagging, making use of a taxonomy we’re developing for the first time. One of the primary reasons we’re doing this is to help our stakeholders find the content they are looking for (which we know is a challenge on the current site), and to help us meet our accountability and transparency obligations. While our project goals are narrow (improving findability in all U.N. six languages, enforcing content governance, and rebuilding infrastructure), think of this work as foundational that will set the stage for the entire ICANN information ecosystem. To try to bring benefits to the community as soon as possible, the community-observable part of the project starts first with icann.org<http://icann.org/>, meetings.icann.org<http://meetings.icann.org/>, and 13 other external websites. Once this work is complete, this foundational technical infrastructure and system-wide governance and taxonomy, will serve our SO/AC and remaining sites. If you have time in your ICANN60 schedules, we encourage you to participate in the Information Transparency Initiative session on: Thursday 2 November, 1330-1400 in Hall 3. This session is intended to give our stakeholders an overview of the project, but it will primarily be focused on listening to stakeholder feedback and answering questions. We need your feedback to get this right, but we know you may not have time to attend this ICANN60 session. Because of this, we’re looking to schedule individual telephone interviews with you after ICANN60. These interviews are intended to gather some initial thoughts, feedback, current pain points with the site, and ideally, what you think would help make the icann.org<http://icann.org/> experience and ICANN’s content governance processes better. We’ll send out emails after ICANN60 to arrange a time that best works for your schedules. We look forward to these initial conversations, and your ongoing support and input throughout this project, which is so crucial to the project successfully meeting its goals. Best regards, ICANN’s ITI Team David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

REMINDER Re: Your input requested - topics and owners for joint sessions at ICANN60
by Marika Konings Oct. 23, 2017

Oct. 23, 2017

Reminder – please review the different wiki pages and volunteer for any topics that you would like to introduce. Note that some updates have been made to the proposed agenda for the meeting with the ccNSO and GAC based on feedback from those groups. Thanks, Marika From: <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, October 16, 2017 at 07:24 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Your input requested - topics and owners for joint sessions at ICANN60 Dear All, As discussed during last week’s Council meeting, staff has gone ahead and created wiki pages for each of the joint sessions at ICANN60 (with ccNSO, GAC and ICANN Board). You are requested to review these pages, identify whether there are any topics that need to be added and/or edited, and identify for which topics you would like to serve as a topic owner. As a topic owner, you are requested to provide a number of proposed speaking points that will allow others to review and contribute to. You can find the wiki pages here: Joint meeting with the ccNSO: https://community.icann.org/x/DCMhB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Joint meeting with the GAC: https://community.icann.org/x/-JNEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Joint meeting with the ICANN Board: https://community.icann.org/x/BZREB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you for your collaboration. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

FYI: ICANN Announcement Call for Volunteers for WT 5
by Nathalie Peregrine Oct. 23, 2017

Oct. 23, 2017

https://www.icann.org/news/announcement-2017-10-22-en. Call for Volunteers: GNSO New gTLD Subsequent Procedures PDP WG Work Track 5 (Geographic Names at the top-level) In Brief The New gTLD Subsequent Procedures Policy Development Process Working Group seeks volunteers to serve on a new sub team, known as Work Track 5, which will focus exclusively on the treatment of geographic names at the top level. This issue is one of the topics in the WG's charter<https://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-charter-21…> [PDF, 196 KB]. What This Team Will Do Work Track 5 will focus on developing proposed recommendations regarding the treatment of geographic names at the top-level. The Work Track may make recommendations on policy and/or implementation related to 2-letter codes, 3-letter codes, short form and full country and territory names, city/state/region names, and other geographically significant names. How This Team Will Work ICANN WGs use transparent, open processes. The meetings of this Work Track will be recorded, transcribed, and the recordings will be made available to the public. The mailing list for the Work Track will be archived publicly. The group will collaborate using a public workspace for draft materials and all final work products and milestones will be documented on the WG's wiki<https://community.icann.org/display/NGSPP/New+gTLD+Subsequent+Procedures+PD…>. In addition to a Terms of Reference, the Work Track will be governed under the GNSO Working Group Guidelines<https://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf> [PDF, 349 KB] as well as the GNSO PDP Manual<https://gnso.icann.org/en/council/annex-2-pdp-manual-24jun15-en.pdf> [PDF, 260 KB]. The Work Track will be structured to encourage broad and balanced participation from different parts of the community, and includes joint community Work Track leadership from ALAC, GAC, ccNSO and GNSO. As with the other Work Tracks, WT5 leadership will be coordinated by the PDP WG co-chairs. How to Participate There are two ways to volunteer: · Members – anyone interested can volunteer to join the Work Track as a member, regardless of whether they are members of the ICANN community. Members are expected to actively contribute to mailing list conversations as well as meetings – it is anticipated that the Work Track will meet on a weekly basis via teleconference. Members are expected to provide essential input to the process, orally or through written input. Members will be required to provide a Statement of Interests (SOI<https://community.icann.org/display/gnsosoi/New+SOIs>). · Mailing list observers – for those who are merely interested in monitoring the Work Track's conversations, there is the possibility to sign up as a mailing list "observer" which offers read-only access to the mailing list. Mailing list observers will not be permitted to post, will not receive invitations to the various meetings or calls of the Work Track and will not have to complete a Statement of Interest. At any point in time, a mailing list observer can join the Work Track as a member simply by informing the GNSO Secretariat. In addition, there may be opportunities to provide input through public consultations and public comment processes. Note, joining Work Track 5 as a member or mailing list observer does not require joining or participating in the full Working Group, though it is encouraged. How to Join If you are interested in joining Work Track 5 as a member or mailing list observer, please fill in the sign up form<https://goo.gl/forms/Pgl7NMbocc1Qz7pq1>. If you are having trouble using the sign-up form, please email gnso-secs(a)icann.org<matilto:gnso-secs@icann.org> for assistance. All members and observers will be listed on the PDP WG's wiki page. Next Steps The call for volunteers will be circulated as widely as possible in order to ensure broad representation and participation in Work Track 5. This initial call will remain open until 20 November. Volunteers are also welcome to join the Work Track at any time after 20 November. Members who join the Work Track after work has begun will be responsible for reviewing all Work Track deliberations, agreements, and documents so that they are prepared to participate fully. Regular online meetings will be scheduled in accordance with the Work Track's work plan, which it is expected to develop as one of its first tasks. Drafting of WT5 Terms of Reference is currently underway with the WT leadership and will be finalized in the near future. Background In 2005, the Generic Names Supporting Organization (GNSO) began a Policy Development Process (PDP) to consider the introduction of new gTLDs. The two-year PDP process resulted in a set of 19 GNSO policy recommendations for implementing new gTLDs. In order to implement the policy recommendations of the GNSO, a number of draft Applicant Guidebooks (AGBs) were developed by ICANN staff in consultation with the community. In June 2011, ICANN's Board of Directors approved the final AGB and authorized the launch of the New gTLD Program. The New gTLD Program application window opened on 12 January 2012 and a total of 1930 complete applications were received. The first set of Initial Evaluation results were released on 22 March 2013, followed by the first set of new gTLD delegations on 21 October 2013. All applications have now completed the evaluation process and as of mid October 2017, there are over 1,200 gTLDs delegated. Although the 2012 round is ongoing, efforts to examine the round have already begun, which included the initiation of the GNSO’s PDP on New gTLD Subsequent Procedures in early 2016. Although the original charter<https://gnso.icann.org/en/issues/new-gtlds/subsequent-procedures-charter-21…> [PDF, 196 KB] approved by the GNSO Council put the topic of geographic names at the top level in Work Track 2 dealing with legal and regulatory issues, the full PDP Working Group approved the creation of this new Work Track 5 to focus exclusively on the treatment of geographic names at the top level.

1 0