- Ccnso-council - lists.icann.org

21 May 2020
by ICANN Community Leadership Digest May 21, 2020

May 21, 2020

Thursday, 21 May 2020 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing NEW: Registrant Program Update: New Report on Registrant Issues and Challenges REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process ICANN68 Planning DUE MONDAY: ICANN68 Publication Support Public Comment ICANN Africa Regional Plan for Fiscal Years 2021-2025 Draft PTI FY21-24 Strategic Plan Proposal for Malayalam Script Root Zone Label Generation Rules – Second Public Comment Proceeding Name Collision Analysis Project (NCAP) Study 1: Proposed Final Report ccNSO PDP3: Initial Proposals for Process to Retire ccTLDs Information Sharing NEW: Registrant Program Update: New Report on Registrant Issues and Challenges From: Brian Gutterman, Registrant Program Manager, Global Domains Division (GDD) On 19 May 2020, the ICANN org Registrant Program published the third edition of its ongoing reporting series on Issues and Challenges Impacting Domain Name Registrants containing updated data (from the reporting period of September 2019 – February 2020) from the ICANN Global Support Center (GSC) and Contractual Compliance. The report also provides observations of registrant issues and challenges from GSC and Contractual Compliance based on their interactions with registrants. As always, we encourage everyone to take a look at the report and share any data you might have regarding issues impacting registrants to inform ongoing conversations and work. We'll continue to work with departments across the organization who engage with registrants to gather and analyze data on an ongoing basis in addition to publishing similar data online at icann.org/registrants as part of our broader effort to raise awareness about the issues and challenges registrants face. Learn More. REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process Announcement On 31 March 2020, ICANN opened a call for Expressions of Interest for panelists to serve on the omnibus Standing Panel for ICANN's Independent Review Process (IRP). Candidates for the IRP omnibus Standing Panel should review the Expressions of Interest document before submission. The document includes the following information: Panel Position Description Required or Highly Preferred Skills Required or Highly Preferred Experience Time Commitment Compensation and Selection Expressions of Interest should be submitted to irp-standingpanel-eoi2020(a)icann.org by 23:59 UTC on Friday, 31 July 2020. ICANN68 Planning DUE MONDAY: ICANN68 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support Translation-only Deadline If your publication requires translation, please provide the final material(s) by Monday, 25 May 2020. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. Public Comment ICANN Africa Regional Plan for Fiscal Years 2021-2025 Close Date: Wednesday, 27 May 2020 Draft PTI FY21-24 Strategic Plan Close Date: Monday, 1 June 2020 Proposal for Malayalam Script Root Zone Label Generation Rules – Second Public Comment Proceeding Close Date: Wednesday, 17 June 2020 Name Collision Analysis Project (NCAP) Study 1: Proposed Final Report Close Date: Wednesday, 17 June 2020 ccNSO PDP3: Initial Proposals for Process to Retire ccTLDs Close Date: Friday, 10 July 2020 Volume 2, Issue 41 | Archive | Next Issue: Monday, 25 May 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | About Constant Contact Sent by david.olive(a)icann.org in collaboration with Try email marketing for free today!

1 0

NOTES ccNSO Council Meeting: 21 May 2020 | Noon (12.00) UTC
by Joke Braeken May 21, 2020

May 21, 2020

