March 2022 - council - lists.icann.org

On in 30 mins: joint GNSO & GAC Session 16:30 AST - 20:30 UTC
by Nathalie Peregrine 07 Mar '22

07 Mar '22

Dear all, A reminder to join the upcoming joint GNSO & GAC Session on in about 30 mins’ time. Please refer to the ICANN73 schedule<https://73.schedule.icann.org/agenda> to retrieve the Zoom access information. You will need to be logged in to the website to access the relevant pages. Thank you! Nathalie

1 1

FW: [gnso-secs] New GNSO Counselor
by Nathalie Peregrine 07 Mar '22

07 Mar '22

Dear all, Please see below the communication from the Chair of the RrSG announcing the election of Theo Geurts as RrSG councilor, replacing Kristian Ørmen. His first Council meeting in this role will be this coming Wednesday during ICANN73. Please join me in welcoming Theo to the GNSO Council! Kind regards, Nathalie From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Reply to: Ashley Heineman <aheineman(a)godaddy.com> Date: Monday, 7 March 2022 at 15:23 To: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Cc: Zoe Bonython <secretariat(a)icannregistrars.org>, Kristian Ørmen <koe(a)one.com>, Theo Geurts <email(a)dcx.nl> Subject: [gnso-secs] New GNSO Counselor Dear GNSO Secs, Please note that the Theo Geurts has been elected and thus replaced Kristian Ormen as RrSG Councilor for the remainder of his term… as Kristian is leaving us. Please let me know if you need any additional information to make this change official. Thanks, Ashley Heineman Chair, RrSG

7 6

On today ! Joint GNSO & GAC Session: PLEASE READ: ICANN73 Sessions - GNSO Council
by Nathalie Peregrine 07 Mar '22

07 Mar '22

Dear all, 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 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/iIoxWhSuDevyDaBS…> 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

1 0

Please read: Upcoming GNSO Council meeting prep 09 March 2022 at 12:30 AST 16:30 UTC
by Nathalie Peregrine 07 Mar '22

07 Mar '22

Dear all, A few reminders of prep for the Council meeting 09 March 2022 at 12:30 AST, 16:30 UTC, this week: 1. Please review the new GNSO Council meeting Cheat Sheet [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. 1. Several slide decks are available and published on the Council agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>. All documents mentioned on the Council agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> are listed on the Document wiki page<https://community.icann.org/display/gnsocouncilmeetings/Documents+2022-03-09> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/download/attachments/150178775/GNSO_Council_Pro…> and the Project List<https://community.icann.org/download/attachments/150178773/GNSO_Council_Pro…> which have been updated for this month’s Council meeting. 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Nathalie

1 0

Re: [council] DNS abuse small team update
by Steve Chan 07 Mar '22

07 Mar '22

Dear Councilors, I just wanted to confirm that the letters were sent to the ALAC, GAC, SSAC, and the DNS Abuse Institute earlier today. Council leadership thought it helpful that the letters be sent prior to the Council’s bilateral sessions with the GAC and ALAC. Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of Steve Chan via council <council(a)gnso.icann.org> Reply-To: Steve Chan <steve.chan(a)icann.org> Date: Thursday, March 3, 2022 at 2:45 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] DNS abuse small team update 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] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1rpmBJZ5Ewbzt…>. 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

Slide deck | ICANN73 | Finalized Agenda Joint Session: ALAC and GNSO Council | Wednesday, 09 March 2022 16:30 AST
by Terri Agnew 07 Mar '22

07 Mar '22

Dear all, Please find attached the slides for the Joint Session: ALAC and GNSO Council<https://73.schedule.icann.org/meetings/2ZFiYDeZBdKfZL42r> on Wednesday, 09 March 2022 16:30 AST. 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 Thank you. With kind regards, Terri --- Terri Agnew Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: terri.agnew.icann 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

