April 2018 - Ccnso-council - lists.icann.org

Draft Agenda + first batch background material Council meeting 26 April 2018, 18.00 UTC
by Bart Boswinkel April 19, 2018

April 19, 2018

Dear all, Please find included the draft agenda and first batch of background material for the upcoming Council meeting. With respect to Action Item 139-04 Bart Boswinkel to circulate Terms of Reference for Study Group on use of Emojis as top-level domains. Council to revisit call for volunteers in April. The ToR are posted at: https://ccnso.icann.org/sites/default/files/field-attached/emoji-sld-purpos…, and were adopted by Council at its February meeting ( for reference included in package as well) Agenda and resolutions ccNSO Council Meeting 26 April 2018, 18.00 UTC 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2) Minutes and Actions Minutes 14 March 2018 meeting. Circulated 3 April 2018. Action Item 139-01: The Secretariat is requested to seek reconfirmation of those persons who were appointed in January 2017 for the ccNSO Review Working Party (RWP) Completed Action Item 139-02: The ccNSO Council requests the Secretariat to send out a call for volunteers (GRC) as soon as possible to invite new members to the Guideline review committee Completed Action Item 139-03: With respect to the work plan, the Chair and Secretariat are requested to complete the draft prior to the next meeting for discussion and adoption, considering the results of the Council Workshop Completed, included in background material Action Item 139-04: Bart Boswinkel to circulate Terms of Reference for Study Group on use of Emojis as top-level domains. Council to revisit call for volunteers in April. Completed, included in background material Action Item 139-05: Guidelines Review Committee is asked to review the Rules of the ccNSO and make recommendations. Completed, on work schedule GRC Action Item 139-06: Start process of selecting new liaison to the GNSO Completed, process ongoing Action Item 139-07: Council to review/discuss topic of disaster recovery – ways forward Ongoing, included on agenda Action Item 139-08: Secretariat to summarize discussions from joint sessions (board, gnso, gac) and Council workshop Ongoing Action item 139-09 The chair, vice chair and Alejandra Reynoso to select a candidates (mentor and mentee) for ICANN’s mentor/mentee programme. Completed 3) Overview inter-meeting Council decision Appointment additional members SOPC Appointment additional member PDP Retirement WG Appointment additional members GRC Adoption timeline and selection method ccNSO liaison to GNSO 4) Adoption Work Plan 2018-2020 For decision This is follow-up from the ccNSO Council Workshop in San Juan. 5) Next steps discussion balancing workload and volunteer capacity For discussion. Background material: Overview of outcome brainstorm session San Juan meeting. 6) Structuring next steps of discussion of ccTLD related Disaster Recovery planning For discussion Council decided to follow up/further discuss topic of disaster recovery/mitigation, business continuity. 7) Study Group Emoji: Need for call for volunteers? For decision The Board requested the ccNSO to look into the use of Emoji as Second level domains as currently some ccTLDs allow registration (for example see: http://domainincite.com/22575-emojis-coming-to-another-cctld ). Related, is the need to ensure that the Fast Track Implementation Plan and the overall IDN ccTLD policy refer to the IDNA 2008 suite and its successor, to avoid misunderstanding about the use of Emoji. Following the Board request the Council initially adopted the terms of Reference for a Study Group. After the presentations and discussions on the topic at Tech Day and de ccNSO Meeting days in San Juan, Council deferred a decision on a call for volunteers to its next (this) meeting. Purpose of Emoji Study Group is to provide to ccTLD community, the ccNSO Council a comprehensive overview of the issues associated with the use of Emoji as second level domains, and the need for and current practice by ccTLD managers to allow Emojis as second level domains. If considered appropriate by the Study group, the Study group may advise on a course of further actions, if any. 8) Update SSR 2 Informational 9) Special Elections European Region For Decision. Nigel Roberts indicated he will step down from his position as a Councillor by the end of the Panama meeting. His regular term would end in March 2020. As a result, the members in the EU region need to elect a new member to the ccNSO Council for the remainder of his period (until March 2020). Follow-up discussion meeting January and February 2018 on timing of election process: 2 scenarios and there implications. Depending on the preferred timeframe, the Council may need to appoint the Election Manager and adopt timeline for Special Election European Region at this meeting. 10) PDP Retirement Informational. Update progress (Stephen Deerhake) 11) ECA, RZERC Update 11.1 ECA (Stephen Deerhake) 11.2 RZERC Update (placeholder) 12) ccNSO Organisational Review update Informational Background Material. Draft Scope document and tentative timeline 13) CSC related Topics 13.1 General CSC update (Byron) 13.2 CSC Charter review 13.2.a Update current state of affairs (Abdalla) Proposed changes 13.2. b Next Steps: Preparing for joint decision making. The CSC Review team expects to complete its work by the Panama meeting and submit its final report to the ccNSO and GNSO. As the Review Team proposes amendments to the charter of the CSC, the ccNSO and GNSO jointly need to adopt the changes each according to their own rules and procedures. 13.3 Upcoming CSC members Selection process For Informational purposes Timeline and expected role of the Council 13.4 Overlap CSC Effectiveness review and first IANA Function Review For information and decision. According to the ICANN Bylaws (section 17.3) and current charter of the CSC the CSC Effectiveness will need to be reviewed starting 1 October 2018 and the ccNSO and GNSO are tasked to determine the method of this review. At or around the same time the first IANA Function Review (IFR) will commence. This review is defined in the ICANN Bylaws (Article 18). The IFR should, among others, look at how the CSC has performed its oversight role. As the CSC Charter Review Team has noted “There is concern about the potential burden that these simultaneous reviews could place on the CSC, as well as the real possibility of significant overlap of the two reviews. The RT recommends that the ccNSO and GNSO Councils conduct an analysis of the requirements of the reviews with a view to creating synergies and avoiding overlap.” The GNSO Council has appointed a small team (Donna Austin and Phillipe Fouquart) to coordinate next steps with ccNSO. For discussion and decision: does the Council wish to appoint a small group to coordinate actions and prepare decision-making pertaining to the different topics around the CSC? If so, limit this group to Councillors? 14) ICANN 62 14.1 ccNSO Council meetings Monday, 25 June (Day 1) 12:15-13:30 – ccNSO Council Preparatory Meeting (lunch) Monday, 25June 2018 (Day 1) 17.00-18:30 – Joint ccNSO / GNSO (with cocktail) Topics: CSC charter update, initiating CSC Effectiveness review, progress cross-community groups (Auction Proceeds, Internet Governance) Tuesday, 26 June 2018 (Day 2) 13.30:15-16:15 – Joint ccNSO / GAC Topics meeting with GAC? Wednesday 27 June 2018 (Day 2) 17:00-18:30 or Thursday 28 June 2018 (Day 4) 9.00-10.30: ccNSO Council Face to Face Meeting. Depends on topic session. 14.2 ICANN62 ccNSO Meetings Agenda (Alejandra) 15) Council Updates 15.1 Chair Update 15.2 Vice-Chair Update 15.3 Councilors Update 15.4 Regional Organizations Update 15.5 Secretariat update 16 WG update 16.1 GRC update (Katrina) 16.2 CCWG Auction Proceeds (Peter Vergote) 16.3 CCWG Internet Governance (Young Eum) 16.5 ccNSO Meeting Strategy review 17) Liaison Updates 17.1 GNSO Update 17.2 ALAC update 18) Next meetings (2018) 24 May – 12:00 UTC 27 or 28 June – face to face, Panama City 23 August – 12:00 UTC (July and Aug combined) 20 September 18:00 UTC October – face to face, Barcelona (date tbd) 15 November – 11:00 UTC 13 December – 17:00 UTC 19) AOB 20) Closure Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org --

