Dear Councilors, A reminder that Council is in dire need for liaison to EPDP phase 2A, so please let us know if you’re interested. This phase 2A is expected to be much more limited in time than the previous expedited PDPs(!). Thanks, Regards, Philippe From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Steve Chan Sent: Tuesday, January 12, 2021 2:19 AM To: council@gnso.icann.org Subject: Re: [council] GNSO Council Liaisons Dear Councilors, I just wanted to follow-up on the message below. After reviewing the email, I realized I made a typo that hopefully did not create too much confusion. For the second liaison vacancy, I put EPDP Phase 2 instead of EPDP Phase 2A. With the EPDP Phase 2A having already kicked off, there remains an immediate need to identify a Council liaison to this group. Please give some consideration to whether you might able to serve in this role. Best, Steve From: council <council-bounces@gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> Date: Monday, December 21, 2020 at 3:31 PM To: "council@gnso.icann.org<mailto:council@gnso.icann.org>" <council@gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] GNSO Council Liaisons Dear Councilors, Following the affirmative vote to approve the Consent Agenda on the 17 December 2020 meeting, a number of GNSO Council liaisons are now confirmed. However, note that during the meeting, Olga withdrew her name as the GNSO Council liaison to the EPDP Phase 2 and that there is still an outstanding vacancy for the EPDP Phase 2A. In consultation with Council leadership, here is the proposed path forward. EPDP Phase 2: As this PDP has now concluded, there does not appear to be a pressing need to identify a new liaison, though one will be needed once an Implementation Review Team (IRT) is established. However, and without making too many assumptions, there may be reason that the IRT for Phase 2 will be merged or perhaps be a continuation of the existing IRT, which could allow Sebastien to serve as the single Council liaison to the IRT (assuming there is some form of streamlined IRT and Sebastien is willing of course). The Council leadership proposal here is to leave this position vacant, at least for the moment. EPDP Phase 2A: There is however a need to identify a liaison here, in a timely fashion, as the EPDP Team has already held its first meeting. To give you a sense of the commitment, liaisons typically take part in leadership planning meetings, share information and updates between the WG and Council, provide guidance regarding WG processes, etc. (see role description here: https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-liais...). However, I would note that during the EPDP Phase 2, the liaison also served as the vice-chair, and this possibility is I understand under discussion within the EPDP Phase 2A currently. Assuming that ends up being the outcome, the liaison would then be asked to both fulfill the requirements of being a GNSO Council liaison to the WG, as well as that of being a vice-chair, which is primarily chairing WG calls when the Chair is unavailable. That said, the Chair has indicated that he fully anticipates being available for this limited duration effort. The Council leadership proposal here is of course to identify a volunteer to fill this position. Best, Steve Steven Chan Senior Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@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=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> 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_group...> _________________________________________________________________________________________________________________________ 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.