October 2021 - council - lists.icann.org

Motion for Approval of the Revised GNSO Councilor Job Description for the Nominating Committee_17Oct2021.docx
by Pam Little 17 Oct '21

17 Oct '21

Dear Councilors, Please find attached a motion for the approval of the revised GNSO Councilor Job Description for the Nominating Committee to be considered at the GNSO Council meeting on Wednesday, 27 October 2021 at 19:30 UTC. Respectfully submitted, Pam Little

3 2

GNSO Council Portfolio Management Tool Suite - 27 Oct 2021 Meeting
by Berry Cobb 17 Oct '21

17 Oct '21

Dear all, Please find attached links to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 27 October 2021. Agenda: * https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen… Links to the Program Suite: * Program/Project Management Framework (PPMF): https://community.icann.org/x/0YvzC * Portfolio Management Tool (PMT): https://community.icann.org/x/04vzC * Action/Decision Radar (ADR): https://community.icann.org/x/14vzC * Project List (PL): https://community.icann.org/x/1YvzC * Action Items (AIs): https://community.icann.org/x/RgZlAg * Council Small Teams (CSTs): https://community.icann.org/x/kwANCQ Key Program Suite Structural Changes for this Period: * None for this period. Key Project Changes for this Period: * Close of Public Comment on EPDP-SCRP-IGO on 24 Oct 2021 * EPDP-P2A – Motion on Final Report recommendations * Selection of GNSO Council’s Liaison for SubPro ODP * Confirmation of the GNSO Council’s Liaison to the GAC * Confirmation of EPDP-IDN Project Plan * RPM-P2 Policy Status Report * Initial meetings of Registration Data Accuracy Scoping team Key Project/Operations Activities for Nov. 2021: * Refresh roster membership of SCBO; select a Vice-Chair * Refresh roster membership of the SSC * Council produce a response to GAC Advice, as applicable * Council to determine vehicle of implementation of WS2 recommendations within scope of the GNSO Council Please let me know if you have any questions. Thank you. B Berry Cobb Policy Development - Portfolio Manager Internet Corporation for Assigned Names and Numbers (ICANN) berry.cobb(a)icann.org

1 0

Motion - GNSO liaison to the GAC
by philippe.fouquart＠orange.com 17 Oct '21

17 Oct '21

Dear Councilors, Please find attached the motion I submit for the reappointment of our GNSO liaison to the GAC. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

FOR DISCUSSION: Document for Agenda Item #6 GDS Update on the Framework for the Policy Status Report Framework on the UDRPs
by Julie Hedlund 17 Oct '21

17 Oct '21

