December 2018 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 4

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong 03 Jul '19

03 Jul '19

Dear Ayden and all, We apologize if there were difficulties with accessing the feedback tool – there ought not to be any, so please do try it again if you wish to provide feedback. Please be assured that ICANN organization is committed to and interested in gathering the community’s feedback on each of the features that we will be rolling out with the objective of improving the findability, transparency, and accessibility of ICANN public content. The deadlines are, unfortunately, what they are in order to ensure that we are able to deliver on this major project on budget and on time. There will certainly be multiple and additional opportunities and forums for continuing community feedback, as noted in David’s blog that is referenced in the announcement below. Thank you. Best regards, Mary From: council <council-bounces(a)gnso.icann.org> on behalf of Ayden Férdeline <icann(a)ferdeline.com> Reply-To: Ayden Férdeline <icann(a)ferdeline.com> Date: Wednesday, April 25, 2018 at 09:17 To: Heather Forrest <haforrestesq(a)gmail.com> Cc: GNSO Council List <council(a)gnso.icann.org> Subject: Re: [council] Fwd: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad Given comments are being sought for less than a week, this does not strike me as a genuine consultative activity but appears to be a token form of participation intended to manipulate public opinion. This new website implies a shift towards greater consultation and community participation in ICANN's content strategy, but we cannot actually wield any influence by commenting here. (And not just because if you press the 'provide feedback' button, you see "The feedback survey is temporarily unavailable.") From what I understand we are not even being asked to comment on anything important. The list of 250 definitions, which I would like to review for neutrality and accuracy, are not online and it sounds like they have already been approved internally and are not open to community review. Are we really being asked to comment on just the glossary tool itself, and did ICANN really produce a video mockup and slide deck of something so incredibly mundane when it is up for public comment for just a week? Please forgive the negative sentiment to my message here, but it really seems a poor allocation of resources to me. Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 25 April 2018 3:03 PM, Heather Forrest <haforrestesq(a)gmail.com> wrote: Dear Council colleagues, I am pleased to pass on David Olive's update, below, on the Information Transparency Initiative. Best wishes, Heather ---------- Forwarded message ---------- From: "David Olive" <david.olive(a)icann.org<mailto:david.olive@icann.org>> Date: 24/04/2018 10:37 AM Subject: [So-ac-sg-cleaders] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad To: "so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>" <so-ac-sg-cleaders(a)icann.org<mailto:so-ac-sg-cleaders@icann.org>> Cc: "David Conrad" <david.conrad(a)icann.org<mailto:david.conrad@icann.org>>, "Jana Juginovic" <jana.juginovic(a)icann.org<mailto:jana.juginovic@icann.org>> https://www.icann.org/news/blog/the-information-transparency-initiative-iti…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> The Information Transparency Initiative (ITI) Feedback Site is Now Live I'm pleased to announce that today, we launched the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> (feedback.icann.org[feedback.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__feedback.icann.org&d=Dw…>). As I have written about in previous blogs and discussed at ICANN60 and ICANN61 sessions, this site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is intended to provide you, the ICANN community, with the ability to share your input on the content and features the ITI team is working on to improve the findability, transparency, and accessibility of ICANN public content. The first item we are looking for your comments on is an updated Acronyms and Terms feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to replace the existing feature[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Our update doubles the number of terms available, provides up-to-date definitions for the terms, and improves search. Unlike most of the ITI project, we will launch this updated feature on the current https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…> before 31 May 2018. The deadline to provide your input on the proposed updates to Acronyms and Terms is 30 April 2018, 23:59 UTC. Please visit feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> to experience the proposed changes and complete a short survey. How the ITI Feedback Site Works The ITI Team will regularly post documents, mockups, or video walkthroughs of new content and features. The proposed content or feature items are listed on the homepage under the heading "Feedback Needed." Each item lists a deadline by which you need to provide input. Simply click on the item you're interested in. This will take you to another page, which provides you with the option to either download a mockup or watch a video walkthrough. Once you have completed that task, click on the "Feedback" button to complete a short survey or email your feedback to informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Once the deadline has passed, the ITI Team will collect and publish all comments to feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…>. All published results of the survey will be anonymous, unless otherwise requested by the submitter. We will review all submissions and make our best efforts to implement the feedback, prioritizing input that serves the goals of improving search and accessibility, and increasing the transparency of our content. Feedback Deadlines We do have a tight deadline for community comments – one week for each new item. The reason for this timeline is we need to maintain a rigorous development schedule to ensure we are delivering the project on time and within budget. However, feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> is not your only avenue to share input. ITI has many other opportunities to learn about ITI and provide comments including: * Regular sessions at ICANN Public Meetings. * Special sessions or webinars for Supporting Organizations and Advisory Committees (SO/ACs) on request or for special features and content like Public Comment. * Monthly blogs and newsletters. * Via email at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org> Feedback Translations As I outlined above, we are working at a brisk development pace. This does limit our ability to fully translate feedback.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and its survey. But, if you want to share feedback in another language, email us at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. It is important to emphasize that one of the primary goals of ITI is a multilingual https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, and the sooner we complete this project, the sooner we can deliver on that goal. ITI Goals ITI's goal is not a revamp of https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>. While the ITI team is working on making improvements to your User Experience (UX) on https://icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMGa…>, the vast majority of our efforts are focused on: * Creating content governance through new, enforced workflows and the creation of a consistent, multilingual taxonomy. * Building new technical infrastructures including a first-ever for ICANN document management system (DMS) and a new content management system (CMS). This new infrastructure will enforce this governance and enable improved content findability. Much of this foundational work won't be available on the feedback site for your input, but we will show the intended benefits of this work through the content and features we will share. ITI Update The ITI team has been hard at work completing that foundational work I mentioned above. We have completed the following tasks since the January 2018 launch of ITI: * The foundational build of the DMS and CMS, and the integration between the two platforms. * Sixty percent of the content audit and the taxonomy creation. * Interviews with SO/AC leaders, registrants, registrars, Fellows, and other ICANN stakeholders. We have also begun work on the following items: * Content modelling, workflow creation, and content governance enforcement in the DMS. * Accessibility guidelines and multilingual site implementation planning. ITI will launch in December 2019. ITI Backgrounders For those of you unfamiliar with ITI, you can read about what it is and how it will benefit the ICANN community in my kickoff blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. You can learn more about how the content audit and taxonomy will help your search experience in my January blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We also outlined the differences between ITI and the Open Data Initiative (ODI) in our pre-ICANN61 blog[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>. We Need Your Feedback Remember, we need your input to help us make the specific improvements to search, transparency, and accessibility that you need and want. Please visit the ITI feedback site[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_itifeedb…> and email us anytime at informationtransparency(a)icann.org<mailto:informationtransparency@icann.org>. Comments Log in to Comment[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> or Sign Up[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_users_si…> Details * ICANN Blog * Author: David Conrad, Chief Technology Officer (CTO) and Senior Vice-President * 23 Apr 2018 David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org<mailto:So-ac-sg-cleaders@icann.org> https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