1 0

Triage recommendation 20-2018: The CSC Charter Review Team's Initial Report is now out for public comments
by Joke Braeken April 17, 2018

April 17, 2018

Dear ccNSO council members, Please find below the proposed triage recommendation [20 - 2018]. Kindly provide me with your input by the end of 19 April 2018, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 20-2018: The CSC Charter Review Team’s Initial Report is now out for public comments Summary of request: The Customer Standing Committee (CSC) was established on 1 October 2016 and has been operating in accordance with a Charter that was developed by the Cross Community Working Group IANA Transition (CWG). The ICANN Bylaws (section 17.3) and CSC Charter include a provision that the first review of the Charter of the CSC needs to be conducted one year after the first meeting of the CSC. The CSC Charter Review Team seeks comments and input on its findings and proposed amendment of the CSC Charter, as included in its Initial Report. Based on public hearing of the direct customers, community members, PTI Board, the CSC itself and the former PTI president, the RT proposed changes to the charter, including: * The ability for CSC and PTI to agree on minor changes to the Service Levels without the need to go through an extensive public comment process, and * An arrangement to deal with changing circumstances of appointed members. In addition the charter will reflect that CSC and PTI have agreed on a remedial action procedure (a formal escalation methodology) in case of poor performance of PTI. https://www.icann.org/public-comments/csc-charter-rt-initial-2018-04-11-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Date received: 12 April 2018 Last day for comments/input/response, if any: 1 June 2018 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> , cctldworld(a)icann.org<mailto:cctldworld@icann.org> and on the ccNSO social media channels. Expertise needed, if any: CSC, charter, review, PTI, Service Levels Date of submission to Triage Committee: 12 April 2018 Deadline Triage Committee input: 16 April 2018, 23:59 UTC Date of submission to Council: 17 April 2018 Deadline Council decision: 19 April 2018, 23:59 UTC Impact on ccNSO/ccTLDs: medium Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