Dear GNSO Councilors, Pursuant to the Proposed GNSO Council meeting agenda below, please see the attached document for discussion relating to the following agenda item: Item 6: COUNCIL DISCUSSION - GDS Update on the Framework for the Policy Status Report Framework on the UDRP (20 minutes) Kind regards, Julie Julie Hedlund, Policy Director From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine via council <council(a)gnso.icann.org> Reply-To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Sunday, October 17, 2021 at 2:59 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Proposed Agenda GNSO Council Meeting part 1 (Public) and part 2 (Admin) - 27 October 2021 at 19:30 UTC Dear all, Please find below the final proposed agenda for the GNSO Council Meeting part 1 and part 2 on 27 October 2021 at 19:30 UTC. Draft GNSO Council Agenda 27 October 2021 - 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/_ABmCg This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5, updated on 24 October 2019 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. GNSO Council meeting held 12:30 PDT (Seattle, WA) Coordinated Universal Time: 19:30 UTC: https://tinyurl.com/h73u9hxs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/h73u9hxs__;!!PtGJab4!uQISZab…> 12:30 Los Angeles; 15:30 Washington DC; 20:30 London; 21:30 Paris; 22:30 Moscow; (Thursday) 06:30 Melbourne GNSO Council Meeting Remote Participation: https://72.schedule.icann.org/meetings/iRtcZAfitd6mpyyyW [72.schedule.icann.org]<https://urldefense.com/v3/__https:/72.schedule.icann.org/meetings/iRtcZAfit…> 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 (10 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 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council meeting on 19 August 2021 were posted on 04 September 2021 Minutes [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> of the GNSO Council meeting on 23 September 2021 were posted on 08 October 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/project__;!!Pt…>and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (5 minutes) * 3.1 - Approval<https://community.icann.org/x/_gBmCg> of the GNSO Council liaison to the New gTLD Subsequent Procedures Operational Design Phase - Jeff Neuman (SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI>) * 3.2 - Approval<https://community.icann.org/x/_gBmCg> of the GNSO liaison to the Governmental Advisory Committee - Jeff Neuman (SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI>) Item 4: COUNCIL VOTE - EPDP Phase 2A Final Report (30 minutes) On 21 October 2020, the GNSO Council approved the initiation [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…>of EPDP Phase 2A, to examine the topics of legal/natural and feasibility of unique contacts. In doing so, the Council required that the GNSO Council Liaison to the EPDP report back to the GNSO Council on the status of deliberations. Accordingly, status updates were regularly provided to the GNSO Council over the course of the EPDP Phase 2A’s deliberations. The EPDP Team published its Initial Report for public comment<https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06-…> on 3 June 2021, which included preliminary recommendations as well as questions for community input. The EPDP Team delivered its Phase 2A Final Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/issues/epdp-phase-2a-u…> to the GNSO Council on 3 September 2021, which was updated on 13 September 2021 with the minority statements incorporated into the Final Report The GNSO Council received a presentation on the Final Report, which also included a draft motion circulated to the GNSO Council on 13 September 2021 for discussion purposes. During the 23 September 2021 Council meeting, Kurt Pritz, Council member from the Registries Stakeholder Group (RySG) requested that the Council first examine the request in the RySG’s minority statement that relates to Recommendation 1 of the Phase 2A Final Report which seeks the GNSO Council’s determination of whether the proposal contained in Recommendation 1, the creation of a mandatory data element, is out of scope with the GNSO Council’s instructions to the EPDP phase 2A team. As an action item from the September Council meeting, the Council leadership considered the scope issue raised and concluded that it concurs with the assessment by the EPDP Phase 2A Chair that Recommendation 1 is in scope and communicated the same to the GNSO Council on 30 September 2021 (see Council leadership’s full response here https://mm.icann.org/pipermail/council/2021-September/025035.html). Here, the GNSO Council will vote to adopt the EPDP Phase 2A Final Report. 4.1 - Presentation of motion<https://community.icann.org/x/_gBmCg> (GNSO Council vice-chair, Pam Little) 4.2 – Council discussion 4.3 – Council vote (voting threshold: supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1: GNSO Expedited Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL VOTE - Revised GNSO Councilor Job Description for the Nominating Committee (20 minutes) The GNSO Council is invited on an annual basis to review the job description and criteria contained in order to better assure that the Nominating Committee selects appointees that match the Council’s expectations. The Council has made incremental revisions to the job description each time that it has been invited to do so. This cycle, the Council is considering revising the job description to reflect a preference for appointees that are not currently affiliated with any Stakeholder Group or Constituency, recognizing that this may not always be feasible. Some concerns were expressed about the proposed revisions on the Council’s email list to which the Council leadership has responded with some clarifications (see https://mm.icann.org/pipermail/council/2021-September/025013.html). Here, the GNSO Council will vote to approve the revised job description [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>. 5.1 - Presentation of motion<https://community.icann.org/x/_gBmCg> (GNSO Council vice-chair, Pam Little) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL DISCUSSION - GDS Update on the Framework for the Policy Status Report Framework on the UDRP (20 minutes) On 21 January 2021, the GNSO Council approved the recommendations from the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs, covering RPMs applicable to gTLDs launched under the 2012 New gTLD Program. The Council has discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP, which is focused on the UDRP. Council leadership had considered the best path forward to initiating this work and shared their thoughts [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> for advancing this effort on 13 July 2021, which considers a Policy Status Report (PSR) as a possible next step. The Council discussed the approach during its July meeting and agreed that ICANN org should consider how to conduct the PSR and return to the Council to present their proposed framework for the PSR, in advance of initiating the actual work. ICANN org provided a presentation on the proposed framework for the PSR during the Council’s September meeting. Some concerns were expressed during the meeting and on the email list after the meeting. ICANN Org has taken into account the input and concerns received and will seek to respond to them, in advance of initiating the PSR. Here, the Council will receive a follow-up presentation, to help clarify the scope and purpose of the PSR as well as to address certain concerns raised. 6.1 – Introduction of topic (Council leadership) 6.2 – Presentation (Antonietta Mangiocotti - ICANN org) 6.3 – Council discussion 6.4 – Next steps Item 7: ANY OTHER BUSINESS (25 minutes) 7.1 - Seek vice-chair for Standing Committee on ICANN Budget & Operating Plan, to prepare for a chair succession plan for the FY24 cycle. 7.1 - Acknowledgment of the Project Plan for the EPDP on Internationalized Domain Names. 7.3 - Suggestion to assign a Council liaison to Accuracy Scoping Team 7.4 - Farewell and thanks to outgoing Councilors: Carlton Samuels, Osvaldo Novoa, Pam Little, Tatiana Tropina, Tom Dale 7.5- 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/sites/default/files/file/field-file-attach/op-proced… [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> References for Coordinated Universal Time of 19:30 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 12:30 San José, Costa Rica (CST) UTC-6 13:30 New York/Washington DC, USA (EDT) UTC-4 15:30 Buenos Aires, Argentina (ART) UTC-3 16:30 Rio de Janeiro, Brazil (BRST) UTC-3 16:30 London, United Kingdom (GMT) UTC+1 20:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:30 Paris, France (CEST) UTC+2 21:30 Moscow, Russia (MST) UTC+3 22:30 Singapore (SGT)(+1day) UTC+8 03:30 Melbourne, Australia (AEDT)(+1day) UTC+11 06:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 31 October 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 7 November 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com [timeanddate.com]<https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!uQISZabI…> and https://tinyurl.com/jw684set [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/jw684set__;!!PtGJab4!uQISZab…> Draft GNSO Council Agenda 27 October 2021 - Part II (Admin) 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/_ABmCg This agenda was established according to the GNSO Operating Procedures [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> v3.5 updated on 24 October 2019 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. GNSO Council meeting held 12:30 PDT (Seattle, WA) Coordinated Universal Time: 19:30 UTC: https://tinyurl.com/h73u9hxs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/h73u9hxs__;!!PtGJab4!uQISZab…> 12:30 Los Angeles; 15:30 Washington DC; 20:30 London; 21:30 Paris; 22:30 Moscow; (Thursday) 06:30 Melbourne GNSO Council Meeting Remote Participation: (link) 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 2021 / 2022 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest INCOMING COUNCILORS: Antonia Chu: SOI<https://community.icann.org/x/DYUzBw> Registrars Stakeholder Group (RrSG) Desiree Miloshevic Evans: SOI<https://community.icann.org/x/zAJyCg> Contracted Party House NomCom Appointee-Voting Greg DiBiase: SOI<https://community.icann.org/x/uCEnAw> Registrars Stakeholder Group (RrSG) Manju Chen: SOI<https://community.icann.org/x/cIImCQ> Non-Commercial Stakeholder Group (NCSG) Paul McGrady: SOI<https://community.icann.org/x/cTCfAg> Non-Contracted Party House NomCom Appointee-Voting Thomas Rickert: SOI<https://community.icann.org/x/2YTDAQ> Internet Service Providers and Connectivity Providers (ISPCP) Thank you again to outgoing Councilors: Carlton Samuels, Osvaldo Novoa, Pam Little, Tatiana Tropina, Tom Dale. 1.3 - Review / Amend Agenda Item 2. Election of the Chair (20 mins) One nomination was received for this position from Philippe Fouquart of the Non Contracted Party House. Philippe circulated his candidate statement [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/elections/fouquart-sta…> to the GNSO Council on 9 October 2021. Here the GNSO Council will proceed to hold the election for its Chair for 2021-2022, 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. Election of GNSO Council Vice Chair 2021-2022 Non-Contracted Party House - Tomslin Samme-Nlar Contracted Party House - Sebastien Ducos Item 4. Any Other Business (0 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2) 2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/op-procedures-…> 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. a. 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. b. 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. c. 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.” d. 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.” e. 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. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. 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. 5. 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 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/op-procedures-…> Appendix 1 GNSO Council Voting Results table Absentee Voting Procedures https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/op-procedures-…> 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.

