- Gnso-epdp-team - lists.icann.org

Two errors in the ALAC Initial Report submission
by Alan Greenberg Jan. 4, 2019

Jan. 4, 2019

One of the eagle-eyed ALAC members has caught two errors in the ALAC submission which unfortunately have the effect of reversing the meaning. Question 45: Without the Admin fields, there is the potential for a registration record having telephone or email contact details for the entity responsible for the registration. should read Without the Admin fields, there is the potential for a registration record NOT having telephone or email contact details for the entity responsible for the registration. Question 87: (this one will hopefully be recognized as an error and not ignorance) GDPR only applies to Legal Persons. should read GDPR only applies to Natural Persons. Alan

1 0

Recordings, Attendance & AC Chat / GNSO Temp Spec gTLD RD EPDP / Thursday, 03 January 2019
by Andrea Glandon Jan. 4, 2019

Jan. 4, 2019

Dear all, Please find the attendance and AC chat attached to this email, and the MP3 and AC recording below from the GNSO Temp Spec gTLD RD EPDP call held on Thursday, 03 January 2019 at 14:00 UTC. These have also been posted on the agenda wiki page: https://community.icann.org/x/-Aj_BQ MP3: https://audio.icann.org/gnso/gnso-epdp-gtld-registration-data-specs-03jan19… AC Recording: https://participate.icann.org/p9c1ehjl4s4/<https://participate.icann.org/p9c1ehjl4s4/?OWASP_CSRFTOKEN=42cbcfdcadb04b8a…> ** Please let me know if your name has been left off the list ** Mailing list archives of the GNSO Temp Spec gTLD RD EPDP : https://mm.icann.org/pipermail/gnso-epdp-team/ Main wiki page for the working group: https://community.icann.org/x/IYEpBQ Thank you. Kind Regards, Andrea Glandon

1 0

Notes and action items from EPDP Team Meeting #37
by Marika Konings Jan. 3, 2019

Jan. 3, 2019