Dear All, Please find included below some notes from today’s ccNSO Council meeting, held on Thu, 21 May 2020 at noon UTC. Best regards, Joke Braeken 1. Welcome and roll call To be quorate, we need 1 person per region. Hope all are safe and well. Calls are recorded and transcribed; recordings/transcripts posted on the public wiki: https://community.icann.org/x/V4HfBw. 2. Minutes, Action Items & To-Do’s Most of the action items have been completed 3. Intermeeting ccNSO Council decisions & Actions (since 16 April 2020) * Guideline board seat 11& 12 process: updated version sent to Council. 1 question from Jordan, was then sent to community for further comments * 1 additional member appointed to the ccPDP3-RM: Ann-Cathrin Marcussen (.no) 4. ccPDP 3 a. Part 1 Retirement – Update Public comment has been opened on 5 May 2020 and will close 10 July 2020. * Part 2 Review Mechanism – Update Last meeting was held yesterday. Upcoming: presentation by IANA, with ICANN legal 5. IDN ccTLD related work items a. ccPDP4 Issue Report We received input from ICANN legal on the issue report. Issue Report has been available for the oversight group since February. Was updated, based on their input. Was circulated to ICANN general council. Is it within icann’s mission? Within the scope of the ccNSO policy? Does the policy have lasting impact? All confirmed. IDN string selection would replace Fast Track Process. Also inclusion of IDN ccTLDs in the ccNSO: separate track (see 5.b. On today’s agenda). Council sent a letter with proposed changes to the bylaws to icann. Board has responded that ICANN org will look at it, and will issue a public comment on the recommendations. Hopefully the process will be launched by ICANN68. The council as a start of the roadmap, first tasked a review team, to look at areas that need to be updated in the proposed policy PDP2 (which was concluded in 2013). Fast track evolved, and other issues emerged in the meanwhile (e.g. confusing similarity). This PDP is an update of the proposals at the time, plus review confusing similarity and introduce variant management. One major addition, at request of the ccPDP3-ret: this PDP should also define the trigger event for the de-selection and removal/retirement of IDN ccTLDs. Additional requirements for requesting an IDN ccTLD string. The group is quorate. We can officially launch the work on this. Annex B, section 3 & 4. Development policy recommendations, then assemble a working group. Secretariat to send out a call for volunteers, after ICANN68. Other stakeholders need to be invited to participate in the work as well. We need to formally inform the GAC Chair, ask their advice/opinion. After publication, this decision is effective immediately. Move? Giovanni Second? Pablo Questions or comments? Bart: adding detail to 2 decisions. * Regarding the mid-july timeframe: before we launch the call for volunteers, we will organise a webinar on the scope and working methods. This paid off for the ccPDP3-RM. * The WG: usual method. However, we introduced the opportunity to create subgroups. Based on previous conversations, it is clear that other communities are interested in the similarly aspect. So we will have the opportunity to treat this topic separately, and focus the efforts of the WGs. All in favour. * Progress Bylaw Change We submitted the request to the Board, and received acknowledgement from the Board. Waiting for response from icann legal. 6. ccNSO Board Seat 12 Nomination process a. Adoption Updated Guideline: ccNSO Board Seat 11 & 12 Nomination Process We can move fwd with approval of the guideline. Major changes: * Clarification provided regarding secondments and nominations * Majority votes “none of the above” terminate the process. * Nomination manager become nomination process manager Decision into effect 7 days after publication Move? Pablo Second? Alejandra No comments or questions All in favour * Adoption Timeline Board Seat 12 Nomination Process & Appointment Nomination. Last year, when we went through the process, it turned out that the background checks lasted longer than expected. Additional layer of complexity to the selection process. Need to start the process earlier. First term of Nigel ends next year in October, AGM in 2021. He can be re-appointed, for 2 more terms. Stephen: 6 month deadline prior to AGM (28 April 2021), specified in the ICANN Bylaws. Needs to be respected. We will announce the nomination: start 9 June, close 30 June. Background checks follow, and Q&A at ICANN69 (Hamburg). Move? Alejandra Second? Giovanni Questions/comments? Joke Braeken appointed as Nomination Process Manager. Guideline was adopted today, timeline to be adopted as well. Against? None Abstain? None All in favour 7. NomCom Related Matters a. Review Implementation: Letter Chair of the Review WP Asked us some questions. We missed the original deadline. Google doc. Giovanni added some comments and suggestions. 2 parts: 1. Nomcom members 2. NomCom appointees. They want to have our appointees already in June (see 7.b.) See google doc: https://docs.google.com/document/d/1u4yapu0rW72gg4vCzxIGkxlWfTZF4Rg2QcboDfM…<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Composition of NomCom should be more balanced, but the decision is not ours. (e.g. GNSO appoints 7, ccNSO appoints 1). Marie-Noemie supports gender and geographic diversity. Suggest to be more critical. Constructive suggestion. Lengthy discussion with the Vice Chairs on this topic. If we appoint 1 person, diversity is impossible. It also depends on the number of volunteers. This year our representative to the NomCom is Annebeth Lange (.eu). Should we then appoint next time a male person? From a different region? We only have 1 delegate, as ccNSO. Response will be sent to Chair RP Move? Giovanni Second? Pablo Comments/questions? None Against? None Abstain? None All in favour * Selection ccNSO appointee NomCom FY 21 Annebeth is not term-limited. Proposal to issue a call for volunteers, start 26 May and close 9 June. Council to select the preferred candidate between 10 and 17 June. Selection procedure and timeline adopted Against? None Abstain? None All in favour 8. Closure of follow-up discussion CSC Effectiveness Review on potential gap between remit of CSC and RZERC. Review was efficient. One of the ccTLDs asked us to request clarifications from ICANN. GAP analysis. Not clear what kind of gap analysis was meant. Clarification requested. We reached out to the ccTLD repr that raised the issue. After numerous requests and reminders, so that we could go back to ICANN org, we still have not received that clarification. Suggested not to take any further steps. Consider the item closed. Against? None Abstain? None All in favour Philippe: is the GNSO council cc-ed on the response letter to org? I'm just thinking maybe we should inform the GNSO council given that the CSC effectiveness review was a "joint effort". Just as a "matter of courtesy"...  Bart: original correspondence needs to be checked. Will get back to Philippe on this. 9. Approval updated Terms of Reference Internet Governance Liaison Committee (IGLC) Updated Tor. Selection Chair: groups nominates the chair, council appoints. Move? Alejandra seconded Any questions? None Abstain? None All in favour 10. Update ECA & CSC a. ECA Phase 2 rejection action processes. Draft FY21-25 Operating and Financial Plan. Board approved the documents on 7 may. Notice 7 days later from ICANN Secretary. Could be something that we propose to change in the bylaws. Public comments period in December, and then the COVID-19 pandemic changed everything. Was responsible to review the projections and numbers. Budget was changed, reduced in light of the pandemic. 2 webinars where the changes were represented. Those 2 webinars were referred to as “consultations with the community”. Question about the process? Was this an appropriate community consultation? No question about the fact that the adjustments had to be made. What is the Council’s view? Should we react somehow? Or consider this as something inevitable? Giovanni (SOPC Chair): sopc members also commented on the procedure by icann to approve the revised docs. Also other comments by SOPC members, about the fact that this is a responsible decision. Blog entry by ICANN CEO and Board chair: they define the 2 webinars as having high levels of participation and engagement. ICANN could have reached out more and consulted more with the community. Nonetheless, this is a responsible decision. Estimated funding reduced by 5 %. Estimated decline by 8%. 410 staff members, getting stable at 395. (revised projection at end of FY21). Formal call with Xavier Calvez, ICANN CFO, to point out that there are these concerns among some members of the ccTLD community. He understood that communication was not optimal. However, pressure to complete this in a short timeframe. No-one questions the decision itself, but rather the process. Stephen: Council to draft correspondence to Board that this should not set precedence. Giovanni: agrees. Katrina: consider expedited procedure, for instance with shorter comments period. Draft letter will be shared with the full Council. Suggested to do so next week. Rejection Action Period closes 4 June. We could submit it afterwards, as a statement, not as a rejection action. b. CSC i. Update from CSC PTI performance was 100%. SLA update, on the transfer and delegation of ccTLD is on the agenda of GNSO Council, consent agenda for today. Likely to be adopted. New SLA will be implemented, as soon as CSC informs PTI. ii. Appointment ccNSO Appointed Member on CSC, consultation with RySG and approval of full membership CSC was informed that the procedure will be launched on 1 June. Council can take a decision to launch a process in anticipation of the upcoming CSC members selection, and in anticipation of the role of the selection committee, which needs to be confirmed again. Brett Carr has completed his 1st term. His term ends 1 october. He is vice chair, willing to stand again, he is not term-limited. In the proposed timeline: correct typo. 2019 should read 2020. Move? Stephen Second? Pablo Approve timeline with corrections, request secr to launch the call. We need the CSC Selection Committee, that will approve the full slate on behalf of the council, Council will still approve the volunteers. All in favour 11. Council updates (Chair, Vice-Chairs, Councillors, Regional Organisations, Secretariat) 12. WG/Committee Updates a. GRC Working on the same doc as last time: recall appointed board members. That doc covers also in case there is a request to recall a nomcom appointee, or the entire Board. According to the bylaws, request can be submitted by any individual. Not sure when we will be ready to share it with the Council, Work ongoing. b. SOPC Had a call, planning to meet at ICANN68. At the same time, charter review will start. All committed to feedback that ICANN Finance provided to comment on the financial and operating plan. Questions on what is next c. TLD-Ops none d. Tech WG Stephen: Tech WG is working on a Virtual Tech Day. DNSSEC oriented, some deferred presentations from Cancun e. IGLC Revised ToR. will meet at ICANN68, and contribute to ccNSO Members Meeting ICANN68 f. MPC Update by Alejandra 1. June activities: · Virtual ccTLD News session on 2 June 2020 | 11 UTC & 19 UTC · Council workshop: 3 June · GAC webinars: 3 and 4 June · 9 and 11 June: ccTLD Community webinars for newcomers, and introducing the plans for ICANN68 2. Draft ICANN68 ccNSO Schedule. 3. Details on ccTLD News session and the 3 ICANN68 sessions as part of ccNSO Members Meeting. Katrina: changes to usual ccNSO members meeting. Get members more engaged, even outside of the ICANN meeting. That is why the ccTLD News session is held virtually, ahead of the icann68 schedule. g. CCWG Auction Proceeds leadership team now considers the Final Report complete. The next step in the process is for the Co-Chairs to make a designation of the level of consensus for the recommendations in the report (see charter<https://community.icann.org/display/CWGONGAP/CCWG+Charter> for detail, and to send the report to the Chartering organisations for adoption. 13. Update liaisons a. Update ALAC Liaison (written update) * Update GNSO Liaison (written update) 14. Upcoming Meetings a. Update, if any, ICANN68 i. Schedule ICANN68 meetings ii. Joint Meeting with GNSO Council Is the joint meeting with GNSO Council happening? Pending confirmation b. Council virtual workshop Some volunteers stepped forward. c. Meeting with the GAC Webinar on update Policy development efforts & “DNS Abuse” and ccTLDs prior to ICANN68. d. Schedule upcoming webinars e. Next Council Meeting schedule · ICANN68 (Virtual): Wednesday 24 June 2020, Block 5 (7 UTC, 15:00 Kuala Lumpur) · August 20 – 12:00 UTC · September 17 – 18:00 UTC · October @ICANN69 · November 19 – 12:00 UTC · December 17 – 18:00 UTC 15. AOB None 16. Closure Thank you, and Bye all. 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

