September 2022 - council - lists.icann.org

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Wednesday, 15 March 2023 at 18:15 UTC for 2 hours **See ICANN schedule for join information

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Wednesday, 14 June 2023 at 17:15 UTC for 2 hours Please see ICANN schedule for join information

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Thursday, 25 May 2023 at 13:00 UTC for 2 hours Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Passcode: 5d$X0$^0L2 Or One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# Webinar ID: 978 9162 7902 Passcode: 9844091488 International numbers available: https://icann.zoom.us/u/abaexQvkCI

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Thursday,20 April 2023 at 21:00 UTC for 2 hours Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Passcode: 5d$X0$^0L2 Or One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# Webinar ID: 978 9162 7902 Passcode: 9844091488 International numbers available: https://icann.zoom.us/u/abaexQvkCI

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Wednesday, 15 March 2023 at 18:15 UTC for 2 hours Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Passcode: 5d$X0$^0L2 Or One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# Webinar ID: 978 9162 7902 Passcode: 9844091488 International numbers available: https://icann.zoom.us/u/abaexQvkCI

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Thursday, 16 February 2023 at 14:00 UTC for 2 hours Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Passcode: 5d$X0$^0L2 Or One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# Webinar ID: 978 9162 7902 Passcode: 9844091488 International numbers available: https://icann.zoom.us/u/abaexQvkCI

1 0

GNSO Council Meeting
by ICANN Policy Calendar 29 Sep '22

29 Sep '22

Meeting: GNSO Council Meeting Date/Time: Thursday, 19 January 2023 at 21:00 UTC for 2 hours Please click the link below to join the webinar: https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09 Passcode: 5d$X0$^0L2 Or One tap mobile : US: +13126266799,,97891627902#,,,,*9844091488# or +13017158592,,97891627902#,,,,*9844091488# Webinar ID: 978 9162 7902 Passcode: 9844091488 International numbers available: https://icann.zoom.us/u/abaexQvkCI

1 0

Fwd: Clarification Question on the GAC Communique (SubPro)
by Jeff Neuman 28 Sep '22

28 Sep '22

Dear Council, Please find below the response from the GAC point of contact. The communique does indeed ask for more than just having an observer, but for the ability to have additional participants in the group, but also recognizing the need for a closed group. I know there is a small group that is reviewing this, but I will leave it to the Council to decide if it wants to discuss this as a whole. Sincerely, Jeffrey J. Neuman GNSO Liaison to GAC ________________________________ From: Jorge.Cancio(a)bakom.admin.ch <Jorge.Cancio(a)bakom.admin.ch> Sent: Wednesday, September 28, 2022 1:15 AM To: Jeff Neuman <jeff(a)jjnsolutions.com> Cc: manal(a)tra.gov.eg <manal(a)tra.gov.eg>; sebastien(a)registry.godaddy <sebastien(a)registry.godaddy> Subject: AW: Clarification Question on the GAC Communique (SubPro) Dear Jeff Thanks very much for your question. IMO the GAC Communique calls for something more than just "observer" status beyond the one member slot accorded to the GAC (as to other ACs). At the same time I feel the GAC is not asking the GNSO to completely get rid of a closed approach for the membership of the GGP WG, but perhaps allowing for 3 GAC Members or perhaps 2 Members and 2 Alternates - in order to allow for full participation of those in the GAC who have shown interest in having an active role. I have informally exchanged on this with Manal, and she’ll follow-up on Philippe‘s letter calling for volunteers shortly, making reference to the GAC Communique and our reading of it. hope this helps for the time being kindly jorge ________________________________ Von: Jeff Neuman <jeff(a)jjnsolutions.com> Datum: 26. September 2022 um 23:40:13 MESZ An: Cancio Jorge BAKOM <Jorge.Cancio(a)bakom.admin.ch> Cc: Manal Ismail <manal(a)tra.gov.eg>, Sebastien(a)registry.godaddy <sebastien(a)registry.godaddy> Betreff: Clarification Question on the GAC Communique (SubPro) Dear Jorge, In the GAC Communique, it states: “Stressing the need to promote diversity and a balanced geographical engagement among stakeholders, the GAC reaffirmed its continued interest in the improvement of Applicant Support for the next round of New gTLDs, noting the importance of active GAC participation in the upcoming GGP. In this regard, the GAC calls on the GNSO Council to allow broader participation from interested GAC participants, as well as other members of the community, beyond the single member per Advisory Committee presently envisioned by the call for volunteers communicated to the GAC.” As you may be aware, all members of the community, including the GAC, are invited to be observers to the GGP group which will provide them with read only access to the mailing list and the ability to join all group calls in listen-only mode. Is the Communique asking the GNSO to open the GGP group up to all community members to be participants and not just observers? Or does the “observer” status for all members of the community satisfy the GAC’s request? Sincerely, Jeff Neuman GNSO Liaison to GAC [cid:image001.png@01D8D1CE.FC3B1BF0] 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

