January 2021 - Ccnso-council

Apologies and ECA Update
by Stephen Deerhake ＠ ASNIC Jan. 22, 2021

Jan. 22, 2021

Greetings, Please accept my apologies for not pitching up at yesterday’s Council call. It’s the first time that has happened in a very long time. My excuse is the installation of our new President and the spontaneous outdoors, socially distanced, village-wide celebration that involved a lot of fire pits, chimeneas, and bubbly. A lot of the latter I might add. 😉 7AM was not in the cards as a result. In any event, for the record, please accept my apologies for being a no-show. Also, for the official record, there was one bit of activity that the Empowered Community Administration undertook between the December and January Council meetings that I would like noted in the minutes of yesterday’s call if possible. On 19 December 2020, on behalf of the ECA, I wrote to the ICANN Secretary affirming the selection of Katrina to assume ICANN Board Seat 12 at the conclusion of ICANN’s Annual General meeting, scheduled for ICANN72 in Seattle from 23-28 October 2021. Congratulations Katrina! Best Regards, /Stephen

1 0

ccNSO Council 21 January 2021 decisions
by Kimberly Carlson Jan. 22, 2021

Jan. 22, 2021

Dear all, Please find the resolutions (resolved) from the ccNSO Council meeting on Thursday, 21 January 2021: https://ccnso.icann.org/en/announcements/announcement-21jan21-en.htm Previous Resolutions: https://ccnso.icann.org/en/about/council/decisions-resolutions/2021 Meeting agenda: https://ccnso.icann.org/sites/default/files/field-attached/agenda-draft-cou… Council meeting wiki: https://community.icann.org/x/tABACQ Thank you, Kim

1 0

DAAR Activity Project: Now Providing Personalized Monthly Reports for ccTLDs
by Kimberly Carlson Jan. 22, 2021

Jan. 22, 2021

For those interested. Announcement: https://www.icann.org/news/blog/daar-activity-project-now-providing-persona… In order to expand the effectiveness of Domain Abuse Activity Reporting (DAAR) for the community, in November 2019, country code top-level domains (ccTLDs) were invited to participate in the DAAR system designed by ICANN's Office of the Chief Technology Officer (OCTO). ccTLDs could volunteer to participate by sharing their zone files. These zone files would only be used in the DAAR system and would not be used or shared for any other purpose or in ICANN's Centralized Zone Data Service (CZDS). Every ccTLD that joined the project would be able to receive DAAR data on a daily basis via ICANN's Monitoring System API (MoSAPI<https://www.icann.org/mosapi>). In July 2020, I published a blog<https://www.icann.org/news/blog/country-code-top-level-domain-participation…> announcing that several ccTLDs were voluntarily participating in the DAAR system. To date, 12 ccTLDs have joined this effort. This not only benefits the DAAR system by allowing a broader spectrum of domains and therefore better indication of security threat concentrations, but we expect it to also provide significant benefits to the ccTLD community. We are now providing customized monthly reports to the participating ccTLDs. These reports contain analytics specifically based on the data submitted by each ccTLD, and are only shared with them. In each report ccTLD-related statistics are shown with all the other ccTLDs and generic TLDs (gTLDs) being anonymized. The intention of these personalized reports is to help ccTLDs understand where they stand in terms of the security threat data listed by Reputation Block Lists (RBLs) in comparison to other TLDs. These documents are a supplement to the DAAR reports published monthly and daily scores. About DAAR ICANN's DAAR system is used to study and report on domain name registration and security threat behavior across top-level domain (TLD) registries. The domain name data is obtained from zone files to which ICANN has access. The threat data is obtained from a curated list of Domain Name System (DNS) RBL providers. For each gTLD, DAAR provides raw counts and scores of security threats based on what is listed in the RBLs we use to identify phishing, malware, spam, and botnet command-and-control threats via ICANN's MoSAPI<https://www.icann.org/mosapi>. DAAR reports go as far back as 2018 and can be found here<https://www.icann.org/octo-ssr/daar>. The data being collected by the DAAR system is helping ICANN org and the community to facilitate discussions on security threat trends over time. Through the MoSAPI, individual registries can compare their DAAR data against the aggregate data for all registries in the DAAR system. Even in its anonymous form, the data has incentivized multiple large contracted parties to enhance their own anti-abuse measures and frameworks. Furthermore, independent researchers are adopting our methodology and producing measurements that help enhance the community's understanding of the DNS security threats landscape. What Comes Next It's important to note that these initial personalized reports shared with participating ccTLDs are still considered drafts. To continue to produce regular reports and improve features, we are asking the volunteer ccTLDs to review the reports and share their feedback with us<mailto:samaneh.tajali@icann.org>. We sincerely appreciate and thank the ccTLDs who have volunteered to join DAAR. We hope the personalized monthly reports are useful and that feedback from the ccTLDs will help improve DAAR for the community. Finally, in order to generate more accurate and reliable analyses and comparisons within the DAAR system, more ccTLD participation is desirable. We encourage all ccTLDs to learn about the benefits of participating in the DAAR system for themselves and the community. For discussions regarding DAAR project data-sharing and any other measurement of DNS security threats and abuse-related topics, please join the DNS-Abuse-Measurements<https://mm.icann.org/mailman/listinfo/dns-abuse-measurements> mailing list or visit the DAAR webpage: https://www.icann.org/octo-ssr/daar.