MPC Update
by Alejandra Reynoso May 21, 2020

May 21, 2020

Dear All Please find in attachment the documents shared today in our call. Best regards, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11-42 Zona 15, V.H. III. Guatemala, Guatemala www.gt

1 0

notes: ccNSO Council | 21 may 2020 (12 UTC)
by Joke Braeken May 21, 2020

May 21, 2020

hello All, To follow the live-note taking during today’s ccNSO Council meeting (21 May, 12 UTC), go to https://docs.google.com/document/d/1WmvObEM5eNZDE8MAdptPCYV2Kfj342Ka1SjSDDs… 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

NEXT: ccNSO Council teleconference | 21 May at 12:00 UTC
by Kimberly Carlson May 21, 2020

May 21, 2020

***STARTING IN 30 MINUTES*** THIS CALL IS PASSWORD PROTECTED – PLEASE DO NOT FORWARD THE INFORMATION FOUND IN THIS EMAIL. OBSERVERS WILL BE ASKED TO CONTACT ME FOR CALL DETAILS. Dear Councilors, The next ccNSO Council teleconference has been scheduled for 21 May at 12:00 UTC. PLEASE NOTE: The Secretariat requests Councilors add (Councilor) to the end of their name when joining. This is necessary to identify the Council for quorum, chat, etc. This also should be considered best practice when attending ICANN-wide meetings/webinars/teleconferences. Example: Stephen Deerhake (Councilor) or for an ICANN-wide meeting: Stephen Deerhake (ccNSO Council) Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/92360122413?pwd=bFpBeFIzM2VMR0FkeFRVb2h4K1JTQT09 Meeting ID: 923 6012 2413 Password: 163841 One tap mobile +12532158782,,92360122413#,,1#,163841# US (Tacoma) +13462487799,,92360122413#,,1#,163841# US (Houston) Wiki page: https://community.icann.org/x/V4HfBw (recording, transcript and background material will be posted as it becomes available) Find your local number: https://icann.zoom.us/u/aAAP6aGAx An agenda will be circulated prior to the call. Best, Kim