call for volunteers: ccNSO appointed Liaison to the Generic Names Supporting Organisation (GNSO)
by Joke Braeken April 17, 2018

April 17, 2018

Dear All, Per ccNSO council decision, the ccNSO launches a call for volunteers to fill the vacancy of the ccNSO appointed Liaison to the Generic Names Supporting Organisation (GNSO). Read this announcement here: https://ccnso.icann.org/en/announcements/announcement-16apr18-en The ccNSO is looking for a member of the ccTLD community to be appointed as ccNSO liaison to the GNSO. Opening date of this call for volunteers is Tuesday, 17 April 2018 (00:01 UTC), whereas the call for volunteers will close on Wednesday 2 May 2018 (23:59 UTC). If you are interested in applying for this position, kindly send an e-mail to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>. Further instructions are included under the heading "How to apply?". Roles and responsibilities of the ccNSO Liaison to the GNSO As specified in the ccNSO Guideline Liaison and Observers (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/…) the ccNSO appointed liaison to the GNSO shall report to the ccNSO Council not less than monthly on the activities of the respective organization. The ccNSO appointed Liaison to the GNSO shall represent ccNSO values in these efforts, shall pursue specific direction from the ccNSO Council as and when given, and shall seek ccNSO Council advice as and when needed. Furthermore, the ccNSO Liaison to the GNSO is committed to: * Participate diligently and actively in the meetings and activities of the GNSO on an ongoing and long-term basis * Communicate and advocate the positions of the ccNSO to the GNSO; * Report to the ccNSO on current and upcoming activities of the GNSO that may be of relevance to the ccNSO and broader ccTLD community. * If feasible and considered relevant ask to the ccNSO for advance guidance, if any, on matters that are going to be discussed by the GNSO. * Participate in GNSO-ccNSO Council meetings agenda committee to prepare the f-2-f meetings, if any. The ccNSO liaison to the GNSO shall not be a member of or entitled to vote on the ccNSO council or the Councils of other organizations, but otherwise shall be entitled to participate in the respective Council meetings. How to Apply? Interested individuals are invited to provide the following: * A resume, curriculum vitae, or biography * A letter of motivation detailing your interest in serving as ccNSO Liaison to the GNSO and what you will bring to this position. * Letter from your employer supporting you with respect to the required time commitments, confirming that you will attend GNSO meetings regularly and inform the ccNSO Council and broader ccTLD community. * If not directly linked to or employed by a ccTLD Manager, demonstrate active backing by a ccTLD manager * Statement of interest that identifies potential conflict of interest in your service as Liaison If you are interested in applying for this position, kindly send an e-mail to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>. Closing date of this call for volunteers is Wednesday, 2 May 2018, 23:59 UTC. Next Steps Timeline * Call for volunteers: Tue, 17 April 2018 until Wed, 2 May 2018 * Evaluation of the candidates and selection by the council: Thu, 3 May 2018 until Thu, 10 May 2018 * Appointment selected candidate: as of the date the results are published by the election manager, as of 11 May 2018 Once we have received your intent to apply for this position, the ccNSO Secretariat will send you a link to an online Public Data Consent Form. (consult the template here: https://ccnso.icann.org/about/personal-data-publication-consent-16feb18-en.…<https://ccnso.icann.org/about/personal-data-publication-consent-16feb18-en.…>) Via this form, you consent to ICANN processing data in order to appoint you as a Liaison and to subscribe you to the relevant mailing list(s). The form explains the information ICANN will process to administer your participation as ccNSO appointed Liaison to the GNSO and how the information will be used this purpose. It also describes the rights you have regarding your information. In the event only one person has volunteered, this person shall be appointed by the ccNSO Council at the first meeting following the call for volunteers. In the event two or more persons have volunteered for the same position, the ccNSO Council will conduct an email vote for the appointment. The Secretariat will then act as Selection manager. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date the results are published by the election manager. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/…<https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Proposed Agenda item
by Stephen Deerhake April 13, 2018

