April 2022 - council - lists.icann.org

GNSO Council Absence Notification Form: Marie Pattullo
by GNSO Council via ICANN April 6, 2022

April 6, 2022

Full Name of Officer: Mason Cole Officer Email Address: mason.cole(a)appdetex.com Date Prepared: 6 April 2022 GNSO Organization: Business Constituency Officer Position or Title: Chair Name of Absent Councilor: Marie Pattullo Voting Remedy: Temporary Alternate Temporary Alternate Information Reason(s) for or condition(s) leading to the remedy: Marie Pattullo is unavailable for the 14 April GNSO Council meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: All matters before the GNSO Council. Date upon which the remedy will expire or terminate: 15 April 2022 Full Name of Councilor's Temporary Alternate: [Note: if not already published and available, a short bio and Statement/Disclosure of Interest should be prepared by the Temporary Alternate and delivered to the GNSO Secretariat in advance of any discussion or voting scheduled to take place]. Steve DelBianco Temporary Alternate Email Address: sdelbianco(a)netchoice.org By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

GNSO Council Portfolio Management Tool Suite - 14 Apr 2022 Meeting
by Berry Cobb April 6, 2022

April 6, 2022

Dear all, Please find attached links to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 14 April 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: * PMT: EPDP-P1 IRT now linked to its project plan. The IRT published its plan and timeframe at ICANN73. Public comment for the draft policy is anticipated in Q3 2022. As a result, I’ve removed the previous detail of all the Wave 1 report updates to impacted consensus policies to slim down the PMT. As the IRT project plan is updated, it will automatically update the PMT. * PMT: Added the NCAP projects as part of the gTLD Program. The GNSO did not sponsor these efforts, but GNSO resources participate and this is a best effort attempt to track that activity. * PMT: Reviews Program updated based on latest Board resolution deferring SSR3 Review. This is a best effort representation for reviews that impact the GNSO and in summary, all are linked to completion of the Holistic Review Pilot. At this time, there is no precise date when that effort will begin, but defining Terms of Reference has begun. And as noted on the ADR, the GNSO Council is monitoring for any implementation required as part of previously completed Review recommendations. * PMT: Added a placeholder section to develop and map election cycles for GNSO Chair and Board seats #13 and #14. This will be completed for the May cycle. * PMT: Updated CCOICI with dedicated plans for each assignment and task force, leaving intact a review of the pilot by the GNSO Council. * ADR: The ADR is now updated to reflect required actions and decision ahead of the GNSO one month after the AGM in September. Key Project Changes for this Period: * SSAD ODA response review – small team * EPDP_SCRP_IGO – Delivery of Final Report * Next steps on DNS Abuse – small team * SubPro: Closed Generics – small team * 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 May 2022: * EPDP_SCRP_IGO – Consider resolution on Final Report * EPDP_IDN: Project Plan adjustment * Modifying Consensus Policies response – small team * RPM_P2: Council to consider Policy Status Report for UDRP Review 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

FW: [Ext] RE: Modifying consensus policies
by philippe.fouquart＠orange.com April 6, 2022

April 6, 2022

