- Ccnso-council - lists.icann.org

Letter regarding ICANN 71 At-Large Policy Session 2
by Alejandra Reynoso July 23, 2021

July 23, 2021

Dear Maureen Please find the attached letter, on behalf of the ccNSO Council, regarding the ICANN71 At-Large Policy Session 2: *ccTLD Governance Models - Testimonies from At-Large End Users*. Best regards, Alejandra -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt

1 0

REMINDER: Planning & Prioritization Framework teleconference with the SOPC call #2 | 26 July at 15:00 UTC
by Kimberly Carlson July 23, 2021

July 23, 2021

Dear all, As a reminder, the Planning & Prioritization Framework teleconference with the SOPC call #2 is scheduled for Monday, 26 July at 15:00 UTC. Call details: Join Zoom Meeting https://icann.zoom.us/j/94026694201?pwd=VTJLVXBzWlliWWp4S1FYTDlUbHRKUT09 Meeting ID: 940 2669 4201 Passcode: SOPC-Jul26 Background: This year the org planning dept has started a project to design a work prioritization framework that once agreed upon will become a step in the ICANN Annual Operating Planning process. The step of work Prioritization will be received as input for development of the 5 year and 1 year Operating Plans and Budgets. We would like to facilitate 2 workshop meetings to review the proposed Design Elements in this process. * The first meeting will include the definition of Participants and the Roles and Responsibilities of the participants. * The 2nd workshop will include the review of several researched Prioritization techniques to see which ones fit the ICANN model the best.

1 0

ccPDP3-RET | Remember to vote: Your participation in this election is important!
by Joke Braeken July 23, 2021

July 23, 2021

Dear ccNSO Members, Councillors, This is a reminder to vote on the ccNSO Council's recommendation to adopt the proposed policy on the retirement of ccTLDs. Your participation in this election is important! Below is the latest status update regarding the ongoing ccPDP3 retirement policy election. We also added some frequently asked questions and answers. STATUS UPDATE Total Ballots Cast (including duplicates): 91 Ballots Counted (excluding duplicates): 84 Voters Who Haven't Voted: 88 FAQ FAQ#1. What is this vote about? To determine whether the ccNSO Community supports the proposed policy on the retirement of ccTLDs FAQ#2. Who can vote? The ballots have been sent to the e-mail address of the primary contacts of each ccNSO Member. Questions? Contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> FAQ#3. When will the election close? Voting ends 28 July 2021, at 23:59 UTC FAQ#4. What is the policy about? 1. The trigger event for a ccTLD retirement process. The retirement process starts with the removal of a country code from the ISO3166-1 list of country names. For exceptionally reserved domain names, the trigger event is the fact that the ISO Maintenance Agency makes changes to the reserved 2-letter codes. For IDN ccTLDs, the trigger event will be identified under the ccNSO policy on the (de)selection of IDN ccTLD strings (ccPDP4). Note: * the trigger is the removal of a country code, not the country code Top Level Domain * RFC1591: IANA (the IANA Functions Operator) is not in the business of determining what is and what is not a country. ISO has a process to determine this. 1. Impact of the trigger event on the Root Zone Database. Once a country code is removed from the ISO3166-1 list, the ccTLD MUST be removed from the DNS rootzone database. The rationale for this is that the link between the ISO3166-list and the list of ccTLDs should be maintained. Also, the ISO Maintenance Agency should be able to assign a 2-letter code to a new Territory. 2. ccTLD retirement process. Once there is a trigger event, the IANA Functions Operator sends a notice of retirement to the ccTLD Manager, with an invitation to discuss a retirement plan. The removal of the ccTLD from the root zone is foreseen to happen 5 years after the retirement notice. The ccTLD manager - together with PTI - can potentially agree to extend this deadline, with an additional 5 years. FAQ#5. Does this policy apply to all ccTLDs? The policy is directed at ICANN, and is within scope of the ccNSO policy development process, as stated in Annex C of the ICANN Bylaws. FAQ#6. Where can I read more about the ongoing election? To learn more about the ongoing election, the proposed policy on the retirement of ccTLDs, as well as ccNSO Council's Recommendation to adopt the proposed policy, go to https://ccnso.icann.org/en/announcements/announcement-06jul21-en.htm Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Register for FY23 IANA Functions and PTI Planning Webinar
by Kimberly Carlson July 22, 2021

July 22, 2021

