April 2018 - council - lists.icann.org

Re: [council] The Information Transparency Initiative (ITI) Feedback Site is Now Live - ICANN - Blog by David Conrad
by Mary Wong July 3, 2019

July 3, 2019

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

RPM Working Group status report on its Council-approved data collection exercise
by Mary Wong Aug. 15, 2018

Aug. 15, 2018

Dear Councilors, Please find attached the first report from the RPM Review PDP Working Group, summarizing where things stand with the extensive data collection effort that the Council approved in September 2017, for the Sunrise and Trademark Claims RPMs. You may recall that the Council’s approval also expressly requested monthly reports beginning in January 2018. As the Request for Proposal was issued at the end of January, with interested potential vendors beginning to engage in February, the report consolidates the January and February activities. It also includes the full RFP timeline. Please let staff or the current Working Group chairs (Kathy Kleiman and Phil Corwin, cc’d on this email) know if you have any questions or comments. Thank you! Cheers Mary

3 2

Status Update: Privacy and Proxy Services Accreditation Implementation Review Team
by Darcy Southwell July 16, 2018

July 16, 2018

Dear Councilors, I wanted to provide you with an update regarding the Privacy and Proxy Services Accreditation Implementation Review Team. Accreditation Agreement IRT members have been working with Staff for some time on the draft accreditation agreement and have gotten to a place where most of the language is supported by a general consensus. However, there is one key issue that remains unresolved – the PSWG insists the contract require Privacy/Proxy providers to respond to “high priority” requests within 24 hours. In Puerto Rico, a small group of registrars met with key PSWG representatives to try to reach a resolution on this issue, and then the entire IRT working group met again to continue attempts to reach a resolution. The discussion has continued on the email list, but remains unresolved. It is the PSWG’s position that disclosure of customer information for “high priority” requests must be done within 24 hours because lives are in danger. They were clear in their statements during the small group meeting in Puerto Rico that these “high priority” requests should ideally be responded to immediately upon receipt but at least within one hour. The PSWG feels they have compromised extensively by agreeing to 24 hours. Registrar members of the IRT are concerned with the contractual language for a few reasons: (1) it creates a presumption of immediate disclosure (assuming the provider doesn’t have to perform any investigation/verification relating to the request, (2) a potential demand to bypass or ignore due process, and 3) creates an unworkable expectation of privacy/proxy providers around the globe, many of whom who do not operate with 24x7 staffing for this type of issue. Some registrar members have also expressed concern that establishing this 24-hour disclosure requirement is stepping beyond the policy recommendations of the PDP and effectively creating new policy. Accreditation Pricing In Puerto Rico, Staff presented its accreditation pricing model, based on simple cost recovery for ICANN. IRT member asked a number of questions about the detail behind the pricing model, and await that detail from Staff. Based on various meetings in Puerto Rico, some IRT members expressed concern that the pricing model simply mirrors the registrar accreditation model and was not based on any sort of actual cost-recovery plan. And as mentioned on the Council list last month and during our Council meetings in Puerto Rico, there is also concern that some affected departments within ICANN org are not aware of the impact this program may have on its needs for personnel or other support. Data Escrow Specification Significant revisions were needed by Staff to adjust the current registrar data escrow specification to fit into this accreditation program. Staff is expected to deliver that draft to the IRT this week. Last week’s meeting was canceled due to the AdobeConnect issues. This week’s meeting was canceled to allow staff time to get the data escrow specification draft done and circulated to the members. Next meeting should be Tuesday, April 10. Staff has indicated the proposed documents will be ready for publication for public comment in late April or Early May. I understand this issue will be listed for discussion on our April 26, 2018, Council meeting agenda. Thanks, Darcy ---------------- Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart

2 6

Agenda for Council meeting
by Heather Forrest June 2, 2018

June 2, 2018

Colleagues, Without the AC room, we'll be relying on the agenda and links as posted in the ICANN61 meeting schedule, here: https://61.schedule.icann.org/meetings/647702 Many thanks and best wishes, Heather

5 6

Community member liability for participation in PDPs
by Ayden Férdeline May 31, 2018

May 31, 2018