1 0

Join the Virtual ccTLD News Session | Tue, 2 June 2020 (11:00 & 19:00 UTC)
by Joke Braeken May 20, 2020

May 20, 2020

Dear All, The ccNSO Meetings Programme Committee (MPC) invites you to join the first ever Virtual ccTLD News Session. There will be 2 options to participate: * ccTLD Virtual News Session #1: Tuesday, 2 June 2020 | 11:00 UTC * ccTLD News Virtual Session #2: Tuesday, 2 June 2020 | 19:00 UTC Kindly note that the 11:00 UTC session and the 19:00 UTC each have a separate agenda. Agenda ccTLD Virtual News Session #1 Tuesday, 2 June | 11:00 UTC * Lessons from initiatives to support registrants in areas affected by bushfires/forest fires in Australia in early 2020 | Bruce Tonkin (.au) * .am/.հա activity during the last COVID-19 months | Anna Karakhanyan (.am/.հա) * Right protection mechanisms within .rs and .срб domains | Dejan Djukic (.rs/.срб) * Update by .uk | Eleanor Bradley (.uk) ccTLD News Virtual Session #2 Tuesday, 2 June 2020 | 19:00 UTC * How to help authorities sorting out covid19-related registrations | Henriette Vignal-Schjoeth (.dk) * Preliminary study for .py IDN domain deployment with cyrllic characters | Gabriel Valdez (.py) * Anycast cloud for LACTLD | Miguel Ignacio Estrada (LACTLD) * The impact of COVID-19 on APTLD members: Survey findings and report on a webinar regarding lessons learned | Leonid Todorov (APTLD) Consult the agenda here<https://community.icann.org/display/ccnsowkspc/ccNSO+Members+Meeting+%7C+IC…>. How to participate To participate, please RSVP here <https://forms.gle/itKVmAB8viXn9L7t9> to receive a calendar invite and dial-in details. Go to https://forms.gle/itKVmAB8viXn9L7t9 A recording will be made available here<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars>. 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

1 0

REMINDER: ccNSO Council Teleconference | 21 May @12:00 UTC
by Kimberly Carlson May 19, 2020

May 19, 2020

Dear Councilors, As a friendly reminder, next ccNSO Council teleconference has been scheduled for 21 May at 12:00 UTC. PLEASE NOTE: The Secretariat requests Councilors add (Councilor) to their end of their name when joining. This is necessary to identify the Council for quorum, chat, etc. This also should be considered best practice when attending ICANN-wide meetings/webinars/teleconferences. Example: Stephen Deerhake (Councilor) or for an ICANN-wide meeting: Stephen Deerhake (ccNSO Council) Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/92360122413?pwd=bFpBeFIzM2VMR0FkeFRVb2h4K1JTQT09 Meeting ID: 923 6012 2413 Password: 163841 Wiki space: https://community.icann.org/x/V4HfBw (Background material, recording/transcript and attendance will be posted as it becomes available) If you are unable to attend the call, please let Bart and I know as soon as possible. Best, Kim