1 0

Proposed Agenda GNSO Council Meeting part 1 (Public) and part 2 (Admin) - 27 October 2021 at 19:30 UTC
by Nathalie Peregrine 17 Oct '21

17 Oct '21

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting part 1 and part 2 on 27 October 2021 at 19:30 UTC. Draft GNSO Council Agenda 27 October 2021 - 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/_ABmCg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5, updated on 24 October 2019 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. GNSO Council meeting held 12:30 PDT (Seattle, WA) Coordinated Universal Time: 19:30 UTC: https://tinyurl.com/h73u9hxs 12:30 Los Angeles; 15:30 Washington DC; 20:30 London; 21:30 Paris; 22:30 Moscow; (Thursday) 06:30 Melbourne GNSO Council Meeting Remote Participation: https://72.schedule.icann.org/meetings/iRtcZAfitd6mpyyyW 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 (10 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/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 19 August 2021 were posted on 04 September 2021 Minutes<https://gnso.icann.org/sites/default/files/policy/2021/minutes/minutes-gnso…> of the GNSO Council meeting on 23 September 2021 were posted on 08 October 2021. Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 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 minutes) * 3.1 - Approval<https://community.icann.org/x/_gBmCg> of the GNSO Council liaison to the New gTLD Subsequent Procedures Operational Design Phase - Jeff Neuman (SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI>) * 3.2 - Approval<https://community.icann.org/x/_gBmCg> of the GNSO liaison to the Governmental Advisory Committee - Jeff Neuman (SOI<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI>) Item 4: COUNCIL VOTE - EPDP Phase 2A Final Report (30 minutes) On 21 October 2020, the GNSO Council approved the initiation <https://gnso.icann.org/en/council/resolutions/2020-current#20201021> of EPDP Phase 2A, to examine the topics of legal/natural and feasibility of unique contacts. In doing so, the Council required that the GNSO Council Liaison to the EPDP report back to the GNSO Council on the status of deliberations. Accordingly, status updates were regularly provided to the GNSO Council over the course of the EPDP Phase 2A’s deliberations. The EPDP Team published its Initial Report for public comment<https://www.icann.org/public-comments/epdp-phase-2a-initial-report-2021-06-…> on 3 June 2021, which included preliminary recommendations as well as questions for community input. The EPDP Team delivered its Phase 2A Final Report<https://gnso.icann.org/en/issues/epdp-phase-2a-updated-final-report-13sep21…> to the GNSO Council on 3 September 2021, which was updated on 13 September 2021 with the minority statements incorporated into the Final Report The GNSO Council received a presentation on the Final Report, which also included a draft motion circulated to the GNSO Council on 13 September 2021 for discussion purposes. During the 23 September 2021 Council meeting, Kurt Pritz, Council member from the Registries Stakeholder Group (RySG) requested that the Council first examine the request in the RySG’s minority statement that relates to Recommendation 1 of the Phase 2A Final Report which seeks the GNSO Council’s determination of whether the proposal contained in Recommendation 1, the creation of a mandatory data element, is out of scope with the GNSO Council’s instructions to the EPDP phase 2A team. As an action item from the September Council meeting, the Council leadership considered the scope issue raised and concluded that it concurs with the assessment by the EPDP Phase 2A Chair that Recommendation 1 is in scope and communicated the same to the GNSO Council on 30 September 2021 (see Council leadership’s full response here https://mm.icann.org/pipermail/council/2021-September/025035.html). Here, the GNSO Council will vote to adopt the EPDP Phase 2A Final Report. 4.1 - Presentation of motion<https://community.icann.org/x/_gBmCg> (GNSO Council vice-chair, Pam Little) 4.2 – Council discussion 4.3 – Council vote (voting threshold: supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1: GNSO Expedited Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL VOTE - Revised GNSO Councilor Job Description for the Nominating Committee (20 minutes) The GNSO Council is invited on an annual basis to review the job description and criteria contained in order to better assure that the Nominating Committee selects appointees that match the Council’s expectations. The Council has made incremental revisions to the job description each time that it has been invited to do so. This cycle, the Council is considering revising the job description to reflect a preference for appointees that are not currently affiliated with any Stakeholder Group or Constituency, recognizing that this may not always be feasible. Some concerns were expressed about the proposed revisions on the Council’s email list to which the Council leadership has responded with some clarifications (see https://mm.icann.org/pipermail/council/2021-September/025013.html). Here, the GNSO Council will vote to approve the revised job description<https://gnso.icann.org/sites/default/files/file/field-file-attach/nomcom-po…>. 5.1 - Presentation of motion<https://community.icann.org/x/_gBmCg> (GNSO Council vice-chair, Pam Little) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL DISCUSSION - GDS Update on the Framework for the Policy Status Report Framework on the UDRP (20 minutes) On 21 January 2021, the GNSO Council approved the recommendations from the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs, covering RPMs applicable to gTLDs launched under the 2012 New gTLD Program. The Council has discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP, which is focused on the UDRP. Council leadership had considered the best path forward to initiating this work and shared their thoughts<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpms-pdp-…> for advancing this effort on 13 July 2021, which considers a Policy Status Report (PSR) as a possible next step. The Council discussed the approach during its July meeting and agreed that ICANN org should consider how to conduct the PSR and return to the Council to present their proposed framework for the PSR, in advance of initiating the actual work. ICANN org provided a presentation on the proposed framework for the PSR during the Council’s September meeting. Some concerns were expressed during the meeting and on the email list after the meeting. ICANN Org has taken into account the input and concerns received and will seek to respond to them, in advance of initiating the PSR. Here, the Council will receive a follow-up presentation, to help clarify the scope and purpose of the PSR as well as to address certain concerns raised. 6.1 – Introduction of topic (Council leadership) 6.2 – Presentation (Antonietta Mangiocotti - ICANN org) 6.3 – Council discussion 6.4 – Next steps Item 7: ANY OTHER BUSINESS (25 minutes) 7.1 - Seek vice-chair for Standing Committee on ICANN Budget & Operating Plan, to prepare for a chair succession plan for the FY24 cycle. 7.1 - Acknowledgment of the Project Plan for the EPDP on Internationalized Domain Names. 7.3 - Suggestion to assign a Council liaison to Accuracy Scoping Team 7.4 - Farewell and thanks to outgoing Councilors: Carlton Samuels, Osvaldo Novoa, Pam Little, Tatiana Tropina, Tom Dale 7.5- 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/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 19:30 UTC Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 12:30 San José, Costa Rica (CST) UTC-6 13:30 New York/Washington DC, USA (EDT) UTC-4 15:30 Buenos Aires, Argentina (ART) UTC-3 16:30 Rio de Janeiro, Brazil (BRST) UTC-3 16:30 London, United Kingdom (GMT) UTC+1 20:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:30 Paris, France (CEST) UTC+2 21:30 Moscow, Russia (MST) UTC+3 22:30 Singapore (SGT)(+1day) UTC+8 03:30 Melbourne, Australia (AEDT)(+1day) UTC+11 06:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 31 October 2021, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 7 November 2021 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/jw684set Draft GNSO Council Agenda 27 October 2021 - Part II (Admin) 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/_ABmCg This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced…> v3.5 updated on 24 October 2019 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. GNSO Council meeting held 12:30 PDT (Seattle, WA) Coordinated Universal Time: 19:30 UTC: https://tinyurl.com/h73u9hxs 12:30 Los Angeles; 15:30 Washington DC; 20:30 London; 21:30 Paris; 22:30 Moscow; (Thursday) 06:30 Melbourne GNSO Council Meeting Remote Participation: (link) 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 2021 / 2022 Council (20 mins) 1.1 - Roll Call 1.2 - Statements of Interest INCOMING COUNCILORS: Antonia Chu: SOI<https://community.icann.org/x/DYUzBw> Registrars Stakeholder Group (RrSG) Desiree Miloshevic Evans: SOI<https://community.icann.org/x/zAJyCg> Contracted Party House NomCom Appointee-Voting Greg DiBiase: SOI<https://community.icann.org/x/uCEnAw> Registrars Stakeholder Group (RrSG) Manju Chen: SOI<https://community.icann.org/x/cIImCQ> Non-Commercial Stakeholder Group (NCSG) Paul McGrady: SOI<https://community.icann.org/x/cTCfAg> Non-Contracted Party House NomCom Appointee-Voting Thomas Rickert: SOI<https://community.icann.org/x/2YTDAQ> Internet Service Providers and Connectivity Providers (ISPCP) Thank you again to outgoing Councilors: Carlton Samuels, Osvaldo Novoa, Pam Little, Tatiana Tropina, Tom Dale. 1.3 - Review / Amend Agenda Item 2. Election of the Chair (20 mins) One nomination was received for this position from Philippe Fouquart of the Non Contracted Party House. Philippe circulated his candidate statement<https://gnso.icann.org/en/elections/fouquart-statement-09oct21-en.pdf> to the GNSO Council on 9 October 2021. Here the GNSO Council will proceed to hold the election for its Chair for 2021-2022, 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. Election of GNSO Council Vice Chair 2021-2022 Non-Contracted Party House - Tomslin Samme-Nlar Contracted Party House - Sebastien Ducos Item 4. Any Other Business (0 min) None Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.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. a. 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. b. 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. c. 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.” d. 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.” e. 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. 1. Each house shall select a Council Vice-Chair from within its respective house. 2. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. 3. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). 4. 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. 5. 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.