Dear Councilors, Please see Theresa's early input for future exchanges, soon to be scheduled, and follow-up to the "modifying consensus policy" thought paper. Regards, Philippe Orange Restricted From: Theresa Swinehart <theresa.swinehart(a)icann.org> Sent: Tuesday, March 29, 2022 12:11 AM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc: Karen Lentz <karen.lentz(a)icann.org>; Steve Chan <steve.chan(a)icann.org>; David Olive <david.olive(a)icann.org>; Mary Wong <mary.wong(a)icann.org>; gnso-secs(a)icann.org; gnso-chairs(a)icann.org Subject: Re: [Ext] RE: Modifying consensus policies Dear Philippe, I hope you and the team have recovered well from the ICANN 73 meeting, and we appreciated all the discussions. Thank you also for proposing the opportunity to engage further on this topic through a series of meetings. We are working with the GNSO Secretariat on scheduling a time. In addition to the topics mentioned in your previous email, here are a few questions that we would add in advance of our next discussion. 1. We have seen some instances in recent policy work where a new set of policy recommendations explicitly or implicitly requires updates to existing policies. We do recognize that in the context of the EPDP Ph 1 Recommendation 27 these updates could only be considered in detail during the implementation phase as a result of the time constraint that existed. Nevertheless, we think there may still be value in considering how the Council and the org might work better together in the future to identify and address when such updates are needed and how these are expected to be made. Does the Council agree that there is value in this, and if so, what could be done better / differently? 2. How can this "thought paper" supplement or act as input to support discussions around the current pipeline of improving different steps throughout the PDP process? We look forward to our continued engagement with the Council and the small team on this topic. Thank you, Theresa From: Theresa Swinehart <theresa.swinehart(a)icann.org<mailto:theresa.swinehart@icann.org>> Date: Tuesday, February 8, 2022 at 10:57 To: "philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: Karen Lentz <karen.lentz(a)icann.org<mailto:karen.lentz@icann.org>>, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>, Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Subject: Re: [Ext] RE: Modifying consensus policies Dear Philippe, Thank you for your email, and for the good suggestions on next steps. We look forward to working with you and the team and scheduling times for further discussions. Hoping all are well, Kind regards, Theresa From: "philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Date: Tuesday, February 1, 2022 at 11:19 To: Theresa Swinehart <theresa.swinehart(a)icann.org<mailto:theresa.swinehart@icann.org>> Cc: Karen Lentz <karen.lentz(a)icann.org<mailto:karen.lentz@icann.org>>, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>, Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, "gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Subject: [Ext] RE: Modifying consensus policies Dear Theresa, Thanks again for sharing this "thought paper" and allow the GNSO to engage in this. As you are aware, following your email of October 23rd, the GNSO Council formed a small team consisting of Council members as well as interested SG/C representatives to review the discussion draft and propose to the GNSO Council how to proceed. The Council and the small team appreciate the engagement with ICANN org on some of the procedural questions and welcomes the invitation to engage on this important topic. However, instead of sending papers and letters back and forth, the Council is of the view that this topic may benefit from a dialogue between Council, interested SG/C representatives, ICANN org as well as interested Board members. To this end, we would like to propose to schedule a meeting, or a series of them, during which we can go into further details on topics and questions such as: 1. Ensuring a common understanding of the problem we trying to fix; 2. Is the "fixing" expected to require changes to existing procedures or do existing procedures provide for sufficient flexibility to address the problem should it arise again? 3. Having a common assessment of the urgency of the problem so we can decide how to prioritize this effort and ensure that community resources are available to work on this topic jointly; The GNSO Council wants to emphasize that it fully supports the notion that any modifications to existing gTLD Consensus Policies need to be clear and should be identified as part of any policy recommendations that are submitted to the GNSO Council and subsequently the ICANN Board. The Council realizes that because of the time constraints under which it and the ICANN Board operated in the context of the EPDP Phase 1, this clarity may not have been provided in all cases, which resulted in delays and questions around the intended impact on some existing Consensus Policies. We have nonetheless been able to resolve these issues through our existing processes and procedures, but obviously, we would have saved substantial time and frustration if we had not found ourselves in this position in the first place. If you are supportive of this approach, we would suggest that you work with the GNSO Secretariat to identify a time / date that works for all those that should be part of this conversation. Thank you. Best regards, Philippe Orange Restricted From: Theresa Swinehart <theresa.swinehart(a)icann.org<mailto:theresa.swinehart@icann.org>> Sent: Saturday, October 23, 2021 1:21 AM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: Karen Lentz <karen.lentz(a)icann.org<mailto:karen.lentz@icann.org>>; Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>; David Olive <david.olive(a)icann.org<mailto:david.olive@icann.org>>; Mary Wong <mary.wong(a)icann.org<mailto:mary.wong@icann.org>> Subject: Modifying consensus policies Dear Philippe, I would like to share with you and the GNSO Council a discussion draft of the attached paper, Modifying Consensus Policies. The ICANN organization has developed this paper as a thought exercise to share with the community for information and input on existing processes. As mentioned in some of our previous interactions, this piece has been developed within the org, considering what procedures are in place for modifying consensus policies, and where there may be gaps, ambiguities, or opportunities for additional collaboration. The Board has expressed interest in understanding these processes and discussing possible mechanisms to address where there are identified and agreed needs for greater clarity or elaboration. As the GNSO's processes are interwoven with those of the Board and org in the consensus policy lifecycle, the org is seeking input from GNSO stakeholders before taking this paper to the Board. To date for the org, this review of applicable procedures to modify policies has been helpful in identifying gaps that might benefit from further clarification or discussion, relating to how to modify an existing policy in varying circumstances. Some possible gaps are further described in section 3 of this paper, to provide an opportunity for community discussions on identifying the source of gaps and confirming where they exist. In the spirit of sharing ideas and observations, we hope you also find this useful, and the org looks forward to hearing from GNSO stakeholders on these topics. I appreciate that this comes at a busy time, and look forward to engaging on this in due course. And, wishing the best for a successful ICANN72 meeting. Kind regards, Theresa _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

