March 2022 - council - lists.icann.org

DNS abuse small team update
by Steve Chan 03 Mar '22

03 Mar '22

Sent on behalf of the DNS abuse small team co-leads Dear Councilors, The DNS abuse small team met on 9 February to discuss the assignment form (here<https://community.icann.org/download/attachments/178587048/Small%20Team%20A…>) and discuss possible next steps. The Council agreed to create this small team at ICANN72, but it was done without a great deal of elaboration. As such, the small team discussed and quickly agreed that its central question should be to consider what DNS abuse issues are best mitigated via policy development specifically, if any, as a mechanism to help determine the Council’s next steps on DNS abuse. The small team also agree that a good first step in helping to answer that question is to reach out to community groups that have expressed a keen interest in DNS abuse and seek their input. You can see the draft communications here: https://docs.google.com/document/d/1rpmBJZ5EwbztuoNH8r36lCxVo_VD4mEDwloFyEr… [docs.google.com]<https://docs.google.com/document/d/1rpmBJZ5EwbztuoNH8r36lCxVo_VD4mEDwloFyEr…>. The group also quickly agreed that these letters should be sent via Council leadership rather than the small team. The initial set of outreach targets includes these four: ALAC, GAC, SSAC, and the DNS Abuse Institute. There was a suggestion to also reach out to eco’s topDNS initiative and the Internet & Jurisdiction’s Domains & Jurisdiction Program, but there is a concern that with all of the community work on DNS abuse, the Council is bound to miss a group in its formal outreach. Therefore, it was decided to leave it up to small team members to reach out to additional groups as they deem helpful. With ICANN73 approaching quickly, we think it would be helpful to get these letters out as quickly as possible, since ICANN73 should present itself as a good forum for groups to consider the Council’s questions. For that reason, we’re seeking any objections to the draft communications by 23:59 UTC on 4 March, and assuming Council leadership agrees, they will be sent out shortly afterwards. Best, Mark & Paul, small team co-leads Steven Chan  Senior Director, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Proposed Agenda | GNSO Council Meeting | Wednesday, 09 March 2022 at 16:30 UTC
by Terri Agnew 03 Mar '22

03 Mar '22

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on Wednesday, 09 March 2022 at 16:30 UTC for 2 hours. Make sure all have registered for ICANN73 Participation Links Zoom participation links will be published 24 hours before the session starts. For more information on how to participate, visit: https://73.schedule.icann.org/attend Draft GNSO Council Agenda 09 March 2022 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/09MGCw. 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 16:30 UTC (12:30 local time): https://tinyurl.com/yck4ykvp 08:30 Los Angeles; 11:30 Washington DC; 16:30 London; 17:30 Paris; 19:30 Moscow; (Thursday) 03:30 Melbourne GNSO Council Meeting Remote Participation: (See ICANN73 schedule for Zoom URL 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: 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/2022/minutes/minutes-gnso…> of the GNSO Council meeting on 20 January 2022 were posted on 03 February 2022. Minutes of the GNSO Council meeting on 17 February 2022 were posted on 07 March 2022. Item 2: Opening Remarks / Review of Projects & Action List (5 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) * Reappointment of Becky Burr to seat 13 on the ICANN Board. The CPH has reappointed Becky Burr for Seat 13 on the ICANN Board of Directors. This agenda item is intended to acknowledge the selection and confirm that the notification process as outlined in Section 7.25 of the ICANN Bylaws will be completed subsequently. * Motion<https://community.icann.org/x/2NMGCw> to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items. Item 4: COUNCIL DISCUSSION - Nominating Committee Outreach Subcommittee Outreach (10 minutes) The Nominating Committee (NomCom) initiated<https://www.icann.org/en/announcements/details/apply-now-for-icann-and-pti-…> its application process on 15 December 2021. For this cycle, the NomCom will be selecting one member of the GNSO Council, a non-voting appointee. The GNSO Council provided updated criteria<https://www.icann.org/resources/pages/nomcom2022-positions-2021-12-15-en#gn…> to the NomCom to be used in the recruitment and selection processes. Here, the NomCom Outreach Subcommittee will provide information about the NomCom panel, about the position being filled for the GNSO Council, and answer questions that the Council might have. 4.1 - Introduction of topic (NomCom Outreach Subcommittee) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION - Small Team Reviewing the System for Standardized Access/Disclosure (SSAD) Operational Design Assessment / Debrief From Meeting With the ICANN Board (25 minutes) On 25 January 2022, the Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> (ODA), the final output of the System for Standardized Access/ Disclosure (SSAD) to Nonpublic generic Top-Level Domain Registration Data Operational Design Phase (ODP) was published. Just prior to the publication of the ODA, the ICANN Board sent a letter<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/botte…> to the GNSO Council, outlining some of its concerns as well as questions it hoped to receive input on from the Council. The Council agreed to establish a small team to review the ODA in detail, focusing on the following elements as identified in the assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20A…>: * Whether the ODA has correctly interpreted the intent of the SSAD recommendations in the proposed implementation; * Whether the ODA has overlooked any key aspects of the SSAD recommendations that should be factored in by the ICANN Board when it considers the recommendations; * Its view on the concerns identified by the ICANN Board and potential options that could be considered, either in the form of changes to the proposed implementation or the policy recommendations themselves, to address these concerns(note, these are expected to be high level suggestions at this stage); * Any other aspects that help inform the Council’s deliberations and consultation with the ICANN Board. The GNSO Council will have met with the ICANN Board on 8 March, just prior to the March Council meeting, and will have discussed the ODA and the efforts of the small team with the Board. Here, the Council will receive an update on the status of the small team and hold a debrief from the meeting with the ICANN Board. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION - Update on the SubPro ODP / Debrief From Meeting With the ICANN Board (20 Minutes) On 12 September 2021 the ICANN Board directed<https://www.icann.org/resources/board-material/resolutions-2021-09-12-en#1.a> the ICANN President and CEO to organize the resources required to begin work on the Operational Design Phase (ODP) for the GNSO’s New gTLD Subsequent Procedures Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> and the Affirmations, Recommendations, and Implementation Guidance contained in that report. On 27 November 2021, the Council appointed Jeff Neuman to serve as its liaison to the SubPro ODP. On 20 December 2021, ICANN org announced<https://www.icann.org/en/announcements/details/icann-launches-new-gtld-subs…> that the SubPro ODP had formally launched, starting at the beginning of January 2022. ICANN org shared question set #2<https://mm.icann.org/pipermail/subpro-odp/attachments/20220211/93bd5c93/Sub…> with the GNSO Council’s liaison to ODP on 11 February 2022, who subsequently shared the questions and an update<https://mm.icann.org/pipermail/council/2022-February/025440.html> with the Council. While the question set was specifically about the topic of Applicant Support, it introduced broader procedural concerns, about whether the level of substantive work recommended by SubPro to be conducted by an IRT, would be beyond the commonly understood scope of the IRT. As with the above item, the Council will have met with the ICANN Board just prior to the March Council meeting, and will have discussed the broader question of the Council conducting additional SubPro related work concurrent with the ODP and in advance of a Board vote on the recommendations. Here, the Council will receive an update from the liaison, as well as hold a debrief from the meeting with the ICANN Board. 6.1 – Introduction of topic (Council leadership) 6.2 – Update (GNSO Council liaison to the SubPro ODP, Jeff Neuman) 6.3 – Council discussion 6.4 – Next steps Item 7: COUNCIL DISCUSSION - DNS Abuse Small Team (15 minutes) At ICANN72, the GNSO Council agreed to establish a small team to consider and recommend next steps for the Council related to DNS abuse, if any. An assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20A…> was drafted and the team held its first meeting 9 February 2022. The team agreed that as a first step, the Council should conduct outreach to interested community groups to better understand what DNS abuse related issues need to be addressed specifically via gTLD policy development. The small team expects to consider this same question amongst its members. Here, the small team will provide an update on its efforts. 7.1 – Introduction of topic (Small team co-leads: Mark Datysgeld & Paul McGrady) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION - Dialogue With ICANN’s Global Domains and Strategy (GDS) Department (20 Minutes) The GNSO Council and ICANN’s Global Domains and Strategy (GDS) team share a very important relationship. The GDS team, in coordination with the GNSO policy support staff, track and support the policy development process. Recently, especially where the PDP charters call for it specifically, GDS has appointed liaisons to PDPs to help provide background information, channel feedback and input from the Org, and to closely monitor the deliberations of the PDP. Once the Council adopts the recommendations and they are adopted by the ICANN Board, GDS is responsible for implementing the recommendations. Given this important relationship, it is helpful for the Council and GDS to regularly communicate with each other. Here, the Council will receive a high-level update on GNSO-related work being performed by GDS, as well as look ahead to work on the horizon, including the impact on resources. The dialogue is also expected to include discussion on how the shared portfolio of work can be executed more effectively and efficiently. 8.1 – Introduction of topic (ICANN Org staff - GDS) 8.2 – Council discussion 8.3 – Next steps Item 9: ANY OTHER BUSINESS (10 minutes) 9.1 – 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 16:30 UTC (12:30 local time) Local time between November and March Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 08:30 San José, Costa Rica (CST) UTC-4 12:30 New York/Washington DC, USA (EST) UTC-5 11:30 Buenos Aires, Argentina (ART) UTC-3 13:30 Rio de Janeiro, Brazil (BRT) UTC-3 13:30 London, United Kingdom (GMT) UTC+0 16:30 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 17:30 Paris, France (CET) UTC+1 17:30 Moscow, Russia (MSK) UTC+3 19:30 Singapore (SGT) UTC+8 (Thursday) 00:30 Melbourne, Australia (AEDT) UTC+11 (Thursday) 03:30 ---------------------------------------------------------------------------- DST starts/ends on Sunday 27 March 2022, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 13 March 2022 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/yck4ykvp

2 1

FW: [Ext] Thursday, 03 March 2022 | ICANN73 Begins Monday-Register Now!
by Julie Bisland 03 Mar '22

03 Mar '22

FYI: From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, March 3, 2022 at 10:04 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 03 March 2022 | ICANN73 Begins Monday-Register Now! [https://r20.rs6.net/on.jsp?ca=cf25b75b-5f94-46c0-b657-1c8410e15375&a=112202…] Thursday, 03 March 2022 ICANN Community Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. The ICANN Community Digest will not be published during ICANN73 and will return on Monday, 14 March 2022. 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=001i-p4FmhMwpM3NVC1…> Table of Contents ICANN73 · Policy Outlook Report · Registration · Schedule · Zoom Backgrounds Webinars · NEW: Draft Planning Prioritization Framework Webinar Information Sharing · DEADLINE TODAY: Apply Now for the ICANN75 Fellowship Program · NEW: ICANN Org's Draft Prioritization Framework (Version 1) Now Available · NEW: Improving Access to ICANN's Government Engagement Content · NEW: DNS Resolvers Used in the EU · NEW: Chair's Blog: Preview of March ICANN Board Workshop · REMINDER: Calling for NextGen@ICANN Applications for ICANN74 · REMINDER: Apply Now for ICANN and PTI Leadership Positions · REMINDER: ICANN Community Excellence Award Nomination Period Now Open Public Comment · CLOSES TODAY: Proposal for Myanmar Script Root Zone Label Generation Rules · Name Collision Analysis Project (NCAP) Study 2 Documents ICANN73 Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Zoom Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Webinars NEW: Draft Planning Prioritization Framework Webinar ICANN org will hold a webinar about the Draft Planning Prioritization Framework on Tuesday, 29 March 2022 at 14:00 UTC. Please register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> in advance of the meeting. Information Sharing DEADLINE TODAY: Apply Now for the ICANN75 Fellowship Program ICANN opened the Fellowship Program application round for the ICANN75 Annual General Meeting. The meeting is scheduled for 17–22 September 2022. If ICANN75 is held virtually, the Fellowship Program will also be held virtually. The deadline to apply is Thursday, 3 March 2022 at 23:59 UTC. Successful candidates will be announced on Tuesday, 17 May 2022 on the ICANN website. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> NEW: ICANN Org's Draft Prioritization Framework (Version 1) Now Available ICANN org recently published the initial draft [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> of its Planning Prioritization Framework. Since FY21, planning at ICANN has been one of 15 Operating Initiatives included in ICANN’s Operating Plan. As part of this initiative, the draft Planning Prioritization Framework is designed to help the ICANN ecosystem prioritize its work within the planning cycle in a manner that is transparent, inclusive, and efficient. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> NEW: Improving Access to ICANN's Government Engagement Content Governments are a crucial part of ICANN's multistakeholder model. At ICANN organization, I lead our Government and Intergovernmental Organization Engagement (GE) team, which is responsible for developing and implementing a global strategy to engage with governments and Intergovernmental Organizations (IGOs). We also monitor and analyze government and IGO activities to ensure that our ICANN community and our stakeholders are aware of and have the necessary information to address geopolitical issues that could impact ICANN's role and the community's ability to make policy. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> NEW: DNS Resolvers Used in the EU The ICANN Office of the Chief Technology Office (OCTO) has published OCTO-032: DNS Resolvers Used in the EU. DNS resolution is typically done either by Internet service provider (ISP) resolvers or by public resolvers. In January 2022, ICANN’s Office of the Chief Technical Officer (OCTO) observed that 95% of consumers served by large European Union (EU) consumer ISPs are using their ISP provided Domain Name System (DNS) resolvers. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> NEW: Chair's Blog: Preview of March ICANN Board Workshop The ICANN Board will meet virtually for their second Board Workshop of the year. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> REMINDER: Calling for NextGen@ICANN Applications for ICANN74 ICANN wants to hear from university students living and studying in Europe who are interested in the future of the Internet and in participating in the ICANN74 Policy Forum Meeting. ICANN74 is scheduled to be held in The Hague, Netherlands from 13 to 16 June 2022. If ICANN74 is held virtually, the NextGen@ICANN Program will also be held virtually. The NextGen application window will remain open until Friday, 11 March 2022. Successful candidates will be announced Friday, 25 March 2022 on the ICANN website. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> REMINDER: Apply Now for ICANN and PTI Leadership Positions The ICANN Nominating Committee invites interested individuals to submit applications for key leadership positions within ICANN Supporting Organizations and Advisory Committees, the ICANN Board, and the Public Technical Identifiers (PTI) Board of Directors. Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the Internet's technical coordination and policy development. The deadline to submit applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> is Friday, 11 March 2022 at 23:59 UTC. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> REMINDER: ICANN Community Excellence Award Nomination Period Now Open The nomination period for the ICANN Community Excellence Award is now open. The deadline for submissions is Monday, 21 March 2022 and the winner(s) will be announced at ICANN74. Learn more about the nomination process [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…>. Submit your nominations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…>. Public Comment CLOSES TODAY: Proposal for Myanmar Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Open for submissions Date: Thursday, 13 January 2022 Closed for Submissions Date: Thursday, 03 March 2022 Name Collision Analysis Project (NCAP) Study 2 Documents [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Open for Submissions Date: Thursday, 27 January 2022 Closed for Submissions Date: Friday, 18 March 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> Volume 4, Issue 18 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…> | Next Issue: Monday, 14 March 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001i-p4FmhMwpM3NVC1…>

1 0

IMPORTANT - Session change ICANN73: New gTLD Subsequent Procedures: Operational Design Phase
by Julie Bisland 03 Mar '22

03 Mar '22

Dear all, ⚠️ Due to scheduling conflicts the ICANN73 session New gTLD Subsequent Procedures: Operational Design Phase will take place at a different time and date. ⚠️ Previously scheduled for Wednesday 9 March 2022 at 09:00 am local time (13:00 UTC), it will now take place on Monday 7 March 2022 at 12:30 local time (16:30 UTC). To update your calendars please follow the below steps: 1. Remove the entry for New gTLD Subsequent Procedures: Operational Design Phase on Wednesday 9 March 2022 09:00 am local time. 2. If you had already selected the new gTLD Subsequent Procedures: Operational Design Phase entry in your “My Agenda” on the ICANN73 website, you will not need to re-select it. You will however need to export that session once again to your own calendar. 3. Please refer to the attached “How to Get Organised” email to refresh your memories on how to download sessions! Please reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you have any questions. Kind regards, Nathalie

1 0

FW: Reply to the Deputy Prime Minister, Minister of Digital Transformation of Ukraine
by philippe.fouquart＠orange.com 03 Mar '22

03 Mar '22

Dear Councilors, For your information, David circulated ICANN CEO's reply to the Minister of Digital Transformation of Ukraine on restricting Russia's access to the Internet. Regards, Philippe Orange Restricted From: soac-chairs <soac-chairs-bounces(a)icann.org> On Behalf Of David Olive via soac-chairs Sent: Thursday, March 3, 2022 4:50 AM To: soac-chairs(a)icann.org; mason.cole(a)appdetex.com; lschulman(a)inta.org; wuknoben(a)gmail.com; bruna.mrtns(a)gmail.com; benakin(a)gmail.com; plommer(a)gmail.com; aheineman(a)godaddy.com; sdemetriou(a)verisign.com; seun.ojedeji(a)gmail.com; sb(a)inapp.com; sebastien(a)bachollet.fr; aho(a)usma.ac.pa; eduardodiazrivera(a)gmail.com Cc: Team-leaders(a)icann.org; Sally Newell Cohen <sally.newellcohen(a)icann.org> Subject: [soac-chairs] Reply to the Deputy Prime Minister, Minister of Digital Transformation of Ukraine Dear Community Leaders: As you are likely aware, on 28 February, we received a letter from the Deputy Prime Minister, Minister of Digital Transformation of Ukraine addressed to Göran. ( https://www.icann.org/en/system/files/correspondence/fedorov-to-marby-28feb…) The ICANN org Executive Team understands that there is wide community interest in this matter. As such, and for transparency, I would like to share with you Göran's reply. https://www.icann.org/en/system/files/correspondence/marby-to-fedorov-02mar…. The Internet is a decentralized system. No one actor can control it or shut it down. ICANN's role is to ensure the security, stability, and resiliency of the Internet, and we do this by ensuring that the identifiers we allocate through the Internet Assigned Numbers Authority functions are unique and consistent, in line with global policies. I wish to emphasize that ICANN's role with country-code top-level domains (ccTLDs) is limited and predominantly involves validating requests that come from within the respective country or territory. ICANN cannot take unilateral action against a country to limit or restrict Internet access and we do not play a role in the day-to-day management of ccTLDs, which is a local responsibility. The ICANN org Executive Team understands that this is a difficult time for many members of the ICANN community. We thank you all for your continued commitment to our multi-stakeholder model of participation, inclusiveness, and representativeness, and we look forward to engaging further with you at ICANN73 next week. Best regards, David Olive Senior Vice President, Policy Development Support ICANN David Olive Senior Vice President Policy Development Support Managing Director - ICANN Washington DC Office Internet Corporation for Assigned Names and Number (ICANN) _________________________________________________________________________________________________________________________ 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.

4 4

PLEASE READ: Reminder: Prep Week recordings & ICANN73 Sessions - GNSO Council
by Nathalie Peregrine 03 Mar '22

03 Mar '22

Dear all, Please find below the recordings of both the Policy Update and the GNSO Update webinars which took place during Prep Week. As a reminder, these are sessions aimed at preparing the GNSO, and GNSO Councilors specifically, for further discussions during ICANN73. * GNSO Update Webinar: https://icann.zoom.us/rec/share/bAln5pljZSdd4UJCda6MpUYt5Qtcb4o3yJpCrFJThuU… * Policy Update Webinar: https://icann.zoom.us/rec/share/iIoxWhSuDevyDaBSqT50bv_w5P8QH-x-fUtBC0Ei-oe… KEY POINTS TO REMEMBER: * Email and calendar invitations will not be sent out for ICANN73 sessions. * Refer to the How to Get Organized email circulated<https://mm.icann.org/pipermail/council/2022-February/025439.html> on the GNSO Council mailing list and attached to this email for your convenience. * You will need to register to the ICANN73 website<https://icann.zoom.us/rec/share/iIoxWhSuDevyDaBSqT50bv_w5P8QH-x-fUtBC0Ei-oe…> and download the sessions you are interested in to your individual calendars. ICANN73 SESSIONS WHERE COUNCILOR ATTENDANCE IS HIGHLY ENCOURAGED: 1. Joint GAC and GNSO Session Monday 7 March 2022 at 16:30 local time (20:30 UTC) 1. Joint GNSO & ICANN Board Session Tuesday 8 March 2022 at 09:00 local time (13:00 UTC) 1. GNSO Council meeting Wednesday 9 March 2022 at 12:30 local time (16:30 UTC) 1. Joint GNSO & ALAC session Wednesday 9 March 2022 at 16:30 local time (20:30 UTC) 1. GNSO Council Wrap Up Thursday 10 March 2022 at 10:30 local time (14:30 UTC) ADDITIONAL SESSIONS OF INTEREST TO COUNCILORS: * Monday 7 March: Q&A with ICANN Org Executive Team followed by the Plenary Session: The Global Public Interest Framework: Is it Useful? * Wednesday 9 March: Plenary Session: Evolving the DNS Abuse Conversation * Thursday 10 March: Discussion Forum on Geopolitical Legislative and Regulatory Developments, followed by the ICANN Public Forum and the ICANN Public Board Meeting. Please reach out the gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> should you run into any issues. Kind regards, Nathalie

2 1

GNSO Council Portfolio Management Tool Suite - 09 Mar 2022 Meeting
by Berry Cobb 02 Mar '22

02 Mar '22

Dear all, Please find attached links to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 09 March 2022. 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 * ** denotes the required two work products for review by Councilors in preparation for monthly meetings Key Program Suite Structural Changes for this Period: * None for this period Key Project Changes for this Period: * EPDP_IDN: Project Plan adjustment * RPM_P2: Policy Status Report for UDRP Public Comment – Opens 3 March 2022 * Project Packages: * RDA_ST: https://community.icann.org/x/PQ2HCg * EPDP_IDN: https://community.icann.org/x/cYbOCg * TPR_P1: https://community.icann.org/x/MQDQCQ * EPDP_SCRP_IGO: https://community.icann.org/x/FwDQCQ Key Project/Operations Activities for April 2022: * EPDP_SCRP_IGO – Delivery of Final Report * Next steps on DNS Abuse. – small team * Modifying Consensus Policies response – small team * SSAD ODA response review – small team Please let staff know if you have any questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) berry.cobb(a)icann.org

1 0

SPS follow-up with GNSO-appointed Board members (was: RE: Action Items | GNSO Council meeting 17 February 2022)
by philippe.fouquart＠orange.com 02 Mar '22

02 Mar '22

Dear Councilors, In follow up to Action Item 11 from our last Council call, I wanted to take the opportunity to share some further details from leadership's conversation with Becky and Matthew following the Council's Strategic Planning Session (SPS). Follow up after GNSO policy recommendations are adopted by the GNSO Council and GNSO Council - Board interaction were identified as key topics of mutual interest. It was noted that in the past there has been little dialogue between the Board and the GNSO Council outside of ICANN meetings, and generally only in a formal manner such as through correspondence which may cause unnecessary delay. Similarly, it was noted that there is currently no joint problem-solving mode - each group works in its own silo until it is time to pass it on or pass it back to the next in line. Fortunately we have seen some new initiatives that try to break that mold, such as the informal consultation that took place in the context of the EPDP Phase 1 Recommendation 12 as well as the participation of Board liaisons in recent EPDPs. In order to facilitate further exchanges on this topic as well as exploring other ideas and suggestions, we thought it might be of interest to set up an informal brainstorming session for interested Board and Council members in the margins of the follow up SPS meeting to tackle questions such as: * What are the main obstacles to effective Board-Council interaction and how can these be overcome? * How can additional transparency be introduced in the post-Council adoption part of the PDP? * How can the Council facilitate the Board's consideration of whether adoption of PDP recommendations are in the best interest of the ICANN community or ICANN org? * Should further interaction be built into the process as part of the handover of GNSO Council recommendations to the ICANN Board post Council adoption? The idea is that the session would be facilitated by Melissa Allgood, who also facilitated our SPS, and that it would be an informal (non-recorded) brainstorming session to allow for the free exchange of ideas and suggestions that may help inform possible next steps. If there is support for this idea, leadership will work with Becky and Matthew to further develop the concept for this brainstorming session that is expected to be scheduled in the May timeframe. Thank you. Regards, Philippe on behalf of Council Leadership Orange Restricted From: council <council-bounces(a)gnso.icann.org> On Behalf Of Nathalie Peregrine via council Sent: Friday, February 25, 2022 4:43 PM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [council] Action Items | GNSO Council meeting 17 February 2022 Dear Councilors, With apologies for the delay (the GNSO Council leadership call to review the AIs was held later than usual) please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 17 February 2022. 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 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 Motion to approve Chris Disspain to serve as the GNSO's ICANN Fellowship Program mentor Action Items: * The GNSO Secretariat to notify Chris Disspain that the GNSO Council has approved his appointment as the GNSO's ICANN Fellowship Program mentor. * The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program. * The GNSO Council requests the GNSO Secretariat to send a response to the applicant who was not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise.[ Item 4: COUNCIL DISCUSSION - Update on the Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) Pilot Action Items: * With respect to the suggested revisions to the Working Group Self-Assessment, the CCOICI to consider those made during the meeting for incorporation in its Final Report which will be submitted after review of public comments (namely, whether it should be possible for respondents who choose to, to have their name published in the summary report and adding "At-Large Community" as one of the respondent affiliations to the survey). * Councilors to review the proposed changes and new documents (see https://mm.icann.org/pipermail/council/2022-February/025426.html) and share any suggestions / comments with the mailing list so that these can be considered by the CCOICI. Item 5: COUNCIL DISCUSSION - Update on GNSO Council Implementation of Workstream 2 (WS2) Action Items: * The GNSO Council to consider the proposal for the CCOICI to undertake the implementation work of relevant WS2 recommendations and if there is no objection from the Council by the next Council meeting, the CCOICI to start the deliberation based on the path proposed in the presentation provided during the Council meeting (see https://gnso.icann.org/sites/default/files/policy/2022/presentation/update-…). Item 6: COUNCIL DISCUSSION - ICANN73 Planning Action Items: * GNSO Council leadership to initiate a discussion on the GNSO Council list concerning the Board topics to obtain input on proposed speaking points / positions. GNSO Secretariat to send out list of ICANN73 sessions of interest to GNSO Council * Council leadership to submit proposed Council topics (update on EPDP Phase 2 small team activities and SubPro ODP to Board Support) Item 7: COUNCIL DISCUSSION - Status Update on Select Strategic Planning Session Action Items Action Item 1: Council leadership to develop a first draft of a proposed "Council Commitments" for Council consideration. Action Item 6: Council leadership to explore possibility to set up a regular informal Q & A session with ICANN CEO for GNSO Council, either as part of future SPS or intersessionally. / Action Item 12: To check on the progress of the implementation of these action items as well as allow for updates to be made, a post-SPS meeting will be scheduled in the 4-6 month timeframe after this meeting. Following Action Items: None - AI6 is considered complete as a meeting has been scheduled that will allow for informal Q & A session with ICANN CEO as well as review of outstanding SPS Action items. Action Item 11: Council leadership to set up an informal conversation with Becky and Matthew to obtain their feedback on the SPS discussions as well as their suggestions on how the Council can best engage with the ICANN Board on this topic. Further Action Item: Council leadership to share further details from the meeting with Becky and Matthew with the Council mailing list. Council members to provide their input on these details and more specifically the suggestion to schedule a brainstorming session with interested Board members to discuss in an informal and open manner how interaction and engagement between the GNSO Council and ICANN Board can be improved. Council leadership to continue working on a proposed approach for such a session. Item 8: ANY OTHER BUSINESS 8.1 - EPDP Phase 2 small team update Action Items: This work is in progress. 8.2 - DNS abuse small team update Action Items: This work is in progress. 8.3 - SubPro ODP Update Action Items: GNSO leadership to develop a draft of next steps for the GNSO Council to review to discuss with the Board at the ICANN73 bilateral meeting. See above - COMPLETED. 8.5 - GNSO Council Representative WS2 Community Coordination Group - Olga Cavalli Action Items: On behalf of the GNSO Council the GNSO Secretariat will thank Olga Cavalli for volunteering to be the GNSO Council Representative to the WS2 Community Coordination Group. Thank you! Nathalie _________________________________________________________________________________________________________________________ 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

ICANN73 Virtual Community Forum | Guidelines for Speakers
by Devan Reed 01 Mar '22

01 Mar '22

Dear all, As we are just a week away from the ICANN73 Virtual Community Forum, the ICANN Language Services Team has created a document to serve as a guideline for speakers. As a reminder, GNSO-supported ICANN meetings do not use interpretation services. However, the reminders and pointers included are useful for all. Thank you! Kind regards, Devan

1 0

EPDP Phase 2 Small Team Update
by Marika Konings 01 Mar '22

01 Mar '22

Dear All, On behalf of Sebastien Ducos, lead for the EPDP Phase 2 Small Team, I am sharing with you a proposed initial response to the ICANN Board’s letter of 24 January. The idea would be that this letter is sent by the end of this week in advance of the ICANN Board – GNSO Council joint meeting at ICANN73 during which this topic is expected to be discussed further. For your information, you will find below the most recent communication to the EPDP Phase 2 small team that sets out the proposed next steps to provide the GNSO Council with a response to the questions outlined in the assignment by the end of March. This will hopefully allow the Council to consider this input and agree on the next steps during its April meeting, or if additional time is needed, the May Council meeting at the latest. Note that you’ll have a further opportunity to discuss the timeline and proposed next steps during the upcoming Council meeting at ICANN73. If you have any concerns/comments about the attached letter, please indicate so on the list at the latest by Thursday 3 March. Best regards, Marika From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces(a)icann.org> on behalf of "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Date: Friday, 25 February 2022 at 11:36 To: "gnso-epdpp2-smallteam(a)icann.org" <gnso-epdpp2-smallteam(a)icann.org> Subject: [GNSO-EPDPP2-SmallTeam] EPDP Phase 2 Small Team Update Dear All, Thank you to those who were able to provide initial input by the deadline and thank you to those who are still working on it. I appreciate that there is a lot of information to digest and consultations to undertake with your respective groups. As was previously indicated, this input is not expected to be the final determination by the small team, but the idea was that it would provide some initial indications of the common as well as different views that would allow the GNSO Council to provide the ICANN Board with a high-level update during its joint session at ICANN73. At the same time, there is an expectation that the small team will be able to provide its input to the GNSO Council as soon as feasible as this is just the first step in a longer process. As such, I would like to suggest proposing the following to the GNSO Council with regards to next steps and timeline: Date What Whom Wednesday 2 March Initial reactions to google doc questions (Q1-7) Small team (those that have not provided input yet) Friday 4 March Questions concerning ODA (Q.A-C) Small team (those that have not provided input yet) Thursday 3 March Share high level summary of responses to google doc questions with small team for review (Q1-7) Sebastien Ducos Friday 4 March Share high level summary of responses to google doc questions with GNSO Council (Q1-7) Sebastien Ducos Tuesday 8 March Share high level summary of responses during ICANN Board – GNSO Council session (noting that this is initial input that the Council will need to consider further) Sebastien Ducos Wednesday 9 March GNSO Council Meeting – update on small team progress and debrief from Council – Board meeting GNSO Council By 31 March Small team to finalize its input to the GNSO Council Small Team 14 April GNSO Council meeting - Council to review small team input and determine response to the ICANN Board / next steps GNSO Council 19 May (if necessary) GNSO Council meeting - Council to review small team input and determine response to the ICANN Board / next steps GNSO Council Note that I do not anticipate that the work of the small team will end by 31 March. As also noted previously, regardless of the path that is ultimately chosen, whether the Board makes a determination next on whether or not to adopt all or part of the recommendations or whether the Council decides to undertake further work on the recommendations, there is a likely role for the Council to take a further look at the recommendations themselves. I anticipate that the Council will continue to lean on the expertise of this small team to assist with such an effort. I am of the view that such further consideration would benefit from informal interaction with interested Board members. This has proven to be very beneficial in instances where the ICANN Board has expressed concerns as recent experience in the context of the EPDP Phase 1 recommendation 12 demonstrated. Of course, we are already benefiting from the participation of Becky in the small team, as the Board liaison to the EPDP Phase 2, but maybe informal interaction could be considered between the small team and the Board GDPR Caucus to better help inform further consideration of potential changes / modifications. Before sharing this suggestion with the Council, I would appreciate hearing your feedback on this idea. In preparation for ICANN73, Council leadership would like to provide the ICANN Board with an update on the work that has been undertaken to date as well as expected next steps & timing. Please find this in the proposed draft message attached. I plan to share it with the GNSO Council for its review on Monday. I hope this approach can count on your support. As always, please feel free to share your comments and suggestions. Kindly, Sebastien Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1709708321] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0