1 0

Draft ccNSO response to Board OEC
by Joke Braeken Jan. 21, 2021

Jan. 21, 2021

Dear Councilors. As per the discussion during the ccNSO Council meeting on 21 January at noon UTC, I am sending you a google doc with the draft response to the Board Organisational Effectiveness Committee (OEC), regarding the second ccNSO organizational review. Please find the google doc here: https://drive.google.com/file/d/1zn7sUq99JCIBB0PkyWizFg5FeXdoz5tD/view?usp=… Deadline for comments: Friday, 29 January 2021 (23:59 UTC) Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

we seek your feedback | ccNSO response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO.
by Joke Braeken Jan. 21, 2021

Jan. 21, 2021

Dear ccNSO Members, I am forwarding you an email on behalf of Ai-Chin Lu, ccNSO Councillor leading the drafting team for the ccNSO response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO. Kindly note that the drafting team seeks your input. Close date is Monday, 1 February 2021 (23:59 UTC). Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org = = = = Dear ccNSO Members, In order to include IDN ccTLDs as members to the ccNSO, the ccNSO Council requested changes to article 10 in the ICANN Bylaws. Since ICANN legal raised some questions, a drafting team was tasked with writing a ccNSO response. The drafting team now seeks your input and feedback on the proposed draft, allowing for further considerations, and eventually adoption of a response by the ccNSO Council. Please find enclosed the proposed letter to ICANN legal, including an Annex. The drafting team seeks your comments. Close date is Monday, 1 February 2021 (23:59 UTC). Your input will be reviewed by the drafting team, prior to adoption of the final response by the ccNSO Council. Thank you. Best regards, Ai-Chin Lu (.tw) | drafting team Chair Hirofumi Hotta (.jp), Jiankang Yao (.cn), Mira Fajri (.id) Background * ccNSO request to amend article 10 of the ICANN bylaws<https://ccnso.icann.org/sites/default/files/field-attached/sataki-to-botter…>. (7 february 2020) * Response from ICANN legal - October 2020<https://drive.google.com/file/d/1ZDpynivqNcPU4JYmKnMnfdv9uW-sjfyr/view?usp=…> * Guideline: ccNSO statements<https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-stat…> * ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en>

1 0

Thursday, 21 January 2021
by ICANN Community Leadership Digest Jan. 21, 2021

Jan. 21, 2021

