June 2022 - council - lists.icann.org

GNSO representative to the ICANN Fellowship Selection Committee
by philippe.fouquart＠orange.com 08 Jun '22

08 Jun '22

Dear Councilors, As you will recall, the GNSO has one representative sitting on the ICANN Fellowship Selection Committee<https://www.icann.org/resources/pages/fellowship-selection-committee>, the group responsible for evaluating applications for the ICANN Fellowship Program and choosing individuals to participate as fellows. Heather Forrest has been serving in this role since 2018, but has informed Council leadership that she needs to step down. The GNSO needs to identify an interim replacement before the end of July to serve the remainder of the current term, which ends in April 2023. Heather first entered the role when she was GNSO Chair and sought to represent the GNSO as a whole in fulfilling that role. Given the short timeline for finding a replacement and keeping this history in mind, it seems fitting that as an interim solution that a member of the current leadership team fill her slot. Sebastien has offered step in through April 2023 and complete the two remaining selection processes in this term. If there are any concerns about the proposed approach or proposals for alternatives please raise them on list no later than 2 weeks from today, 21 June 2022. Absent concerns or alternatives, Sebastien's confirmation will be added to the consent agenda for the July 2022 Council meeting. Kind regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

5 4

For review - PDP Improvements Tracker
by Marika Konings 07 Jun '22

07 Jun '22

Dear All, In preparation for agenda item #9 on the Council agenda (GNSO PDP Improvements - Tracking and Coordination Discussion Paper), please find attached a first draft of the proposed tracker. Before going into a substantive review of the items included in the tracker, there are a number of practical questions that we hope to get feedback on during the upcoming Council meeting, namely: 1. Does the tracker provide the expected information for Council to consider and keep track of the different proposed improvements? If not, what is missing? 2. At the suggestion of Council members an entry for “impact” has been added. Council to identify who/how to determine impactfullness of each proposed improvement – is this referring to impact on the PDP, impact on resources, a combination of both or something else? 3. As not all improvements are solely within the remit of Council, what is the best way to consult with the broader GNSO community, and possibly beyond that, about this approach and how to enable regular consultation / input? 4. How often should review / updates be planned for? 5. Where should this information be housed – GNSO wiki? 6. How much time is needed for the Council to consider these above questions that need to be addressed before the first substantive review can commence? Following your feedback, we’ll make any updates to the tracker, as agreed, before planning for a substantive review of the proposed improvements and suggested next steps. We look forward to receiving your feedback. Best regards, Marika

1 0

FW: Impact of SSAD Light on Other Work
by philippe.fouquart＠orange.com 07 Jun '22

07 Jun '22

Dear Kurt, Thanks for the early input. Your email doesn't seem to have made it to the council list - or to its archive - (or use of a different email than the one subscribed, anyway I hope this one does.) Dear Councilors, The follow-up discussion on the impact of SSAD Light on Other Work is on next week's agenda under item 5, so please consider chiming in. Thank you. Regards, Philippe Orange Restricted -----Original Message----- From: Kurt Pritz <kp(a)art.art> Sent: Tuesday, June 7, 2022 10:09 AM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc: GNSO Council List <council(a)gnso.icann.org>; RySG ExComs <excoms(a)rysg.info> Subject: Impact of SSAD Light on Other Work Dear Philippe: During the 17 May Council discussion on the Impact of SSAD Light on Other Work, the RySG representative indicated that our stakeholder group had not had the opportunity to meet and develop a recommendation, given our meeting cadence and the timing of the publication of the meeting agenda. In order to keep the discussion timely, you requested, and we agreed, that the RySG provide feedback via email rather than wait for the next Council meeting. We appreciate the sense of urgency and are providing that feedback now. Our initial and stronger inclination is that this prioritization is an ICANN call. These are managerial decisions based on operational analysis of available resources, skillset requirements, competing projects, efficiencies, and scheduling impacts. This level of complexity gives us pause as to whether we or the Council can competently provide advice based on the information provided to us. When called upon to opine, we find ourselves asking the sorts of detailed questions that anyone faced with operational decisions would ask: about switching costs, risks, alternatives, and so on. We think it is appropriate for us to avoid operations questions such as these that are better left to staff expertise. Decisions regarding whether to keep or slip schedules are ICANN’s. Our second inclination is that these projects should not be paused at this time. Ordinarily (and even though decisions of how to proceed with an SSAD-light model is a still a matter of close debate), it would make sense to pull this work forward as a low-risk way to accelerate the schedule. However, this type of acceleration would be preferred only in cases where there exist slack resources that are available to perform the work. This request for re-prioritization guidance demonstrates that this is not the case. We recognize the importance of SSAD progress but, given what we know, believe these other ongoing projects (i.e., the SubPro ODP, CZDS and EBERO) should not be paused at this time. The facts that an SSAD-light approach is not settled, slack resources are not available, and reorganizing the three other projects presents an un-described set of risks has resulted in a stakeholder group preference in favour of continuing the projects where the scope is known, and the timetables are comparably urgent. Sincerely, Maxim Alzoba Sebastien Ducos Kurt Pritz RySG Councilors _________________________________________________________________________________________________________________________ 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