Dear EPDP Team, Please find below the notes and action items from today’s EPDP Team meeting. Best regards, Caitlin, Berry and Marika =================== EPDP Team Meeting #37 Thursday, 3 January 2019 Notes and Action Items High-level Notes/Actions: Action item #1: EPDP Team to review all public comments to the Initial Report using the Public Comment Review Tool (PCRT). The Google form is available for comment review also. The agenda for each meeting will indicate which recommendations will be reviewed for each meeting but please review all comments for Recommendation 1 (all purposes) now. Action item #2: EPDP Team to notify staff support of any unintentional errors as they appear in the PCRTs. Action item #3: Staff support team to update PCRT with notes and agreed upon actions by EPDP Team in review of the comments to Recommendation 1, Purpose 1. Action item #4: RySG reps to prepare an explanation to the rationale (without editing the input received) separating out Purpose 1 into two parts. Action item #5: Staff support team to send latest version of the workbooks to RySG reps for reference in preparation for creating two workbooks to match the RySG comment. Action item #6: Leadership team to give further consideration to whether small teams could accelerate review of proposed edits. Action Item #7: Entire team to consider if there is another place in the report for proposed change #4. Questions for ICANN Org from the EPDP Team: None Notes & Action items These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/ZwPVBQ Proposed Agenda: 1. Roll Call & SOI Updates * Attendance will be taken from Adobe Connect * Remember to mute your microphones when not speaking and state your name before speaking for transcription purposes. * Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. 2. Welcome and Updates from EPDP Team Chair (5 minutes) * Make sure to have https://community.icann.org/display/EOTSFGRD/Public+Comment+Review+Tool readily available during the meeting. This page contains the public comment review tool for all purposes and recommendations. a. Update from legal committee * Second meeting took place yesterday. Further reviewed process for refining questions as well as procurement process with focus on how to avoid conflicts. Three small teams will work on refining the questions outlined in the Initial Report. Next legal committee meeting will take place next Wednesday. b. Review of outstanding action items - see https://community.icann.org/x/NwSNBQ c. Other updates, if applicable 3. Public Comments on the Initial Report (85 minutes) a. High level overview of input received (10 minutes) (see https://community.icann.org/x/R4cWBg) * Obligation for EPDP Team to review and consider all input received. EPDP Team is expected to document how input has been dealt with, even if it is decided that no change is made as a result of the comment. * Need to consider how to document this consideration - PCRT is expected to aid with that. * Agendas for upcoming meetings will include links to the relevant PCRTs that are expected to have been reviewed. Action item #1: EPDP Team to review all public comments to the Initial Report using the Public Comment Review Tool (PCRT). The Google form is available for comment review also. The agenda for each meeting will indicate which recommendations will be reviewed for each meeting but please review all comments for Recommendation 1 (all purposes) now. b. Review and discuss proposed approach for review of public comments (15 minutes) (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-January/001131.html) * See proposed approach circulated * Want to focus on rationale and new thinking - not focus attention on arguments that have already been made and considered. * Need to consider time available and how to best use that time. * Idea for this call would be to focus on purpose 1 and 3 to ease into the process as there appears to be general support for these purposes. * Consider categorization as proposed by Milton on the mailing list: 1. those which are clearly consensual (1, 3, 4,) 2. those which seem to be easily amendable to attain consensus (5, 6) 3. those which have serious opposition and may need to be discarded or greatly modified. EPDP Team should first agree on a categorization of all purposes and where they belong in these categories. * Need to avoid wordsmithing on a call - try to focus on what are themes and have a small team working on those edits that enjoy general support. * Chart in PCRT provides an illustration of types of comments received, however it cannot be taken as a perfect delineation of support across the group as all commenters have been 'counted' individually. Yellow and red parts may need to be the focus areas for EPDP. Could serve as an indicator, but this is not a numbers game as input is not necessarily representative of different interests / parties affected. Nevertheless, still important to hear and listen to other voices. Focus on where same point is made by different stakeholders across the divides. Action item #2: EPDP Team to notify staff support of any unintentional errors as they appear in the PCRTs. c. Commence review of public comments (60 minutes): Purpose 1 – Establish rights of Registered Name Holder (see PCRT) Purpose 3 – Enable communication with Registered Name Holder (see PCRT) * Purpose 1 - see PCRT as well as overview of proposed changes. * Consider how to deliberate on these changes - one by one, or in a group? Could ask for a show of hands to determine support or lack thereof. * Should the word 'activate' be replaced by 'activating a domain name registration'? Note that activate appears 18 times in the Registry and Registrar Agreements. Concern #2 considered addressed. * Proposed change #1 - is there any support for further discussing this proposed change? Should transfer and recovery be added or is this already covered by the reference to the term 'use'? Not necessary to achieve the objective of the purpose. Transfer and Recovery are different data processing steps that described in other purposes, Post-recovery consensus policy may need to be reviewed as follow up work - consider flagging that. You can allocate a domain name and decide not to activate it. You can also activate a domain name and not have a web-page, this is only one function. Agreement that proposed edits are not considered necessary as it is already considered covered by the existing language. * Proposed change #2 - adding obligations here is trying to convert this purpose into something else as it would bring in 3rd party obligations. If considered, it should be responsibilities, instead of obligations. Need to keep clear boundaries between purpose 1 and 2. Obligations are already covered in other purposes. Rationale provided conflates this purpose with other purposes. Rationale is to also reflect responsibilities a domain name registrant has in relation to a domain name registration, not only its rights. Third party access comes from other purposes, this is a registrant specific purpose - for example, updating of registrant data to maintain accurate data. Rights and responsibilities of registrant are framed in the context of responsibilities towards registrars, registries and ICANN. If responsibilities is added, it needs to be made to be very clear to whom these responsibilities are. Intro (subject to registry and registrar terms, conditions, policies and ICANN Consensus Policies) already covers any such obligations. Would legal basis change as a result of rewording the purpose? Proposal to not accept this change for now as there is not sufficient support for making this change. Leave as is. May come back at a later stage to see if opinions have changed as further changes may be made. * Proposed change #3 - no support for discussing this proposed change. The team thought that the suggested rewording succinctly captures a reason for collecting data but, on-balance, preferred the detail included in the bullets of the previously agreed-upon Purpose 1. Already captured by the existing wording. * Proposed change #4 - proposed as a fourth bullet. Comment is based on a policy objective not a data collection / purpose. Is this about zone file access? Not clear how processing domain name registration relates to domain name availability. Does not belong on purpose 1. Put in meeting notes to think about this recommendation as consideration is given to other purposes and comments to see if it belongs somewhere else. Also consider at the end whether issues are caused as a result of the policy recommendation. Is this out of scope for the EPDP Team? Rationale provided by commenter: "It is important to ensure the availability of unregistered names to natural and artificial persons without the availability status being masked in the middle paving way for speculative transactions by intermediaries which may not always be fair. This purpose is added to ensure fairness in the availability of Domain Names to natural and artificial persons; It is acknowledged that some names that are beyond the purview of Trade Marks are desirable names by many, hence have a premium value. To ensure fairness and transparency of opportunities for registering premium names by existing and new processes between ICANN and Registries. * Consider asking legal counsel for guidance on how to draft purposes." Up to proponents to bring this up at appropriate time - no specific action for the EPDP Team at this point in time. * Proposed change #5 - may be helpful to see the detailed data processing steps. Main reasoning related to transfer of data that is required for some registries and not others, for activating very little transfer of personal data is needed, while second purpose addresses those that do require transfer of additional data. Action item #3: Staff support team to update PCRT with notes and agreed upon actions by EPDP Team in review of the comments to Recommendation 1, Purpose 1. Action item #4: RySG reps to prepare an explanation to the rationale (without editing the input received) separating out Purpose 1 into two parts. Action item #5: Staff support team to send latest version of the workbooks to RySG reps for reference in preparation for creating two workbooks to match the RySG comment. Action item #6: Leadership team to give further consideration to whether small teams could accelerate review of proposed edits. Action Item #7: Entire team to consider if there is another place in the report for proposed change #4. 4. Next steps to get to Final Report (15 minutes) a. Preparations for F2F meeting (16-18 January) * Everyone should have made their arrangements by now - in case of questions, please contact gnso-secs(a)icann.org. * CBI has been contracted to facilitate and mediate the meeting. Leadership team and staff support will be meeting with CBI shortly to prepare for and plan the meeting. Further details to follow shortly. b. Decision-making methodologies / Consensus call process * As the EPDP Team moves towards a Final Report on the Temporary Specification, a formal consensus call will need to be conducted on the different recommendations. The EPDP Team should familiarize itself with the decision-making methodology as outlined in the EPDP Team Charter. The leadership team will develop further details as to how the consensus calls are expected to be conducted. c. Final Report development * Unless there are any objections, the staff support team is happy to start working on transforming the Initial Report into a Final Report by making the necessary administrative updates, followed by any updates that are the result of the EPDP Team’s review of the comments received or prior agreements. Any such changes will be tracked in redline to facilitate review. d. Timeline * The EPDP Team is still working towards the existing deadline of delivery of a Final Report on the Temporary Specification by 1 February. Progress is very much dependent on the F2F meeting. 5. Wrap and confirm next meeting to be scheduled for Tuesday, 8 January 2019 at 14.00 UTC (5 minutes) a. Confirm action items b. Confirm questions for ICANN Org, if any Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__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