**Sent on behalf of the IANA Department** Dear colleagues, Please join our planning team and the IANA department as they request your input to develop the FY23 PTI/IANA Operating Plan & Budget. More on the webinar and how to register here: https://www.icann.org/en/announcements/details/register-for-fy23-iana-funct… Best regards, IANA

1 0

[Ext] Annotate option
by Kimberly Carlson July 22, 2021

July 22, 2021

**Sent on behalf of Sean Copeland** Hi everyone, I was having a conversation with another council member on the annotated voting, which I thought was good. I'm not sure if zoom’s approach works well, though. I could not see names associated with clicks, and I while I thought I was clicking 8 on someone else’s screen, it appeared at 5. Not knowing what everyone else experienced, on my side there was three checks at 8, one of them mine, that I had to keep clicking back because it went away, and a mass ball of green at 5. Something to look at / mention to zoom. Other take away, on calling emergent council call we all need to remember any one of us can put that forward, I in particular dropped the ball in not suggesting it. Stephen is correct in that the ALAC issue clearly rose to that level of importance, Nick also correct on time. Clearly a gap that needs to be isolated and addressed in what we should all hope is a rarely required practice. Me Sent from my iPhone

1 0

Thursday, 22 July 2021
by ICANN Community Leadership Digest July 22, 2021

July 22, 2021

Thursday, 22 July 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. How Domain Name System Policy is Developed, and How You Can Get Involved Table of Contents Webinars TODAY: DNS Security Threat Mitigation Program Webinar NEXT WEEK: FY23 IANA Functions and PTI Planning Webinar REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars Information Sharing TODAY: Community Input Needed: SSAD ODP Questionnaire NEXT WEEK: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building REMINDER: Request for Early Input - GNSO Transfer Policy Review PDP Working Group REMINDER: APIGA 2021 Application Period Is Now Open REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open Public Comment Proposed Renewal of the .AERO Registry Agreement Proposal for Greek Root Zone Label Generation Rules Webinars TODAY: DNS Security Threat Mitigation Program Webinar ICANN will host a webinar on Thursday, 22 July 2021 at 16:00 UTC to provide the ICANN community with updates on its DNS Security Threat Mitigation Program, community-facing initiatives, Domain Abuse Activity Reporting System (DAAR), and Domain Name Security Threat Information Collection and Reporting (DNSTICR) project. Register here. Read more. NEXT WEEK: FY23 IANA Functions and PTI Planning Webinar ICANN invites the community to join one of two public webinars to discuss planning for the fiscal year 2023 (FY23) Operating Plan and Budget (OP&B) for delivering the Internet Assigned Numbers Authority (IANA) functions. The webinar will explain the planning process, the proposed operational priorities for FY23, timelines, and key assumptions. ICANN welcomes the community's questions and comments. Webinar 1 | Tuesday, 27 July 2021 | 00:00 UTC | Register Webinar 2 | Tuesday, 27 July 2021 | 16:00 UTC | Register The annual OP&B for the IANA functions has two components: a budget and operating plan for Public Technical Identifiers (PTI), the ICANN affiliate that performs the IANA functions, which outlines the planned activities and resources to deliver the core IANA functions. The second component includes the PTI budget plus additional programs and costs that the ICANN organization incurs overseeing and enabling the IANA functions. In addition to the webinars, the community has further opportunity to participate in this planning process. The draft plans will be put out for Public Comment in September before being considered for formal adoption in late 2021. REMINDER: ITI Update: Register Now for ICANN Public Comment Submission Training Webinars ICANN org will hold a series of training webinars outlining the new Public Comment submission process. During these sessions, our teams will provide the ICANN community with step-by-step instructions on how to draft and publish a Public Comment submission and outline how to manage your current and past submissions. You are encouraged to ask questions throughout these webinars to ensure you are well-prepared to use this improved feature. Read more. Webinar 1 | Tuesday, 3 August 2021 | 14:00 UTC | Register Webinar 2 | Wednesday, 4 August 2021 | 21:00 UTC | Register Information Sharing TODAY: Community Input Needed: SSAD ODP Questionnaire ICANN has launched the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP) Community Questionnaire to help determine how many potential users are expected to use the SSAD and the anticipated volume of requests if it is implemented. The questionnaire will play a critical role in assessing the feasibility and associated risks, costs, and resources required in the potential deployment of SSAD. ICANN org is looking for participation from community members who request nonpublic domain name registration data. The questionnaire will be open until Thursday, 22 July (23:59 UTC). For questions, please contact jane.sexton(a)icann.org or isabelle.colas(a)icann.org. Read more. NEXT WEEK: Ninth Africa DNS Forum to Take Place Virtually 27-28 July 2021 The ninth Africa DNS Forum will be held virtually Tuesday and Wednesday, 27-28 July 2021 with the theme of "Evolving the DNS Ecosystem in Africa." The Africa DNS Forum is organized by the Africa Top Level Domains Organization (AFTLD), the Africa Registrar Association (AfRegistrar), and ICANN. The 2021 edition will take place as a two-day virtual event open to stakeholders in the African domain name industry. Sessions will cover topics including the evolution of the DNS ecosystem in the region, national and regional DNS Forum initiatives, emerging technical issues, financing and insurance in the DNS business, and compliance in the domain name industry. Participants will be able to join sessions through Zoom, and view through YouTube and Facebook streaming. To register, click here. REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building ICANN org opened a one-month nomination period for the Dr. Tarek Kamel Award for Capacity Building. Please submit your nominations via this nomination form by 23:59 UTC on Monday, 2 August 2021. Any additional information in support of nominations or questions about the award process may be submitted via email to kamelaward(a)icann.org. Read more. REMINDER: Request for Early Input - GNSO Transfer Policy Review Policy Development Process Working Group The GNSO Transfer Policy Review PDP Working Group requests input from Supporting Organizations, Advisory Committees, Stakeholder Groups, and Constituencies on topics within the PDP charter. The request was sent on Wednesday, 30 June 2021 to ICANN community leaders. A copy of the letter is available here: https://community.icann.org/x/tIT8CQ. Responses to gnso-secs(a)icann.org are requested by Wednesday, 4 August 2021. REMINDER: APIGA 2021 Application Period Is Now Open The 2021 Asia Pacific Internet Governance Academy (APIGA) announced its application period is now open for their virtual program, which will run from Friday, 1 October through Tuesday, 30 November 2021. Sessions will be held once or twice a week to accommodate the schedules of students and young professionals. Participants will be expected to complete preparatory work between sessions. The final day of the academy will be a hybrid event in South Korea. Applications are due by Sunday, 8 August 2021. Please note that a stable Internet connection is required for participation. The application procedure and more information on APIGA can be accessed here. REMINDER: Nominations for NextGen@ICANN Mentor Positions Now Open The NextGen@ICANN Program seeks nominations for its Mentor Program through Tuesday, 31 August 2021. The community-nominated selection committee will be responsible for overseeing the mentor selection process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here. Interested community groups should select their respective volunteers and notify deborah.escalera(a)icann.org. Public Comment Proposed Renewal of the .AERO Registry Agreement Close Date: Monday, 16 August 2021 Proposal for Greek Root Zone Label Generation Rules Close Date: Thursday, 26 Aug 2021 Volume 3, Issue 53 | Archive | Next Issue: Monday, 26 July 2021 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | Constant Contact Data Notice Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