Consideration for policy review
by philippe.fouquart＠orange.com April 6, 2022

April 6, 2022

Dear Councilors, Since we are now just about two weeks before our call, this is a reminder to consider taking the conversation that Flip initiated in his personal capacity during wrap up to your SG/Cs for further consideration for a review of the impact of conflicts such as the war in Ukraine on existing gTLD policies. Upon request we may obviously add an AOB to our call. Regards, Philippe Orange Restricted From: Flip Petillion <fpetillion(a)petillion.law> Sent: Wednesday, March 9, 2022 4:17 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: Re: An additional issue for AOB at our next meeting Thank you Philippe, That indeed was the intention. Best regards, Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> [cid:image002.png@01D849F4.9D6BDF90]<https://www.petillion.law/> Attorneys - Advocaten - Avocats From: "philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>" <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Date: Wednesday, 9 March 2022 at 16:12 To: Flip Petillion <fpetillion(a)petillion.law<mailto:fpetillion@petillion.law>>, "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: An additional issue for AOB at our next meeting Dear Flip, Thanks for the proposal. We will have this as an AOB item to give you the opportunity to elaborate even as an individual, for the benefit of those who would not have consulted their mailbox. Given the importance of those events, the expectation would only be at this stage to bring councilors attention to this question of whether any policy related initiative is warranted with this context, not for them to "give an answer" this afternoon. So probably not much of a substantive discussion to be had, but as you point out, this will enable councilors to consult with the SG/Cs and come back to Council as they see fit. Regards, Philippe Orange Restricted From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Flip Petillion via council Sent: Wednesday, March 9, 2022 11:30 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] An additional issue for AOB at our next meeting Dear All: I propose that we put the following issue as an AOB on the agenda of our next meeting. The incident that generated the letter from the Deputy Prime Minister, Minister of Digital Transformation of Ukraine, and the response by G. Marby, raises questions on ICANN's role at the occasion of certain Internet activities in conflict situations. There is more to this than the question of restricting access to the Internet, the need to act neutral and within ICANN's core mission. The questions cover a broad scope of legal and ethical considerations that may need to be fully explored. Above all, the security and stability of the Internet and the systems reliant upon it are at risk. The question is: how does ICANN ensure the openness (including accessibility) of the Internet in conflict situations and how does ICANN manage the impact on the security and stability of the Internet? In my humble opinion, this calls for a thorough impact analysis and policies that effectively map, identify and combat forms of abuse as warranted by overarching global security concerns. Ultimately, this approach may set more realistic expectations in the Community. I have not been able to discuss this at the IPC and, hence, the IPC has not been able to express a position on this subject, yet. But I think the discussion is timely. I propose that the GNSO councilors go back to their SGCs and inform the GNSO council if they wish to ask council to consider the impact analysis that I am referring to above. Best regards, Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> [id:image001.png@01D3691D.DA7539C0]<https://www.petillion.law/> Attorneys - Advocaten - Avocats _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

Proposed Agenda | GNSO Council Meeting | 14 April 2022 at 13:00 UTC
by Nathalie Peregrine April 4, 2022