Working Group Self-Assessment - EPDP on Specific Curative Rights Protections for IGOs
by Emily Barabas 07 Jun '22

07 Jun '22

Dear Councilors, Please find attached a summary of the results of the Working Group Self-Assessment survey conducted for the EPDP on Specific Curative Rights Protections for IGOs. Kind regards, Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

GNSO Council Portfolio Management Tool Suite - 15 June 2022 Meeting
by Berry Cobb 06 Jun '22

06 Jun '22

Dear all, Please find attached links to the latest version of the GNSO Council’s Portfolio Management Tool Suite for the meeting on 15 June 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: * Given the activity across several communities, “IDNs” is now its own Program and distinct from the “gTLD” Program where these activities used to reside. Key Project Changes for this Period: * EPDP_IGO – Council to vote of EPDP’s Final Report, as deferred from May 2022. * TPR_P1 – Release of Initial Report for public comment on 20 June. * Small Team work: Modifying Consensus Policies, DNS Abuse, SSAD ODA, Closed Generics * 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 Key Project/Operations Activities for July/August 2022: * EPDP_SCRP_IGO – Consider resolution on Board Report * RDA_ST – Assignments #1/#2 report and Project Change Request * Modifying Consensus Policies response – small team * GGP for select SubPro topics * RPM_P2 – Council to consider the Policy Staff Report * ICANN74 – Council response to GAC advice, if applicable * EDDP_PSR – Council to consider requesting a Policy Status Report on Expiration Policies * Council to consider CSC Effectiveness Review 2021 final report * Council to approve full-slate of CSC members 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] Monday, 06 June 2022 | DEADLINE WEDNESDAY: ICANN74 Registration
by Julie Bisland 06 Jun '22