Thursday, 21 January 2021 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: Stakeholder Assembly about ICANN's Perspectives on EU Digital Initiatives DUE TOMORROW: Revised Operational Design Phase Concept Paper NEXT WEEK: Request for Community Selection Panel Participants – 2021 Community Excellence Award Program NEXT WEEK: FY22 Additional Budget Requests Due Friday, 29 January 2021 REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members REMINDER: Volunteers Needed for Advisory Group on ICANN's North America Stakeholder Engagement Plan REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program REMINDER: Nomination Period for the ICANN Community Excellence Award Now Open Public Comment NEXT WEEK: Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget Information Sharing NEW: Stakeholder Assembly about ICANN's Perspectives on EU Digital Initiatives From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement An ICANN European regional stakeholder assembly will present ICANN org reflections on current European Union (EU) initiatives on Wednesday, 27 January, 15:00-16:00 UTC. This interactive webinar is open to all who register and will provide an overview of areas where EU legislative and regulatory initiatives make mention of, or potentially affect, the Domain Name System. We will present potential impacts on the ICANN mission and technical remit; and invite discussion on how various members of the broader ICANN community and ICANN policy development may be affected. Wednesday, 27 January, 2021,15:00 - 16:00 UTC Register Learn more. DUE TOMORROW: Revised Operational Design Phase Concept Paper From: Theresa Swinehart, Senior Vice President, Global Domains & Strategy ICANN org has shared a revised version of the Operational Design Phase Concept Paper. The new version follows community consultation during ICANN69, including written feedback by a number of community groups. The concept paper proposes an Operational Design Phase (ODP) that is to become part of the policy and implementation life cycle. The ICANN organization will conduct the ODP for consensus policy recommendations that are approved by the Generic Names Supporting Organization (GNSO) Council. The purpose of the ODP is to provide the Board with relevant information to decide, as required by the Bylaws, whether a recommendation is in the best interest of the ICANN community or ICANN. Please provide your input by Friday, 22 January 2021, to mary.wong(a)icann.org. NEXT WEEK: Request for Community Selection Panel Participants – 2021 ICANN Community Excellence Award Program From: David Olive, Senior Vice President, Policy Development Support On 1 December 2020, Supporting Organization and Advisory Committee chairs received an email request to provide up to two members from their respective group to help choose the recipient of the 2021 ICANN Community Excellence Award. The deadline to provide names to david.olive(a)icann.org is Monday, 25 January 2021. The 2021 ICANN Community Excellence Award will be presented during ICANN71 in June 2021. A community selection panel will be formed to review the nominations and select the award recipient. Ideally, panelists will serve a maximum of two consecutive terms on the selection panel to ensure diversity and equal opportunity among community members. The time commitment for the selection panel includes weekly one-hour calls between the end of March through June 2021. NEXT WEEK: FY22 Additional Budget Requests Due Friday, 29 January 2021 ICANN org has launched the FY22 Additional Budget Request process. This process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget. Submissions are due on Friday, 29 January 2021 at 23:59 UTC to planning(a)icann.org. Learn more. REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members From: Sally Costerton, Senior Vice President, Global Stakeholder Engagement ICANN has announced a call for nominees to volunteer to serve as mentors to the Fellowship Program and as members to its Selection Committee. There will be a total of seven mentors and seven Selection Committee members, and each group is welcome to nominate one individual for each role. Interested Supporting Organizations and Advisory Committees should select their respective Fellowship Program mentor and Selection Committee representative by Sunday, 31 January 2021 and notify fellowshipconsultation(a)icann.org. Individual self-nominations will not be considered. Criteria for mentors and Selection Committee members can be found here. REMINDER: Volunteers Needed for Advisory Group on ICANN's North America Stakeholder Engagement Plan From: Naela Sarras, Vice President, Global Stakeholder Engagement, North America Community members are invited to join a short-term regional advisory group, that will help advise the GSE North America team on the development of the next iteration of the North America Stakeholder Engagement Plan. This effort seeks community input to enhance the important work of stakeholder engagement across North America by actively soliciting input into ICANN policy and work processes. This advisory group will be time-limited (February - May 2021), will include two webinars, and be directed toward answering specific questions. With help from the community, the team hopes to surface implementable ideas with measurable impact to enhance engagement. Kindly send your reply with one or two named volunteers for this activity by Friday, 12 February 2021. Please send your reply to naela.sarras(a)icann.org and joe.catapano(a)icann.org. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested community members must apply in advance of ICANN70, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 5 March 2021 at 23:59 Coordinated Universal Time (UTC). The application process will open 8 February 2021 and program details are available here. The goal of this program is to facilitate participation in ICANN Public Meetings during this global pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Learn more. REMINDER: Nomination Period for the ICANN Community Excellence Award Now Open From: David Olive, Senior Vice President, Policy Development Support The nomination period for the ICANN Community Excellence Award 2020 is now open. The deadline for submissions is Monday, 29 March 2021, and the winner(s) will be announced during ICANN71. The ICANN Community Excellence Award recognizes ICANN community members who substantively contribute to policymaking within the ICANN ecosystem and who are deeply invested in developing consensus-based solutions within ICANN’s multistakeholder model. Learn more about the nomination process and submit your nominations here. Public Comment NEXT WEEK: Priority 2 Policy Recommendations for ICANN Board Consideration from EPDP Phase 2 Close Date: Friday, 22 January 2021 Draft FY22-26 Operating & Financial Plan and Draft FY22 Operating Plan & Budget Close Date: Monday, 15 February 2021 Volume 3, Issue 6 | Archive | Next Issue: Monday, 25 January 2021 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | About our service provider Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

NOTES | ccNSO Council Meeting 169 | 21 January 2021 | 12.00 (noon) UTC
by Joke Braeken Jan. 21, 2021

Jan. 21, 2021

