May 2022 - council - lists.icann.org

Reminder RSVP: ICANN74 GNSO Council dinner Monday 13 June 2022
by Nathalie Peregrine 05 May '22

05 May '22

Dear all, Even though ICANN74 is the very first iteration of a hybrid meeting, the aim is for councilors on-site in the Hague to be able to convene for a traditional GNSO Council dinner on Monday 13 June 2022, at the end of Day 1. As a reminder, this is an informal gathering for councilors to be able to get to know each other. Each councilor pays for their own meal, menu prices will be communicated ahead of time. Sebastien Ducos has very kindly accepted to take on the role of Council dinner sponsor and will therefore find a venue, and take care of organizing the event. The dinner will be held close to the World Forum, a very short cab ride away at the most. In order for Sebastien to proceed with his research in an informed manner, would you please RSVP to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> with the following details: 1. Will you be travelling to the Hague? 2. Will you be attending the Monday 13th June 2022 Council dinner? 3. Do you have any food allergies or intolerances we would need to be informed of? Thank you in advance for your responses! Once we have received them all, a venue selection will be made and of course shared on the Council mailing list. Kindest regards, Nathalie

1 0

Re: [council] [Ext] RE: Notes - Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs - 4 May 2022 at 13:00 UTC
by Emily Barabas 05 May '22

05 May '22

Hi Jeff, Thanks for your careful review of the high-level notes. We briefly tried to capture Becky’s point with the bullet, “It was noted that it is important for the Board to know clearly if there is an intention by a PDP to change a policy.” Thanks for elaborating further on this point and making sure it is well understood by those who were unable to attend. Kind regards, Emily From: Jeff Neuman <jeff(a)jjnsolutions.com> Date: Thursday, 5 May 2022 at 15:20 To: Emily Barabas <emily.barabas(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] RE: Notes - Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs - 4 May 2022 at 13:00 UTC Thanks Emily. The notes are great. One thing that I do not believe was captured in these notes, however, was a point raised by Becky Burr which was that if there is a recommendation in a PDP and that recommendation supplements, changes or reverses an existing policy, then the PDP Working Group should indicate in its final report that it is specifically intending to supplement, change or reverse the impacted policy. Therefore, it will be clear to the Board that the new PDP did consider the impact of the new recommendations on existing policies and that it specifically intended the impact on the existing policy. I believe that was a recommendation that was supported by those participating in the discussion. Perhaps that was covered in your notes on expanding the role of the Liaisons, but I think it is a point that is worth calling out on its own. Sincerely, Jeff [cid:image001.png@01D86094.C67A4DC0] 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 [jjnsolutions.com]<https://urldefense.com/v3/__http:/jjnsolutions.com__;!!PtGJab4!pmTpZW2gAFtM…> From: council <council-bounces(a)gnso.icann.org> On Behalf Of Emily Barabas via council Sent: Thursday, May 5, 2022 5:06 AM To: council(a)gnso.icann.org Subject: [council] Notes - Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs - 4 May 2022 at 13:00 UTC Dear all, Please find below high-level notes from yesterday’s meeting. Kind regards, Marika and Emily Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs 4 May 2022 at 13:00 UTC Introductory remarks * Philippe noted that this discussion is part on of several related threads of work, which have been captured in a PDP improvements discussion paper [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> developed by policy support staff with Council leadership. The paper tries to categorize items that are high-impact and low effort as well as items that require more work or planning, and tries to capture specific suggestions from the Modifying Consensus Policies paper and from other sources. * Theresa shared that the Modifying gTLD Consensus Policies [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> paper was developed by her team in the spirit of contributing to the conversation about how to improve and evolve our work. Group discussion * Some support was expressed for the items on pages 10-14 of the Modifying Consensus Policy paper, noting that these items seem like improvements that are relatively straightforward and do not require the addition of heavy process elements. * With respect to modifying consensus policies, the group discussed that there might be a range of issues that could come up and it is not always easy to anticipate and develop processes to anticipate the types of issues that need to be addressed. At the same time, as more policy development takes place and the number of policies increases, it is likely that there will be more cases of policy recommendations having an impact on existing consensus policy. * ICANN org staff emphasized that while each case is different, when a new policy impacts existing policy, it is important to understand the roles involved and what is the proper place to have a discussion. This does not necessarily mean that processes need to be complex and burdensome. The goal is clarity. It was also suggested that in those cases where there is an impact on existing consensus policies, it might be possible to distinguish between those updates that would not significantly impact contractual requirements of Contracted Parties, vs. those that would. Different approaches might need to apply depending on the impact of the changes that would need to be applied. * Some participants in the conversation expressed concern that additional process could create additional burden on the GNSO community, slow down the progression of work, and create unnecessary barriers. Similarly, some noted that this should not be a way to circumvent the Policy Development Process as that is how new and/or changes to existing Consensus Policies should be developed / confirmed. * There was general agreement that the evolving role of GDS liaisons to PDPs is a positive step, and that this may enable early identification of issues before the PDP concludes. Further evolution of this role could help to reduce the need to address issues related to modifying consensus policies, but will not eliminate the need altogether. Some also viewed early engagement by the Board as a positive step, because it helps to ensure that the Board has a clearer sense of the community’s work and expectations with respect to the recommendations. * It was noted that it is important for the Board to know clearly if there is an intention by a PDP to change a policy. * Additional support was expressed for the items on pages 10-14 of the Modifying Consensus Policy paper. Next Steps * The next Council meeting is on 19 May during which the Council will consider the PDP Improvements discussion paper [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> and proposed approach for tracking and coordinating on the different threads of conversation. If there is support for moving forward, Council will work to identify who is responsible and next steps. This is a continuous process for improvement and the door is not closed for additional input. * Org may build on the Modifying gTLD Consensus Policies [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> paper and today’s discussion by putting forward additional suggestions for improvement for Council and community consideration. * An additional follow-up call may be appropriate with ICANN Org, GNSO Council and SG/C Chairs following the Council discussion. 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 1

