November 2017 - council - lists.icann.org

Fwd: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review
by Heather Forrest 08 Dec '17

08 Dec '17

Dear colleagues, Following up on our discussion just now on SSR2 RT, please find here the skills matrix and scoping document developed by the Review Team. The formal scope approved by the SSR-RT can be found on https://community.icann.org/display/SSR/Terms+of+Reference. Scope is on pages 4-5. Staff - could you please help us to coordinate volunteers for a small team to review these documents? I'll follow up by separate post on logistics of meeting with our SSR2 members. Many thanks to all for an effective Council meeting! Best wishes, Heather ---------- Forwarded message ---------- From: Denise Michel <denisemichel(a)fb.com> Date: Sat, Nov 11, 2017 at 3:11 PM Subject: Re: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org> Dear SO & AC Chairs: Please find attached a description of the SSR2 Review Team’s perspective of the scope of this review, and a skill matrix developed and completed by a majority of the Team. As requested, the SSR2 is completing these requested items to “[resolve] the issues identified and discussed before and during ICANN60 related to scope and skills.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review and relevant, useful skills. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here <https://community.icann.org/display/SSR/Terms+of+Reference?preview=/6407612…>. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki <https://community.icann.org/display/SSR/SSR2+Review>. Please let us know if you require anything further. We’d appreciate confirmation of receipt of this email and of the 4 Nov. email (copy included below), as well as a response to our previous request for information regarding the Team’s “un-pausing” (see below). Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) *From: *<ssr2-review-bounces(a)icann.org> on behalf of Denise Michel < denisemichel(a)fb.com> *Date: *Saturday, November 4, 2017 at 12:16 AM *To: *SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> *Cc: *SSR2 <ssr2-review(a)icann.org> *Subject: *[Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review Dear SO/AC Chairs: As one of the co-chairs of the SSR2, I’ve been asked to share an informal update on the Review Team’s work, and a query. The SSR2 met Friday 3 Nov., addressed scope and skills as directed, and then adjourned, since our work is “paused.” Specifically, the Review Team developed a skills matrix and a document clarifying SSR2’s scope/terms of reference. These drafts have been shared with all Review Team members for edits (not all participated in the 3 Nov. meeting), and we plan to finalize and deliver them to you next week. (Note that SSR2 operates by consensus and input from all Team members may necessitate a slight extension of this schedule, or not). The SSR2 would appreciate receiving information from the chairs on how and when you will decide on “un-pausing” this review. As you can appreciate, the Review Team’s volunteers would like more certainty as to their schedules. SSR2 previously planned a January face-to-face drafting session for which time has been blocked on our calendars and travel arrangements have been made. Please advise if we should cancel these. Please let us know if you need anything else from the Review Team (cc’d). Best, Denise Denise Michel *denisemichel(a)fb.com <denisemichel(a)fb.com>* *From: *Patrik Fältström <paf(a)frobbit.se> *Date: *Thursday, November 2, 2017 at 7:29 PM *To: *Denise Michel <denisemichel(a)fb.com> *Cc: *SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Eric Osterweil <eosterweil(a)verisign.com> *Subject: *Re: Statement from SO/AC Chairs on the suspension of the Security and Stability Review Your interpretation is correct. The goal now is to unpause SSR2. Please not that I do not have posting rights to the SSR2 list, so the moderated message must be released or forwarded by someone with posting rights. Best, Patrik On 2 Nov 2017, at 21:06, Denise Michel <denisemichel(a)fb.com> wrote: Thanks for forwarding, Patrick. Could the SO/AC Chairs please clarify the SSR2’s status tonight as the SSR2 is meeting tomorrow morning. My quick read of this indicates that SSR2 is still “paused” except that the Team is to address “resolving the issues identified and discussed before and during ICANN60 related to scope and skills.” That takes the work plan and other items off the table. Thanks for clarifying. Best Denise Denise Michel Sent via phone _____________________________ From: Patrik Fältström <paf(a)frobbit.se> Sent: Thursday, November 2, 2017 7:42 PM Subject: Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Osterweil, Eric <eosterweil(a)verisign.com>, Denise Michel <denisemichel(a)fb.com> STATEMENT FROM SO/AC CHAIRS ON THE SUSPENSION OF THE SECURITY AND STABILITY REVIEW The Chairs of ICANN’s Supporting Organizations (SOs) and Advisory Committees (ACs) acknowledge the 28 October 2017 announcement from the Board of Directors, pausing the work of the Security, Stability and Resiliency Review Team (SSR2-RT), and the Board's having tasked the SOs and ACs in sessions this week with addressing concerns raised by the Board, Organizational Effectiveness Committee (OEC), and the Security and Stability Advisory Committee (SSAC). Collectively, we accept responsibility for getting SSR2-RT restarted as expeditiously as possible. During various sessions throughout ICANN60, our groups have met with the Board and/or members of SSR2-RT to hear their concerns. We intend to continue to consult with our respective communities, and each other, to assess and address issues relating to the scope, composition and participation, resource utilization, and overall work plan of the Review. Additionally, the Board’s unilateral decision to suspend the work of a key accountability mechanism has raised questions that go to the independence of SSR2-RT, and specific reviews going forward. As a follow-on effort, we intend to examine the selection and scoping process for review teams, and develop a clear and predictable process for raising and addressing concerns about review teams. We also intend to carefully consider the Board's action, with a view to preventing similar instances in the future. We look forward to working collaboratively with the Board, SSR2-RT and the broader community on this task. The SO/AC Chairs support the SSR2 RT meeting on Friday, 3 November 2017, and followup telephone conferences when needed. These are necessary so that the team can work on resolving the issues identified and discussed before and during ICANN60 related to scope and skills. Finally, we wish to acknowledge the efforts of our colleagues on the SSR2-RT to date, and thank them for their continued commitment towards security, stability and resiliency. Alan Greenberg (Chair ALAC) Patrik Fältström (Outgoing Chair SSAC) Rod Rasmussen (Incoming Chair SSAC) Katrina Sataki (Chair ccNSO) Thomas Schneider (Outgoing Chair GAC) Manal Ismail (Incoming Chair GAC) James Bladel (Outgoing Chair GNSO Council) Heather Forrest (Incoming Chair GNSO Council) Tripti Sinha(Co-Chair RSSAC) Brad Verd (Co-Chair RSSAC) _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