4 5

Please verify your google email address
by Julie Bisland 28 Sep '22

28 Sep '22

Dear GNSO Councilors, Please be so kind as to verify your gmail address to allow for accessing shared google docs. Although you may have provided this in the past, we are asking all to reconfirm; please send your google account email address off-list to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> 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

Re: [council] ICANN75 GAC Communique
by Julie Hedlund 27 Sep '22

27 Sep '22

Hi Anne and all, Staff notes that there may have been a misunderstanding stemming from an error in the original Call for Volunteers for the GGP. Specifically, in respect of Observers to the GGP, the Call stated, "Note that in addition to the single representative from your group, the GGP permits Observers to the process. Observers are anyone interested in the GGP, who are provided with read-only access to the mailing list and are not invited to attend meetings." Subsequently, the GNSO Secretariat sent a message last week to all SGs/Cs, SOs, and ACs to clarify that Observers will in fact be able to sign-up and receive invitations for the meeting and will be able attend GGP meetings in real-time, though they will only be able to listen to the conversation. Kind regards, Julie From: council <council-bounces(a)gnso.icann.org> on behalf of "Aikman-Scalese, Anne via council" <council(a)gnso.icann.org> Reply-To: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Monday, September 26, 2022 at 4:01 PM To: Jeff Neuman <jeff(a)jjnsolutions.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [council] ICANN75 GAC Communique Hi Jeff and everyone, I noted in the GAC Communique that there is a “call upon GNSO Council” to broaden the GAC representation in the GGP on Applicant Support. See language below. Anne “Stressing the need to promote diversity and a balanced geographical engagement among stakeholders, the GAC reaffirmed its continued interest in the improvement of Applicant Support for the next round of New gTLDs, noting the importance of active GAC participation in the upcoming GGP. In this regard, the GAC calls on the GNSO Council to allow broader participation from interested GAC participants, as well as other members of the community, beyond the single member per Advisory Committee presently envisioned by the call for volunteers communicated to the GAC.” Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8D1C4.B5A982D0] From: council <council-bounces(a)gnso.icann.org> On Behalf Of Jeff Neuman via council Sent: Monday, September 26, 2022 10:49 AM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>; council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: Re: [council] ICANN75 GAC Communique [EXTERNAL] ________________________________ Thanks Nathalie. As a reminder from the wrap-up, Susan (and I believe Desiree) volunteered to have a look at the Communique to see whether there is anything they would recommend to the Council that we may wish to address. There is no GAC Advice or follow up to GAC Advice, but there are a number of Issues of Importance which involve GNSO topics. If there is anyone else that wants to do such a review, please let me know. If this group does want to address anything, and the Council agrees, we can then propose the best mechanism for such a response (even if not using the formal response template reserved for responses to GAC Advice). Sincerely, Jeff Neuman GNSO Liaison to GAC [cid:image003.png@01D8D1C4.B5A982D0] 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!-DRZsDl3Pjyk…> From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Nathalie Peregrine via council Sent: Monday, September 26, 2022 1:26 PM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] ICANN75 GAC Communique Dear all, Please find attached the ICANN75 GAC Communique. You may also find it online at: https://gac.icann.org/contentMigrated/icann75-kuala-lumpur-communique [gac.icann.org]<https://urldefense.com/v3/__https:/gac.icann.org/contentMigrated/icann75-ku…> Thank you! Nathalie ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

3 3