December 2020 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine Oct. 20, 2022

Oct. 20, 2022

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. 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 4

Letter to ICANN Secretary re interim appointment of the GNSO representative to the Empowered Community Administration
by Nathalie Peregrine Oct. 27, 2021

Oct. 27, 2021

Dear all, Please find attached the letter informing John Jeffrey and the Empowered Community administration of the interim appointment of Philippe Fouquart as GNSO representative to the Empowered Community administration. The letter will be posted on the Correspondence page[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_corr…> of the GNSO website. 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

Nominating Committee Criteria for Appointing GNSO Councilors
by Steve Chan Jan. 28, 2021

Jan. 28, 2021

Dear Councilors, The GNSO Council was invited to review the position description that the ICANN Nominating Committee uses in order to fulfill its appointments to the GNSO Council. You can find the position description for the 2020 cycle here: https://www.icann.org/resources/pages/nomcom2020-positions-2020-01-13-en#gn…. The position description is of course an important piece of guidance for the NomCom, to ensure that it appoints GNSO Councilors that will succeed in their role. Staff, in coordination with Council leadership, has taken that existing description and dropped it into a Google document, where it has undergone some preliminary redlines. A fair amount of those edits are mostly structural, to have the position description look more like a job description (e.g., separating out criteria and skillset and also separating out job responsibilities and time commitment). You can find that redline here, where you are invited to add in your own suggested edits: https://docs.google.com/document/d/1WzjvntnliTSZ43b0hJkhh_Hb2onzxXufmTnZJCE…. The target date to receive and integrate feedback as appropriate is early January. Finally and most importantly, happy holidays to you all! Best, Steve Steven Chan  Senior Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

8 12

GNSO Standing Committee for Continuous Improvement – Ideas and Possible Approach
by philippe.fouquart＠orange.com Jan. 20, 2021

Jan. 20, 2021

Dear Councilors, SG/C Chairs, As you may be aware, there are quite a number of projects on the Council’s Action Decision Radar (see https://community.icann.org/x/14vzC) that deal with improvements to GNSO processes and procedures. We heard from you during the Strategic Planning Session about the importance of prioritizing work as well as considering the resources available to conduct work as efficiently as possible. To this end, the suggestion was made to explore the possibility of creating a Standing Committee that would be tasked with addressing projects or assignments that are mainly focused on improving existing GNSO processes and procedures. To further explore this possible approach, the Council leadership team has worked with the staff support team on developing a high-level outline for your review and input (see https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit) Although the Standing Committee would be chartered by and operate under the oversight of the GNSO Council, it is intended to be a GNSO effort which can only be successful with the full support and participation of all SG and Cs. We appreciate that it may be challenging to comment on this approach without having all the details, but our hope is that by soliciting input at this point in time, we would be able to develop a more detailed proposal as a next step factoring in your suggestions and perspectives. Some of the questions we hope you can focus on are: · Is this the right approach to benefit from synergies? If not, how should all the projects listed be tackled instead? · How to ensure appropriate scoping of work? The idea is that the standing committee would tackle topics that cut across the GNSO community and/or would benefit from a cross-GNSO collaboration. A possible approach could be that the charter provides an indication of the topics that are expected to be tackled, but specific assignments are confirmed in the form of a clear scoping document and work plan that is approved by the GNSO Council, with input from SG/Cs via their respective Council members. Are there other approaches that could be considered? · What should membership look like? How to ensure a balanced composition which at the same time is nimble enough to work effectively? How to introduce sufficient flexibility to allow for expert participation? · What decision-making methodology should be applied? Or is this to be determined based on the assignment the Standing Committee is tasked with? · Is it feasible to consider tackling some of the projects identified in parallel through different sub-committees? · How should the work be prioritized if a Standing Committee is created? Each of the possible projects identified could take a substantial amount of time to address and resolve which means certain items could take a while to get addressed. Of course, there may be other topics you want to weigh in on. We hope to receive your feedback in advance of the next Council meeting which is scheduled for Thursday 21 January, either via your input on the google doc (see https://docs.google.com/document/d/1HBCXMkLb7vFkWClgCpsr8WjYScz3UDh4/edit) or in response to this email. As you will have seen, a number of the possible projects for the Standing Committee are fairly high on the Council’s Action Decision Radar so we hope to agree on an approach for tackling these sooner rather than later. Best regards and happy holidays, Philippe Fouquart Chair, GNSO _________________________________________________________________________________________________________________________ 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.

6 6

Re: [council] FW: [Ext] 21 December 2020
by Steve Chan Dec. 23, 2020

Dec. 23, 2020

Dear Councilors, Like Tom regarding the revised ODP paper, I just wanted to draw your attention to the particular item regarding Additional Budget Requests (ABRs). As you can see below, the deadline for requests is 29 January 2021. Some background that you all may or may not be aware of is that the GNSO Council in recent years has consistently submitted two ABRs, one for the Strategic Planning Session and one for travel funding to PDP Chairs who would be otherwise unable to attend ICANN public meetings. Both of those items are now included in the core budget and will not require the submission of an ABR this cycle (see page 15 of the Draft FY22 Budget here: https://www.icann.org/en/system/files/files/draft-budget-fy22-2020-en.pdf) Please give some thought to whether or not the GNSO Council specifically should submit any ABRs this cycle, which are of course separate and apart from any ABRs that the SG/Cs may submit. Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Monday, December 21, 2020 at 8:46 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] FW: [Ext] 21 December 2020 Monday, 21 December 2020 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. ICANN offices will be closed from Thursday, 24 December 2020 through Friday, 1 January 2021 and reopen on Monday, 4 January 2021. Table of Contents Information Sharing · NEW: Operational Design Phase: Updated Concept Paper · NEW: ICANN Draft FY22-26 Operating and Financial Plan, and the ICANN Draft FY22 Operating Plan and Budget Now Available · NEW: Nomination Period for the ICANN Community Excellence Award Now Open · REMINDER: Request For Community Selection Panel Participants – 2021 Community Excellence Award Program · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members · REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 Public Comment · Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 · NEW: Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget Information Sharing NEW: Operational Design Phase: Updated Concept Paper From: Theresa Swinehart, Senior Vice President, Global Domains & Strategy ICANN org has shared an updated version of the Operational Design Phase Concept Paper [r20.rs6.net] The new version follows community consultation during ICANN69, including written feedback by a number of community groups. The community is asked to provide input by Friday, 22 January 2021. ICANN org will also conduct a webinar; details will be shared shortly. The concept paper proposes an Operational Design Phase (ODP) that is to become part of the policy and implementation life cycle. The ICANN organization will conduct the ODP for consensus policy recommendations that are approved by the Generic Names Supporting Organization (GNSO) Council. The purpose of the ODP is to provide the Board with relevant information to decide, as required by the Bylaws, whether a recommendation is in the best interest of the ICANN community or ICANN. NEW: ICANN Draft FY22-26 Operating and Financial Plan, and the ICANN Draft FY22 Operating Plan and Budget Now Available From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer On Thursday, 17 December 2020, ICANN published the Draft FY22 Plans for Public Comment [r20.rs6.net] The three documents published are: 1. Highlights of the Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget 2. Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan 3. Draft FY22 Budget Two community webinars will be held in January to provide an overview of the draft plans: · Webinar 1 | Tuesday, 12 January 2021, 16:00 UTC, please register here [r20.rs6.net] · Webinar 2 | Wednesday, 13 January 2021, 01:00 UTC, please register here [r20.rs6.net] Please register in advance to receive details on hot to join these webinars. NEW: Nomination Period for the ICANN Community Excellence Award Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The deadline for submissions is Monday, 29 March 2021, and the winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within the ICANN multistakeholder model. Learn more about the nomination process [r20.rs6.net] and submit your nominations here [r20.rs6.net] REMINDER: Request for Community Selection Panel Participants – 2021 ICANN Community Excellence Award Program From: David Olive, Senior Vice President, Policy Development Support ICANN Supporting Organizations and Advisory Committees will be requested to provide up to two members from their respective group to help choose the recipient of the 2021 ICANN Community Excellence Award. The 2021 ICANN Community Excellence Award will be presented during ICANN71. A community selection panel will be formed to review the nominations and select the award recipient. Ideally, panelists will serve a maximum of two consecutive terms on the selection panel to ensure diversity and equal opportunity among community members. The time commitment for the selection panel includes weekly one-hour calls between the end of March through June 2021. Further information will be available in the upcoming weeks. REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement ICANN has announced [r20.rs6.net] a call for nominees to volunteer to serve as mentors to the Fellowship Program and as members to its Selection Committee. There will be a total of seven mentors and seven Selection Committee members, and each group is welcome to nominate one individual for each role. Interested Supporting Organizations and Advisory Committees should select their respective Fellowship Program mentor and Selection Committee representative by Sunday, 31 January 2021 and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. Criteria for mentors and Selection Committee members can be found here [r20.rs6.net] REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 ICANN org has launched the FY22 Additional Budget Request process. This process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget. Submissions are due on Friday, 29 January 2021 at 23:59 UTC to planning(a)icann.org. Learn more [r20.rs6.net] Public Comment Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 [r20.rs6.net] Close Date: Friday, 22 January 2021 NEW: [r20.rs6.net]Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget [r20.rs6.net] Close Date: Monday, 15 February 2021 Volume 2, Issue 97 | Archive [r20.rs6.net] | Next Issue: Monday, 4 January 2021

1 0

Draft minutes of the GNSO Council meeting 17 December 2020
by Andrea Glandon Dec. 22, 2020

Dec. 22, 2020

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting held on Thursday, 17 December 2020 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 01 January 2021. Thank you. Kind Regards, Andrea

1 0

Action Items: GNSO Council meeting 17 December 2020
by Andrea Glandon Dec. 22, 2020

Dec. 22, 2020

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 17 December 2020. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. Item 3: Consent Agenda (10 minutes) 3.1 - Approval of SSC Leadership for 2020-2021: Carlton Samuels, Chair and Sophie Hey, Vice-Chair 3.2 - Approval of Heather Forrest to serve an additional term as GNSO nominated member of the Fellowship Selection Committee 3.3 - Approval of Keith Drazek to serve as EPDP 2A Chair 3.4 - Approval of Chris Disspain to serve as IGO Curative Rights Work Track Chair 3.5 - Confirmation of Council liaisons to respective efforts: * All Rights Protection Mechanisms in All gTLDs / IGO Curative Rights Work Track - John McElwaine * New gTLD Subsequent Procedures - Flip Petillion * EPDP Phase 2 - Olga Cavalli * EPDP Phase 2A - TBD * Standing Committee on Budget & Operations (SCBO) - Philippe Fouquart (ex officio) * Standing Selection Committee (SSC) - Tatiana Tropina (ex officio) * IRT: EPDP Phase 1 - Sebastien Ducos * IRT: Privacy & Proxy Services Accreditation Issues PDP Recommendations (PPSAI) IRT - TBD (paused) * IRT: Translation and Transliteration of Contact Information (T/T) - Maxim Alzoba (paused) * GNSO Council liaison to the ccNSO - Sebastien Ducos * GNSO Council liaison to the GAC - Jeff Neuman (already approved but included for completeness) Action Item: * Staff to inform Fellowship Selection Committee of GNSO Council’s approval of Heather Forrest as the GNSO nominated member for an additional term. [COMPLETED] * Staff to send a call for volunteers for the EPDP Phase 2A Liaison position, with the aim to fill the position by the 21 January 2021 Council meeting. (EPDP Phase 2 liaison position is not needed) Item 4: COUNCIL VOTE - Affirm Intent of EPDP Phase 1 Recommendation 7 (25 minutes) Action Item: * GNSO Council small team on EPDP Phase 1 Rec 7 to reconvene and further consider an improved approach and propose updated motion for the January 2021 Council meeting as a vote item, with the caveat that the intent of Rec 7 be maintained. Staff to send out a doodle poll to schedule a placeholder meeting (preferably before 11 Jan 2021) for the small team. Item 6: COUNCIL DISCUSSION - Update from Council small team on GNSO next steps to implement WS2 recommendations (10 minutes) Action Item: * Staff to place this item on the GNSO Council January 2021 meeting agenda (discussion deferred) Item 7: ANY OTHER BUSINESS (20 minutes) 7.1 - Notification of SG/C and Council discussion and agreement on process to appoint GNSO members for the Community Representatives Group to select IRP Standing Panel (i.e., assign to SSC and provide the SSC with briefing document to help guide their selection process) (GNSO Chair - Philippe Fouquart) 7.2 - Update from SO/AC leadership roundtable (GNSO Chair - Philippe Fouquart) 7.3 - Update on SubPro PDP WG Final Report delivery (Council leadership & Flip Petillion) 7.4 - Next steps for the letter from the Board regarding EPDP Phase 1, Recommendation 12 7.5 - GNSO Council Additional Budget Requests (due 29 January 2021) Action Item: * Staff to circulate an email to the GNSO Council, providing context about previous Council Additional Budget Requests and seeking input for potential requests for the next fiscal year. * GNSO Council leadership to send a call for volunteers message to form a Council small team (likely composed of CPH Councilors) to prepare a draft response to the Board letter regarding EPDP Phase 1 Rec 12. Thank you! Andrea

1 0

GNSO Council Liaisons
by Steve Chan Dec. 21, 2020

Dec. 21, 2020

Dear Councilors, Following the affirmative vote to approve the Consent Agenda on the 17 December 2020 meeting, a number of GNSO Council liaisons are now confirmed. However, note that during the meeting, Olga withdrew her name as the GNSO Council liaison to the EPDP Phase 2 and that there is still an outstanding vacancy for the EPDP Phase 2A. In consultation with Council leadership, here is the proposed path forward. EPDP Phase 2: As this PDP has now concluded, there does not appear to be a pressing need to identify a new liaison, though one will be needed once an Implementation Review Team (IRT) is established. However, and without making too many assumptions, there may be reason that the IRT for Phase 2 will be merged or perhaps be a continuation of the existing IRT, which could allow Sebastien to serve as the single Council liaison to the IRT (assuming there is some form of streamlined IRT and Sebastien is willing of course). The Council leadership proposal here is to leave this position vacant, at least for the moment. EPDP Phase 2: There is however a need to identify a liaison here, in a timely fashion, as the EPDP Team has already held its first meeting. To give you a sense of the commitment, liaisons typically take part in leadership planning meetings, share information and updates between the WG and Council, provide guidance regarding WG processes, etc. (see role description here: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liai…) However, I would note that during the EPDP Phase 2, the liaison also served as the vice-chair, and this possibility is I understand under discussion within the EPDP Phase 2A currently. Assuming that ends up being the outcome, the liaison would then be asked to both fulfill the requirements of being a GNSO Council liaison to the WG, as well as that of being a vice-chair, which is primarily chairing WG calls when the Chair is unavailable. That said, the Chair has indicated that he fully anticipates being available for this limited duration effort. The Council leadership proposal here is of course to identify a volunteer to fill this position. Best, Steve Steven Chan  Senior Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

1 0

FW: [Ext] 21 December 2020
by Andrea Glandon Dec. 21, 2020

Dec. 21, 2020

[http://r20.rs6.net/on.jsp?ca=63703272-2d45-4a88-a65c-de02487a0199&a=1122025…] Monday, 21 December 2020 ICANN Community Leadership 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. ICANN offices will be closed from Thursday, 24 December 2020 through Friday, 1 January 2021 and reopen on Monday, 4 January 2021. Table of Contents Information Sharing · NEW: Operational Design Phase: Updated Concept Paper · NEW: ICANN Draft FY22-26 Operating and Financial Plan, and the ICANN Draft FY22 Operating Plan and Budget Now Available · NEW: Nomination Period for the ICANN Community Excellence Award Now Open · REMINDER: Request For Community Selection Panel Participants – 2021 Community Excellence Award Program · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members · REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 Public Comment · Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 · NEW: Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget Information Sharing NEW: Operational Design Phase: Updated Concept Paper From: Theresa Swinehart, Senior Vice President, Global Domains & Strategy ICANN org has shared an updated version of the Operational Design Phase Concept Paper [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. The new version follows community consultation during ICANN69, including written feedback by a number of community groups. The community is asked to provide input by Friday, 22 January 2021. ICANN org will also conduct a webinar; details will be shared shortly. The concept paper proposes an Operational Design Phase (ODP) that is to become part of the policy and implementation life cycle. The ICANN organization will conduct the ODP for consensus policy recommendations that are approved by the Generic Names Supporting Organization (GNSO) Council. The purpose of the ODP is to provide the Board with relevant information to decide, as required by the Bylaws, whether a recommendation is in the best interest of the ICANN community or ICANN. NEW: ICANN Draft FY22-26 Operating and Financial Plan, and the ICANN Draft FY22 Operating Plan and Budget Now Available From: Xavier Calvez, Senior Vice President, Planning and Chief Financial Officer On Thursday, 17 December 2020, ICANN published the Draft FY22 Plans for Public Comment [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. The three documents published are: 1. Highlights of the Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget 2. Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan 3. Draft FY22 Budget Two community webinars will be held in January to provide an overview of the draft plans: · Webinar 1 | Tuesday, 12 January 2021, 16:00 UTC, please register here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. · Webinar 2 | Wednesday, 13 January 2021, 01:00 UTC, please register here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. Please register in advance to receive details on hot to join these webinars. NEW: Nomination Period for the ICANN Community Excellence Award Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The deadline for submissions is Monday, 29 March 2021, and the winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within the ICANN multistakeholder model. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…> and submit your nominations here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. REMINDER: Request for Community Selection Panel Participants – 2021 ICANN Community Excellence Award Program From: David Olive, Senior Vice President, Policy Development Support ICANN Supporting Organizations and Advisory Committees will be requested to provide up to two members from their respective group to help choose the recipient of the 2021 ICANN Community Excellence Award. The 2021 ICANN Community Excellence Award will be presented during ICANN71. A community selection panel will be formed to review the nominations and select the award recipient. Ideally, panelists will serve a maximum of two consecutive terms on the selection panel to ensure diversity and equal opportunity among community members. The time commitment for the selection panel includes weekly one-hour calls between the end of March through June 2021. Further information will be available in the upcoming weeks. REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement ICANN has announced [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…> a call for nominees to volunteer to serve as mentors to the Fellowship Program and as members to its Selection Committee. There will be a total of seven mentors and seven Selection Committee members, and each group is welcome to nominate one individual for each role. Interested Supporting Organizations and Advisory Committees should select their respective Fellowship Program mentor and Selection Committee representative by Sunday, 31 January 2021 and notify fellowshipconsultation(a)icann.org<mailto:fellowshipconsultation@icann.org>. Individual self-nominations will not be considered. Criteria for mentors and Selection Committee members can be found here [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. REMINDER: FY22 Additional Budget Requests Due Friday, 29 January 2021 ICANN org has launched the FY22 Additional Budget Request process. This process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget. Submissions are due on Friday, 29 January 2021 at 23:59 UTC to planning(a)icann.org<mailto:planning@icann.org>. Learn more [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>. Public Comment Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…> Close Date: Friday, 22 January 2021 NEW: [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…>Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…> Close Date: Monday, 15 February 2021 Volume 2, Issue 97 | Archive [r20.rs6.net]<https://urldefense.com/v3/__http:/r20.rs6.net/tn.jsp?f=001Tv9e9K9oUsPb8KyHg…> | Next Issue: Monday, 4 January 2021

2 1

GNSO Council resolutions 17 December 2020
by Nathalie Peregrine Dec. 17, 2020

Dec. 17, 2020

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday 17 December 2020 which will be posted shortly on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page. Consent agenda 3.1 - Approval of SSC Leadership for 2020-2021: Carlton Samuels, Chair and Sophie Hey, Vice-Chair 3.2 - Approval of Heather Forrest to serve an additional term as GNSO nominated member of the Fellowship Selection Committee 3.3 - Approval of Keith Drazek to serve as EPDP 2A Chair 3.4 - Approval of Chris Disspain to serve as IGO Curative Rights Work Track Chair 3.5 - Confirmation of Council liaisons to respective efforts: * All Rights Protection Mechanisms in All gTLDs / IGO Curative Rights Work Track - John McElwaine * New gTLD Subsequent Procedures - Flip Petillion * EPDP Phase 2 - Olga Cavalli * EPDP Phase 2A - TBD * Standing Committee on Budget & Operations (SCBO) - Philippe Fouquart (ex officio) * Standing Selection Committee (SSC) - Tatiana Tropina (ex officio) * IRT: EPDP Phase 1 - Sebastien Ducos * IRT: Privacy & Proxy Services Accreditation Issues PDP Recommendations (PPSAI) IRT - TBD (paused) * IRT: Translation and Transliteration of Contact Information (T/T) - Maxim Alzoba (paused) * GNSO Council liaison to the ccNSO - Sebastien Ducos * GNSO Council liaison to the GAC - Jeff Neuman (already approved but included for completeness) Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-17dec20-en.…> GNSO Council Input on Recommendation 7 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data Phase 1 Final Report and Thick Whois Transition Policy Submitted by: Pam Little Seconded by: John McElwaine WHEREAS 1. The Thick RDDS (Whois) Transition Policy for .COM, .NET and .JOBS<https://www.icann.org/resources/pages/thick-whois-transition-policy-2017-02…> (Thick Whois Transition Policy) is an ICANN consensus policy resulting from the implementation of the policy recommendations in the Final Report on the Thick WHOIS Policy Development Process<https://gnso.icann.org/sites/default/files/filefield_29151/final-report-thi…>(“Thick Whois PDP”). 2. Section 16 of ANNEX 2: Policy Development Process Manual<https://gnso.icann.org/en/council/annex-2-pdp-manual-24oct19-en.pdf> to the GNSO Operating Procedures v3.5<https://gnso.icann.org/en/council/op-procedures-24oct19-en.pdf> provides: “Approved GNSO Council policies that have been adopted by the ICANN Board and have been implemented by ICANN Staff may only be amended by the initiation of a new PDP on the issue.” 3. On 17 May 2018, the ICANN Board adopted the Temporary Specification for gTLD Registration Data (“Temporary Specification”). 4. On 19 July 2018, the GNSO Council initiated an Expedited Policy Development Process (“EPDP”) and chartered the EPDP on the Temporary Specification for gTLD Registration Data Team to determine if the Temporary Specification should become an ICANN consensus policy as is, or with modifications (emphasis added). 5. Recommendation #7 in the EPDP Phase 1 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> (“Final Report”) makes transfer of registrant contact information optional, depending on whether the registry operator in question has an appropriate legal basis to require the data and a data processing agreement is in place. 6. To the extent the Thick Whois Transition Policy is modified by Recommendation #7, the EPDP Team recommends the Thick Whois Transition Policy and other impacted consensus policies be updated to ensure consistency (see Recommendation #27 of the Final Report). 7. Recommendation #7 was developed in response to the questions in Section C of the EPDP Charter, with a consensus designation of “Full Consensus / Consensus” (see Annex E of the Final Report). 8. On 4 March 2019, the GNSO Council adopted<https://gnso.icann.org/en/council/resolutions#20190304-1> all the policy recommendations in the Final Report, including Recommendation #7, with the required GNSO Supermajority. 9. On 15 May 2019, the ICANN Board passed a resolution<https://features.icann.org/consideration-gnso-epdp-recommendations-temporar…> adopting most of the policy recommendations contained in the Final Report, including Recommendation #7 and noting Recommendation #7 does not repeal or overturn the Thick WHOIS Policy [sic] and directed “ICANN org to work with the Implementation Review Team to examine and transparently report on the extent to which these Recommendations require modification of existing Consensus Policies, including the Thick WHOIS Transition Policy”. 10. Section 7 of Annex A-1 to the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en> provides: “Upon a final decision of the Board adopting the EPDP recommendations, the Board shall, as appropriate, give authorization or direction to ICANN staff to implement the EPDP Recommendations. If deemed necessary, the Board shall direct ICANN staff to work with the GNSO Council to create a guidance implementation plan, based upon the guidance recommendations identified in the Final EPDP Recommendation(s) Report.” 11. Section III. A of the Consensus Policy Implementation Framework<https://www.icann.org/policy/implementation> provides: The GNSO Council may continue to provide input on the implementation of a policy, for example, if the GNSO Council believes that the implementation is inconsistent with the policy [recommendation]”. RESOLVED 1. The GNSO Council confirms that the EPDP had the mandate to modify the Thick Whois Transition Policy under the EPDP 2. The GNSO Council determines that in light of the EPDP being chartered by the GNSO Council, among other things, to address the questions in Part 2(c) under “Mission and Scope” to specifically address the transfer of data from registrar to registry, the resulting recommendation #7 appropriately fulfills this purpose. Furthermore, the requirement of Section 16 of the PDP Manual is deemed satisfied for the purpose of amending the Thick Whois Transition Policy. 3. The GNSO Council determines, notwithstanding the absence of a clear statement, the intent of EPDP Phase 1 Recommendation #7 to modify the Thick Whois Transition Policy is implied, taking into account the history, background, context and purpose of the EPDP, the specific language of Recommendation #7 and the EPDP Phase 1 Final Report in its entirety. 4. The GNSO Council determines that the Recommendation #7 language, “must be transferred from registrar to registry provided an appropriate legal basis exists and data processing agreement is in place” should be included in the Registration Data Policy in order to conform with the intent of the EPDP Phase 1 Team’s policy recommendation and the subsequent GNSO Council adoption (“GNSO Council Input”). 5. The GNSO Council instructs the Council’s Liaison to communicate the GNSO Council Input to the Registration Data Policy Implementation Review Team pursuant to Section III.A of the Consensus Policy Implementation Framework<https://www.icann.org/policy/implementation>. 6. The GNSO Council shall communicate the GNSO Council Input to the ICANN Board of Directors. RATIONALE The Thick Whois PDP Final Report anticipated that its recommendations might be affected by evolving privacy regulation. In particular, Recommendation 3 states, “As part of the implementation process a legal review of law applicable to the transition of data from a thin to thick model … due consideration is given to potential privacy issues that may arise from the discussions on the transition from thin to thick Whois … Should any privacy issues emerge from these transition discussions that were not anticipated by the WG and which would require additional policy consideration, the Implementation Review Team is expected to notify the GNSO Council of these so that appropriate action can be taken.” In addition, the implementation advice (“Other Observations”) mentions in part, “...the increasing number of data protection and privacy laws and regulations around the world, as well as specific Whois-related concerns raised by the public. While recognizing that this exceeds the scope of our remit, we suggest that, as part of the development of the registration data directory system model currently in process, ICANN ensure that the ramifications of data protection and privacy laws and regulations with respect to Whois requirements be examined thoroughly.” In effect, the Temporary Specification and the EPDP accomplished the legal review of the ramifications of data protection laws required by Recommendation 3 of the Thick Whois PDP Final Report . The requirements set out in the Temporary Specification supersede and replace the contractual requirements in the Registrar Accreditation Agreement and the Registry Agreements, which incorporate by reference all ICANN consensus policies. There is a conflict between the data processing principles under the Temporary Specification and the requirements under existing gTLD Registry Agreements as well as the Thick Whois Transition Policy. In other words, the Thick Whois Transition Policy was modified by the Temporary Specification and further modified by Recommendation #7 in the EPDP Phase 1 Final Report, as the EPDP Team was mandated to do. While there is no explicit reference to the Thick Whois Transition Policy, this consensus policy and others that are affected by the GDPR and other relevant data privacy laws fell squarely within the scope of the Temporary Specification and hence they are also within the scope of the EPDP. The EPDP Charter states: “Mission and Scope This EPDP Team is being chartered to determine if the Temporary Specification for gTLD Registration Data should become an ICANN Consensus Policy, as is or with modifications, while complying with the GDPR and other relevant privacy and data protection law. As part of this determination, the EPDP Team is, at a minimum, expected to consider the following elements of the Temporary Specification and answer the following charter questions. The EPDP Team shall consider what subsidiary recommendations it might make for future work by the GNSO which might be necessary to ensure relevant Consensus Policies, including those related to registration data, are reassessed to become consistent with applicable law.” Specifically, Section C of the EPDP Charter contains a set of questions regarding “transfer of data from registrar to registry”: c1) What data should registrars be required to transfer to the registry? c2) What data is required to fulfill the purpose of a registry registering and resolving a domain name? c3) What data is transferred to the registry because it is necessary to deliver the service of fulfilling a domain registration versus other legitimate purposes as outlined in part (a) above? c4) Is there a legal reason why registrars should not be required to transfer data to the registries, in accordance with previous consensus policy on this point? c5) Should registries have the option to require contact data or not? c6) Is there a valid purpose for the registrant contact data to be transferred to the registry, or should it continue to reside at the registrar? While the Final Report does not contain express language that the policy recommendations are intended to supersede the requirements in the existing ICANN consensus policies, in this case, the Thick Whois Transition Policy, such intent is implied (i.e., it goes without saying in light of the history, background, context and purpose of the EPDP). The EPDP was conducted in an open and transparent manner with representatives from all GNSO Stakeholder Groups and Constituencies, as well as some ICANN Advisory Committees. As such, Recommendation #7 cannot be considered to be a “shadow repeal” of the Thick Whois Transition Policy. The recommendations contained in the Thick WHOIS PDP Final Report anticipated that the implementation of those recommendations might be affected by new privacy regulations and the GNSO should address such an occurrence. Therefore, while there is no “clear statement in new consensus policy recommendations that the new policy is intended to supersede (in whole or part) requirements in existing consensus policies,” claiming otherwise ignores the history, background, context, purpose of the EPDP as well as the Thick Whois PDP Final Report itself. The intent and meaning of Recommendation #7 is clear. It is the role of the Implementation Review Team (IRT) to ensure that the implementation of Recommendation #7 conforms to the intent of the policy recommendation. The IRT is not a forum for opening or revisiting policy discussions (see III.A and III.B, Implementation Review Team (IRT) Principles and Guidelines https://www.icann.org/resources/files/1201611-2016-08-23-en) The Policy Development Process Manual makes clear that “Approved GNSO Council policies that have been adopted by the ICANN Board and have been implemented by ICANN Staff may only be amended by the initiation of a new PDP on the issue.” It can therefore be concluded that where there is a conflict between an existing consensus policy and subsequent policy recommendation(s) on the same subject matter, the newer policy recommendation prevails. While the EPDP was scoped differently and under different circumstances than the Thick Whois PDP, it is undeniable that the two policy development processes overlapped in covering the same issue of transfer of Registration Data from registrar to registry, and therefore, the IRT should implement Recommendation #7 as written and intended. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-17dec20-en.…> Thank you. Kind regards, Nathalie

1 0