Many thanks Jeff. This is very helpful. Kind regards, Julie On Sep 26, 2022, at 5:34 PM, Jeff Neuman <Jeff@jjnsolutions.com> wrote: Thanks Julie for the clarification. However, I believe the GAC is referring not just to observing the GGP, but actually participating. I will send a clarification question to the GAC’s point of contact to see if he can shed any further light on this statement. Sincerely, Jeff Neuman GNSO Liaison to the GAC [image004.png] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com [jjnsolutions.com]<https://urldefense.com/v3/__http://jjnsolutions.com__;!!PtGJab4!-FNgkfwoXkrI...> From: Julie Hedlund <julie.hedlund@icann.org> Sent: Monday, September 26, 2022 4:26 PM To: Aikman-Scalese, Anne <AAikman@lewisroca.com>; Jeff Neuman <jeff@jjnsolutions.com>; Nathalie Peregrine <nathalie.peregrine@icann.org>; council@gnso.icann.org Cc: gnso-secs@icann.org Subject: Re: [council] ICANN75 GAC Communique 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@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Aikman-Scalese, Anne via council" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Reply-To: "Aikman-Scalese, Anne" <AAikman@lewisroca.com<mailto:AAikman@lewisroca.com>> Date: Monday, September 26, 2022 at 4:01 PM To: Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>>, Nathalie Peregrine <nathalie.peregrine@icann.org<mailto:nathalie.peregrine@icann.org>>, "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@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@lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [image006.png] From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Jeff Neuman via council Sent: Monday, September 26, 2022 10:49 AM To: Nathalie Peregrine <nathalie.peregrine@icann.org<mailto:nathalie.peregrine@icann.org>>; council@gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs@icann.org<mailto:gnso-secs@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 [image007.png] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com [jjnsolutions.com]<https://urldefense.com/v3/__http:/jjnsolutions.com__;!!PtGJab4!-DRZsDl3PjykJ...> From: council <council-bounces@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@gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs@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-kua...> 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.