1 0

Deadline today: Document and Motion deadline Sunday, 17 October 2021 at 23:59 UTC for GNSO Council Meeting 27 October 2021 at 19:30 UTC
by Nathalie Peregrine 17 Oct '21

17 Oct '21

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 17 October 2021 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 27 October 2021 at 19:30 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/_gBmCg Thank you. Nathalie

1 0

GNSO Liaison to GAC 2021 Annual Report
by Jeff Neuman 16 Oct '21

16 Oct '21

All, Please find enclosed my 2021 GNSO Liaison to the GAC Annual Report. I do not believe this is, or needs to be, an agenda item for the next Council meeting, but it is a document that is required to be submitted at this meeting. I am happy to answer any questions that you may have on this report. Thanks for allowing me to serve this past year as the GNSO Liaison to the GAC. Sincerely, Jeff Neuman [cid:image001.png@01D7C2B3.814C6140] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com

1 0

FW: [CORRESPONDENCE] Maarten Botterman to Alejandra Reynoso and Philippe Fouquart RE: Customer Standing Committee Review
by philippe.fouquart＠orange.com 15 Oct '21

15 Oct '21

Dear Councilors, Please note the attached. Regards, Philippe -------- Message d'origine -------- De : Wendy Profit <wendy.profit(a)icann.org> Date : 15/10/2021 02:43 (GMT+01:00) À : alejandra.reynoso(a)cctld.gt, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc : Goran Marby <goran.marby(a)icann.org>, Secretary <secretary(a)icann.org>, Correspondence <Correspondence(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org>, gnso-secs(a)icann.org, Jennifer Bryce <jennifer.bryce(a)icann.org>, Maarten Botterman <maarten.botterman(a)board.icann.org>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, ccnsosecretariat(a)icann.org, liman(a)netnod.se Objet : [CORRESPONDENCE] Maarten Botterman to Alejandra Reynoso and Philippe Fouquart RE: Customer Standing Committee Review ….with attachment. 😊 From: Board-Ops-Team <board-ops-team-bounces(a)icann.org> on behalf of ICANN Board Ops <board-ops-team(a)icann.org> Reply-To: Wendy Profit <wendy.profit(a)icann.org> Date: Thursday, October 14, 2021 at 8:27 PM To: "alejandra.reynoso(a)cctld.gt" <alejandra.reynoso(a)cctld.gt>, "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Cc: Goran Marby <goran.marby(a)icann.org>, Secretary <secretary(a)icann.org>, Correspondence <Correspondence(a)icann.org>, ICANN Board Ops <board-ops-team(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Jennifer Bryce <jennifer.bryce(a)icann.org>, Maarten Botterman <maarten.botterman(a)board.icann.org>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, "ccnsosecretariat(a)icann.org" <ccnsosecretariat(a)icann.org>, "liman(a)netnod.se" <liman(a)netnod.se> Subject: [Board-Ops-Team] [CORRESPONDENCE] Maarten Botterman to Alejandra Reynoso and Philippe Fouquart RE: Customer Standing Committee Review Dear Alejandra Reynoso and Philippe Fouquart, Please find the attached letter from ICANN Chair Maarten Botterman in response to your letter of 30 September<https://www.icann.org/en/system/files/correspondence/reynoso-fouquart-to-bo…> regarding the Customer Standing Committee (CSC) Review. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Begin forwarded message: From: Alejandra Reynoso <alejandra.reynoso(a)cctld.gt> Date: 30 September 2021 at 20:57:34 CEST To: Maarten Botterman <maarten.botterman(a)board.icann.org>, Göran Marby <goran.marby(a)icann.org>, Lars-Johan Liman <liman(a)netnod.se> Cc: ccNSO Secretariat <ccnsosecretariat(a)icann.org>, Philippe Fouquart <philippe.fouquart(a)orange.com>, "Demetriou, Samantha" <sdemetriou(a)verisign.com>, gnso-secs(a)icann.org Subject: Customer Standing Committee Review Dear Maarten, Göran and Lars-Johan According to Section 17.3 (b) of the ICANN Bylaws, the effectiveness of the Customer Standing Committee shall be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of the review needs to be determined by the ccNSO and GNSO, and the findings of the review must be published on the Website. On behalf of the ccNSO and GNSO Councils, we are pleased to inform you that the ccNSO and GNSO have determined the method of the Effectiveness Review by adopting the TEMPLATE Second CSC EFFECTIVENESS REVIEW, as included. The ccNSO Council passed the resolution online; it became effective on 26 August 2021 and the GNSO Council passed the relevant resolution on 19 August 2021. In addition, both Councils each appointed the following two members to the Review Team ccNSO: Jens Petur Jensen and Maarten Simon GNSO: Donna Austin and Jonathan Robinson If you have any questions, please do not hesitate to contact us. Best regards, Alejandra Reynoso, Chair, ccNSO Council and Philippe Fouquart, Chair, GNSO -- [Image removed by sender. Photograph] Alejandra Reynoso Investigación & Desarrollo | Dominios .gt P: +502 23688565 E: alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt> 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt [gt]<https://urldefense.com/v3/__http:/www.gt/__;!!PtGJab4!qxSVnM_WnLoFQhWMfF_Zb…> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