Hello everyone, Please find included below some notes from today’s ccNSO Council meeting, held on 21 January at noon UTC. Best regards, Joke 1. Welcome and roll call Welcome by Katrina. Welcome to Sebastien, new GNSO appointed Liaison to the ccNSO Council 2. Minutes & Action Items a. Minutes Meeting 168, circulated 18 January 2021. b. Action items and To-do’s, if any 3. Intermeeting decisions (since 17 December 2020) * Mentor Fellowship Program (1) * Fellowship Program Selection Committee (1) Congratulations and good luck to those appointment 4. ccPDP 3 a. Part 1 Retirement – Update Finalising the Final Paper hopefully next week. Soon to be sent to the issue manager, who will publish it for public comment, together with the question whether to separate part 1 and part 2. No major changes, mainly editorial edits. Some further clarifications b. Part 2 Review Mechanism –Update The WG concluded its work on decisions that should be subject to a review mechanism. Do alternative mechanisms apply? They started focusing on getting ready to describe the process in detail, including the review procedure. First preliminary work on that started yesterday. ICANN legal will participate in the next meeting. Could the existing processes be used? 5. IDN ccPDP4: Update The WG is moving along steadily with a reasonable pace. The basic principles underlying the IDN have been reviewed and updated. Will be used for the policy, and the interpretation. They started to review the criteria. Some are in second reading. Next week they will start with a call for volunteers for a sub WG on Variant Management. Group will start prior to ICANN70. Both the full WG and the subgroup meet in alternating weeks. They will liaise closely with the GNSO effort. GNSO Council appointed its liaison to ccPDP4. Board request to coordinate activities. This person is already on the WG. Discussed with Chair and Vice Chair. A WG liaison to be linked to the GNSO policy effort. 6. Selecting members for the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel 1 strong candidate, who seeks endorsement from the ccNSO: David McAuley (.cc) Move? Pablo Second? Alejandra Against? None Abstain? None All in favour Thanks to David for standing! 7. Update Review and Implementation Dashboard Updated version of dashboard was circulated Recommendation on WG and Vice Chair nomination was included as well. Now in the implementation phase, see today’s agenda. There is not a focused effort on implementation, but it is gradually moving forward. We are ahead of the scheme, since some of the recommendations have already been implemented. 8. Draft response to Board OEC letter Some already reviewed the draft. Alejandra made some suggestions. We will have a google doc for comments by others. Please only comment in the google doc. Questions from OEC. Several sections in the response. Recommendations that have been fully implemented. List recommendations which are in process of implementation. Followed by a list of recommendations that should not be implemented (as proposed), others are directed at ICANN. Explanation why 1 specific recommendation should be deferred to the next review, if any. 2.b. Quote for newcomers. Absurd mathematically speaking. Number of WG members not limited. Giovanni asks about the next steps, once we send our response. Rephrase: addressed, eliminate “in our view”. Implementation completed, no further action needed. Leave room for the next steps OEC gives recommendation to the Board, to close ccNSOReview2. When ICANN org comes up with an implementation plan, it needs to be reviewed again. The ccNSO already started implementing, via the GRC. ICANN org also started with the bylaws changes. Discussion whether ccNSO accepts or does not accept recommendations, to be closed. Katrina: tomorrow discussion regarding ccNSO website. Hopes to be able to give an update shortly 9. Update Rules and Guidelines a. Update discussion Rules of ccNSO Name of the doc: Rules of the ccNSO. From 2004. GRC started identifying issues that should (not) be covered in a new version of the Rules of the ccNSO. See end meeting today, on how to engage councilors in this topic b. Introduction of Consolidated appointment and selection procedures. Councillors feed-back People to be appointed to different WG, committees, review teams etc. Separate guideline for some of those groups. GRC wanted to have a guideline for selecting members to those groups. Basic procedure. Process is the same for all appointments, except for those explicitly mentioned. Specifics for certain groups. Feedback needed from Council, before we send it to the members. Process manager to filter out those applications that do not meet the criteria. Automatically disqualify those candidates. Bart: question for Alejandra. Whether or not a required doc is included. Is that what staff should check? Staff should not check whether a doc meets a certain standard. Bart: should we also provide feedback to the applicant? Should we reach out to the applicant. Be active, to make it as complete as possible, or should we just be on the receiving end? Alejandra: submit docs before deadline. Good faith element. Warning. Katrina: conservative requirements, limit the number of documents. In light of recent appointment. One of the candidates did not submit anything. Informed decision was not possible for some c. Introduction WG/Committee Chair and Vice-chair nomination and appointment. Councillors feed-back We discussed this some meetings ago. We thought the process was clear, but it was not. Process needs to be clarified. Feedback needed from Council, before it is sent to the community. 10. Terms of Reference Outreach & Involvement Standing Committee (OISC) Draft Terms of Reference: Scope, Composition and Working Methods Google doc with draft OISC. Questions or comments? None 11. Update ccNSO Statement procedure regarding the Amendment of Article 10 ICANN Bylaws DT met yesterday. Revised the cover letter. Doc to be sent for comments to today In order to include IDN ccTLDs as members to the ccNSO, the ccNSO Council requested changes to article 10 in the ICANN Bylaws. Since ICANN legal raised some questions, a drafting team was tasked with writing a ccNSO response. The drafting team now seeks your input and feedback on the proposed draft, allowing for further considerations, and eventually adoption of a response by the ccNSO Council. Close date is Monday, 1 February 2021 (23:59 UTC). Once the drafting team is ready to send the final table/text to Council for adoption, the DT will inform Council about the need to address the following topics: · impact of the bylaw changes on the existing ccNSO Guidelines, and the need to review the guidelines · consequences for those organisations having multiple memberships in ccNSO, and the impact on their voting rights 12. Update ICANN70 (related) sessions a. ICANN response on comments ccNSO and others on proposed evolution of meeting strategy In December 2020, the ccNSO leadership team and MPC Chair hosted two consultation sessions via Zoom, aimed at collecting the ccTLD community’s feedback regarding ICANN org’s recommended strategic changes for future ICANN Public Meetings and its impact on the ccNSO schedule. The topic was also discussed by the ccNSO Meeting Programme Committee (MPC) during its 10 December meeting, and by the ccNSO Council during its 17 December meeting. The ccNSO Chair submitted consolidated feedback to ICANN org on 18 December. Highlights input by the SO/ACs: overall * Improvements to virtual elements of the meetings should be prioritized separately from changes to the overall meeting strategy. * More time and consultation needed for strategic changes for future face-to-face meetings * Opposition against moving sessions currently held during ICANN public meetings to be spread throughout the year * Unified online calendar for SO/AC work throughout the year is supported, but not seen as a tool to support the redistribution of public meeting sessions throughout the year Highlights input by the SO/ACs: ICANN70 * Immediate need for an ICANN70 block schedule * A reduced, four-day meeting is preferred * Schedule that allows sufficient time for community groups to meet and is not limited to plenary sessions. * Networking slots should be fewer, clearly defined, and offer both intra- and inter- community networking opportunities. * Plenary (2) and Public Forum to be non-conflicted * Plenary sessions and virtual networking slots scheduled at varying times of day to provide more opportunity for participation from different time zones. * Should all SO/AC/SG/C meetings with the Board be conducted during the official meeting? TBD Overall, the input by the ccNSO was taken onboard by ICANN org. ICANN org intends to continue consultation with community leaders about the evolution of future meetings. Regarding ICANN70: * Virtual public meeting * 4-day meeting: 22-25 March 2021 * will be held in the Cancún, Mexico, time zone (UTC +5). * Plenaries and networking activities will continue to be a priority, and will be scheduled at varying times to improve opportunities from different time zones. * ICANN org is testing: * better integration between Zoom and the interpretation platform, which will likely eliminate the need for a second device. * live real-time transcription in English within the Zoom platform. * plan to expand limited YouTube live streaming pilot from ICANN69, live-streaming more key ICANN70 sessions on YouTube<https://www.youtube.com/user/ICANNnews> for attendees with limited bandwidth. b. ccTLDs related sessions i. Tech Day ii. Members meeting sessions · Governance session · ccTLDs: looking at the future · Q&A ccTLD related Board members iii. ccTLD News sessions The ccNSO Meetings Programme Committee started planning for the upcoming virtual ICANN70 Community Forum. Here is a sneak preview of the ccNSO Members Meeting sessions you may expect (subject to changes): Pre-ICANN70 * 2 editions of the ccTLD community webinar, targeted at newcomers and those that would like to learn more about the work of the ccNSO. The sessions are scheduled for Wednesday, 17 March (19 UTC) and Thursday, 18 March (11 UTC) * 2 editions of the popular ccTLD News Session Mark your calendars for Tuesday, 9 March 2021 (19 UTC) and Thursday, 11 March 2021 (11 UTC). The MPC still seeks presenters: the call for presentation proposals closes 10 February 2021 (23:59 UTC). Read more here:https://ccnso.icann.org/en/announcements/announcement-12jan21-en.htm ICANN70 ccNSO Members Meeting * Governance session, as a follow-up from the ICANN69 session * ccTLDs and the future. ccTLD stakeholders expect resiliency, no matter what. ccTLD managers do the same things, but differently. Do ccTLDs need to adapt to the future? If so, how do we make our ccTLDs future-proof? Join us for testimonials from ccTLD Managers across the globe, followed by an interactive discussion. * And finally, join us at ICANN70 for the Question and Answer Session with ccTLD-related ICANN Board members The ccNSO Secretariat will post additional information on the ccNSO ICANN meetings Workspace shortly. https://community.icann.org/display/ccnsowkspc/ICANN+Meetings. The ccNSO seeks additional volunteers for the ccNSO Meetings Programme Committee (MPC). The MPC has been established to coordinate and manage the high-level schedule of the ccNSO-related sessions, including the ccNSO Members Meeting agenda at ICANN public meetings, and related matters. Members shall be appointed by the ccNSO Council after closure of the call for volunteers. Closing date: Tuesday, 26 January 2020 (23:59 UTC). On 20 January at 14 UTC, Chair Barbara Povse hosted a webinar for potential interested parties on 20 January at 14 UTC. Read more: https://ccnso.icann.org/en/announcements/announcement-18jan21-en.htm Some potential topics of higher interest to the broader ICANN community were suggested as potential plenary (i.e. unconflicted) or cross-community dialogue sessions: Potential topics for Plenary Sessions * Registry Voluntary Commitments: Practicality and Enforceability (proposal from At Large) * Applicant Support: What does success look like? (from At Large) * Regulatory updates – specifically, the recent actions in the EU (the proposed NIS2 directive, Digital Services Act, Digital Markets Act and the Data Governance Act) and the US (Congressional direction to the NTIA regarding WHOIS access) (from the Business Constituency) Potential topics for Cross Community Discussion * New gTLD Subsequent Procedures PDP (proposal from At Large) * A session involving NextGen primarily, but also former Fellowship and ATLAS participants who currently work in constituencies across ICANN, to discuss the future of the Internet from an ICANN policy perspective (from At Large) The current version of the draft block schedule by ICANN org foresees 2 slots for plenary sessions. Should you have suggestions for further topics of higher interest or input regarding the aforementioned topics, to be organized as a plenary sessions at ICANN70, your input is much appreciated. In case of new topics, kindly send me and joke.braeken(a)icann.org your suggestions, including: * a proposed session title, * a short description of the session, * the rationale, * desired outcome, * session format and * how other SO/ACs are involved. The deadline for this is Friday, 22 January 2021 (end of day). Nick: suggestions for plenary sessions. gTLD specific, not so relevant for the ccTLD Community. What is the Council's view to the extent we do not support any plenary sessions. Compromise: not have both focusing on gTLDs. Katrina: suggestions by other SO/ACs. Other SO/ACs might be interested in those GNSO-focused sessions. Nick: good point. We should be more proactive in suggesting topics we think are interesting to us. Not enthusiastic about any of the current proposals. Peter: Realising that this is an ICANN problem, not for ccNSO, but networking during breaks doesn't work online. Breaks are there to get away from the screen and headset. :) Re plenary: It's also a matter of timing: suggesting relevant topics three months in advance is not always probably. Bart: be aware it requires a lot of effort to organise plenary sessions. Especially in the current virtual environment. Margarita: proposals form At-Large? Anything needed? Alejandra: just a proposal from At-Large. SO/ACs still need to decide on the final selection Byron: NCSG proposal. How are they differentiating it? Potentially interesting for us, especially seen the regulatory changes globally. We are layer 3 and are required to do the work of the 7th layer. Is there an opportunity to participate or contribute, or to find out what is intended? Katrina: no further info at the time Byron: to keep an eye on. Is relevant to us Alejandra: proposal, once selected. Open for all to contribute Peter: TIG is a concept ICANN/Göran came up with in a belated attempt to get ICANN to back out of content discussions. I am afraid that ship has sailed.referring to ICANN having waded too deep in this debate to now retract from it. (Which is what I am hearing to be the reason for this TIG concept). I am all in favour of discussing the regulatory threat to the technical layer ops. Crucial times in Europe too. c. Joint meetings i. Meeting with the Board Do we have anything to discuss with the Board? After this meeting, we will send 2 questions, do we want to meet, what would be topics for discussion? Short response time. We need to move fast this time. Alejandra: also, let us know if there is anything to address with Goran. ii. Meeting with GAC iii. Meeting with GNSO Council d. Council workshop: Tuesday 16 March 2021, noon UTC (TBC) Summary by Jordan about the previous workshop. Thanks to Jordan, we accept his offer regarding future proposed work. Next workshop: Tue, 16 March noon UTC. Bart suggests to send out a doodle, so that as many people as possible can attend. Hopefully the new incoming councillors are also available to attend Suggested topics: i. Review role of chair and vice -chairs, Roles and responsibilities of Councillors ii. Work plan e. Council Preparatory meeting, Thursday 18 March 18.00 UTC (Tentative) 13. Update ECA & CSC a. ECA (Informational) Nothing happening. Waiting for budgets/plans b. CSC (Informational) IANA missed 1 SLA, due to the holiday season. Nothing to worry about 14. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 15. Update WGs a. SOPC The ccNSO SOPC has started its work to comment on the Five Year Plan and FY 22 Ops Plan and budget. As part of their work they will meet with the GNSO SCBO on 29 January 2021. b. IGLC Joke: This session will focus on the popular topic of digital sovereignty. Digital sovereignty touches everyone. The IGLC decided to further explore this topic, following a well attended and lively discussion during the ICANN69 IGLC meeting, and other sessions held as part of the ICANN69 Annual General Meeting, such as for instance a stakeholder roundtable organised by EURALO, where IGLC Chair Pierre Bonis was invited to speak. The IGLC started to define various categories of digital sovereignty, and is currently discussing examples belonging to the previously mentioned categories, in preparation of a potential session to be held as part of ICANN70. The target audience are ccTLD managers, but not only. The IGLC noticed from previous experiences that an interaction with other SO/ACs has proven to be valuable. Hence the request to organise this session as part of the ICANN70 public agenda. Ongoing call for volunteers. Chair Pierre Bonis will host a webinar for new potential members next week. 16. Update liaisons a. Update ALAC Liaison (written update to follow) b. Update GNSO Liaison (written update to follow) 17. Meetings Next Council Meetings: · February 18 – 20:00 UTC · March (ICANN70 TBD) · April 22 – 12:00 UTC · May 20 – 18.00 UTC · May 20 – 18:00 UTC 18. AOB 19. Discussion session on what needs to be included in future Rules of the ccNSO (if time permits) Katrina introduces JamBoard and explains how it works. Previously, the GRC was using this for some break-out sessions, as well as the ccPDP3-RM. Suggestion is to use JamBoard for the Council discussions too, in the future. Kim will circulate the link to the test environment (sandbox). 20. Closure Happy New Year! Thank you all. Bye. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