1 0

Updated agenda and draft resolutions 21May 2020
by Bart Boswinkel May 19, 2020

May 19, 2020

Dear all, Please find included the updated agenda (includes the selection of the ccNSO respresentative on the NomCom) and the document Selection Process ccNSO member NomCom FY 2021. Kind regards, Bart Agenda and draft Resolutions ccNSO Council Meeting 163 21 May 2020 Noon (12.00) UTC Welcome and roll call Minutes, Action Items & To-Do’s Minutes of the 16 April 2020 meeting have been distributed on 13 May 2020. Action items and To-do’s Action Item 157-01 Call to review charters, pending Action Item 161-01 Chair, with assistance from Secretariat, built Council Chair “knowledge base”. Ongoing 162-01: Secretariat to send consent/assign Patricio Poblete to ccPDP-RM mailing list, webpage, etc. – Completed 162-02: Secretariat to circulate Activity Overview and Work Plan documents to mailing list – Completed. 162-03 Further discussion from Council (small group) on developing a way forward in “shaping ccNSO strategy” and possibly present to the community 162-04: Plan/coordinate a virtual ccNSO Council Workshop – prior to ICANN68 Suggest timing To-do: Stephen Deerhake to provide a summary (CCWG Auction Proceeds) Done Intermeeting ccNSO Council decisions & Actions (since 16 April 2020) Comments updated Guideline: ccNSO Board Seat 11 & 12 Nomination Process ccPDP 3 Part 1 Retirement – Update Informational: Public comment has been opened on 5 May 2020 and will close 10 July 2020. Feedback if any on webinar to solicit public comment. Part 2 Review Mechanism –Update Informational IDN ccTLD related work items ccPDP4 Issue Report For decision: adoption of the Issue Report ccPDP4 Draft Resolution to Initiate ccPDP4 Background In September 2013 the ccNSO submitted the IDN country code policy development process (ccPDP2) Board Report to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: · Proposals (at a high level) for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. · Proposals to enable the inclusion of IDN ccTLDs in the ccNSO. By mutual understanding, the ccNSO Council and the ICANN Board allowed the Fast Track Process to evolve, to test and gain experience with the policy aspects pertaining to the introduction of IDN ccTLDs under the Fast Track Process. The aim was to further inform the overall policy, specifically with results of the different reviews of the Fast Track process[1]. The latest step in the evolution of the Fast Track Process was the introduction of the community developed Guideline with regard to the Risk Mitigation Panel and related process. In March 2019 the ccNSO Council tasked a team (Preliminary Review Team or PRT) to review ccPDP2 in light of the impact of the following related processes on the recommended policies: · The evolved Fast Track Process, · The request of the ICANN Board of Directors with respect to IDN Variants and · Other relevant developments such as retirement of the (IDN) ccTLDs · The short term need to allow IDN ccTLD Managers to become members of the ccNSO. The PRT was requested to advise the Council on whether or not to launch an additional Policy Development Process to address open issues, if any, or take other steps. Based on its high-level analysis, the PRT identified various issues with the recommended policy for the selection of IDN ccTLD strings and advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address the various issues it had identified, including the de-selection of IDN ccTLD strings. With respect to the recommendations in ccPDP2 pertaining to the inclusion of IDN ccTLDs, the PRT did not identify any issues and therefore advised the ccNSO Council to request a change of Article 10 of the ICANN Bylaws and Annex B. At its meeting on 22 August 2019, the ccNSO Council adopted the recommendations of the PRT. To implement these recommendations, the ccNSO Council requested the ICANN Board of Directors to agree to take no additional steps with respect to ccPDP2 and to stop the evolution of the Fast Track Process[2]. In October 2019, the ICANN Board confirmed and agreed with this approach[3]. In addition on 7 February 2020 the ccNSO Council requested the ICANN Board of Directors to change the ICANN Bylaws to enable IDN ccTLD to become members of the ccNSO[4]. The Board of Directors responded to first look at the proposals and then open a public comment period on the proposed changes.[5] At its December 2019 meeting, and in accordance with Annex B section 1 of the ICANN Bylaws, the ccNSO Council appointed the Issue Manager and requested an Issue Report, which should address the following topics: 1. Whether or not the ccNSO should initiate the ccNSO Policy Development Process on the (de)selection of IDN ccTLD strings (ccPDP4) and other areas listed in the Final Report of the Preliminary Review Team and, with respect to the de-selection be guided by and build-upon the process for the retirement of ccTLDs. 2. Whether or not to convene a taskforce or use other method to address these issues. On 14 May 2020 , the Issue Manager, submitted the ISSUE REPORT to Council, including the opinion of ICANN’s General Counsel, recommending that based on a review of the issues raised in the PRT Final Report, considering that the Threshold Criteria are met, and taking into account General Counsel’s opinion, the Issue Manager recommends that the ccNSO Council initiates ccNSO Policy Development Process 4 to develop policy for the (de-)selection of IDN ccTLD strings. In addition, the Issue Manager proposes to conduct ccPDP 4 by way of a chartered working group according to the proposed timeline (PDP Time Line). Decisions 1. In accordance with Annex B section 3 and 4 of the ICANN Bylaws, the ccNSO Council decides to: A. Initiate the development of policy recommendations on the (de-)selection of IDN ccTLD strings (ccPDP4) to address the issues identified in the Issue Report dated 14 May 2020, taking into account that: a. the Threshold criteria to initiate a ccNSO Policy Development Process have been met as documented in the Issue Report; b. ICANN’s General Counsel’s opinion that the development of policy for the selection and delegation of IDN ccTLDs is within the scope of the ccNSO and the ICANN policy process; c. the recommendation of the Issue Manager to initiate a ccNSO Policy Development Process to develop and recommend a policy on the (de-)selection of IDN ccTLD strings. B. To appoint one Working Group in accordance with the recommendations of the Issue Manager and adopt the charter, working method and schedule for such a Working Group. 3. The Secretariat is requested to send out a call for volunteers by mid-July 2020 (post ICANN68) for the WG, and invite other stakeholders listed in the charter, to participate in the WG in the manner most suited to them. 4. As required under Annex B, the Chair of the ccNSO is requested to formally inform the Chair of the GAC and ask the GAC to advise or provide an opinion. 5. The Secretariat is requested to publish this resolution as soon as possible. Upon publication of this resolution it becomes effective. Progress Bylaw Change Informational. No further progress to date, awaiting the response from ICANN Legal. ccNSO Board Seat 12 Nomination process a. Adoption Updated Guideline: ccNSO Board Seat 11 & 12 Nomination Process For decision Draft Resolution Background Following adoption of the Nomination Report at its meeting on 21 February 2020, the cNSO Council requested the ccNSO Guidelines Review Committee to review the Guideline: ccNSO Nomination Process Board Seat 11 and 12, taking into account the recommendations and observations from the Nomination Manager (see https://community.icann.org/display/ccNSOCWS/14+February+2020?preview=/1264…) In addition, other concerns have been addressed. The major changes are: · A ccNSO member can only nominate one candidate; additional nominations are invalid, but will be published. A member may second as many candidates as wanted, with no impact. · If majority of votes cast is “None of the Above”, nomination process will be terminated and start again with a new timeline and the appointment of the Nomination Process Manager. · Terminology change: Nomination Manager has been changed to Nomination Process Manager Decision The ccNSO Council adopts the amended version 3.5 Guideline: ccNSO Nominations Process ICANN Board Seats 11 and 12. The Secretariat is requested to publish this decision and the amended Guideline as soon as possible on the ccNSO website. This decision becomes effective seven (7) days after publication. b. Adoption Timeline Board Seat 12 Nomination Process & Appointment Nomination Process Manager. For decision Resolution Background In accordance with the Guideline, the ccNSO Council needs to appoint the Nomination Process Manager, to manage the Board Seat 12 Nomination Process. The first term of Nigel Roberts (Board Seat 12) ends at the end of the ICANN FY 22 AGM in October 2021. The ccNSO Council is required to select a candidate in accordance with the relevant ICANN Bylaws and internal rules of the ccNSO applicable at the time of the call for nominations. Under the current Guideline the timing and duration of the background check need to be considered and taken into account before the Q&A session and before the selection by the ccNSO Members. Also, to be considered is the Bylaws provision when ECA needs to be informed about the candidate (28 April 2021) and the Bylaws provision that internal rules and procedures of the ccNSO are required to be consistent with the ICANN Bylaws (section 10.3 (k)). The ccNSO Council was informed (see: item 6b 21 May 2020 Timeline Nomination Board 12) that in order to meet all the relevant deadlines, the call for nominations would need to be sent out by 9 June and close on 30 June 2020. Decisions 1. The ccNSO Council appoints Joke Braeken (ccNSO Secretariat) as the Nomination Process Manager, in accordance with the relevant Guideline. 2. The ccNSO Council adopts the timeline and sequence of call for nominations, background check, Q&A session with the candidate(s), and selection by the members of the ccNSO according to the Guideline amended at the 21 May 2020 meeting and as proposed. The Secretariat is requested to publish this resolution on the ccNSO website as soon as possible. This resolution becomes effective seven (7) days after publication. NomCom Related Matters a. Review Implementation: Letter Chair of the Review WP For discussion and approval See: proposed response at: https://docs.google.com/document/d/1u4yapu0rW72gg4vCzxIGkxlWfTZF4Rg2QcboDfM… [docs.google.com] Draft Resolution The ccNSO Council supports the response to the Nominating Committee review implementation questionnaire as proposed and request the Chair of the ccNSO Council to inform the Nominating Committee accordingly. b. Selection ccNSO appointee NomCom FY 21 For Decision Draft Resolution Background The ccNSO was requested to select a member for the FY 2021 Nominating Committee (NomCom), as the term of Annebeth Lange ends. Annebeth Lange is not term limited. The Secretariat has prepared a timeline for the call for volunteers: Launch call for volunteers 26 May 2020 and closing 9 June 2020 Start Council Selection procedure 10 June 2020 and ending 17 June 2020. On 18 June 2020 the secretariat will circulate overview of level of support per candidate. Candidate receiving highest level of support is selected The procedure and call for volunteers is detailed in the Selection Process ccNSO Member NomCom FY 2021. Decision The ccNSO Council adopts the proposed timeline, selection procedure and call for volunteers as detailed in the Selection Process ccNSO Member NomCom FY 2021. The ccNSO Council requests the Secretariat to launch call for volunteers accordingly. Closure of follow-up discussion CSC Effectiveness Review on potential gap between remit of CSC and RZERC. For decision The CSC Effectiveness Review Team suggested that the ccNSO Council would follow up with ICANN org regarding a question by a representative from one of the ccNSO members. The ccNSO has contacted and ICANN Org asked for further clarifications. The chair of the Council contacted the representative and despite numerous follow-up queries for over a period of one year, no response from the ccTLD representative has been received. Proposal is to close the query as it has lost its relevancy and urgency. Draft Resolution Background The CSC Effectiveness Review Team suggested that the ccNSO Council would follow up with ICANN org regarding a question by a representative from one of the ccNSO members on clarifying the remit of RZERC and the CSC and potential gap between these remits. The ccNSO Council has forwarded the question to ICANN Org and ICANN Org asked for further clarifications. The chair of the Council contacted the representative and despite numerous follow-up queries for over a period of one year, no response from the ccTLD representative has been received. Decision The ccNSO Council will take no further steps to seek clarification, and closes the query. The Council requests its chair to inform ICANN Org and the concerning representative from the ccNSO member. Approval updated Terms of Reference Internet Governance Liaison Committee (IGLC) For Decision Draft Resolution Background The Internet Governance Liaison Committee reviewed its Terms of Reference, and suggest some changes. Specifically it has introduced a mechanism for the IGLC to select the chair of the committe, aligning it with the regular mechanism that the chair is appointed by the Council after being nominated by the group. Decision The ccNSO Council adopts the amended version of the Terms of Reference of the Internet Governance Liaisons Committee as proposed, and request the secretariat to publish the updated Terms of Reference and inform the Committee accordingly. Update ECA & CSC ECA Informational CSC i. Update from CSC ii. Appointment ccNSO Appointed Member on CSC, consultation with RySG and approval of full membership For decision: adoption of Timeline and Mandate Selection Committee Draft Resolution Background The ccNSO Council will be invited to select a member for the Customer Standing Committee, to replace Brett Carr, whose term ends on 1 October 2020. In accordance with the internal ccNSO Guideline: ccNSO Actions respecting the Customer Standing Committee (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2016-12/… ) the ccNSO Council will need to adopt a timeline for selection and to appoint the selection committee from among its members, that will consult with the RySG and GNSO and approve the full slate of CSC membership. The proposed timeline is: ActionStarting date Closing date Comment, if any Council decision to launch call 21 May 2020 Council decision to appoint Committee 21 May 2020 Advised to appoint committee mandated to consult and approve Call for Nomination2 June 202016 June 2020 Selection Process by Council22 June 202003 July 2019 Consultation RySG06 July 201917 July 2019Depends on progress other selection committees Council Decision to select member20 July 202024 July 2020ccNSO Council meeting Approval full slate2 August 2020 25 September 2019 Discussion and Approval Selection Report by Council September/October Council Meeting Decision The ccNSO Council adopts the timeline as proposed for the selection of a ccNSO appointed member on the CSC, and request the Secretariat to launch the call for volunteers at the time foreseen in the schedule and in accordance with the mechanism in the Guideline: ccNSO Actions respecting the Customer Standing Committee. The ccNSO Council also confirms the appointment of the CSC selection committee: Katrina Sataki, Margarita Valdes, Pablo Rodriguez, Ai-Chin Lu, Souleymane Oumtanage and Marie-Noemie Marques. The mandate of this Council committee will be to consult with the RySG and GNSO Council and approve the full slate of membership. The Secretariat is further requested to inform the community as soon as possible on the upcoming CSC member nomination and selection process. Council updates (Chair, Vice-Chairs, Councillors, Regional Organisations, Secretariat) WG/Committee Updates GRC SOPC TLD-Ops Tech WG IGLC MPC CCWG Auction Proceeds Update liaisons Update ALAC Liaison (written update) Update GNSO Liaison (written update) Upcoming Meetings Update, if any, ICANN68 i. Schedule ICANN68 meetings ii. Joint Meeting with GNSO Council Council virtual workshop Meeting with the GAC Webinar on update Policy development efforts & “DNS Abuse” and ccTLDs prior to ICANN68 Schedule upcoming webinars Next Council Meeting schedule ICANN68 (Virtual): Wednesday 24 June 2020, Block 5 (23.00 UTC) August 20 – 12:00 UTC September 17 – 18:00 UTC October @ICANN69 November 19 – 12:00 UTC December 17 – 18:00 UTC AOB Closure [1] See: https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-2…, general introduction page 4. [2] https://ccnso.icann.org/sites/default/files/field-attached/sataki-to-chalab…. [3] https://www.icann.org/en/system/files/correspondence/chalaby-to-sataki-31oc… [4] https://ccnso.icann.org/en/about/sataki-to-botterman-07feb20-en.pdf [5] https://www.icann.org/en/system/files/correspondence/botterman-to-sataki-14…

1 0

Save The Date for ICANN68 Prep Sessions
by Kimberly Carlson May 18, 2020

May 18, 2020

https://www.icann.org/news/announcement-2020-05-18-en LOS ANGELES – 18 May 2020 – Today, the Internet Corporation for Assigned Names and Numbers (ICANN) announced that ICANN68 Prep Sessions will take place between 8-18 June 2020. ICANN68 Prep Sessions will prepare the community ahead of ICANN68 Virtual Policy Forum in June. More details including the full Prep Sessions schedule and a registration link will be available soon. Please check ICANN68 Prep Sessions page<https://meetings.icann.org/en/remote68-prep-week> for the current schedule. ICANN Prep Sessions are established to help streamline the pre-meeting experience, increase awareness of current topics of importance, and enhance briefings and readout sessions conducted around an ICANN Public Meeting. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

1 0

18 May 2020
by ICANN Community Leadership Digest May 18, 2020

May 18, 2020

Monday, 18 May 2020 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. Table of Contents Information Sharing NEW: A Preview of the Improved ICANN.org: An Information Transparency Initiative (ITI) Update REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process ICANN68 Planning REMINDER: ICANN68 Publication Support Public Comment ICANN Africa Regional Plan for Fiscal Years 2021-2025 Draft PTI FY21-24 Strategic Plan Proposal for Malayalam Script Root Zone Label Generation Rules – Second Public Comment Proceeding Name Collision Analysis Project (NCAP) Study 1: Proposed Final Report ccNSO PDP3: Initial Proposals for Process to Retire ccTLDs Information Sharing NEW: A Preview of the Improved ICANN.org: An Information Transparency Initiative (ITI) Update From: Göran Marby, President and CEO When I joined ICANN org, many of you told me that it was difficult to find information on our websites. I heard this not only from our community stakeholders, but from ICANN beginners who wanted to participate in our unique multistakeholder model. I knew then that fixing the findability of our public information was something we needed to do. I also knew that it wouldn't be easy, it would require significant resources and time, and we would need to build a scalable solution for our entire ecosystem of sites. During the COVID-19 pandemic, now more than ever, we realize the necessity of and reliance on being able to access and find information easily through digital platforms. Read more. REMINDER: Call for Expressions of Interest: Standing Panel for ICANN’s Independent Review Process Announcement On 31 March 2020, ICANN opened a call for Expressions of Interest for panelists to serve on the omnibus Standing Panel for ICANN's Independent Review Process (IRP). Candidates for the IRP omnibus Standing Panel should review the Expressions of Interest document before submission. The document includes the following information: Panel Position Description Required or Highly Preferred Skills Required or Highly Preferred Experience Time Commitment Compensation and Selection Expressions of Interest should be submitted to irp-standingpanel-eoi2020(a)icann.org by 23:59 UTC on Friday, 31 July 2020. ICANN68 Planning REMINDER: ICANN68 Publication Support Executive: David Olive, Senior Vice President, Policy Development Support Translation-only Deadline If your publication requires translation, please provide the final material(s) by Monday, 25 May 2020. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support staff to submit these requests to chantelle.doerksen(a)icann.org and liana.teo(a)icann.org. Public Comment ICANN Africa Regional Plan for Fiscal Years 2021-2025 Close Date: Wednesday, 27 May 2020 Draft PTI FY21-24 Strategic Plan Close Date: Monday, 1 June 2020 Proposal for Malayalam Script Root Zone Label Generation Rules – Second Public Comment Proceeding Close Date: Wednesday, 17 June 2020 Name Collision Analysis Project (NCAP) Study 1: Proposed Final Report Close Date: Wednesday, 17 June 2020 ccNSO PDP3: Initial Proposals for Process to Retire ccTLDs Close Date: Friday, 10 July 2020 Volume 2, Issue 40 | Archive | Next Issue: Thursday, 21 May 2020 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | About Constant Contact Sent by david.olive(a)icann.org in collaboration with Try email marketing for free today!

1 0