Meeting Invitation: Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 08 January 2019
by Andrea Glandon Jan. 3, 2019

Jan. 3, 2019

Dear all, Non-members can follow the EPDP call taking place on Tuesdays and Thursdays via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/-wj_BQ Thank you. Kind Regards, Andrea

1 0

Proposed Agenda - EPDP Team Meeting #37 Thursday 3 January at 14.00 UTC
by Marika Konings Jan. 3, 2019

Jan. 3, 2019

Dear EPDP Team, Best wishes for 2019! Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 3 January at 14.00 UTC. Best regards, Caitlin, Berry and Marika ========== EPDP Meeting #37 Agenda Thursday, 3 January 2018 1. Roll Call & SOI Updates (5 minutes) 2. Welcome and Updates from EPDP Team Chair (5 minutes) * Update from legal committee * Review of outstanding action items * Other updates, if applicable 1. Public Comments on the Initial Report (85 minutes) * High level overview of input received (10 minutes) (see https://community.icann.org/x/R4cWBg) * Review and discuss proposed approach for review of public comments (15 minutes) (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-January/001131.html) * Commence review of public comments (60 minutes): * Purpose 1 – Establish rights of Registered Name Holder (see PCRT<https://community.icann.org/download/attachments/102139731/gnso-EPDP-pcrt-I…>) * Purpose 3 – Enable communication with Registered Name Holder (see PCRT<https://community.icann.org/download/attachments/102139731/gnso-EPDP-pcrt-I…>) 1. Next steps to get to Final Report (15 minutes) * Preparations for F2F meeting (16-18 January) * Decision-making methodologies / Consensus call process * Final Report development * Timeline 1. Wrap and confirm next meeting to be scheduled for Tuesday, 8 January 2019 at 14.00 UTC (5 minutes) * Confirm action items * Confirm questions for ICANN Org, if any Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