April 13, 2018

Greetings all, Given that Nigel indicated a while back that he intends to step down from Council at the end of ICANN 62 (Panama), I think it would be useful to discuss the procedure and timing of the election of his successor on our next call. I think it would be very useful if, for example, we could have a candidates’ forum as part of the ccNSO Members meeting at ICANN 62. Best Regards, /Stephen

3 2

ICANN Receives Data Protection/Privacy Guidance from Article 29 Working Party
by Joke Braeken April 13, 2018

April 13, 2018

Dear All, ICANN announced that it has received a letter from the Article 29 Working Party (WP29)<https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-11apr…> [PDF, 400 KB] that provides guidance on the European Union's General Data Protection Regulation (GDPR) and its impact on the collection, retention and publication of domain name registration data and the WHOISsystem. ICANN organization’s response to the letter from the Article 29 Working Party will be published shortly here<https://www.icann.org/resources/pages/correspondence>. Read the announcement here: https://www.icann.org/news/announcement-2018-04-12-en “We appreciate the guidance provided by the Article 29 Working Party on this important issue and have accepted an invitation to meet with the WP29 Technology Subgroup in Brussels on 23 April for further discussions,” said Göran Marby, ICANN president and CEO. “However, we are disappointed that the letter does not mention our request for a moratorium on enforcement of the law until we implement a model. Without a moratorium on enforcement, WHOIS will become fragmented and we must take steps to mitigate this issue. As such, we are studying all available remedies, including legal action in Europe to clarify our ability to continue to properly coordinate this important global information resource. We will provide more information in the coming days.” A moratorium on enforcement action by DPAs would potentially allow for the introduction of an agreed-upon accreditation model and for the registries and registrars to implement the accreditation model in conjunction with the measures in the agreed final interim compliance model. It will also allow for reconciliation between the advice ICANN has received from its Governmental Advisory Committee(GAC) and the Article 29 Working Party. Unless there is a moratorium, we may no longer be able to give instructions to the contracted parties through our agreements to maintain WHOIS. Without resolution of these issues, the WHOIS system will become fragmented until the interim compliance model and the accreditation model are implemented. A fragmented WHOIS would no longer employ a common framework for generic top-level domain (gTLD) registration directory services. Registries and registrars would likely implement varying levels of access to data depending on their interpretations of the law. “In parallel, we will carefully consider this advice, along with all of the input we have received from the multistakeholder community, before making changes to the current iteration of the proposed interim model<https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-0…>,” Marby continued. “As a part of this, we will explore all options as we continue dialogues with DPAs and the interested parties that comprise the multistakeholder community.” It’s important to balance the right to privacy with the need for information. While ICANN recognizes the importance of the GDPR and its goal of protecting personal data, parts of the ICANN community have noted the negative impact of a fragmented WHOIS. For example, it will hinder the ability of law enforcement to get important information and the anti-spam community to help ensure the Internet protects end-users. It will also: · Protect the identity of criminals who may register hundreds of domain names specifically for use in cyberattacks; · Hamper the ability of consumer protection agencies who track the traffic patterns of illicit businesses; · Stymie trademark holders from protecting intellectual property; and · Make it significantly harder to identify fake news and impact the ability to take action against bad actors. These are just a few examples from a long list of potentially adverse scenarios. Marby also requested that the DPAs include ICANN in any proceedings relating to WHOIS, and asks that it be included in all discussions and actions of the privacy regulators with the other WHOIS data controllers. He also said that ICANN org is continuing its efforts to prepare for implementation of a new model. Additional information on ICANN’s data protection/privacy activities, including legal analyses, proposed compliance models, and community feedback is published here<https://www.icann.org/dataprotectionprivacy>. ICANN encourages the community to provide feedback and continue our dialogues on future activities. You may share your views via email at gdpr(a)icann.org<mailto:gdpr@icann.org>. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Possible impact of the delay in ICANN Organization's Report on the Draft FY19 Budget Operating Plan
by Stephen Deerhake April 12, 2018