Dear all, As we enter into discussions around next steps re: RDS/GDPR and entertain the possibility of an Expedited PDP, I wanted to re-raise a question that Stephanie Perrin asked in Abu Dhabi, and to ask whether or not a response to it was received. And if the answer is we did not receive a response, I think it is important we obtain one urgently. If, in order to receive a response, we must put this question on Council letterhead and submit it as a formal piece of correspondence, I would like to suggest that we do so. In Abu Dhabi, Stephanie asked the CEO whether community members who participate in Policy Development Processes could be held liable in the event of civil litigation following on from the policies which we develop. She noted that board members, as directors, and employees, as agents of ICANN, have immunity, but wanted to know if ICANN was absorbing this liability too for the community members who participate in the activities of the multistakeholder community. She said we need protection too. I would like to be able to pull out a transcript and to quote Stephanie directly, however I have reviewed many of them today and cannot find her question in there. However, I do distinctly remember it being asked and a follow-up question coming from another member of the Council. Maybe I missed it in the transcripts; if so, I would appreciate if someone could please link to this transcript and provide the page number. Thanks! Best wishes, Ayden Férdeline

5 10

Brief Status Report from the GNSO Review Working Group on Progress and Implementation
by Julie Hedlund May 11, 2018

May 11, 2018

Dear GNSO Council members, In accordance with the document and motion deadline of 04 March, on behalf of the GNSO Review Working Group (WG), here is a brief status report on the progress and implementation of the GNSO Review recommendations. Note also that the previous report provided for the Organizational Effectiveness Committee (OEC) and to the GNSO Council at ICANN60 is available at: https://gnso.icann.org/en/drafts/gnso-review-progress-implementation-report…. As you may know, the GNSO Review WG is executing and overseeing the implementation of the GNSO Review 2 recommendations. This brief status report is a required periodic update to the GNSO Council. The Working Group was initiated on 15 March 2017 and has been meeting bi-weekly. The Working Group expects to complete the implementation of all of the recommendations within the original timeline, not later than September 2018. Kind regards, Julie Julie Hedlund, Policy Director

1 1

Re: [council] Motion in memory of Stéphane
by Mary Wong April 30, 2018

April 30, 2018

Dear all, To follow up on Donna’s note, if you or someone from your communities wish to send a personal note to Stephane’s family, you may use this email address: rip.svg.rip(a)gmail.com<mailto:rip.svg.rip@gmail.com>. Alternatively, if you prefer, staff can forward messages directly from you to Julie (his widow) or Delphine (his ex-wife and mother of their children) to their personal email addresses. Thank you. Cheers Mary From: council <council-bounces(a)gnso.icann.org> on behalf of "Austin, Donna via council" <council(a)gnso.icann.org> Reply-To: "Austin, Donna" <Donna.Austin(a)team.neustar> Date: Monday, April 30, 2018 at 16:45 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: Re: [council] Motion in memory of Stéphane Dear Councilors On our behalf, Glen de Saint Gery sent the Motion in memory of Stéphane, and the recording, to Stéphane's family. Please see Glen’s email below. I’ve also attached an email Glen sent to Heather, Rafik and I about Stephane’s service, which Glen describes beautifully. Donna From: Glen De Saint Gery [mailto:glendesaintgery@gmail.com] Sent: Friday, April 27, 2018 2:48 PM To: Austin, Donna <Donna.Austin(a)team.neustar<mailto:Donna.Austin@team.neustar>> Cc: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>>; Dammak Rafik <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>; Glen de Saint Gery <glendesaintgery(a)gmail.com<mailto:glendesaintgery@gmail.com>> Subject: Re: [EXTERNAL] Re: Motion in memory of Stéphane Dear All, Just to say that Delphine, the mother of Stéphane's two children Mila and Ethan told me that she shared the Council resolution and recording with Stéphane's parents and with his uncle who was a partner in Indom. They were all extremely touched. Warm regards Glen

1 0

Re: [council] Motion in memory of Stéphane
by Austin, Donna April 30, 2018

April 30, 2018

Dear Councilors On our behalf, Glen de Saint Gery sent the Motion in memory of Stéphane, and the recording, to Stéphane's family. Please see Glen’s email below. I’ve also attached an email Glen sent to Heather, Rafik and I about Stephane’s service, which Glen describes beautifully. Donna From: Glen De Saint Gery [mailto:glendesaintgery@gmail.com] Sent: Friday, April 27, 2018 2:48 PM To: Austin, Donna <Donna.Austin(a)team.neustar<mailto:Donna.Austin@team.neustar>> Cc: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>>; Dammak Rafik <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>; Glen de Saint Gery <glendesaintgery(a)gmail.com<mailto:glendesaintgery@gmail.com>> Subject: Re: [EXTERNAL] Re: Motion in memory of Stéphane Dear All, Just to say that Delphine, the mother of Stéphane's two children Mila and Ethan told me that she shared the Council resolution and recording with Stéphane's parents and with his uncle who was a partner in Indom. They were all extremely touched. Warm regards Glen