April 4, 2022

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 14 April 2022 at 13:00 UTC. Draft GNSO Council Agenda 14 April 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/_RQiCw. 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 13:00 UTC: https://tinyurl.com/mwkm43zr 06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris; 16:00 Moscow; 23:00 Melbourne GNSO Council Meeting Remote Participation: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 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 17 February 2022 were posted on 07 March 2022. Minutes<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> of the GNSO Council meeting on 09 March 2022 were posted on 24 March 2022 . Item 2: Opening Remarks / Review of Projects & Action List (10 minutes) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> Item 3: Consent Agenda (0 minutes) * None Item 4: COUNCIL DISCUSSION - Small Team Reviewing the System for Standardized Access/Disclosure (SSAD) Operational Design Assessment Preliminary Draft Report (30 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 met with the ICANN Board on 8 March during ICANN73, just prior to the March Council meeting and discussed the ODA and the efforts of the small team. The small team has continued to meet and has focused on an SSAD Proof of Concept while also engaging with members of the Board GDPR Caucus and ICANN org. The small team delivered its preliminary report<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> to Council on 4 April 2022. Here, the Council will discuss the small team’s preliminary report and discuss next steps, including providing an update to the ICANN Board on the status of work and expected timing. 4.1 – Introduction of topic (Sebastien Ducos, small team lead) 4.2 – Council discussion 4.3 – Next steps Item 5: COUNCIL DISCUSSION - Overview of the EPDP on Specific Curative Rights Protections for IGOs Final Report (30 Minutes) In January of 2020, the GNSO Council approved an Addendum<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> to the All Rights Protection Mechanisms (RPMs) in All gTLDs PDP charter to support work related to Recommendation 5 from the IGO-INGO Access to Curative Rights Protections Mechanisms PDP. During the Council’s August meeting, the Council voted to take the procedural step of initiating an EPDP to allow the efforts of the IGO Work Track to continue in an uninterrupted manner, with an EPDP charter<https://gnso.icann.org/sites/default/files/file/field-file-attach/igo-epdp-…> that substantively mirrors the Addendum that governed the IGO Work Track. The EPDP Team published its Initial Report for public comment<https://www.icann.org/en/public-comment/proceeding/initial-report-epdp-spec…> on 14 September 2021. The EPDP Team duly took into consideration the 33 comments received and made revisions as applicable to its draft recommendations. The EPDP Team completed its deliberations, revised its final recommendations, and prepared its Final Report. The EPDP Team reached full consensus on its five recommendations and delivered its Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-spec…> on 4 April 2022. While the Council will not be voting on the Final Report during this meeting, a draft motion [ADD LINK WHEN AVAILABLE] was also shared on 4 April 2022, which continues a recent practice of the Council reviewing and discussing PDP/EPDP final reports in detail prior to voting on them, generally at the subsequent meeting. Here, the Council will receive an overview of the five recommendations contained in the EPDP Team’s Final Report. 5.1 – Introduction of topic (Council leadership) 5.2 – Update (EPDP Team Chair, Chris Disspain) 5.3 – Council discussion 5.4 – Next steps Item 6: 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. The Council sent outreach letters to the ALAC, GAC, SSAC, and the DNS Abuse Institute, with input due on 4 April 2022 (after an extension was granted). During the intervening time, the small team has worked to more precisely understand its work, developing and discussing a draft work plan<https://urldefense.com/v3/__https:/docs.google.com/document/d/1yfMsj9cv8YqU…>. The work is broken into several phases, starting with the aforementioned outreach to the community, understanding the current landscape of DNS abuse, considering which elements of DNS abuse appear inadequately mitigated AND are in scope for GNSO policy making (if any), then making recommendations on next steps to the Council. Here, the small team will provide an update on its efforts and explain expected next steps. 6.1 – Introduction of topic (Small team co-leads: Mark Datysgeld & Paul McGrady) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - Closed Generics Small Team Update (15 Minutes) On 6 March 2022, the ICANN Board sent a letter<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/botte…> to both the GNSO and the GAC, inviting them to “explore a mutually agreeable way forward, for which the Board could facilitate a dialogue to formulate a workable framework to identify and handle closed generic applications for the immediate next round of new gTLDs.” Shortly thereafter, and as requested by the Board, ICANN org prepared a draft Framing Paper<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/gnso-…> to support the potential collaboration between the GNSO and the GAC. The Council established a small team to consider both the letter and framework, to determine next steps. To support this work, Council leadership and staff developed an assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20A…>, which helps make clear the narrow ask of the small team (i.e., whether the GNSO Council is open to working with the GAC to seek to develop a framework on closed generics). All of the more substantive steps, both to determine the parameters and modalities for a potential GNSO/GAC joint group, as well as seeking to establish a framework for closed generics, are out of scope for this small team. Here, the Council will receive an update on the work of the small team. 7.1 – Introduction of topic (Council leadership) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (10 minutes) 8.1 – ICANN74 update and planning 8.2 - Council expertise survey reminder _______________________________ 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 13:00 UTC Local time between March and November in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 06:00 San José, Costa Rica (CST) UTC-6 07:00 New York/Washington DC, USA (EDT) UTC-4 09:00 Buenos Aires, Argentina (ART) UTC-3 10:00 Rio de Janeiro, Brazil (BRT) UTC-3 10:00 London, United Kingdom (BST) UTC+1 14:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 14:00 Paris, France (CEST) UTC+2 15:00 Moscow, Russia (MSK) UTC+3 16:00 Singapore (SGT) UTC+8 21:00 Melbourne, Australia (AEDT) UTC+11 23:00 ---------------------------------------------------------------------------- DST starts 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. DST ends on Sunday 30 October 2022 for EU countries, and on Sunday 06 November 2022 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and https://tinyurl.com/mwkm43zr.