FW: [Ext] Thursday, 05 May 2022 | TOMORROW: ICANN74 Print Deadline
by Julie Bisland 05 May '22

05 May '22

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, May 5, 2022 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 05 May 2022 | TOMORROW: ICANN74 Print Deadline [https://r20.rs6.net/on.jsp?ca=893cc5f3-7b74-4418-890e-b87aa763b193&a=112202…] Thursday, 05 May 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. 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=001lKZu2pX-L6lsNOYR…> Table of Contents ICANN74 Planning · TOMORROW: Print Deadline · REMINDER: Internet Reimbursement Program · REMINDER: Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Information Sharing · NEW: Washington, D.C. and Seattle Confirmed to Host ICANN Public Meetings in 2023 and 2025 · REMINDER: Call for Expressions of Interest: ICANN 2023 NomCom Chair and Chair-Elect · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · EXTENDED: Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Planning TOMORROW: Print Deadline 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 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>. REMINDER: Internet Reimbursement Program Application Opens: Monday, 02 May 2022 Application Deadline: Friday, 27 May 2022 The application process is now open. Those who meet the eligibility requirements will be able to participate. More information is available on the Pandemic Internet Access Reimbursement Program website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>. The deadline for applications is Friday, 27 May 2022, at 23:59 Coordinated Universal Time (UTC). The ICANN Pandemic Internet Access Reimbursement Program aims to facilitate the active participation in ICANN Public Meetings Meeting for certain community members with limited Internet capacity by offering financial assistance to increase their Internet bandwidth during the meeting. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> REMINDER: 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=001lKZu2pX-L6lsNOYR…> 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=001lKZu2pX-L6lsNOYR…> 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=001lKZu2pX-L6lsNOYR…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>. Information Sharing NEW: Washington, D.C. and Seattle Confirmed to Host ICANN Meetings in 2023 and 2025 ICANN announced the locations for future ICANN Public Meetings in 2023 and 2025. Washington, D.C. has been selected as the location in the North America region to host the ICANN77 Policy Forum. ICANN77 will be held at the Marriott Marquis Washington, D.C. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> from 12-15 June 2023. Seattle, Washington has been selected as the location in the North America region to host the ICANN82 Community Forum. ICANN82 will be held at the Hyatt Regency Seattle [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> from 8-13 March 2025. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> REMINDER: Call for Expressions of Interest: ICANN 2023 NomCom Chair and Chair-Elect ICANN org seeks Expressions of Interest for the chair and chair-elect of the 2023 Nominating Committee (NomCom). Expressions of Interest, which will be maintained as confidential, should be sent to NomComChair2023(a)icann.org<mailto:NomComChair2023@icann.org> by no later than Monday, 9 May 2022. A suggested form for submitting an Expression of Interest is available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>. 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=001lKZu2pX-L6lsNOYR…> Public Comment EXTENDED: Root Zone Label Generation Rules Version 5 (RZ-LGR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> Open for Submissions Date: Thursday, 24 March 2022 Closed for Submissions Date: Wednesday, 11 May 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>. Volume 4, Issue 34 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…> | Next Issue: Monday, 09 May 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001lKZu2pX-L6lsNOYR…>

1 0

Notes - Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs - 4 May 2022 at 13:00 UTC
by Emily Barabas 05 May '22

05 May '22

Dear all, Please find below high-level notes from yesterday’s meeting. Kind regards, Marika and Emily Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs 4 May 2022 at 13:00 UTC Introductory remarks * Philippe noted that this discussion is part on of several related threads of work, which have been captured in a PDP improvements discussion paper<https://gnso.icann.org/sites/default/files/file/field-file-attach/modifying…> developed by policy support staff with Council leadership. The paper tries to categorize items that are high-impact and low effort as well as items that require more work or planning, and tries to capture specific suggestions from the Modifying Consensus Policies paper and from other sources. * Theresa shared that the Modifying gTLD Consensus Policies<https://gnso.icann.org/sites/default/files/file/field-file-attach/modifying…> paper was developed by her team in the spirit of contributing to the conversation about how to improve and evolve our work. Group discussion * Some support was expressed for the items on pages 10-14 of the Modifying Consensus Policy paper, noting that these items seem like improvements that are relatively straightforward and do not require the addition of heavy process elements. * With respect to modifying consensus policies, the group discussed that there might be a range of issues that could come up and it is not always easy to anticipate and develop processes to anticipate the types of issues that need to be addressed. At the same time, as more policy development takes place and the number of policies increases, it is likely that there will be more cases of policy recommendations having an impact on existing consensus policy. * ICANN org staff emphasized that while each case is different, when a new policy impacts existing policy, it is important to understand the roles involved and what is the proper place to have a discussion. This does not necessarily mean that processes need to be complex and burdensome. The goal is clarity. It was also suggested that in those cases where there is an impact on existing consensus policies, it might be possible to distinguish between those updates that would not significantly impact contractual requirements of Contracted Parties, vs. those that would. Different approaches might need to apply depending on the impact of the changes that would need to be applied. * Some participants in the conversation expressed concern that additional process could create additional burden on the GNSO community, slow down the progression of work, and create unnecessary barriers. Similarly, some noted that this should not be a way to circumvent the Policy Development Process as that is how new and/or changes to existing Consensus Policies should be developed / confirmed. * There was general agreement that the evolving role of GDS liaisons to PDPs is a positive step, and that this may enable early identification of issues before the PDP concludes. Further evolution of this role could help to reduce the need to address issues related to modifying consensus policies, but will not eliminate the need altogether. Some also viewed early engagement by the Board as a positive step, because it helps to ensure that the Board has a clearer sense of the community’s work and expectations with respect to the recommendations. * It was noted that it is important for the Board to know clearly if there is an intention by a PDP to change a policy. * Additional support was expressed for the items on pages 10-14 of the Modifying Consensus Policy paper. Next Steps * The next Council meeting is on 19 May during which the Council will consider the PDP Improvements discussion paper<https://gnso.icann.org/sites/default/files/file/field-file-attach/modifying…> and proposed approach for tracking and coordinating on the different threads of conversation. If there is support for moving forward, Council will work to identify who is responsible and next steps. This is a continuous process for improvement and the door is not closed for additional input. * Org may build on the Modifying gTLD Consensus Policies<https://gnso.icann.org/sites/default/files/file/field-file-attach/modifying…> paper and today’s discussion by putting forward additional suggestions for improvement for Council and community consideration. * An additional follow-up call may be appropriate with ICANN Org, GNSO Council and SG/C Chairs following the Council discussion. 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/>

2 1

FW: SubPro Update - May 4, 2022 (SSAD LITE WILL DELAY SUBPRO ODP)
by philippe.fouquart＠orange.com 05 May '22

05 May '22

Dear Councilors, Please find Jeff's update on the SubPro odp. Note also the question on the impact of the SSAD Lite work on the SubPro odp. There will be an agenda item on our May call on this report. Regards, Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 04/05/2022 18:04 (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>, SubPro ODP Mailman List <subpro-odp(a)icann.org> Objet : SubPro Update - May 4, 2022 (SSAD LITE WILL DELAY SUBPRO ODP) Dear GNSO Council Leadership, Please find below my SubPro update from a call I had with the SubPro ODP Team at the end of next week. Can you please forward to the Council List? Please note that we really need to discuss #1 below to make sure that the Council understands and agrees with whether to move ahead with SSAD Lite prior to completing the SubPro ODP. Doing so will cause substantial delay to the SubPro ODP according to ICANN Org. Sincerely, Jeff Neuman GNSO Liaison to the SubPro ODP +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ At the end of last week, the SubPro ODP Team had its monthly meeting with the GNSO Council Liaison and we covered the following topics: 1. Impact of SSAD Lite Work: The Council is considering asking ICANN Org to do some work designing an SSAD Lite and presenting that to the community. The SubPro ODP Team has explained that doing so will cause at least 6 weeks delay in the SubPro ODP. Therefore, the Council needs to consider whether that work should be done and if so whether that should be done before or after the completion of the SubPro ODP. This is only for designing the SSAD Lite. If the Council wants it built after the design, then that could be months more delay for the SubPro ODP. 1. ICANN 74: * According to the ICANN ODP team, the SO/AC team that works on the agenda for the meeting rejected the proposal made by the SubPro ODP team to have a policy meeting that focused primarily on SubPro. We are still unclear if that means that there will be no ODP sessions at ICANN 74 or whether there may be 1. * There will be a SubPro meeting during the Prep Week for ICANN 74. Because this will be near the mid point of the ODP, we will try to make this session interactive (as much as a prep week session will be), but the goal is to not make it an update session where the entire time is spent updating the community on what has been done and whats left to do, but rather to focus on substantive issues (TBD). * The SubPro ODP Team wants to let each of the SGs and Cs know that they are available to have sessions with those groups (as well as ACs) during ICANN 74 should any of them want to schedule that in their sessions. 1. Question Set #3: * On April 11, 2022, Question Set #3 was sent to the Council for its comments. Shortly thereafter I provided draft answers to the questions and sent them out to the Council (found here<https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJm…>). This is a reminder to please give your input into the proposed responses. * Although there has been a comment in the draft responses to the ICANN SubPro ODP Team (who has access to the Google Doc), I formally submitted the comment in the form of a clarifying question today (May 4th) about the meaning of the final question in Question Set #3. 1. Question Set #4: According to the ICANN ODP Team, we are going to shortly get ODP Set #4 which will be lengthy, but will hopefully be one of the last question sets as the ODP Is moving forward in its work. 1. Timeline to Completion: At this point there is nothing to believe that the work will not be completed on time, BUT to the extent that any further work needs to be done on SSAD Lite, this will push the ODP back by at least 6 weeks. See #1. If at all possible, I would like to add an agenda item on SubPro ODP for the next Council meeting so that we can discuss the impact of the SSAD Lite on the SubPro ODP and what the Council wants to prioritize. Sincerely, Jeff [cid:image001.png@01D85F92.A81BD590] 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 _________________________________________________________________________________________________________________________ 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

Draft New gTLD Subsequent Procedures GNSO Guidance Process (GGP) Initiation Request
by Steve Chan 04 May '22

04 May '22

Dear Councilors, There was an action item to prepare a draft GNSO Guidance Process (GGP) Initiation Request for certain New gTLD Subsequent Procedures topics. Attached, please find a draft that staff worked on with Jeff, in consultation with Council leadership. Note that this would be the first GGP ever and hence, here is a general point and some more specific ones to take into account in reviewing the draft. * A GGP does not require a separate charter. Things like scope, working mechanism, and method of operation should all be contained in the initiation request. * The draft contains a concept of Group 1 versus Group 2 topics. Group 1 is where the SubPro Final Report specifically called out substantive work that it envisioned would be completed during the Implementation Review Team phase. Group 2 will be topics that are identified by the ODP Team, where they are able to determine that additional guidance is needed to support the presumed eventual implementation. The specifics for Group 2 are currently to be determined, as we await input from the ODP Team. * You will see that in Section 3 of the document, relevant Outputs from the SubPro Final Report are reproduced, and that there are Tasks identified. These tasks are envisioned as the specific scope of work for the GGP. Per the previous bullet, the tasks for Group 2 are still TBD. * The suggested working model for this group is proposed as a representative steering group, which can do the work itself, but it can also delegate the work to sub-teams where it is evident that the work is best performed by those with specific expertise in a certain field. If you have any questions or comments, please let us know. Council leadership is likely to propose the GGP as a topic for the May Council meeting. Best, Steve 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

Council ST on closed generics: call for additional volunteers &
by philippe.fouquart＠orange.com 04 May '22

04 May '22

Dear Councilors, Under agenda item 7 of the 14 April 2022 GNSO Council meeting, it was agreed that we would seek additional volunteers to participate in the Council small team focused on closed generics. You will recall that this group currently has a relatively small number of team members (three Councilors, the GNSO liaison to the GAC, and the ALAC liaison to the GNSO). Now that Council has provided an initial response<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouqu…> to the Board that it is willing to pursue next steps on a facilitated dialogue, the expanded small group will work to provide suggestions to Council about how the proposed facilitated dialogue could be carried out, namely the conditions, parameters, and methodology for the dialogue, including potential desired attributes for a facilitator. These small team suggestions are intended to form the basis for initial discussions with the GAC to identify a mutually agreeable foundation for the facilitated dialogue. If you are interested in joining the small group effort, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. 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.

2 1

**Cancelled** Meeting Invitation: GNSO Council Strategic Planning Session Catch Up call
by Julie Bisland 04 May '22

04 May '22

The call for 09 May has been cancelled, please remove it from your calendar. Dear all, Please join the GNSO Council Strategic Planning Session Catch Up call taking place on Monday, 09 May 2022 at 20:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92399217049?pwd=WU1GZmla…> Passcode: Y&N1.Y7E%^ Or One tap mobile : US: +13126266799,,92399217049#,,,,*4890633693# or +19294362866,,92399217049#,,,,*4890633693# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 923 9921 7049 Passcode: 4890633693 International numbers available: https://icann.zoom.us/u/abnZisZ3XE [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/abnZisZ3XE__;!!PtGJab4!r…> Thank you! Kind regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 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

Canceled: GNSO SPS Catch up call
by ICANN Policy Calendar 04 May '22

04 May '22

Meeting: GNSO SPS Catch up call Date/Time: Monday, 09 May 2022 at 20:00 UTC for 90 minutes Please click the link below to join the webinar: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 Passcode: Y&N1.Y7E%^ Or One tap mobile : US: +13126266799,,92399217049#,,,,*4890633693# or +19294362866,,92399217049#,,,,*4890633693# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 923 9921 7049 Passcode: 4890633693 International numbers available: https://icann.zoom.us/u/abnZisZ3XE

1 0

Recordings & Zoom chat | Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs | Wednesday, 4 May 2022 at 13:00 UTC
by Nathalie Peregrine 04 May '22

04 May '22

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and zoom chat of the Modifying gTLD Consensus Policies call with ICANN Org, GNSO Council and SG/C Chairs meeting held on Wednesday, 4 May 2022 at 13:00 UTC. Audio only: https://icann.zoom.us/rec/play/PWaNI0Qg8qu0OjjSpfCZ6ldTwE-zQJAhC1s_dIrZACeP… Zoom Recording (includes chat and visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/play/28YrB73NIY5yMw-ljZuUyGYn1mh1l8YkDylHQJQQkmsX… Zoom Chat: https://icann.zoom.us/rec/sdownload/MFVBpEk7-boM0VCd1PHTVZWfJcmKqTJpt7v27qq… The recordings and transcription of the calls are posted on the GNSO Master Calendar page.<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. With kind regards, Nathalie

1 0