FW: [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics
by philippe.fouquart＠orange.com 06 Mar '22

06 Mar '22

Dear Councilors, Please consider the following and attached correspondence from the Board. Regards, Philippe -------- Message d'origine -------- De : Wendy Profit <wendy.profit(a)icann.org> Date : 06/03/2022 22:03 (GMT+01:00) À : manal.ismail(a)board.icann.org, manal(a)tra.gov.eg, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc : Maarten Botterman <maarten.botterman(a)board.icann.org>, gnso-chairs(a)icann.org, GACSTAFF <gac-staff(a)icann.org>, gnso-secs(a)icann.org, Board Ops Team <board-ops-team(a)icann.org>, Correspondence <Correspondence(a)icann.org>, Secretary <secretary(a)icann.org> Objet : [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics Dear Manal and Philippe, Please find the attached letter from ICANN Chair Maarten Botterman regarding a proposed formal consultation between the GAC and GNSO Council on how to handle the subject of closed generics in gTLD applications. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ 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

Update on the UDRP Policy Status Report
by Julie Hedlund 04 Mar '22

04 Mar '22

Dear Councilors, Please see the email below, sent on behalf of our colleagues from the Global Domains & Strategy team. Kind Regards, Julie Julie Hedlund, Policy Director 4 March 2022 Dear Councilors, The Uniform Domain Name Dispute Resolution Policy (UDRP) Policy Status Report (PSR) has been published for Public Comment. Please find the details here: https://www.icann.org/en/public-comment/proceeding/policy-status-report-uni… Note the public comment proceeding will be extended by 7 days due to its overlap with ICANN73 and will close at 23:59 UTC on 19 April 2022. ICANN Org looks forward to receiving input from the GNSO and community on the data and analysis included in the report via Public Comment. Once public comments have been received, ICANN Org will update the Policy Status Report to include relevant information. The updated report will then be returned to the GNSO Council for its consideration. ICANN Org encourages the Council to spread the word about this Public Comment opportunity and to share the report with your stakeholder groups and the constituencies. Please let us know if you have questions or need additional information. We thank the GNSO Council, the GNSO and broader community in advance for reviewing and providing input on the UDRP Policy Status Report. Sincerely, ICANN Org Global Domains & Strategy team

1 0

REMINDER: PLEASE READ: ICANN73 Sessions - GNSO Council
by Terri Agnew 04 Mar '22

04 Mar '22

Dear all, 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 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/iIoxWhSuDevyDaBS…> 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

1 0

EPDP Phase 2 Small Team - Summary Update
by Sebastien＠registry.godaddy 04 Mar '22

04 Mar '22

Dear All, Please find the EPDP Phase 2 Small Team summary update ahead of next week’s ICANN. This is intended to be shared with the Board and the Community, as required, during our bilateral meetings. Disclaimer: It is important to note that this high-level summary update is based on the input received from small team members to date. Not all groups may have provided or finalized their input, nor has the Council considered this input. The small team will continue its deliberations post-ICANN73 in view of providing a response to the GNSO Council on the questions that are part of its assignment, namely: * 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 Council did think it would be of interest to the Board and the broader community to get a sense of the direction of travel based on input from the members of the small team to date. This is what this high-level summary aims to do. It is worth pointing out that many of the comments are in line with comments and suggestions that have already been raised in the meetings to date. High-level summary of small team input to date (2 March 2022): 1. The small team has identified several clarifying questions in relation to the ODA. These have been shared with ICANN org. The small team expects that the responses to these clarifying questions will assist the small team a better understanding of the findings of the ODA; 2. Similarly, small team members have identified a number of assumptions that seem to be inconsistent with the intent of the policy recommendations such as the intent for the Central Gateway to be the single point of contact for requestors instead of going directly to Contracted Parties or having governmental accreditation authorities have a role in the relay of requests; 3. The small team also pointed to a number of issues that may not have been covered or not sufficiently covered in the ODA such as: the concept of “signed assertions” which may have been misunderstood and as a result not included in the ODA; lack of clarity in relation to controllership and roles and responsibilities of the different parties, and; the breakdown of cost could have been clearer about operational costs that are not expected to recovered and the costs that would be expected to be recovered from users. 4. In relation to the concerns expressed by the ICANN Board, the small team has attempted to determine through a number of questions whether small team members share these concerns, and if so, what could/should be further considered to address these concerns: a. Most small team members seem to be of the view that the ODA does not provide enough information to confidently determine the cost / benefit. Some point to the inability to predict costs based on usage, the high variability and range of costs and lack of information on the specific costs of the different components of the system. b. Although some note that this the determination of costs / benefit is one that the Board is expected to make, many small team members are of the view that for certain aspects of the SSAD the costs / complexity outweigh the benefits and point to the different minority statements that accompany the Final Report for further details. c. Some support is expressed for implementing either an SSAD Pilot (possibly on a voluntary basis) or a lightweight ticketing system that could serve as a central point of collection of disclosure requests. These options could provide further insights into the demand and other metrics to help inform subsequent decisions on the SSAD. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_86468551] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0