1 0

FW: Publication of SubPro ODP Community Status Update for 28 March 2022
by philippe.fouquart＠orange.com April 4, 2022

April 4, 2022

Dear Councilors, On Jeff's behalf, please find below the first SubPro ODP Community Status Update. Regards, Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 29/03/2022 20:27 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, "Sebastien(a)registry.godaddy" <sebastien(a)registry.godaddy>, "Tomslin Samme-Nlar (mesumbeslin(a)gmail.com)" <mesumbeslin(a)gmail.com> Cc : Steve Chan <steve.chan(a)icann.org> Objet : FW: Publication of SubPro ODP Community Status Update for 28 March 2022 Dear Council Leadership, Can you please forward this to the Council? This Status Update is one of the milestones that the ODP Team committed to in the timeline provided to Council in February. Please let me know if you have any questions. Sincerely, Jeff [cid:com_samsung_android_email_attachmentprovider_5_116116_RAW_1648590334527] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Chris Bare <christopher.bare(a)icann.org> Sent: Tuesday, March 29, 2022 1:19 PM To: Jeff Neuman <jeff(a)jjnsolutions.com> Cc: SubPro ODP Mailman List <subpro-odp(a)icann.org> Subject: Publication of SubPro ODP Community Status Update for 28 March 2022 Hi Jeff, The org has published the first Community Status Update for the SubPro ODP. This is the first of three such updates planned during the ODP (see high level timeline on the SubPro ODP page). The update appears on the SubPro ODP page in the table titled ‘Announcements, Blogs, Webinars, and More’ as well as in the ‘Work Products’ found further down the page. Please let us know if you have any questions or comments. Link to the SubPro ODP Community Status Update (28 March 2022) https://www.icann.org/en/system/files/files/community-status-updates-28mar2… Link to the SubPro ODP page: https://www.icann.org/subpro-odp Regards, Chris Bare _________________________________________________________________________________________________________________________ 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.

3 3

EPDP Phase 2 Small Team - Preliminary Report
by Sebastien＠registry.godaddy April 4, 2022

April 4, 2022

Dear Council Colleagues, Please find attached the EPDP Phase 2 Small Team - Preliminary Report, on the agenda for our next Council meeting on 14 April. Note that Page 3 we deliberately left a date to be filled. As per the report, ICANN Staff is currently working on scoping a proof of concept in terms of effort and cost. They endeavoured to share their timeline ahead of this report but were not able to. This information will be made available before our meeting takes place. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_4132887379] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

REMINDER | ICANN74 The Hague | Do not book travel until directed
by Terri Agnew April 4, 2022