April 12, 2018

Greetings, As you know, at ICANN 61 on several occasions I discussed the timing of ICANN Org activities associated with the eventual approval of the FY19 Budget Operating Plan by the Board, and the timing of the Board’s approval on the Budget on the ability of the Empowered Community to hold a Rejection Action Petition Public Forum during ICANN 62 in Panama. At that time I calculated that so long as the Rejection Action Board Notice is delivered to the Empowered Community between 8 May 2018 and 31-May 2018 the Empowered Community, should the need to do so arise, would be able to hold a Rejection Action Community Forum during ICANN 62. This continues to be the case despite the push-back from 12 April 2018 to 24 April 2018 of the Staff report on the public comments received regarding the FY19 Budget and Operating Plan. What DOES change is the amount of time the Board will have to digest the Staff’s report on the public comments before adoption of the Budget if indeed it is their intent to trigger the Rejection Action Board notice within the window which would permit a Rejection Action Petition Public Forum during ICANN 62. FYI ICANN Staff has reached out to the Empowered Community Administration to begin planning for a potential Rejection Action Petition Public Forum during ICANN 62. As I have noted previously, the odds of a successful Rejection Action Petition regarding the FY19 Budget and Operating Plan, thus triggering a Rejection Action Petition Public Forum, remain extremely low. Planning never hurts however… Best Regards, /Stephen

1 0

Re: [ccnso-council] [ccnso-members] Proposed Revisions to Bylaws Section 11 – Additional Voting Thresholds
by Stephen Deerhake April 12, 2018

April 12, 2018