For those who missed the Prep Week GNSO Policy Briefing and the Policy Update webinars!
by Nathalie Peregrine 14 Oct '21

14 Oct '21

Dear all, For those of you who couldn’t make the Prep Week GNSO Policy Briefing and the Policy Update webinars, please find the Zoom recordings below: * GNSO Policy Briefing recording: https://icann.zoom.us/rec/share/kgZJI38pUgPKkarmfX622k_Yc9Qoopqg0BRYGzL4YcK… * Policy Update: https://icann.zoom.us/rec/share/2ClWGzd5FhwHq3oVDjh1E8Z0jwvUXbf33wVmaw-8Gd2… As a reminder, ICANN72 Prep week is happening right now, with ICANN72 beginning on Monday 25th October 2021, with sessions being held in Seattle local time. To access Prep Week and ICANN72 sessions, you will need to be registered to the meeting website<https://72.schedule.icann.org/>. Information about sessions where councilor attendance is highly encouraged was circulated<https://mm.icann.org/pipermail/council/2021-October/025058.html> earlier this month. Happy viewing! Kind regards, Nathalie

1 0

Fw: [Ext] Thursday, 14 October 2021 | REMINDER: Register for ICANN72!
by Michelle DeSmyter 14 Oct '21

14 Oct '21

FYI...... [https://r20.rs6.net/on.jsp?ca=f7439980-8c96-48b7-be1d-bd94201ba985&a=112202…] Thursday, 14 October 2021 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Table of Contents ICANN72 Resources * ICANN72 Policy Outlook Report * ICANN72 GNSO Policy Briefing * Virtual Backgrounds * Registration * ICANN72 Prep Week Schedule * ICANN72 Schedule Information Sharing * NEW: ICANN72 Board Workshop: DNS Abuse Informational Discussion * NEW: ICANN 2021 Nominating Committee Publishes Summary Report * NEW: ICANN Announces 2022 Nominating Committee Chair and Chair-Elect * NEW: DNS Security Facilitation Technical Study Group Delivers Final Report * NEW: ICANN Strengthens its Technical Engagement in Africa and the Middle East * REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Public Comment * Proposal for Japanese Script Root Zone Label Generation Rules * Proposal for Latin Script Root Zone Label Generation Rule * Draft PTI and IANA FY23 Operating Plan and Budgets * Initial Report from the EPDP on Specific Curative Rights Protection for IGOs * Proposed Amendment 5 to the .name Registry Agreement * REMINDER: ICANN Launches Improved Public Comment Feature ICANN72 Resources ICANN72 Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> ICANN72 GNSO Policy Briefing [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Virtual Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Registration [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> ICANN72 Prep Week Schedule [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> ICANN72 Schedule [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Information Sharing NEW: ICANN72 Board Workshop: DNS Abuse Informational Discussion The ICANN Board of Directors holds a regular workshop prior to each ICANN meeting. For ICANN72 the Board workshop program will include a Board discussion with a panel of security professionals and experts, to enhance the Board’s understanding of what constitutes DNS abuse and how various organizations are approaching its mitigation. This session will be held on Friday 22 October, from 16:00 - 19:30 UTC. It will be open to the community to attend, although, as is customary with other open Board sessions, attendees will not be able to interact directly with the speakers. Further details about the session, including speakers and how to register, will be published shortly on the ICANN org website. NEW: ICANN 2021 Nominating Committee Publishes Summary Report The Internet Corporation for Assigned Names and Numbers (ICANN) 2021 Nominating Committee (NomCom) has published its summary report [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…>, which reviews its progress since convening at the conclusion of the ICANN69 Annual General Meeting (AGM). The report outlines the criteria that the NomCom was given when searching for potential candidates, and recaps its outreach activities and pre-selection process. It also provides a list of the final selections and a message from the 2021 NomCom Chair. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> NEW: ICANN Announces 2022 Nominating Committee Chair and Chair-Elect The Internet Corporation for Assigned Names and Numbers (ICANN) announced [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> that the ICANN Board has appointed Michael Graham to serve as 2022 Nominating Committee (NomCom) Chair, and J. Damon Ashcraft as 2022 NomCom Chair-Elect. Please note that Tracy Hackshaw, the 2021 NomCom Chair-Elect, withdrew his candidacy for 2022 NomCom Chair due to a new professional role he has taken. He looks forward to working with the NomCom in the future. NEW: DNS Security Facilitation Technical Study Group Delivers Final Report Merike Käo [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> I'm pleased to report that the Domain Name System Security Facilitation Technical Study Group (DSFI-TSG) has delivered our Final Report to the ICANN CEO for his consideration. The TSG was established by the CEO in May 2020 to investigate mechanisms to strengthen collaboration and communication on security and stability issues related to the Domain Name System (DNS). Read more. [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> NEW: ICANN Strengthens its Technical Engagement in Africa and the Middle East Beginning in 2020, the ICANN organization's (org's) Office of the Chief Technology Officer (OCTO) has been strengthening its team in charge of technical engagement with the Internet community. The result, in part, is that we have joined ICANN as technical engagement specialists and are actively providing training, promoting research, and disseminating standards and best practices related to the security, stability, and resiliency of the DNS in the African and the Middle Eastern (MEA) regions. To learn more about improvements to the Technical Engagement team, please read this blog [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Applications for the NextGen@ICANN program at ICANN73 are now being accepted. The deadline for applications is Monday, 25 October 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Public Comment Proposal for Japanese Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Open for Submissions Date: Thursday, 30 September 2021 Closed for Submissions Date: Tuesday, 16 November 2021 Proposal for Latin Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Open for Submissions Date: Thursday, 23 September 2021 Closed for Submissions Date: Tuesday, 23 November 2021 Draft PTI and IANA FY23 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Open for Submissions Date: Wednesday, 15 September 2021 Closed for Submissions Date: Monday, 25 October 2021 Initial Report from the EPDP on Specific Curative Rights Protections for IGOs [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Open for Submissions Date: Tuesday, 14 September 2021 Closed for Submissions Date: Sunday, 24 October 2021 Proposed Amendment 5 to the .name Registry Agreement [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Open for Submissions Date: Friday, 10 September 2021 Closed for Submissions Date: Wednesday, 20 October 2021 REMINDER: ICANN Launches Improved Public Comment Feature The Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Read more about the improvements! [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> Volume 3, Issue 76 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> | Next Issue: Monday, 18 October 2021 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https://r20.rs6.net/tn.jsp?f=001hiCEnXWj893u14w…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe michelle.desmyter(a)icann.org [visitor.constantcontact.com]<https://urldefense.com/v3/__https://visitor.constantcontact.com/do?p=un&m=0…> Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https://visitor.constantcontact.com/do?p=oo&m=0…> | Constant Contact Data Notice [constantcontact.com]<https://urldefense.com/v3/__https://www.constantcontact.com/legal/customer-…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> powered by [Trusted Email from Constant Contact - Try it FREE today.] [constantcontact.com]<https://urldefense.com/v3/__http://www.constantcontact.com/index.jsp?cc=nge…> Try email marketing for free today! [constantcontact.com]<https://urldefense.com/v3/__http://www.constantcontact.com/index.jsp?cc=nge…>

1 0