4 5

Reminder: Document and Motion deadline Monday 11 December 2017 at 23:59 UTC for the GNSO Council Meeting 21 December 2017 at 12:00 UTC
by Nathalie Peregrine 07 Dec '17

07 Dec '17

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 11 December 2017 at 23:59 UTC) of the GNSO Council Meeting on 21 December 2017 at 12:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/6RJyB Thank you very much. With 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 1

GNSO Council response to GAC communique
by Austin, Donna 30 Nov '17

30 Nov '17

Fellow Councilors Please find attached the GNSO Council's proposed response to the GAC communique from Abu Dhabi, along with a motion to approve the response at our upcoming meeting on 30 November 2017. Regards Donna Donna Austin

4 5

GNSO Council Abstention Notification Form [#266]
by ICANN 30 Nov '17

30 Nov '17

1 0

GNSO Council Abstention Notification Form [#265]
by ICANN 30 Nov '17

30 Nov '17

1 0

GNSO Council Abstention Notification Form [#264]
by ICANN 30 Nov '17

30 Nov '17

1 0

Updated Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC
by Nathalie Peregrine 30 Nov '17

30 Nov '17

Dear councilors, Please below find the updated final agenda for the GNSO Council Meeting on 30 November 2017 at 21:00 UTC. Final Agenda 30 November 2017 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/WQByB This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 21:00 UTC: http://tinyurl.com/ybcbm2ev 13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; 08:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-en.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/en/meetings/minutes-council-12oct17-en.pdf> of the meetings of the GNSO Council on 12 October 2017, were posted on 3rd November 2017 Minutes of Part 1<https://gnso.icann.org/en/meetings/minutes-council-1-01nov17-en.pdf> and minutes of Part 2 <https://gnso.icann.org/en/meetings/minutes-council-2-01nov17-en.pdf> of the GNSO Council on the 1 November 2017 were posted on 23 November 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the GNSO Council response to the GAC Communique for submission to the ICANN Board (15 minutes) The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Abu Dhabi Communique (https://gac.icann.org/advice/communiques/public/gac-60-abu-dhabi-communique…), a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. This draft was circulated to the Council mailing list on 20 November 2017 (https://gnso.icann.org/en/drafts/review-gac-communique-21nov17-en.pdf) and updated with edits on the 28 November 2017 (https://gnso.icann.org/en/drafts/review-gac-communique-28nov17-en.pdf). Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board. 4.1 – Presentation of motion <https://community.icann.org/x/VwByB> (Donna Austin) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Referral of the privacy and proxy services issue, related to IRTP-C, to the PPSAI IRT (15 minutes) At the request of the Registrars’ Stakeholder Group (RrSG), which raised a substantive concern regarding the application of Inter-Registrar Transfer Policy-C (IRTP-C) to privacy and proxy services, the GNSO Council wrote to the ICANN Board<https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf> to recommend that the matter be referred to the Privacy/Proxy Services Accreditation Implementation (PPSAI) Implementation Review Team (IRT) for consideration before the Policy effective date. The Board responded on 21 December 2016<https://gnso.icann.org/en/correspondence/crocker-to-bladel-21dec16-en.pdf> to note that it was reviewing the Council’s request and in the interim, directed ICANN Contractual Compliance to defer enforcement of the issue. On 3 February 2017, the Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2017-02-03-en#1.h> confirming its instructions regarding deferral of Contractual Compliance enforcement and declaring its intention of further discussing the concerns raised by the GNSO Council at a subsequent meeting. On 16 March 2017, the Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2017-03-16-en#1.e> directing the ICANN CEO to instruct ICANN staff to work with the RrSG and other interested parties to determine the appropriate path forward. ICANN Staff and the RrSG are in agreement that the discussion should be referred to the PPSAI IRT. Here, the Council will consider a motion to refer the issue of applying IRTP-C to privacy and proxy services to the PPSAI IRT for resolution. 5.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Darcy Southwell) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Confirmation of GNSO Representative to the Empowered Community Administration (15 minutes) The GNSO Council adopted the proposed process and criteria<https://gnso.icann.org/en/council/resolutions#201706> for selecting the GNSO representative to the Empowered Community Administration during its meeting on 28 June 2017. Utilizing that process, the GNSO Council confirmed on 9 November 2017 that Heather Forrest would serve in interim basis to represent the GNSO as the Decisional Participant on the Empowered Community Administration. Further utilizing that process, the GNSO Council leadership has met and agreed that Heather Forrest will perform the role of GNSO representative to the Empowered Community Administration. Here, the Council will vote to confirm this selection. 6.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Donna Austin) 6.2 – Council Discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL VOTE – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation (20 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure<https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts…> on 18 April 2017 to better accommodate issues where Whois requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper<https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedu…> for public comment<https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments<https://www.icann.org/en/system/files/files/report-comments-whois-privacy-l…> was published on 28 July 2017. On 1 August 2017, the Council received a letter<https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en…> from Akram Atallah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure For Handling WHOIS Conflicts with Privacy Law. The Council has since considered the possible modifications to the procedure identified in the letter from Akram Atallah. Here, the Council will vote to confirm that the modifications to the procedure are consistent with the intent of the policy recommendation. 7.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Keith Drazek) 7.2 – Council Discussion 7.3 – Council vote (voting threshold: simple majority) Item 8: COUNCIL DISCUSSION – Update on the GNSO Council Strategic Planning Session (15 minutes) In January of 2017, the GNSO Council submitted a FY18 additional budget request<https://community.icann.org/download/attachments/64066403/FY18%20-%2023%20-…> to support a 3 day face-to-face strategic planning session in January of 2018. At a high-level, the purpose of the meetings is to allow for focused and dedicated sessions to strategically develop a work plan for the upcoming year. This additional budget request was approved<https://www.icann.org/resources/board-material/resolutions-2017-04-19-en#1.b> by the ICANN Board on 19 April 2017. The GNSO Council Strategic Planning Session is scheduled to take place on January 29–31 2018 at the ICANN office in Los Angeles. Here the Council leadership will provide an update to the Council on preliminary planning steps undertaken to date, including review of a draft agenda. 8.1 – Presentation of discussion topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Update on the GNSO Council Standing Committee on ICANN budget (15 minutes) The GNSO Council has determined that it may need to provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. The interim GNSO Council Standing Committee on ICANN budget has considered two public comments 1) Draft PTI and IANA FY19 Operating Plans and Budgets<https://www.icann.org/public-comments/draft-pti-iana-fy19-2017-10-09-en> and 2) ICANN Reserve Fund – Public Comment on Rationale and Target Level<https://www.icann.org/public-comments/reserve-fund-2017-10-12-en> and prepared draft responses( https://gnso.icann.org/en/drafts/draft-comments-plan-budget-26nov17-en.pdf and https://gnso.icann.org/en/drafts/draft-comments-icann-reserve-fund-27nov17-…) to both for Council consideration. The Council may discuss the state of this standing committee’s charter as well. Here, the Council will discuss those draft responses and any possible next steps for the committee’s charter. 9.1 – Presentation of discussion topic (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.1 – Discussion of Council meeting dates and rotation for 2018 10. 2 – Update on the status of the Second Security, Stability, and Resiliency Review Team (SSR2-RT) 10.3 – Other? ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 19:00 London, United Kingdom (GMT) UTC 21:00 Paris, France (CEST) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Islamabad, Pakistan (PKT) UTC+5 (Friday) 02:00 Singapore (SGT) UTC+8 (Friday) 05:00 Tokyo, Japan (JST) UTC+9 (Friday) 06:00 Sydney/Hobart, Australia (AEDT) UTC+11 (Friday) 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and http://tinyurl.com/ybcbm2ev 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…>

2 1

GNSO Council Abstention Notification Form [#263]
by ICANN 29 Nov '17

29 Nov '17

1 0

WHOIS Conflicts with Local Law - Alternate Triggers
by Drazek, Keith 29 Nov '17

29 Nov '17

Hello fellow Councilors, As discussed in Abu Dhabi, I’m re-surfacing the previously drafted motion (thanks Marika) and some proposed language for consideration at our November Council meeting. We need to respond to Akram’s letter on this topic. It could either be via a motion or in a letter response. Substantively, here are two options: Alternate Trigger #1: Written Legal Opinion In the absence of a Whois Proceeding, a registry or registrar may present to ICANN a written legal opinion from a nationally recognized law firm or attorney in good standing that identifies any portion of the collection, retention, display or dissemination of any data element specified by the ICANN contract in question violates or is likely to violate applicable law, statute or regulation. Such written opinion shall identify the provision(s) of the ICANN contract in question that are identified to be in conflict and the manner in which the registry or registrar, by fulfilling the terms of the contract, is likely to violate applicable law, statute or regulation. Alternate Trigger #2: Previously granted waiver If (i) it was previously determined that a provision in the RA, RAA or other contractual obligation conflicted with applicable law, statute, or regulation such that ICANN granted an exception under the terms of this Procedure and (ii) the registry or registrar is subject to the same applicable law, statute, or regulation, then the registry or registrar may request the same exception. Such request shall be granted by ICANN unless ICANN provides reasonable justification for not granting the request, in which case the registry or registrar may utilize another trigger. Thanks and regards, Keith

5 12

Call for volunteers to draft response to public comment forum on Operating Standards for ICANN's Specific Reviews
by Marika Konings 29 Nov '17

29 Nov '17

Dear All, As discussed during the wrap up session at ICANN60, there is currently a public comment forum open on ‘Operating Standards for ICANN's Specific Reviews’ (see https://www.icann.org/public-comments/reviews-standards-2017-10-17-en). Noting the recent community discussions regarding the SSR2-RT, there may be an interest for the Council to review the proposed operating standards and provide input from the Council’s perspective? The purpose of the public comment forum is to solicit feedback on: 1. The underlying principles that are reflected in the draft Operating Standards<https://www.icann.org/en/system/files/files/draft-operating-standards-speci…> especially: for the community to agree on the review scope prior to the review team being selected; to assure selected review teams have the necessary skill set and diversity to conduct a successful review. 2. The specific proposals and content that are contained in the draft Operating Standards<https://www.icann.org/en/system/files/files/draft-operating-standards-speci…> including but not limited to the proposal on scope setting and review team selection. Susan volunteered during the wrap up session to work on this. Are there others that are interested to develop a proposed response for Council consideration? Note that the deadline for input is 15 January. Best regards, 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

3 2