Please find at the attached link the GAC briefing documents which were recently posted on the GAC website: https://gac.icann.org/briefing-materials/icann71-gac-briefings-v1.pdf As an example of briefings regarding GNSO Activities, you can review page 23 (of 117) which looks at “GNSO Policy Development on DNS Abuse Mitigation”. I hope you find this helpful in our discussions. Sincerely, Jeff [cid:image001.png@01D77265.0203DD30] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Marie Pattullo - AIM via council Sent: Tuesday, July 6, 2021 11:05 AM To: philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>; Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; council@gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] Review of the GNSO Liaison to the GAC Role As ever, thanks to leadership for their unflagging work! I admit to being a little confused as to why we need this (especially given the multiple discussions about lack of Council time and resource constraints) and where it came from, but from the perspective of the BC: having an active Council liaison to the GAC is a practical, sensible idea which we support. Not only is communication always a good thing, as is relationship-building, that also helps to surface concerns early on so hopefully we can avoid later bumps in the road. I appreciate the updates on the GAC perspective from someone who can translate them into GNSO-relevant concerns, and I think we should, as part of any request to the GAC about the liaison role, also ask if they appreciate the same in the other direction! I do admit that I am a little concerned about GAC policy staff briefing the GAC on GNSO issues without any sort of input from either GNSO policy staff or the GNSO itself. I’m not for a second suggesting that GAC staff should publicise all drafts or the like, but if GAC staff is issuing briefings about any other SO/AC, there are clear possibilities for misunderstandings. Again on a practical level, it would make sense to me that we were at least consulted on what’s being said just in case nuances are missed and later misunderstood. As for the role of the liaison towards Council, forgive my naivety but I thought that was self-explanatory: reporting back to us on the GAC’s main issues, especially where they concern the GNSO’s issues, and of course interacting with the GAC itself. Looking back at the request for candidates we issued last year, it looks straightforward to me: The Liaison will be primarily responsible for providing timely updates to the GAC on GNSO policy development activities in order to complement the existing notification processes as well as answering questions in relation to these (GNSO) activities that GAC members may have. Furthermore, the Liaison will be responsible for providing the GNSO Council with regular updates on progress, including on GAC activities, specifically in so far as these relate to issues of interest to the GNSO. The objective of the liaison mechanism, in combination with other mechanisms and early engagement tools, is to facilitate effective early engagement of the GAC as well as generally assist with flow of information between the GAC and the GNSO. In addition to these engagement tools, regular co-ordination calls are to be scheduled between the GNSO Liaison to the GAC and the GAC Leadership/GAC Support Staff to ascertain that all the relevant information has been received by the GAC and progress is being made, following which a regular status update is provided by the Liaison to the GNSO Council. Apologies for my confusion/naivety! Best to all, Marie From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Friday, 2 July 2021 17:50 To: Tomslin Samme-Nlar <mesumbeslin@gmail.com<mailto:mesumbeslin@gmail.com>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org>; GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Review of the GNSO Liaison to the GAC Role Thanks Tomslin. Good point, 1) (consultation+revision of the role) and 2) (expected role within council) are largely independent, so they’re meant to run in parallel. Clearly, we don’t want this to be open-ended, and I’m hopeful that by late September, leadership will have something to offer. Regards, Philippe From: Tomslin Samme-Nlar [mailto:mesumbeslin@gmail.com] Sent: Friday, July 2, 2021 1:54 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com<mailto:philippe.fouquart@orange.com>> Cc: GNSO Council List <council@gnso.icann.org<mailto:council@gnso.icann.org>>; gnso-secs@icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] Review of the GNSO Liaison to the GAC Role Hi Philippe, I want to thank the council leadership for this well thought out proposal. Is it possible to have a rough estimate as to how long tasks 1 & 2 would take? Will they happen in parallel or sequentially? Regards, Tomslin @LinkedIn: https://www.linkedin.com/in/tomslin/ On Fri, 2 Jul 2021 at 04:00, philippe.fouquart--- via council <council@gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi again, During wrap-up we initiated a review of the GNSO Liaison to the GAC Role, and agreed for leadership to come up with a proposal for the next steps, which you will find attached for your review and comments (reproduced below). Please note that we consider accommodating the timelines of this review and the appointment of the liaison. 1. The GNSO Chair to reach out to the GAC Chair to seek input from the GAC side on the role and function of the Liaison. In this context, further consideration needs to be given whether a formal review and/or update to the role description is necessary and helpful, and if so, how this could be achieved (for example, both leadership teams with input from the Liaison as well as the GAC point of contact, could take on this task). As part of this conversation, the GNSO Chair would also share the recommended improvements that have been recently put forward by the Liaison with the Council for consideration (see slides<https://community.icann.org/download/attachments/162890199/v2%20GNSO%20GAC%2...>), noting that at this point these are recommendations from the Liaison that have not been fully considered nor endorsed by the Council. 2. Council leadership to develop proposed guidelines in relation to the Liaison’s participation and expected role when engaging with the Council and/or related activities. As this aspect of the Liaison role is solely focused on the engagement of the Liaison with the Council, this is not expected to be part of a possible review as referenced in 1). 3. Council to consider whether to postpone reconfirmation of the Liaison role while 1. and 2. are ongoing. The current Liaison would remain in his post until 1 and 2 are complete so that both the Council and the Liaison can make an informed decision, based on an updated role description, about possible reappointment or whether it will be necessary to launch a new call for volunteers. Thanks, 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. _______________________________________________ council mailing list council@gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ 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.