6 6

Re: [Gnso-epdp-team] [Ext] Re: Proposed Agenda - EPDP Team Meeting #37 Thursday 3 January at 14.00 UTC
by Marika Konings Jan. 3, 2019

Jan. 3, 2019

Alan, all, Please find attached the mind map that provides an overview of the issues that are expected to be addressed in ‘phase 2’ of the EPDP Team’s work, per the EPDP Team’s charter. The Final Report referred to in the agenda refers to the Final Report referenced in the EPDP Team’s charter that is to be produced following the review of the public comments received on the Initial Report ‘on the items related to the Temporary Specification (excluding the Annex)’. The Charter foresees a second Final Report (and Initial Report) that specifically focuses on the issues that are outlined in the mind map. I hope this clarifies that each phase has its own Initial Report and Final Report which focuses on the specific issues per the direction of the EPDP Team Charter. To avoid further confusion, the group could consider referring to the Final Report for phase 1 (Temporary Specification) and Initial & Final Report for phase 2 (System for Standardized Access and Annex issues)? Best regards, Caitlin, Berry and Marika From: Alan Greenberg <alan.greenberg(a)mcgill.ca> Date: Wednesday, January 2, 2019 at 23:49 To: Marika Konings <marika.konings(a)icann.org>, GNSO EPDP <gnso-epdp-team(a)icann.org> Subject: [Ext] Re: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #37 Thursday 3 January at 14.00 UTC I have a question regarding the nomenclature "Next steps to get to Final Report". We have all along been talking about issues that are within our mandate but do not need to be done and implemented by the magic date in May 2019. How does this fit with the concept of a "FINAL Report"? - Will we address these other issues in the FINAL Final Report Or Final Report #2? - Has the "let's defer it till later" been a code phrase for we are never going to do it? These other issues are within our scope in the charter but do not seem to have been contemplated in identifying the deliverables. Alan At 02/01/2019 10:58 AM, Marika Konings wrote: Dear EPDP Team, Best wishes for 2019! Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 3 January at 14.00 UTC. Best regards, Caitlin, Berry and Marika ========== EPDP Meeting #37 Agenda Thursday, 3 January 2018 1. Roll Call & SOI Updates (5 minutes) 2. Welcome and Updates from EPDP Team Chair (5 minutes) * Update from legal committee * Review of outstanding action items * Other updates, if applicable 1. Public Comments on the Initial Report (85 minutes) * High level overview of input received (10 minutes) (see https://community.icann.org/x/R4cWBg) * Review and discuss proposed approach for review of public comments (15 minutes) (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-January/001131.html ) * Commence review of public comments (60 minutes): * Purpose 1 – EEstablish rights of Registered Name Holder (see PCRT<https://community.icann.org/download/attachments/102139731/gnso-EPDP-pcrt-I…>) * Purpose 3 – Enable communication with Registerred Name Holder (see PCRT<https://community.icann.org/download/attachments/102139731/gnso-EPDP-pcrt-I…>) 1. Next steps to get to Final Report (15 minutes) * Preparations for F2F meeting (16-18 January) * Decision-making methodologies / Consensus call process * Final Report development * Timeline 1. Wrap and confirm next meeting to be scheduled for Tuesday, 8 January 2019 at 14.00 UTC (5 minutes) * Confirm action items * Confirm questions for ICANN Org, if any Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporationn for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team