April 4, 2022

Hello all, While ICANN74 meeting planning is ramping up, we wanted to send a brief reminder to not book travel on your own, as if you are a GNSO Supported traveler this could cause difficulties. Please wait for further instructions – coming soon. Thank you for your understanding, 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

Deadline today: Reminder: Document and Motion deadline | Monday, 4 April 2022 at 23:59 UTC for GNSO Council Meeting 14 April 2022 at 13:00 UTC
by Nathalie Peregrine April 4, 2022

April 4, 2022

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 4 April 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 14 April 2022 at 13:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/-BQiCw Thank you. Nathalie

1 0

FW: [Ext] Monday, 4 April 2022 | 📣 Register for the ICANN74 Policy Forum in The Hague, Netherlands 📣
by Julie Bisland April 4, 2022

April 4, 2022

FYI - From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, April 4, 2022 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 4 April 2022 | 📣 Register for the ICANN74 Policy Forum in The Hague, Netherlands 📣 [https://r20.rs6.net/on.jsp?ca=8d4e8b40-a5a5-445c-9ff1-fc37a6eb3ca8&a=112202…] Monday, 4 April 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. 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=001416spojESJ3NtIdO…> Table of Contents ICANN74 · NEW: Design/Translation/Print Deadlines · NEW: Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Webinars · NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet Information Sharing · NEW: Request for Input-GNSO's Statement of Interest · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) · Root Zone Update Process Study · Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Resources NEW: Design/Translation/Print Deadlines FRIDAY, 8 APRIL 2022: DESIGN DEADLINE. If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Friday, 8 April. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. FRIDAY, 29 APRIL 2022: TRANSLATION DEADLINE. If your publication requires translation, please provide the final material(s) by Friday, 29 April. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. FRIDAY, 6 MAY 2022: PRINT DEADLINE ONLY. If you only need your publication printed, meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications, please provide the file to us along with the quantity you want printed and dimensions of the publication by Friday, 6 May. Please send materials to chantelle.doerksen(a)icann.org<mailto:chantelle.doerksen@icann.org>. NEW: Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> for ICANN74 (13-16 June 2022) in The Hague, Netherlands is now open. ICANN74 will take place as a hybrid event to accommodate both in-person and virtual participation. While the ICANN74 Policy Forum [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> presents the first opportunity for the community to come together in more than two years, the health and safety of all community members and staff continues to be ICANN's key priority. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. Webinars NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet ICANN has announced that it will hold a webinar on issues impacting the Internet that are being discussed at the United Nations (U.N.) and the International Telecommunication Union (ITU). The event will take place on Tuesday, 12 April 2022 at 20:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> for the webinar. Information Sharing NEW: Request for Input-GNSO's Statement of Interest The GNSO Council has recently embarked on a review of its Statement of Interest (SOI) requirements to determine whether these are still fit for purpose, and if not, what updates should be considered. To this end, the GNSO SOI Task Force (TF) was formed. As part of its assignment, the TF is reaching out to the ICANN community to solicit input on the current use and experience with SOIs as well as suggestions for possible improvements. We understand that some of you may use the SOI, either in its current form or a modified format, for your own purposes. We would be interested to hear about those experiences as well as any lessons learned that may help inform our recommendations. You are encouraged to share this information with your respective groups. To provide input, please complete the following survey [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> by 4 May at the latest. Your input will be much appreciated! REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May ICANN org's eighth Middle East Domain Name System (DNS) Forum will take place virtually from Monday-Wednesday, 16-18 May 2022 and will offer a closer look at the evolving DNS ecosystem from a technical and policy perspective. It will have a special focus on regional challenges and opportunities for growth. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Public Comment Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Thursday, 03 March 2022 Closed for Submissions Date: Tuesday, 19 April 2022 Root Zone Update Process Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Monday, 14 March 2022 Closed for Submissions Date: Monday, 25 April 2022 Root Zone Label Generation Rules Version 5 (RZ-LGR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Thursday, 24 March 2022 Closed for Submissions Date: Thursday, 05 May 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. Volume 4, Issue 25 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> | Next Issue: Thursday, 7 April 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>

1 0