1 0

Please review: GNSO Council resolutions 26 April 2018
by Nathalie Peregrine April 27, 2018

April 27, 2018

Dear all, Please find below the resolutions from the GNSO Council at its meeting on Thursday, 26 April 2018. They have been posted on the GNSO website here: https://gnso.icann.org/en/council/resolutions Thank you, Nathalie CONSENT AGENDA * Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board Whereas, 1. 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. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. 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. 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. 1. The GNSO Council adopts the GNSO Review of the San Juan GAC Communiqué (see https://gac.icann.org/contentMigrated/icann61-gac-communique) and requests that the GNSO Council Chair communicate the GNSO Review of the San Juan GAC Communiqué to the ICANN Board. 2. 2. The GNSO Council requests that the GNSO Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board. * The GNSO Council agrees that ICANN org should continue to treat the Community gTLD Change Request process as a matter of implementation. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-26apr18-en.…> In Memory of Stéphane Van Gelder - motion updated with friendly amendments proposed by Rafik Dammak & Donna Austin Submitted by: Rafik Dammak Seconded by: the GNSO Council Whereas: 1.Stéphane Van Gelder first entered the domain name business in the late 1990s when he founded Indom, a registrar in France, which later become part of the GroupNBT based in the United Kingdom. It was while Stéphane was General manager of INDOM that he was elected to the GNSO Council by the Registrar Stakeholder Group. 2. Stéphane served on the GNSO Council from 2008 through 2012, as an elected representative of the Registrars Constituency. 3. Stéphane served as Vice Chair of the GNSO Council in 2010 and was elected and served two consecutive terms as Chair of the GNSO Council in 2011 and 2012. 4. As Chair of the GNSO Council, Stéphane was an impartial and neutral facilitator on all issues. For Stéphane, remaining neutral was key to ensuring collective dialogue. 5. Stéphane made significant contributions to ICANN and was a strong and respected community leader. During his tenure as GNSO Chair, Stéphane oversaw and shepherded the: a. completion of an extensive update of the GNSO's operating procedures; b. establishment of the DNS Security & Stability Analysis working group jointly with the ALAC, ccNSO and NRO; c. completion of the Fast Flux, Post-Expiration Domain Name Recovery and Inter-Registrar Transfer Policy (IRTP) Part B Policy Development Processes (PDPs) and the joint ccNSO-GNSO Internationalized Domain Name working group; d. launch of the IRTP Part C, Thick WHOIS and Locking of Domain Names subject to Uniform Dispute Resolution Policy Proceedings PDPs; and (e) continuing work on WHOIS studies, registration abuse policies, and multiple other GNSO projects. e. the completion of the Applicant Guidebook for the 2012 New gTLD Program and the launch of the Program. f. Stéphane was a well-respected and much liked member of not only the GNSO, but of the broader ICANN Community. He was admired for his passion, his fairness, his ability to find the best in people and his true gift for uniting people. g. Stéphane’s passing is a great loss to the many people in the ICANN community that had the pleasure to work and interact with him, and for his many friends at ICANN the loss is significant. Resolved: 1.The GNSO Council wishes to recognize the significant contribution Stéphane made to the GNSO Council during his tenure and his notable achievements during this time. 2. Stéphane’s genuine passion, energy and commitment to the Internet and all that it brought to the world was second to none and we will miss him dearly. 3. On behalf of the current and previous GNSO Councils, we offer our deepest and heartfelt sympathies to his family and friends at this most difficult time. Vote results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-26apr18-en.…>

1 0

MP3 and WebEx recording and chat transcript/ GNSO Council Teleconference 26 April 2018
by Terri Agnew April 26, 2018

April 26, 2018

Dear GNSO Council, Please find below the MP3, WebEx recording and WebEx chat of the GNSO Council teleconference, held on Thursday, 26 April 2018. MP3: https://audio.icann.org/gnso/gnso-council-26apr18-en.mp3 WebEx Recording URL: <https://mytrials.webex.com/mytrials/onstage/playback.php?RCID=39f7ea5d885bd 78f1cea09f049af0945> https://mytrials.webex.com/mytrials/onstage/playback.php?RCID=39f7ea5d885bd7 8f1cea09f049af0945 Recording password: pY4b8PvC WebEx chat at: https://gnso.icann.org/sites/default/files/file/field-file-attach/transcript -chat-council-26apr18-en.pdf all on page: <https://gnso.icann.org/en/group-activities/calendar> 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: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy -efforts.htm#newcomers> GNSO Newcomer pages

1 0