IMPORTANT: ccNSO Governance Survey (rules)
by Kimberly Carlson July 22, 2021

July 22, 2021

**Sent on behalf of David McAuley and the GRC Subgroup** Dear all, The ccNSO Guideline Review Committee Rules Sub-group<https://community.icann.org/x/T4eUCQ> has been tasked to review the 2004 Rules<https://ccnso.icann.org/sites/default/files/filefield_25723/ccnso-rules-dec…>. The sub-group has been working on a basic framework of items they believe should be included in the updated version of the 2004 Rules. As a follow up to the ccNSO Governance Session at ICANN71<https://71.schedule.icann.org/meetings/4SLTHdGRMMMKGComo>, the sub-group has created a survey to seek your input: https://forms.gle/rz7keJeQk7ZjgGrM9 The survey will close on 30 July 2021. The topics and related questions are: - Inclusion of the basic ccNSO principles in the Rules (1 question) - The change mechanism for the Rules and Guidelines (4 questions) - Council decisions which should not be subject to veto by the Members (1 question) - Council decisions that may be subject to a veto by the Members (3 questions) - Requirements to veto a Council Decision (2 questions) - Decision by the Members only (3 questions) - Members vote/Decision-Making (1 question) - Quorum Rule (2 questions) - Mandatory review of the Rules (2 questions) The survey will conclude by giving you an opportunity to provide additional comments. The results of the survey will be shared with the ccNSO community by the end of August 2021 and will be used by the subgroup to inform their discussions. To avoid misunderstanding: this survey is intended to give you an opportunity to influence the process. The results are not intended to be, nor should they be interpreted as, a membership vote on the updated Rules. Thank you for your consideration and best regards, David GRC Rules Subgroup Chair GRC Rules Subgroup Members: David McAuley (Chair) Irina Danelia Stephen Deerhake Chris Disspain Atsushi Endo Ann-Cathrin Marcussen Alejandra Reynoso Katrina Sataki (observer) Sean Copeland (observer)