Dear all, Further to this notification from Joke regarding the Board’s resolution altering Bylaw 11.3.i as per the request of the GNSO, please note that this is a change to a standard Bylaw, which makes the Board’s action subject to a Rejection Action Petition from the Empowered Community as per Annex D Section 2.1(j). The odds of a Rejection Action Petition being filed by a member of the Empowered Community in this matter, let alone any such Rejection Action Petition receiving the support of an additional Decisional Participant, are, in my view, significantly less than the odds associated with winning a national lottery. Best Regards, /Stephen From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, April 12, 2018 at 04:47 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Subject: [ccnso-members] Proposed Revisions to Bylaws Section 11 – Additional Voting Thresholds Dear all, During its meeting on 30 January 2018, the Generic Names Supporting Organization (GNSO) Council resolved unanimously (https://community.icann.org/display/gnsocouncilmeetings/Motions+30+January+…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>) to recommend that the ICANN Board of Directors adopt the proposed changes to section 11.3.i of the ICANN Bylaws to reflect additional GNSO voting thresholds which are different from the current threshold of a simple majority vote of each House (see https://www.icann.org/en/system/files/files/proposed-revisions-bylaws-artic…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 39 KB]). These additional voting thresholds are intended to address all the new or additional rights and responsibilities in relation to participation of the GNSO as a Decisional Participant in the Empowered Community and to fully implement these new or additional rights and responsibilities as they appear in the revised GNSO Operating Procedures published on 30 January 2018 (see https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf[gnso.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> [PDF, 1.68 MB]). In its resolution on 15 March 2018, the Board directs the President and CEO, or his designee(s), to post for public comment for a period of at least 40 days the Standard Bylaw Amendment reflecting proposed additions to section 11.3.i of the ICANN Bylaws to establish additional GNSO voting thresholds. (See: https://www.icann.org/resources/board-material/resolutions-2018-03-15-en[ic…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>) Read more: https://www.icann.org/public-comments/bylaws-section11-voting-2018-03-26-en…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Deadline public comment: 5 May 2018 Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Appointment new member SOPC
by Joke Braeken April 12, 2018

April 12, 2018

Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Friday 13 April 2018, 23:59 UTC, in case you do not agree with the proposed resolution. Appointment new member SOPC For decision: formal appointment new member to the ccNSO Strategic and Operational Planning Standing Committee (SOPC) Sean Copeland (.vi) has applied for membership of the ccNSO SOPC. Draft Resolution The ccNSO Council approves membership of Sean Copeland (.vi) to the ccNSO Strategic and Operational Planning Standing Committee (SOPC). The secretariat is requested to inform the Committee chair and to take all other necessary steps to include Sean as a member of the SOPC. Thank you. Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

6 5

ICANN Organization's Report on the Draft FY19 Budget Operating Plan Now Due 24 April
by Joke Braeken April 12, 2018

April 12, 2018

Dear all, ICANN announced that the ICANN organization's response to the public comments received in the Draft FY19 Operating Plan and Budget[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> has been moved from 12 April to 24 April. This will allow the ICANN org and the Board to have the appropriate time to provide thoughtful and detailed responses. The ICANN org has received valuable and substantive comments from the public comment proceeding and wishes to thank everyone for your contributions in this important planning process. Read this announcement here: https://www.icann.org/news/announcement-2018-04-11-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

Calls-to-Action for Community Participation in ICANN Reviews
by Joke Braeken April 12, 2018

April 12, 2018

Dear all, ICANN has several calls-to-action for community participation in ICANN Reviews below. Reviews are important accountability mechanisms that need community input to help ICANN deliver on its commitments. Organizational Reviews[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> are led by independent examiners to assess the extent to which ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) fulfill their purpose and whether any change in structure or operations is needed. * Provide your Public Comment on the NomCom2 Review Draft Final Report Click here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> to share your public comment, learn about the current status of the review, and next steps. Please share your feedback by 7 May 2018 23:59 UTC [local time[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.timeanddate.com_wo…>] * Visit the Review Status Update Table[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> for the latest status on all active Organizational Reviews and links to background information. Specific Reviews[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> are led by teams of community volunteers to assess the performance of the ICANN organization and make recommendations for improvement. * Join the Second Face-to-Face Meeting of the Registration Directory Services Review Team (RDS-WHOIS2) On 16,17,18 of April, observe the RDS-WHOIS2 Review Team from 07:00 - 15:30 UTC for their second face-to-face meeting where they will discuss the subgroups' findings and potential recommendations. Click here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> for more information. * Visit the Review Status Update Table[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> for the latest information on all Specific Reviews and links to background information. Read this announcement here: https://www.icann.org/news/announcement-2018-04-10-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0