06 Jun '22

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, June 6, 2022 at 10:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 06 June 2022 | DEADLINE WEDNESDAY: ICANN74 Registration [https://r20.rs6.net/on.jsp?ca=a8354f9e-4521-4bd6-921c-aa6d6c1a091b&a=112202…] Monday, 06 June 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=001SHw6epPfKapwYYqd…> Table of Contents ICANN74 Planning · Policy Forum Schedule · Participation Guide · Policy Outlook Report · FAQ · Zoom Backgrounds · Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Information Sharing · REMINDER: Calling for NextGen@ICANN Applications for ICANN75 · REMINDER: SubPro ODP Team Offering Update Session to Community Groups · REMINDER: Request for Appointment of Members and Liaisons to the CSC · REMINDER: NextGen@ICANN Mentor Program Nominations ICANN74 Planning Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> Participation Guide [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> Policy Outlook Report [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> Schedule [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> FAQ [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> Zoom Backgrounds [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> Information Sharing REMINDER: Calling for NextGen@ICANN Applications for ICANN75 ICANN is calling for applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>. ICANN wants to hear from university students living and studying in the Asia Pacific region who are interested in the future of the Internet and in participating in the ICANN75 Annual Meeting. ICANN75 is scheduled to be held in Kuala Lumpur, Malaysia, from 17 to 22 September 2022. If ICANN75 is held virtually, the NextGen@ICANN Program will also be held virtually. The NextGen@ICANN application window will remain open until Friday, 1 July 2022. Successful candidates will be announced on 15 July 2022 on the ICANN website. For more information about the program and to apply, please visit the NextGen@ICANN website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> REMINDER: SubPro ODP Team Offering Update Session to Community Groups In addition to the anticipated plenary session on the New gTLD SubPro ODP, the ICANN org SubPro ODP team is welcoming meetings with interested community groups. If any Supporting Organizations, Advisory Committees, stakeholder, or constituency groups would like to hear from the SubPro ODP team, please email subpro-odp(a)icann.org to schedule time with us. Please be sure to include any specific topic areas for discussion or if you prefer a general update. In addition, we ask that you share a few date and time options so that we can schedule and prepare accordingly. We look forward to meeting you. REMINDER: Request for Appointment of Members and Liaisons to the CSC As of 30 September 2022, several members and liaisons of the Customer Standing Committee (CSC) will complete their term. ICANN org will soon be asking chairs to initiate your respective group's processes to appoint members and liaisons to these seats. While members are required, liaison appointments are optional (albeit strongly encouraged). To ensure that the appointment process is completed in time for the start of the next CSC term, ICANN org will ask to be notified of your appointments by Monday, 1 August 2022. More information will be shared directly via email, including detailed guidance about the process, candidate qualification requirements, and key dates. More information about the CSC can be found here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> REMINDER: NextGen@ICANN Mentor Program Nominations The nomination period for the NextGen@ICANN Mentor Program is now open. Nominations must be submitted by no later than Monday, 1 August 2022. The community-nominated mentor will be responsible for overseeing the mentor process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>. Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Public Comment See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>. Volume 4, Issue 43 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…> | Next Issue: Thursday, 09 June 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001SHw6epPfKapwYYqd…>

1 0

Discussion - Applicant Support Program and the GGP
by kurt kjpritz.com 05 Jun '22

05 Jun '22

Hello Paul (and everyone else): I am writing in follow-up to the Council discussion regarding the SubPro recommended Applicant Support Program. During that agenda item, it was proposed that a GNSO Guidance Process (GGP) be launched to bring the Applicant Support work forward. At that time, you commented (please correct or refine my recollection) that the Applicant Support program seems like straight IRT work and that we needn’t / shouldn’t invoke this specialized procedure. I had thought to respond at the time you made your comment but wanted to pause in order to organize my thoughts. Paul, I hope you don’t mind me using your intervention as a way to make an alternative case (even thought I have a lot of sympathy for your position). However, I think that pulling this work ahead of the IRT start would be beneficial, and the GGP is an available, legitimate path. Background: I. First, sometime after the Council approval of the SubPro final report, it was suggested that implementation work on Applicant Support be pulled forward because: 1. given its potential complexity, designing the Applicant Support program was likely to take the longest of all the implementation tasks – the long pole in the tent. So good business sense would dictate that it be pulled it forward if possible, and 2. the SubPro report indicated that the skillset necessary to complete the work is different from those normally comprised in an IRT. So, there would not be inefficiencies introduced by creating a separate Applicant Support implementation team. II. Then, shortly after that (I might the timing somewhat muddled here), ICANN staff made a statement to the effect of, “this Applicant Support effort seems more like ‘policy’ than ‘implementation,” and put next steps for decision by the Council. Given those two concerns, we find ourselves with an appropriate, lightweight tool in our toolbox that satisfies both concerns, the GGP (https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-5-g…) So, I advocate for its deployment – for this reason, and with this caveat: I think it makes a great deal of sense to pull the Applicant Support work forward. As you will recall, the Applicant Support program in the last round was crap — all due to the lateness of the idea and the limited time to adopt “something.” Devising an effective program will take time and an extraordinary skillset. If we wait for the IRT, the Applicant Support program design will either delay the program launch or fall short of the mark due to inadequate time for design and testing. I am betting it will be the latter. In any event, I think it is in our interest to ensure there is adequate time to develop the program by pulling the work forward using the GGP as a tool. However, I am not for the GGP as proposed in https://mm.icann.org/pipermail/council/attachments/20220504/09360d33/SubPro…. That proposal calls for an overarching, 20-person representative community group to oversee several proposed GGP efforts in what is likely to be a multi-year commitment on the part of our depleted volunteer workforce. I am not convinced that the other post-SubPro report efforts listed in the proposed GGP rise to the level of invoking a GGP. (They are the CPE Threshold, Quick Look Objection Process, Public Comment Role in Evaluations, and supporting Freedom of Expression.) In any event, these could be tackled separately, as they require different skill sets, and it is in our interest to keep this effort streamlined, timely and effective. I believe the GGP as set out in the Bylaws provides the flexibility to devise a lightweight process. I am speaking on my own here and do not know the RySG position. There might be other ways to manage implementation in a timely, economical, effective manner. The GGP requires the approval by Council; so I am writing to continue the discussion that you so thoughtfully started so that we might arrive at some conclusions by our next meeting. I hope you all find this helpful. Best regards, Kurt

2 3

Proposed Agenda | GNSO Council Meeting | 15 June 2022 at 15:15 UTC.
by Terri Agnew 03 Jun '22

03 Jun '22

Dear all, Please find below the final proposed agenda for the GNSO Council Meeting on 15 June 2022 at 15:15 UTC. **Side note, the wiki is currently under temporary maintenance this agenda will be posted once complete (https://community.icann.org/x/dBR1Cw) Draft GNSO Council Agenda 15 June 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/dBR1Cw. 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:15 CEST (15:15 UTC): https://tinyurl.com/bpa9yam3 08:15 Los Angeles; 11:15 Washington DC; 16:15 London; 17:15 Paris; 18:15 Moscow; (Thursday) 01:15 Melbourne GNSO Council Meeting Remote Participation: (TBD) 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 14 April 2022 were posted on 29 April 2022. Minutes<https://gnso.icann.org/sites/default/files/policy/2022/minutes/minutes-gnso…> of the GNSO Council meeting on 19 May 2022 were posted on 03 June 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 (0 minutes) * None Item 4: COUNCIL VOTE - Final Report and Recommendations From the EPDP on Specific Curative Rights Protections for IGOs (20 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, along with a draft motion, which continues a recent practice of the Council reviewing and discussing PDP/EPDP final reports in detail prior to voting on them. The Council received an overview of the recommendations from the Chair of the EPDP, Chris Disspain, during the April meeting. The Council was scheduled to conduct a vote on the EPDP Team’s Final Report during its May meeting but a deferral request was received and granted. Here, the Council will vote to adopt the EPDP Team’s Final Report. 4.1 – Presentation of motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-05-19> (GNSO Council liaison to the EPDP, John McElwaine) 4.2 – Council discussion 4.3 – Council vote (voting threshold: Supermajority) Taking this action is within the GNSO’s remit as outlined in ICANN’s Bylaws as the GNSO ‘shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws’ (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A-1: GNSO Expedited Policy Development Process of the ICANN Bylaws. Item 5: COUNCIL DISCUSSION - Impact of SSAD Light on Other Work (15 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 several elements as identified in the assignment form<https://community.icann.org/download/attachments/178587048/Small%20Team%20A…>: 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. As part of the small team’s consultations with ICANN org, the org provided an SSAD Light Design Concept<https://mm.icann.org/pipermail/gnso-epdpp2-smallteam/attachments/20220406/b…> overview, guided by the proof of concept contained in the preliminary report. The paper anticipates a six week effort to produce the SSAD Light Design Concept paper. Notably, the resources needed to produce that document are responsible for other areas of work and developing the document will delay the timelines for each of the following projects/initiatives by 1.5 months: * SubPro ODP * CZDS 3.0 * EBERO Program and DEA improvements While ICANN org resources are directed by the ICANN Board, the Council may want to provide input to the Board if there are concerns about the impact to these projects. The Council discussed during its May meeting whether or not it had input to provide to the ICANN Board. The small team has since received <https://mm.icann.org/pipermail/gnso-epdpp2-smallteam/2022-June/000149.html> additional information from ICANN Org that indicates that the impact to the three aforementioned projects/initiatives would not be equal. Specifically, CZDS 3.0 and the EBERO Program and DEA improvements would be paused while the SubPro ODP would be delayed but not paused. Further information is expected to better understand the impact, including whether the delays would mean missing key milestones. Here, the Council will discuss next steps for the SSAD Light Design Concept. 5.1 – Introduction of topic (Council leadership) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION - SubPro GGP (20 Minutes) In relation to the SubPro ODP, ICANN org shared question set #2<https://mm.icann.org/pipermail/subpro-odp/attachments/20220211/93bd5c93/Sub…> with the GNSO Council’s liaison to the 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. The Council agreed that it should explore finding avenues to complete that level of substantive work in advance of the expected IRT that would be convened upon ICANN Board adoption of the SubPro Outputs. The potential model to address this work is the GNSO Guidance Process. ICANN org staff worked with Jeff Neuman and Council leadership to prepare a draft GGP Initiation request, which was shared<https://mm.icann.org/pipermail/council/2022-May/025646.html> on Council list on 4 May 2022. The Council first discussed the potential GGP durings its May meeting and concerns, as well as uncertainty about the mechanism itself, were expressed both during the meeting and afterwards on the Council mailing list. With that in mind, this agenda item will provide additional clarity about the GGP mechanism itself, discuss expectations for a potential GGP, and timing considerations. Here, the Council will consider the potential GGP Initiation Request and discuss next steps. 6.1 – Introduction of topic (Council leadership) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION - SubPro ODP Update (15 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. The ODP Team has shared several updates to the community and sent assumptions/questions to the GNSO Council via the Council’s liaison to the ODP. The latest update was shared<https://mm.icann.org/pipermail/council/2022-May/025647.html> on 5 May 2022. Since then, the GNSO liaison to the ODP has shared a Google doc to review Question Set #4<https://urldefense.com/v3/__https:/docs.google.com/document/d/1EQDDfNprHYWW…>, which includes quite a number of questions and responses. Here, the Council will receive an update from the liaison and discuss Questions Set #4. 7.1 – Introduction of topic (Council leadership; GNSO liaison to the ODP - Jeff Neuman) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION - Closed Generics Small Team (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). On 27 April 2022, the Council responded<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouqu…> to the Board affirmatively, that it is willing to pursue next steps. Subsequently, the Council tasked the small team with preparing for the next step, of mutually agreeing with the GAC on the parameters, processes, and procedures for the facilitated dialogue. The small team provided its recommendations to the Council on [date/ TBD]. Here, the Council will receive an update on the work of the small team. 8.1 – Introduction of topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION - GNSO PDP Improvements - Tracking and Coordination Discussion Paper (10 minutes) During the ICANN73 wrap up, the Council discussed a number of parallel conversations that have emerged since implementing PDP 3.0, identifying other aspects of the PDP where improvements could be considered. In addition, there are a number of projects on the Council’s Action Decision Radar (ADR) related to PDP improvements which will need to be addressed at some point in the future. To provide the Council with a clear picture of these different parallel initiatives and projects, and to avoid overlap and ensure complementarity, the staff support team developed a discussion paper<https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-gnso-pdp…>. In addition to an overview of the different initiatives and projects, the paper also suggests a possible approach for managing these different initiatives by focusing on 1) which elements could be implemented with relatively minimal effort, 2) which elements could be implemented with some effort, 3) which elements need careful planning and consideration before these can be implemented. It is envisioned in the paper that going forward, progress on these different initiatives could be tracked through a PDP improvements tracker to ensure oversight and allow for forward planning which can factor in these commitments. The GNSO Council discussed the discussion paper and agreed that to better understand the concept, it would be helpful to have an example of what the tracker may look like. Here, the Council will receive a preview of the potential GNSO PDP Improvements tracker. 9.1 – Introduction of topic (Council leadership) 9.2 - Presentation (ICANN Org - Marika Konings) 9.3 – Council discussion 9.4 – Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.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 15:15 UTC Local time between March and November in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 08:15 San José, Costa Rica (CST) UTC-6 09:15 New York/Washington DC, USA (EDT) UTC-4 11:15 Buenos Aires, Argentina (ART) UTC-3 12:15 Rio de Janeiro, Brazil (BRT) UTC-3 12:15 London, United Kingdom (BST) UTC+1 16:15 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 16:15 Paris, France (CEST) UTC+2 17:15 Moscow, Russia (MSK) UTC+3 18:15 Singapore (SGT) UTC+8 (Friday) 23:15 Melbourne, Australia (AEST) UTC+10 (Thursday) 01:15 ---------------------------------------------------------------------------- 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/5n7ade7t.

1 0

Reminder: Document and Motion deadline | Sunday, 05 June 2022 at 23:59 UTC for GNSO Council Meeting 15 June 2022 at 11:15 UTC
by Nathalie Peregrine 03 Jun '22

03 Jun '22

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 05 June 2022 at 23:59 UTC) of the GNSO Council Meeting on Wednesday, 15 June 2022 at 13:15 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/eBR1Cw Thank you. Nathalie

1 0

Reminder: ICANN74 COMMUNITY UPDATE WEBINAR IN 20 MINS
by Nathalie Peregrine 02 Jun '22

02 Jun '22

Dear all, You may find the Prep Week schedule on the ICANN74 website [74.schedule.icann.org]<https://urldefense.com/v3/__https:/74.schedule.icann.org/__;!!PtGJab4!9AZ7S…>. Given it is for virtual attendance only, there is no limit to Zoom room capacity, and you are free to add these sessions to your schedules. Reminder that there will be no calendar invitations for these sessions, these are for you to download to your calendars. All Prep Week sessions are geared towards preparing for ICANN74 discussions, below however are those of particular interest to councilors, please feel free to share with your community colleagues: Thursday 02 June * 22:00 CEST, 20:00 UTC -> ICANN74 Community Update Please reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you have any questions, Thank you! Nathalie

1 0