1 1

NOTES | ccNSO Council Meeting 175 | 22 July 2021 (noon UTC)
by Joke Braeken July 22, 2021

July 22, 2021

NOTES | ccNSO Council Meeting 175 | 22 July 2021 (noon UTC) 1. Welcome and roll call Welcome by Chair Alejandra Reynoso, who runs quickly through the agenda of today’s meeting. We are quorate. Apologies from Ali and Giovanni. @Councillors: please add “Council” next to your name in Zoom. Background material, recording and attendance can be found on the wiki: https://community.icann.org/x/NIS1CQ Please turn on your camera, if convenient. Item 9: deferred to next meeting. Less urgent now that ICANN72 will be fully virtual 2. Relevant Correspondence since June 2021 None. The correspondence to ALAC: Adoption of the letter is on the agenda of today’s meeting. 3. Minutes & Action Items a. Minutes Meeting 174, transcript. b. Action items and To-do’s, if any All completed. Tech WG Charter Update: See Council meeting in September. 4. Intermeeting Decisions (since 17 June 2021) a. Adoption Members Report ccPDP3- Retirement Ongoing Elections. The vote is to determine whether the ccNSO membership supports the ccNSO Council's recommendation to adopt the proposed policy on the retirement of ccTLDs. The voting starts on Wednesday, 7 July 2021 (00:01 UTC) and shall close on Wednesday, 28 July 2021 (23:59 UTC). Currently: 81 votes received. But: we need at least 86 votes. Read more here: https://ccnso.icann.org/en/announcements/announcement-06jul21-en.htm Please vote. 5. Progress ccPDP3 Retirement members vote Irina: Do we have a list of those who have not yet voted? Would help when sending reminders Alejandra: confirmed voting is anonymous. Joke confirmed too. Any suggestions on how to reach out to ccTLD managers to those who have not voted yet? Marie-Noemie: Why do some ccNSO members not vote? Sean: Can each of us be given a 15-20 block group of TLD’s that we can each reach out to, so we know we don’t duplicate? Alejandra: many reasons why people do not vote. Hence your reminders are important. Perhaps we can explain and stress the importance of voting, and explain what this is all about. Ai-Chin: do we know how many votes from each region? Pablo: Working closely with regional organizations (ROs) to promote voting seems to make sense; however, reaching out to fellow ccTLD operators via phone calls or emails could be very helpful. Jenifer: Maybe they have registered a wrong email? Alejandra: Joke has updated the list Jiankang: have a question and answer session, or FAQ posted. That might help in promoting the voting. Alejandra: We had such sessions already. Secretariat to send a short summary, in the reminders to vote. 6. CSC Related matters a. 2nd CSC Effectiveness Review CSC monitors performance IANA naming function Additional element: have recommendations from previous reviews been implemented? Template. GNSO Council expects to adopt that in the August meeting. Bart displays a .ppt: * Need review * Method effectiveness review. Same procedure, since it has proven previously it works. Touches on all aspects of the CSC. Secondly, it allows for comparison of the CSC effectiveness over time. * Review process * Timeline. Closure in March 2022 (adoption of the final report) b. Update CSC call for expression of interest In April 2021 one of the two current ccNSO appointed members on the CSC, Alejandra Reynoso, indicated she wants to step down from the CSC as she was elected Chair of the ccNSO. Following a call for expressions of interest and a Council selection process, Frederico Neves (.br) was appointed in June 2021 for the remainder of Alejandra's term. Next term starts in October. Hence the new call for EoI. See: https://ccnso.icann.org/en/announcements/announcement-07jul21-en.htm Currently we have received 2 applications, potentially a third one coming in. Council will need to select its preferred candidate. c. CSC update See written update 7. Progress expanded role Triage committee See background material. Evolution triage committee. Nick: charter review is due. Marie-Noemie: prioritising method. Current status: Currently, the Triage Committee is dedicated to quickly review incoming requests for input and make a suggestion to the Council on how to react to the requests. To better balance the workload against the available resources, Council suggested an expanded mandate for the Triage Committee, which includes work on the Council work plan prioritisation. The Triage Committee had its first meeting on 13 July, where the committee members discussed the future role of the Triage Committee, the evolution of the committee and an outline of its new role. Next steps: During its next meeting, scheduled for 17 August, the Triage committee will have a discussion on the prioritisation method to be used for the Council work plan, as well as a high-level discussion on the changes that are needed to its Charter. It will also begin the work of prioritising the work plan, ready for Council consideration in September (in advance of the start of the October-December quarter). Objections or questions? None. Bart: council adopted the baseline of activities at the previous meeting. Jordan and Bart to identify 2 or 3 major work items, detail them, and see if the method of prioritisation would work. Related: the Triage Committee in time will have an oversight role, especially for those work items fully under control of the ccNSO. Some work items are bylaw driven, but there are others where there is more flexibility: For the latter a bit more oversight and accountability would be efficient. 8. ICANN proposal to create an ad-hoc community representative group to coordinate on those WS2 recommendations where community prioritization and coordination may be required Alejandra mentioned 2 reasons to include this on the agenda: * Workshop by icann org from last week. ICANN org held a Planning & Prioritization Framework teleconference with the SOPC (call #1 | 14 July at 13:00 UTC). The SOPC will continue the discussions with the org planning dept regarding an ICANN org project to design a work prioritization framework that once agreed upon will become a step in the ICANN Annual Operating Planning process. The second workshop (Call #2 | 26 July 2021 at 15:00 UTC) will include the review of several researched prioritization techniques to see which ones fit the ICANN model the best. Call #2 is relevant for the Triage Committee too: different scale and scope, but nonetheless relevant. * WS2 recommendations implementation. See next SO/AC roundtable. Suggestion by ICANN org planning team to create an ad-hoc group to work on this. So far we have a checklist of the WS2 recommendations. Not seen as a project. Has been effective. Many are already implemented or ongoing. How much time and resources will this joint effort take? Comments? Suggestions? none 9. ICANN Hybrid Meeting: what are the requirements from a Council perspective? Deferred to the next meeting (September Council meeting). ICANN72 will be fully virtual. Lessons learned from virtual meetings, and start preparations for ICANN72. Monday leadership meeting. 10. Update ALAC -session ccTLD Governance Models - Testimonies from At-Large End Users MPC has a wrap-up meeting after every public ICANN meeting. During the ICANN71 wrap-up, concerns were raised regarding the ALAC session. The concerns were brought to the attention of council. A draft letter has been circulated, from Council to ALAC. Draft was further reviewed after a letter by Garth Miller. Balance: ccNSO needs to continue a good relationship with ALAC. also in light of being a Decisional Participant. Concerns regarding the content of some presentations (mixing up ccTLDs, not speaking to the agreed purpose etc) but also the organisation and prep of the meeting. Letter addresses the concerns, and is forward-looking. Any comments concerning the process that was followed? (not addressing the substance) We will use the annotation-tool in Zoom. similar to “temperature of the room” exercise Responses range from 5 to 8 (9). Quite a number of marks in the 5-6 range. Bart: What is needed to turn this into a process where you have confidence in? Stephen: see correspondence to mailing list from 15 July. Bart: That is on the substance? Stephen: My letter was a comment on the substance indeed. But regarding the process, we should have had an extraordinary council meeting as part of the process. Bart: fair comment from Stephen Nick: hard to schedule extra calls. Rated the process favourably. It was done methodically, and all had the opportunity to contribute to the google doc. Heads up to Maureen, and we know we can expect an apology on this. Javier: found process was inclusive, efficient. Alejandra: Final comments on the draft letter are due on Monday next week. The best is the enemy of good. The letter sends a clear message, but also leaves the door open to future collaboration. Stephen: abstains. Letter is not strong enough. Resolution Move? Javier Second? Pablo Abstain? Stephen Objections? None All in favour 11. Update ICANN Learn Course Any concerns if we move this to an online approval process? No objections. 12. Is there a role for the ccNSO in facilitating the discussion across the ccTLD community with respect to DNS Abuse? See the AOB from the previous Council meeting. Recurring topic. There are a number of DNS Abuse-related sessions and contributions, including during the ccNSO members meeting, ccTLD News sessions, Tech Day etc. GNSO reached out to us. Alejandra explains the exercise (3-12-3 game). Councillors and others expressed their views on the ccNSO and DNS Abuse. Councillors and others asked to identify the top 3 aspects in this respect, and assessed their impact (impact on helping ccTLDs to deal with DNS Abuse) and effort level (what does it take to produce the envisioned result). As a next step, the Secretariat will provide a summary and will formulate a suggested way forward, which will be included into an action plan, which will be sent to Council for their consideration and adoption. Brainstorming report | 3-12-3 game: >> >> Group 1 Bart: * Create blacklist. Terminated registrars across ccTLDs. High effort, very high effort * Sharing information. Increase news. Middle impact to high, middle effort. Supported by all as a quick win. Develop a repository on what has already been presented on what ccTLDs are doing. Easy accessible to everyone else. * Develop common approaches: high effort, high impact (not discussed, but this is Irina’s suggestion) >> >> Group 2 Alejandra: * Repository, good practices. Inspiration for ccTLDs * DNS Abuse WG within ccNSO to handle this. To channel communicatins. High impact, but also high effort. * Channel of communication: council chair. Low impact (just 1 person), but high effort. >> >> Group 3 Pablo: * Collaborate with GNSO RySG on definition of DNS Abuse. high interests in common. Quick win if we agree with the RySG. low effort, high impact. RySG has already a definition. Work has been done there. Maybe we could adopt the same definition? Work has been done already. Send to ccTLD community as a standard. Not be part of the conversation. Should not appear to be a vacuum of what the ccNSO appears to be doing * Webinar. Info sharing for ccTLDs. High impact, low effort * Develop best practices for ccTLD managers. high efforts, many different policies and cctld are different. High effort. Since it is optional, impact probably not so high >> >> Main Group Barrack: * High impact, high effort. Participate in the ongoing ICANN decisions. Conversations in contracted parties house on DNS abuse * High impact, low effort. Discuss what is DNS Abuse within ccTLD environment. Issues that affect registries, registrars * Efforts on what has been done already. In terms of TLD OPS for instance General feeling: * ccTLDs are protectors of ecosystem. More and more regulations forced on ccTLDs Next step: Now that councillors and others assessed the impact (impact on helping ccTLDs to deal with DNS Abuse) and effort level (what does it take to produce the envisioned result). As a next step, the Secretariat will provide a summary and will formulate a suggested way forward, which will be included into an action plan, which will be sent to Council for their consideration and adoption. 13. Updates ccPDPs a. Update ccPDP3 - Review Mechanism b. Update IDN ccPDP4 14. Update ECA 15. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 16. Update WGs c. SOPC d. IGLC e. GRC f. OISC g. TLD-OPS h. Technical WG i. MPC 17. Update liaisons j. Update ALAC Liaison (written update) k. Update GNSO Liaison (written update) 18. Next Meetings 16 September 2021 – 20:00 UTC October @ ICANN72 (23-28 October) 18 November 2021 – 12:00 UTC 17 December 2021 – 18:00 UTC 19. AOB Two from Alejandra: 1. If you have not done so, please provide your input to the GRC Rules sub-group survey! To complete the survey: https://forms.gle/z2sUS7Bzg3JyUN7u5 2. Secondly, next week we will need to start thinking about our bilateral meetings, and other ICANN72 related sessions. We will not have a Council meeting in August so we need to start prep our sessions off-line. Our September meeting will be too late! 20. Closure Next meeting 16 September 2021 – 20:00 UTC Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