1 0

Public Comment review and Thursday meeting agenda
by Kurt Pritz Jan. 2, 2019

Jan. 2, 2019

Hi Everyone: Welcome back. During the break, you will see that the Support Team has worked through and summarized the comments to the Initial Report using the standard format. We have also identified an approach to the public comment review that is outlined in the attached document. It includes prep materials for this Thursday’s meeting - and identifies the path for the next few meetings after that. Please read and consider it carefully, provide any guidance you might have, and prepare for the Thursday meeting. Let us know if you have questions or comments. Best regards, Kurt & Rafik

4 5

**Reminder** Meeting Invitation: Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Thursday, 03 January 2019
by Julie Bisland Jan. 2, 2019

Jan. 2, 2019

Dear all, Non-members can follow the EPDP call taking place on Tuesdays and Thursdays via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/-Aj_BQ Thank you. Kind Regards, Andrea

1 0

ICANN Org response to EPDP Team Question - discussions with EDPB/DPAs
by Marika Konings Dec. 27, 2018

Dec. 27, 2018

Dear All, Please find hereby the ICANN Org response to the following question: Question: Is there any further information that can be provided in relation to the discussions that have been held with the EDPB and/or DPAs in addition to the blog posts and correspondence that have been shared, such as briefing notes and summaries of meetings? Response: Aside from the blog posts and correspondence that have already been shared, and consistent with ICANN Publication Practices<https://www.icann.org/resources/pages/publication-practices-2016-06-30-en>, ICANN org has not identified any additional notes or summaries of meetings that are suitable for publication. ICANN org has previously stated that having clear guidance may increase legal certainty for ICANN and the contracted parties as well as assist the community in the Expedited Policy Development Process (EPDP) to consider the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> (Temp Spec). Our commitment to transparency in publishing summaries of our interactions with the EDPB supports this stated purpose. In this regard, we’ve posted summaries of our conversations with the EDPB and DPAs on ICANN’s Data Protection/Privacy Issues<https://www.icann.org/dataprotectionprivacy> page. The purpose of these conversations has been to educate, inform, and request guidance. In these discussions, we have also relayed to the EDPB the concerns and questions that we have solicited from the community. Additionally, in the Work and Tools section of the EDPB website, the EDPB states that: “We issue general guidance to promote a common understanding of European data protection laws, both across the European Union and around the world. We clarify data protection provisions, advise the European Commission and provide the general public and stakeholders with our interpretation of their rights and obligations. We can issue guidelines, recommendations and best practices about the GDPR and the Law Enforcement Directive, as well as other documents.” Accordingly, guidance from the EDPB to ICANN is publicly posted on their website and ICANN’s website so that the guidance is available for all interested parties and can help inform the work of the community. ICANN org remains available to answer any questions that the EPDP Team may have regarding any specific topic. This response will also get posted here: https://community.icann.org/x/ahppBQ. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

4 3

Public comments on Initial Report available for review
by Marika Konings Dec. 24, 2018

Dec. 24, 2018

Dear EPDP Team, Now that the public comment form is closed, staff has collated all input received via the google form as well as separate statements received here: https://community.icann.org/x/R4cWBg. Overall, 45 submission have been received: 9 SO/AC, SG/C groups submissions and 35 Company or Individual submissions. Staff is working on populating the public comment review tool to facilitate the EPDP Team’s review of the input received, but please already familiarize yourself with the input provided by reviewing all contributions. Happy reading and happy holidays! Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__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