January Council teleconference | 21 January at 12:00 UTC
by Kimberly Carlson Jan. 21, 2021

Jan. 21, 2021

***STARTS IN 25 MINUTES*** Dear all, The January 2021 Council teleconference has been scheduled for 21 January at 12:00 UTC. Agenda will be circulated prior to the call. Call details: Join Zoom Meeting https://icann.zoom.us/j/99124120212?pwd=TWl6ZUVjdkxpYy95OVROM20ybHVZQT09 Meeting ID: 991 2412 0212 Passcode: Council-01 Wiki:  https://community.icann.org/x/tABACQ (background material, attendance, recording, transcript will be posted as it becomes available)

1 0

Re: [ccnso-council] Agenda and draft resolution
by Joke Braeken Jan. 21, 2021

Jan. 21, 2021

Hello All, I will take notes during today’s Council meeting in this document: https://docs.google.com/document/d/1MjWrRjia7cIrSHWly3CndDdjZ7uCW8nuIX60gGk… Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Thursday, 21 January 2021 at 10:06 To: ccnso-council <ccNSO-council(a)icann.org> Subject: [ccnso-council] Agenda and draft resolution Dear all, Please find included the agenda and draft resolution for today’s meeting The only resolution is appointment of David McAuley on the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel. Kind regards, Bart Draft Agenda ccNSO Council Meeting 169 21 January 2021 12.00 (noon) UTC 1. Welcome and roll call 1. Minutes & Action Items * Minutes Meeting 168, circulated 18 January 2021. * Action items and To-do’s, if any Action Item 167 GRC to include note on definition of plurality in relevant guidelines. Ongoing Action Item 168-01 Secretariat to inform SOPC and new members of appointments (listing, consent, etc.) Completed, awaits return all consent forms Action Item 168-02 Council to submit feedback to Google Doc on the future meeting strategies – Bart to add summary to document annex Completed, see item 11 a. Action Item 168-03 Council to draft response to the ICANN Board Org Effectiveness Committee letter Action Item 168-4 Council to share ideas, preferred dates, etc. regarding upcoming Council Workshop Ongoing see item 11 d. agenda Action Item 168-05 Secretariat to publish ICANN Board Nomination resolution as soon as possible Completed Action Item 168-06 Specially designated Chair Byron Holland to inform the ECA, ICANN Secretariat and ICANN Board of nomination of Katrina Sataki to the ICANN Board. Completed Action Item 168-06 Secretariat to publish resolution regarding GRC and Conflict of Interest policy as soon as possible. Completed 1. Intermeeting decisions (since 17 December 2020) * Appointment one (1) volunteer (1) to serve as mentor in its Fellowship Program and one (1) volunteer to serve on the Fellowship Program Selection Committee (to be completed 15 January 2021) 1. ccPDP 3 * Part 1 Retirement – Update Informational * Part 2 Review Mechanism –Update Informational 1. IDN ccPDP4: Update Informational 1. Selecting members for the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel For decision: Selection of member: David McAuley Draft Resolution Background At its 19 November 2020 the ccNSO Council agreed to participate in the selection of members of the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel (decision 165-02). At the time the ccNSO intended to participate with two members. After the launch of the call for expression of interest by ICANN Org, only one person responded. Decision The ccNSO Council appoints David McAuley (Verisign, .cc) to serve on the Community Representative Group. The Chair is requested to inform David and relevant staff of ICANN Org accordingly. The Chair is also requested to inform the other Chairs of the Supporting Organizations and Advisory Committees and relevant ICANN Org staff that the ccNSO will only fill one seat. 1. Update Review and Implementation Dashboard Informational 1. Draft response to Board OEC letter For discussion 1. Update Rules and Guidelines Informational * Update discussion Rules of ccNSO * Introduction of Consolidated appointment and selection procedures. Councillors feed-back * Introduction WG/Committee Chair and Vice-chair nomination and appointment. Councillors feed-back 1. Terms of Reference Outreach & Involvement Standing Committee Draft Terms of Reference: Scope, Composition and Working Methods Informational and discussion. 1. Update ccNSO Statement procedure regarding the Amendment of Article 10 ICANN Bylaws Informational 1. Update ICANN70 (related) sessions * ICANN response on comments ccNSO and others on proposed evolution of meeting strategy * ccTLDs related sessions i. Tech Day ii. Members meeting sessions * Governance session * ccTLDs: looking at the future * Q&A ccTLD related Board members iii. ccTLD News sessions * Joint meetings: i. Meeting with the Board ii. Meeting with GAC iii. Meeting with GNSO Council * Council workshop: Tuesday 16 March 2021, noon UTC (TBC) i. Review role of chair and vice -chairs, Roles and responsibilities of Councillors ii. Work plan * Council Preparatory meeting, Thursday 18 March 18.00 UTC (Tentative) 1. Update ECA & CSC * ECA (Informational) * CSC (Informational) 1. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 1. Update WGs * SOPC * IGLC 1. Update liaisons * Update ALAC Liaison (written update to follow) * Update GNSO Liaison (written update to follow) 1. Meetings Next Council Meetings: * February 18 – 20:00 UTC * March (ICANN70 TBD) * April 22 – 12:00 UTC * May 20 – 18.00 UTC · May 20 – 18:00 UTC 1. AOB 1. Discussion session on what needs to be included in future Rules of the ccNSO (if time permits) Background The current Rules of the ccNSO have been established in 2004. Since 2004 the ccNSO itself and the environment in which it operates has evolved. For example, when the Rules were adopted in 2004, the ccNSO had around 50 members. Currently, there are 172 members. Another example, to address various needs of the growing (membership- and importance-wise) ccNSO, in 2007 the ccNSO started to develop internal procedures (guidelines) as envisioned in the Bylaws (currently, Article 10). Next example, the introduction of the Empowered Community and the role of the ccNSO as a decisional Participant. It is obvious that this new role was NOT envisioned at the time the Rules of the ccNSO were conceived. The need to update the Rules has been recognized and discussed by the ccNSO members at several meetings for the past 3 years. If time permits, this session is intended to ask Councillors through break-out rooms to identify topics and aspects of the ccNSO Governance you would like to see included in future Rules of the ccNSO. Your input will be used by the GRC in its work. Background material Possible topics to include in FUTURE Rules of the ccNSO ccNSO Rules of the ccNSO 2004 1. Closure