2 1

REMINDER: July 2021 Council teleconference | 22 July at 12:00 UTC
by Kimberly Carlson July 22, 2021

July 22, 2021

Dear all, As a reminder, the July 2021 Council teleconference has been scheduled for 22 July at 12:00 UTC. Call details: Join Zoom Meeting https://icann.zoom.us/j/92316801768?pwd=OTNtMmJNSHljdHRUVHpyWm53RG5MZz09 Meeting ID: 923 1680 1768 Passcode: Council-07 Wiki: https://community.icann.org/x/NIS1CQ (background material, attendance, recording, transcript will be posted as it becomes available) If you are unable to attend, please let Bart and I know as soon as possible. Thank you, Kim

2 1

July 2021 Council teleconference | 22 July at 12:00 UTC
by Kimberly Carlson July 22, 2021

July 22, 2021

**STARTING IN 1 HOUR** Dear all, The July 2021 Council teleconference has been scheduled for 22 July at 12:00 UTC. Agenda will be circulated prior to the call. Call details: Join Zoom Meeting https://icann.zoom.us/j/92316801768?pwd=OTNtMmJNSHljdHRUVHpyWm53RG5MZz09 Meeting ID: 923 1680 1768 Passcode: Council-07 Wiki: https://community.icann.org/x/NIS1CQ (background material, attendance, recording, transcript will be posted as it becomes available)

1 0