4 7

Call for volunteers - Operating Standards – Updated Draft for Public Comment
by Marika Konings 04 Jan '19

04 Jan '19

Dear All, As noted on the call earlier today, an updated draft operating standards for specific review has been published for public comment (see below). As you may recall, the GNSO Council provided input on the original version (see https://mm.icann.org/pipermail/comments-reviews-standards-17oct17/2018q1/00…). A small drafting team may want to review how the Council’s input was addressed and/or any other items that may need to be considered. Rafik has already volunteered to participate – are there any other Council members interested to assist in this regard? As the deadline for comments is 11 February, ideally a draft is shared in time for consideration during the GNSO Council meeting on 24 January. Best regard, Marika From: Jennifer Bryce <jennifer.bryce(a)icann.org> Date: Wednesday, December 19, 2018 at 05:07 To: "Drazek, Keith" <kdrazek(a)verisign.com> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Lars HOFFMANN <lars.hoffmann(a)icann.org> Subject: Operating Standards – Updated Draft for Public Comment Dear Keith, This is to inform you that the updated Draft Operating Standards for Specific Reviews [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> have been posted for public comment. The ICANN organization has developed the Operating Standards to provide guidance on conducting Specific Reviews, as mandated by the Bylaws. Building from the prior draft that was published for public comment [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> in October 2017, the updated draft now available for public comment includes feedback from public sessions at ICANN57 [icann572016.sched.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann572016.sched.com_…>, ICANN58 [icann58copenhagen2017.sched.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann58copenhagen2017.…>, ICANN60 [icann60abudhabi2017.sched.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann60abudhabi2017.sc…>, and ICANN63 [63.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__63.schedule.icann.org_…>, webinars conducted in February 2017<https://community.icann.org/x/LKLRAw>, October 2017<https://community.icann.org/x/JZVEB>, and October 2018<https://community.icann.org/x/CwGrBQ>, and submissions [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> to the 2017/2018 public comment period, as well as best practices from Specific Reviews currently conducted. Due to the holidays, the Operating Standards will be available for an extended public comment period of 54 days until 11 February 2019. Subsequently, a public session on the final document is planned for ICANN64 in Kobe. In addition, if the GNSO Council would like a briefing during one of its sessions in Kobe on the outcome of the public comment and next steps regarding the Operating Standards, please, reach out to mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org>. Following Kobe, ICANN organization will incorporate feedback from the public comment proceeding and any feedback received during ICANN64 into an updated final document that will be presented to the ICANN Board, with the aim of adoption in April 2019. Please, feel free to share this information with the GNSO Council at your earliest convenience. Please, do not hesitate to contact me should you have any questions. Many thanks and best wishes, Jennifer Bryce, on behalf of Lars Hoffmann -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

4 3

Two Letters for Council Review
by Drazek, Keith 28 Dec '18

28 Dec '18

Hi all, As we wrap up 2018, I have attached two letters for your review: 1. Draft GNSO Council response to the GAC's Barcelona letter on IGO-INGO CRP. 2. Draft GNSO Council response to Cherine's 14 November letter on the EPDP WG and a potential "Plan B." Pam, Rafik and I have coordinated together and with Staff on developing these responses. Please review and let us know if you have any concerns. We will target delivery of these letters during the first week in January. Thanks, and I wish you all a very happy New Year! Best, Keith

2 1

GNSO Council Abstention Notification Form [#294]
by ICANN 28 Dec '18

28 Dec '18

1 0

Draft minutes of the GNSO Council meeting 20 December 2018
by Nathalie Peregrine 28 Dec '18

28 Dec '18

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting Thursday 20 December 2018 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 7 January 2019. Thank you very much. Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

CPH Letter to EPDP Leadership
by Ayden Férdeline 27 Dec '18

27 Dec '18

Dear all, I suggest reading the attached letter dated 21 December 2018 that the Contracted Parties House [submitted](https://community.icann.org/display/EOTSFGRD/Public+Comments+on+… to the EPDP leadership team. I think it provides an honest assessment of where the EPDP is at, where the EPDP team's Initial Report recommendations originated from, and why the EPDP leadership team's decision to deviate from usual practices vis-a-vis the public comment process was perhaps not recommendable. It is worth emphasizing that this was a leadership team decision which did not have the broader support of the EPDP team. Kind regards, Ayden Férdeline

1 0

MP3, Adobe Connect recording and chat transcript/ GNSO Council meeting on Thursday, 20 December 2018 at 21:00 UTC.
by Terri Agnew 21 Dec '18

21 Dec '18

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the GNSO Council meeting held on Thursday, 20 December 2018 at 21:00 UTC. MP3: https://audio.icann.org/gnso/gnso-council-20dec18-en.mp3 Adobe Connect Recording URL: https://participate.icann.org/p5fo2kpuq89/ Adobe Connect chat at: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcrip… All on page: https://gnso.icann.org/en/group-activities/calendar Thank you. Happy listening and reading! With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_g…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> http://gnso.icann.org/en/ [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_&d=Dw…>

1 0

Update from EPDP leadership regarding the EDPB letter
by Rafik Dammak 21 Dec '18

21 Dec '18

Dear GNSO Councilors: We are writing to report some specific recent actions by the EPDP team. As you know, the EPDP Charter states that, "the Initial Report should be submitted to the European Data Protection Board [EDPB] or other relevant DPAs to request feedback on the applicability of the law in relation to the proposed recommendations, particularly those that may carry over from Temporary Specification to Consensus Policy recommendations to the ICANN Board.” After a detailed and constructive discussion, the EPDP team has decided (for the time being) to not directly contact the EDPB in order to request feedback on the Initial Report. We are writing to explain the thought process that went into that decision and seek any feedback the Council has to offer. As the EPDP team debated and discussed charter questions and issues leading to the publication of the initial report, it identified a set of legal questions (i.e., interpreting the GDPR) that required resolution before certain policy recommendations could be made. During an EPDP meeting, the team debated whether: 1. To send the set of legal questions to the EDPB for input, and 2. To send the Initial Report to the EDPB along with certain messages: o the Initial Report is available for their review and comment, o the Initial Report is a prelude to the Final Report, likely to become ICANN Policy, and o that we are wading through certain legal questions and are getting independent input on those So far, we have decided to do neither, primarily for two reasons. First, the EDPBs own writings and the personal experiences of some EPDP members indicate that the EDPB is NOT a consulting resource. The EDPB provides advisories and guidance to governments and DPAs. The EPDP team determined that we should seek answers to our legal questions through independent legal advice and, perhaps through DPAs. Second, perhaps recognizing that the Initial Report had not yet resolved all issues, the EPDP Team thought that is would not yet be a good use of the EDPB’s time and good will to ask them to opine on something that is incomplete. So, other than a notice that ICANN is working on GDPR issues and is making progress, the team believes that a letter to the EDPB would have little to offer. It was suggested that such a letter would be useful as it would serve to manage EDPB expectations: so that the final report would not provide the “first look” at our work. While some in the EPDP that agreed with this, there were also strong opinions in the EPDP that the letter as currently drafted and timed might actually harm relations with the EDPB. Given that one cannot “unsend” a letter, it was decided to hold off for the time being. As we progress our discussions and watch the interactions between the EDPB and ICANN or between the EDPB and other organizations, we can continue to re-assess our decision and possible send a notice (or a more meaningful notice) at a later date. We would be pleased to provide additional detail or discuss this with the Council in greater detail at your convenience. Sincerely, Kurt & Rafik

2 1

GNSO Council motions 20 December 2018
by Nathalie Peregrine 21 Dec '18

21 Dec '18

Dear all, Please find below the resolutions from the Consent Agenda item during the GNSO Council meeting on Thursday, 20 December 2018 to be posted on the GNSO resolutions<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> page shortly. CONSENT AGENDA Motion - Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board - deferred from the November 2018 meeting Submitted by Pam Little, seconded by Rafik Dammak Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the Barcelona GAC Communiqué (see 2. https://gnso.icann.org/sites/default/files/file/field-file-attach/review-ga…) and requests that the GNSO Council Chair communicate the GNSO Review of the Barcelona GAC Communiqué to the ICANN Board. 3. The GNSO Council requests that the GNSO Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. Nomination of a Mentor for the ICANN Fellowship Program Submitted by: Erika Mann Seconded by: Maxim Alzoba Whereas, 1. On 16 October 2018, the ICANN Fellowship Program invited ICANN’s Supporting Organizations and Advisory Committees to nominate one individual each (total of 7) to serve on the capacity of Fellowship Program mentor for the 2019 calendar year (see https://www.icann.org/news/announcement-2-2018-10-16-en). 2. On 20 November 2018, the GNSO launched an Expression of Interest (EOI) process to solicit volunteers for the GNSO-nominated mentor position (see https://gnso.icann.org/en/announcements/announcement-20nov18-en.htm). 3. The GNSO Council tasked the GNSO Standing Selection Committee (SSC) with reviewing applications and recommending one individual for the GNSO to nominate. 4. The SSC reviewed the applications received, taking into account the criteria outlined in the EOI announcement. 5. The SSC submitted its full consensus recommendation to the GNSO Council on 19 December 2018. 6. The GNSO Council considered the recommendations of the SSC. Resolved, 1. The GNSO nominates Andrew Mack to serve as a ICANN Fellowship Program mentor for a period of one year. 2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to staff supporting the ICANN Fellowship Program. 3. The GNSO Council instructs the GNSO Secretariat to inform the nominated candidate that he or she has been selected. 4. The GNSO Council requests the GNSO Secretariat to send a response to those applicants who were not nominated, thanking them for their interest and encouraging them to apply for future opportunities as they arise. · Confirmation of Heather Forrest to serve as the GNSO Representative to the ICANN Fellowship Program Selection Committee for the remainder of the 2-year term. · Confirmation of the leadership for the GNSO Standing Selection Committee (Chair: Susan Kawaguchi, Vice-Chairs: Poncelet Ileleji and Erica Varlese) Thank you! Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0