1 0

Agenda and draft resolution
by Bart Boswinkel Jan. 21, 2021

Jan. 21, 2021

Dear all, Please find included the agenda and draft resolution for today’s meeting The only resolution is appointment of David McAuley on the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel. Kind regards, Bart Draft Agenda ccNSO Council Meeting 169 21 January 2021 12.00 (noon) UTC 1. Welcome and roll call 1. Minutes & Action Items * Minutes Meeting 168, circulated 18 January 2021. * Action items and To-do’s, if any Action Item 167 GRC to include note on definition of plurality in relevant guidelines. Ongoing Action Item 168-01 Secretariat to inform SOPC and new members of appointments (listing, consent, etc.) Completed, awaits return all consent forms Action Item 168-02 Council to submit feedback to Google Doc on the future meeting strategies – Bart to add summary to document annex Completed, see item 11 a. Action Item 168-03 Council to draft response to the ICANN Board Org Effectiveness Committee letter Action Item 168-4 Council to share ideas, preferred dates, etc. regarding upcoming Council Workshop Ongoing see item 11 d. agenda Action Item 168-05 Secretariat to publish ICANN Board Nomination resolution as soon as possible Completed Action Item 168-06 Specially designated Chair Byron Holland to inform the ECA, ICANN Secretariat and ICANN Board of nomination of Katrina Sataki to the ICANN Board. Completed Action Item 168-06 Secretariat to publish resolution regarding GRC and Conflict of Interest policy as soon as possible. Completed 1. Intermeeting decisions (since 17 December 2020) * Appointment one (1) volunteer (1) to serve as mentor in its Fellowship Program and one (1) volunteer to serve on the Fellowship Program Selection Committee (to be completed 15 January 2021) 1. ccPDP 3 * Part 1 Retirement – Update Informational * Part 2 Review Mechanism –Update Informational 1. IDN ccPDP4: Update Informational 1. Selecting members for the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel For decision: Selection of member: David McAuley Draft Resolution Background At its 19 November 2020 the ccNSO Council agreed to participate in the selection of members of the Community Representatives Group, which will select the Independent Review Process (IRP) Standing Panel (decision 165-02). At the time the ccNSO intended to participate with two members. After the launch of the call for expression of interest by ICANN Org, only one person responded. Decision The ccNSO Council appoints David McAuley (Verisign, .cc) to serve on the Community Representative Group. The Chair is requested to inform David and relevant staff of ICANN Org accordingly. The Chair is also requested to inform the other Chairs of the Supporting Organizations and Advisory Committees and relevant ICANN Org staff that the ccNSO will only fill one seat. 1. Update Review and Implementation Dashboard Informational 1. Draft response to Board OEC letter For discussion 1. Update Rules and Guidelines Informational * Update discussion Rules of ccNSO * Introduction of Consolidated appointment and selection procedures. Councillors feed-back * Introduction WG/Committee Chair and Vice-chair nomination and appointment. Councillors feed-back 1. Terms of Reference Outreach & Involvement Standing Committee Draft Terms of Reference: Scope, Composition and Working Methods Informational and discussion. 1. Update ccNSO Statement procedure regarding the Amendment of Article 10 ICANN Bylaws Informational 1. Update ICANN70 (related) sessions * ICANN response on comments ccNSO and others on proposed evolution of meeting strategy * ccTLDs related sessions i. Tech Day ii. Members meeting sessions * Governance session * ccTLDs: looking at the future * Q&A ccTLD related Board members iii. ccTLD News sessions * Joint meetings: i. Meeting with the Board ii. Meeting with GAC iii. Meeting with GNSO Council * Council workshop: Tuesday 16 March 2021, noon UTC (TBC) i. Review role of chair and vice -chairs, Roles and responsibilities of Councillors ii. Work plan * Council Preparatory meeting, Thursday 18 March 18.00 UTC (Tentative) 1. Update ECA & CSC * ECA (Informational) * CSC (Informational) 1. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 1. Update WGs * SOPC * IGLC 1. Update liaisons * Update ALAC Liaison (written update to follow) * Update GNSO Liaison (written update to follow) 1. Meetings Next Council Meetings: * February 18 – 20:00 UTC * March (ICANN70 TBD) * April 22 – 12:00 UTC * May 20 – 18.00 UTC · May 20 – 18:00 UTC 1. AOB 1. Discussion session on what needs to be included in future Rules of the ccNSO (if time permits) Background The current Rules of the ccNSO have been established in 2004. Since 2004 the ccNSO itself and the environment in which it operates has evolved. For example, when the Rules were adopted in 2004, the ccNSO had around 50 members. Currently, there are 172 members. Another example, to address various needs of the growing (membership- and importance-wise) ccNSO, in 2007 the ccNSO started to develop internal procedures (guidelines) as envisioned in the Bylaws (currently, Article 10). Next example, the introduction of the Empowered Community and the role of the ccNSO as a decisional Participant. It is obvious that this new role was NOT envisioned at the time the Rules of the ccNSO were conceived. The need to update the Rules has been recognized and discussed by the ccNSO members at several meetings for the past 3 years. If time permits, this session is intended to ask Councillors through break-out rooms to identify topics and aspects of the ccNSO Governance you would like to see included in future Rules of the ccNSO. Your input will be used by the GRC in its work. Background material Possible topics to include in FUTURE Rules of the ccNSO ccNSO Rules of the ccNSO 2004 1. Closure

2 1