May 2023 - Ccnso-council - lists.icann.org

Appointment ccNSO Council Chair and Vice-Chairs
by Bart Boswinkel March 24, 2026

March 24, 2026

17 March 2022 Appointment ccNSO Council Chair and Vice-Chairs Dear John, At its meeting on 10 March 2022 and ion accordance with the temporary election procedure adopted on 24 February 2022, the ccNSO Council appointed Alejandra Reynoso (.gt) as Jordan Carter (.nz) and Adebiyi Oladipo (.ng) as Vice-Chairs. The Chair and Vice-Chairs have been appointed to serve until the end of the ccNSO Council during ICANN76. On behalf of the ccNSO Council, Bart Boswinkel ccNSO Secretariat

1 2

REMINDER: ccNSO Council workshop and ICANN77 prep call agenda | 1 June at 20:00 UTC
by Kimberly Carlson May 31, 2023

May 31, 2023

REMINDER: Dear Council, In preparation for the workshop and prep call scheduled on Thursday, 1 June at 20:00 UTC, Council leadership request you review the “Roles and Responsibilities” document prior to the call: https://docs.google.com/spreadsheets/d/1fmToQ3l3nrj78jgwy8RpFGLF4qfq7jrW/ed… Agenda: 1. Welcome and roll call 2. Discussion roles and responsibilities * Recap Council workshop ICANN76 * During the session discussion of the skill set/requirement per role * Agree on overview of roles * Councilors are requested to look at the various roles and indicate, either online or during the meeting, which role they are interested in 1. ccNSO portfolio of activities 2024-2025 * Continue introduction from Council meeting 195 * Detailed overview of work items 1. Prep ICANN77: sessions of interest and assigning rapporteurs 2. AOB 3. Adjourn Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/97059507892?pwd=eVpmd2FlUzN3ekVEcXFxZ2ZDeGc2QT09 Meeting ID: 970 5950 7892 Passcode: ccNS0-prep

1 0

Re: [ccnso-council] [ccnso-members] Apply now for ccNSO Travel funding for ICANN78
by Joke Braeken May 31, 2023

May 31, 2023

Dear All, This is a correction. ICANN78 will take place in Hamburg (DE), 21-26 October 2023. The email below mistakenly mentioned Washington DC, which is the location for ICANN77 in June. Apologies for the confusion. Read more: https://ccnso.icann.org/en/announcements/announcement-29may23-en.htm Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> = = = ICANN77 links to bookmark now * ccNSO Schedule https://community.icann.org/x/IQM5Dg * ccNSO Session Highlights https://community.icann.org/x/RgI5Dg * Tech Day https://community.icann.org/x/MAM5Dg From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 30 May 2023 at 14:00 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] Apply now for ccNSO Travel funding for ICANN78 Apply now for ccNSO Travel funding for ICANN78 ccNSO travel support is available for a limited set of travelers for ICANN78, held 21-26 October 2023 in Washington (US). The ccNSO accepts applications for ccNSO travel support as of Tuesday, 30 May 2023 (noon UTC), until Thursday, 8 June 2023 (noon UTC). Early or late submissions will not be evaluated. What are the requirements for ccNSO applicants? The applicant actively participates in the work of the ccNSO and contributes to its projects and meetings. Examples of contributions to the work of the ccNSO: an active engagement in a ccNSO working group, a role as presenter/session chair/moderator during ccNSO sessions at the public meeting, or other engagements that strengthen the activities of the ccNSO. Important: Applications which do not clearly state an active contribution, are not eligible and will not be taken into consideration. What is included? The ccNSO travel funding covers an economy class ticket to the travel destination, the hotel costs for the time of the meeting and a per diem (either full funding, or partial funding). For more details, consult the ccNSO Travel Fund Guideline: https://ccnso.icann.org/en/about/ccnso-draft-oisc-07jun21-en.pdf [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/ccnso-draft-ois…> How to apply? Review all materials and fill in the form located here: https://ccnso.icann.org/en/about/travel-funding/form<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/travel-funding/…> Next Steps? Once the application window is closed, a subcommittee of the ccNSO Council will evaluate all applications. The outcome of the committee's deliberations will be published on the ccNSO website. All applicants will receive a personal notification. Consult the list of ccNSO funded travelers, per ICANN meeting on https://ccnso.icann.org/en/about/funded-travel [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/funded-travel__…> Background ICANN TRAVEL SUPPORT. Consult the ICANN Community Travel Support Guidelines here: https://www.icann.org/en/system/files/files/community-travel-support-guidel… ICANN might require funded Travelers to sign an acknowledgement and waiver, built in the meeting registration for anyone that is registering for in-person participation. Instructions on how to book travel will be provided by ICANN Travel Support to funded travelers who are confirmed and eligible. TRAVEL ARRIVAL MEASURES. All travelers have a responsibility to understand the entry and exit requirements of their travel and determine if they can meet those requirements before committing to the travel. Travelers may review specific travel requirements by visiting https://apply.joinsherpa.com/map [apply.joinsherpa.com]<https://urldefense.com/v3/__https:/apply.joinsherpa.com/map__;!!PtGJab4!-yJ…> or their local government international traveler websites. ICANN is committed to ensuring inclusive Public Meetings that provide an equal opportunity for all to engage. If funded travelers are not eligible or cannot meet the entry requirements as outlined by the government of the meeting location, ICANN aims to offer an engaging virtual participation experience. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> = = = ICANN77 links to bookmark now * ccNSO Schedule https://community.icann.org/x/IQM5Dg * ccNSO Session Highlights https://community.icann.org/x/RgI5Dg * Tech Day https://community.icann.org/x/MAM5Dg

1 0

REMINDER: .US Networking Event (ccNSO cocktail) RSVP by 31 May
by Kimberly Carlson May 30, 2023

May 30, 2023

Please RSVP by 31 May, 23 UTC. Only those on the list, will be allowed into the venue/event. Thank you, Kim [cid:image001.png@01D992C2.1323E310][forms.gle]<https://urldefense.com/v3/__https:/forms.gle/sycVnEbVSoGw3G5Z6__;!!PtGJab4!…> (Click image to register)

1 0

Apply now for ccNSO Travel funding for ICANN78
by Joke Braeken May 30, 2023

May 30, 2023

Apply now for ccNSO Travel funding for ICANN78 ccNSO travel support is available for a limited set of travelers for ICANN78, held 21-26 October 2023 in Washington (US). The ccNSO accepts applications for ccNSO travel support as of Tuesday, 30 May 2023 (noon UTC), until Thursday, 8 June 2023 (noon UTC). Early or late submissions will not be evaluated. What are the requirements for ccNSO applicants? The applicant actively participates in the work of the ccNSO and contributes to its projects and meetings. Examples of contributions to the work of the ccNSO: an active engagement in a ccNSO working group, a role as presenter/session chair/moderator during ccNSO sessions at the public meeting, or other engagements that strengthen the activities of the ccNSO. Important: Applications which do not clearly state an active contribution, are not eligible and will not be taken into consideration. What is included? The ccNSO travel funding covers an economy class ticket to the travel destination, the hotel costs for the time of the meeting and a per diem (either full funding, or partial funding). For more details, consult the ccNSO Travel Fund Guideline: https://ccnso.icann.org/en/about/ccnso-draft-oisc-07jun21-en.pdf How to apply? Review all materials and fill in the form located here: https://ccnso.icann.org/en/about/travel-funding/form<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/travel-funding/…> Next Steps? Once the application window is closed, a subcommittee of the ccNSO Council will evaluate all applications. The outcome of the committee's deliberations will be published on the ccNSO website. All applicants will receive a personal notification. Consult the list of ccNSO funded travelers, per ICANN meeting on https://ccnso.icann.org/en/about/funded-travel Background ICANN TRAVEL SUPPORT. Consult the ICANN Community Travel Support Guidelines here: https://www.icann.org/en/system/files/files/community-travel-support-guidel… ICANN might require funded Travelers to sign an acknowledgement and waiver, built in the meeting registration for anyone that is registering for in-person participation. Instructions on how to book travel will be provided by ICANN Travel Support to funded travelers who are confirmed and eligible. TRAVEL ARRIVAL MEASURES. All travelers have a responsibility to understand the entry and exit requirements of their travel and determine if they can meet those requirements before committing to the travel. Travelers may review specific travel requirements by visiting https://apply.joinsherpa.com/map or their local government international traveler websites. ICANN is committed to ensuring inclusive Public Meetings that provide an equal opportunity for all to engage. If funded travelers are not eligible or cannot meet the entry requirements as outlined by the government of the meeting location, ICANN aims to offer an engaging virtual participation experience. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> = = = ICANN77 links to bookmark now * ccNSO Schedule https://community.icann.org/x/IQM5Dg * ccNSO Session Highlights https://community.icann.org/x/RgI5Dg * Tech Day https://community.icann.org/x/MAM5Dg

1 0

New Public Comment Proceeding: Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations
by ICANN Community Digest May 29, 2023

May 29, 2023

Monday, 29 May 2023 ICANN Community 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 Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org! Table of Contents ICANN77 REGISTER Policy Outlook Report Prep Week Schedule Policy Forum Schedule Zoom Backgrounds ICANN Continues the Pandemic Internet Access Reimbursement Program Information Sharing NEW PUBLIC COMMENT PROCEEDING: Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations REMINDER: Calling for NextGen@ICANN Applications for ICANN78 Action Items 🔥 ACTION ITEM: Call for Expressions of Interest: 2024 ICANN NomCom Chair and Chair-Elect 🔥 ACTION ITEM: Register for the Asia Pacific Domain Name System Forum 2023 Public Comment Phase 1 Initial Report on the Internationalized Domain Names EPDP Bylaws Amendments and Documents to Implement the NomCom2 Review ISPCP Constituency Charter Amendments PTI / IANA Governance Proposal NEW: Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations ICANN77 REGISTER Policy Outlook Report Prep Week Schedule Policy ForumSchedule Zoom Backgrounds ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN77, and those who meet the eligibility requirements will be selected to participate. The application process opens 17 May 2023. The application deadline is 05 June 2023 at 23:59 UTC. Program webpage and application The goal of this program is to facilitate participation in ICANN Public Meetings during the pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Since ICANN77 will be conducted as a hybrid meeting. Only applicants that participate virtually are eligible for this program. Please contact internetreimbursement(a)icann.org for more information Information Sharing NEW PUBLIC COMMENT PROCEEDING: Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations The ICANN organization seeks Public Comment on the proposed amendments to the base generic top-level domain Registry Agreement (gTLD RA) and the 2013 Registrar Accreditation Agreement (RAA). The targeted amendments will strengthen obligations to require registrars and registries to stop or otherwise disrupt Domain Name System (DNS) abuse. For more information and to participate in this proceeding, please visit this webpage. Submissions Opening Date: Monday, 29 May 2023 Submissions Closing Date: Thursday, 13 July 2023 REMINDER: Calling for NextGen@ICANN Applications for ICANN78 ICANN is calling for applications for the NextGen@ICANN Program for the ICANN78 Annual General Meeting. ICANN wants to hear from university students living and studying in the European region who are interested in the future of the Internet and in participating in the ICANN78 Annual General Meeting. ICANN78 is scheduled to be held in Hamburg, Germany from 21–26 October 2023. The NextGen@ICANN Program application window will remain open until 19 June 2023. Read more. Action Items 🔥 ACTION ITEM: Call for Expressions of Interest: 2024 ICANN NomCom Chair and Chair-Elect ICANN is seeking Expressions of Interest for the Chair and Chair-Elect of the 2024 Nominating Committee. For additional information on the positions, please refer to the Call for Expressions of Interest here. Expressions of Interests, which will be maintained as confidential, should be sent to NomComChair2024(a)icann.org no later than Monday, 12 June 2023. A suggested form for submitting an Expression of Interest is available here. 🔥 ACTION ITEM: Register for the Asia Pacific Domain Name System Forum 2023 ICANN and the Hong Kong Internet Registration Corporation (HKIRC) invite interested participants to register for the Asia Pacific (APAC) Domain Name System (DNS) Forum 2023 in Hong Kong, China. A dedicated website has also launched to provide more information about the forum. The APAC DNS Forum 2023 will be held 4–5 July 2023 as a hybrid event at the Hong Kong Convention and Exhibition Centre (HKCEC). Read more. Public Comment Phase 1 Initial Report on the Internationalized Domain Names EPDP Open for submissions date: 24 April 2023 Closed for submissions date: 05 June 2023 EXTENDED: Bylaws Amendments and Documents to Implement the NomCom2 Review Open for submissions date: 17 April 2023 Closed for submissions date: 15 June 2023 ISPCP Constituency Charter Amendments Open for submissions date: 09 May 2023 Closed for submissions date: 26 June 2023 PTI / IANA Governance Proposal Open for submissions date: 16 May 2023 Closed for submissions date: 05 July 2023 NEW: Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations Open for submissions date: 29 May 2023 Closed for submissions date: 13 July 2023 See upcoming proceedings. See other public consultations. Volume 5, Issue 40 | Archive | Next Issue: Thursday, 01 June 2023 STAY INFORMED: Subscribe here 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

Draft submission on the Proposed NomCom related Bylaw changes
by Bart Boswinkel May 29, 2023

May 29, 2023

Dear all, Please find included the latest version of the draft ccNSO Council statement as prepared by Irina, Jordan, Chris and Alejandra. Please reply to the list if you have any concerns, questions etc. as soon as possible, but no later then Sunday 28 May 23.59 UTC. Deadline for submission is Monday 29 May 2023, 23.59 UTC. On behalf of the drafting team, kind regards, Bart Draft submission --------------------------- Comments of the ccNSO Council on the Bylaws Amendments and Documents to Implement the NomCom2 Review Introduction The Country-Code Name Supporting Organization (ccNSO) Council welcomes the opportunity to provide a response and input to the proposed Bylaws Amendments and Documents to Implement the NomCom2 Review. This response and input reflects the views of the ccNSO (Council) and was adopted as such in accordance with the Guideline: ccNSO Statements (2016)[1]. ________________________________ [1] https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-stat… On the introduction of “Unaffiliated” Directors (Section 7.2 & 7.4) It is the understanding of the ccNSO Council that “unaffiliated” Directors are suggested to effectuate recommendation 27 from the Independent Reviewer and the related suggestions from the Nominating Committee Review Implementation Working Group. The ccNSO Council fully supports the recommendation of the reviewer that NomCom appointees are expected to be independent and prioritize the interests of the global Internet community in their decision making. It is the view of the Council that this reflects the intent behind the creation of the NomCom in 2002 ( see ICANN: A Blueprint for Reform https://archive.icann.org/en/committees/evol-reform/blueprint-20jun02.htm) The purpose of the Nominating Committee is to select Directors and other individuals as otherwise described in the applicable sections of this document, and who conform to the criteria in those sections. The purpose of NomCom selections is to balance the representative selection of other Directors and positions to ensure that ICANN can continue to benefit from participants in the ICANN process (Directors or otherwise) of the highest integrity and capability who place the public interest ahead of any particular special interests, but who are nevertheless knowledgeable about the environment in which ICANN operates. This implies a NomCom composed both of persons deeply involved with the various constituencies of ICANN and also of persons knowledgeable but less directly involved. One of the underlying principles of the NomCom is that its very functional and geographic diversity would tend towards selection of Directors and persons filling other positions who are broad in outlook, individually and as a group, and not beholden to particular interests. To ensure that independent views are taken into account by the ccNSO Council, the Council has developed a set of specific requirements for NomCom appointees to the ccNSO Council in 2008, and which have evolved over time (latest version https://ccnso.icann.org/sites/default/files/field-attached/nomcom-appointee…) Over time this set of requirements have proven to be very helpful in maintaining a balanced, knowledgeable Council with a broad outlook. The ccNSO Council appreciates that the role of the ICANN Board of Directors should not be compared with the role and responsibilities of the ccNSO Council. However the ccNSO Council believes that the proposed changes to introduce “unaffiliated” Directors as proposed, might be too onerous on the Nomcom and related parties. We suggest that to give direction to NomCom on the nomination of independent directors (as originally envisioned when the NomCom was created) a section will be introduced in the Nominating Committee Operating Procedures to provide guidance to the Nomcom on appointment of directors. This would in our view not require a specific condition in the Bylaws to appoint at least a limited number of the category of “unaffiliated” Directors. Ultimately, if this proves not to result in the intended goal of appointing more “independent” directors, a Bylaw change could again be considered. On transforming all NomCom delegates into voting delegates (section 8.2) The ccNSO Council believes that the proposed amendment should be introduced only if there is a clear support for the change of role by the relevant Advisory Committee (GAC, SSAC, RSSAC). If the amendment is not supported, the change for the specific Advisory Committee should not be considered. On change of Terms on NomCom appointee (section 8.3) The ccNSO is generally supportive of the proposed extension of the term of the appointee to the NomCom. A two-year period seems to be appropriate. Further, the Council is supportive of the possibility to serve two terms maximum on the NomCom. However the Council believes that it should be up to the appointing organizations, whether they allow the appointee to serve two consecutive terms or with a minimum of two years between the end of their first term and the beginning of the second term. The Council believes that the appointing organizations and their respective communities are best positioned to assess the optimal duration to serve on the Nomcom, factoring considerations as continuity, institutional power.. Secondly, the ccNSO Council is aware that ICANN has launched a discussion on the composition of the NomCom. Although as said we are in general supportive of the proposed change, we also believe that this proposed amendment preempts the outcome of this “re-balancing” discussion. If this amendment was adopted and re-balancing was subsequently agreed upon, implementation of the highly needed re-balancing would be made more complex and take additional time as some members would be in their first year of appointment. On the inclusion of the NomCom Standing Committee (section 8.7) The ccNSO Council appreciates the suggestion to create a body that will ensure greater continuity and alleviate the burden on NomCom and the already tight timelines. This being said the Council also believes that this would be better achieved by starting with a light-weight structure with a more focused mandate. If the formation of the Standing Committee would prove to be a success, by achieving the goals that were set out when it was established, the mandate of the committee could be expanded. In our view Recommendation 24 of the Independent reviewers does provide such a light weight mandate. The independent reviewer recommended to form an empowered body “to ensure greater continuity across NomComs, and in particular, to suggest and assist in implementing changes to NomCom processes.” On the change to Section 12.2 It is the understanding of the ccNSO Council that the RSSAC requested a change to section 12.2 of the Bylaws. Accordingly, members of RSSAC would no longer be appointed by the ICANN Board. The ccNSO Council reluctantly expresses some concern about the proposed change. By removing the appointment by the Board, with no other mechanism in place, it is unclear to us (and we assume to the wider community as well) who is eligible to become part of RSSAC and how? We appreciate that RSSAC is changing and these changes will be reflected in the Bylaws in time. It is our understanding that such an amendment would avoid potential cooptation: a person appointed by RSSAC becomes a voting member of NomCom, this person would vote on the nomination of a Board member, who in turn would appoint members to RSSAC. In addition, we note that although currently section 12.2 (c ) (ii) and section 12.2 (b) (ii) are currently the same: The SSAC's/RSSAC’s chair and members shall be appointed by the Board. Before making the change as requested the ccNSO Council would appreciate the need for the change to section 12.2 (c) ( ii) and not to change 12.2 (b) (ii). We hesitantly suggest that, before becoming a voting member of the NomCom, both the mechanism of section 12.2 (b ) and (c ) (ii) should be amended to include an alternative mechanism to appoint members to SSAC and RSSAC. On the NomCom Standing Committee Charter According to the proposed charter the purpose of the NomCom Standing Committee is to: * Support continuous improvement to the NomCom Operating Procedures and associated processes to increase the effectiveness and efficiency of the NomCom while enhancing the NomCom’s transparency and accountability to the overall ICANN community. * Provide continuity across annual NomCom cycles and to build the institutional memory of the NomCom. The Council notes that the purpose statement provides elements that are not directly related to the recommendation of the independent reviewer, and at a minimum will need further explanation and discussion in this context, as they are not detailed in the proposed charter and lend themselves to different interpretations. These elements are: * Continuous improvement – It is unclear whether this would refer to the continuous improvement framework to be developed by the community as suggested by ATRT 3 or to some other method. In section VIII of the proposed charter Review and Continuous Improvement this element is not detailed either. * “effectiveness and efficiency of the NomCom” – The Council appreciates the goal to be effective and efficient, but notes the objective may be in conflict with the goal of the NomCom, which is responsible for nominating Board members and others in leadership positions. * “enhancing the NomCom’s transparency and accountability to the overall ICANN community.” – This part of the purpose statement is again not aligned with the recommendations of the independent reviewer. We understand that section VII is intended to detail Accountability and Transparency. However we believe that the proposed mechanisms do not measure up to the method the reviewers recommended. Any suggestion should be provided to the ICANN Community for public comment, which in our view is a fundamental feature to build trust in the NomCom Standing Committee and in the view of the Council this suggestion is not included in the Charter of the NomCom Standing Committee. Further, the purpose of the Committee is further refined by the scope of responsibilities. Accordingly, the Standing Committee is expected to: Provide continuity across annual NomCom cycles - In cooperation with the relevant ICANN staff the Committee is expected to standardize the work across NomCom cycles, such as planning, documenting and review of the NomCom’s processes. Further, the Standing Committee is also charged with participating in ICANN’s annual budget and planning processes on behalf of the NomCom. With respect to this activity by the use of the wording “in cooperation” it is unclear to the Council whether the staff has a supporting role or a more independent role, with respect to this activity, including, but not limited to the participation of the committee in ICANN’s annual planning processes. The ccNSO Council appreciates the need to provide adequate staff support and other resources to the NomCom. As such the Council notes that according to section 8.6 of the ICANN Bylaws ICANN “shall provide administrative and operational support necessary for the Nominating Committee to carry out its responsibilities.” The Council also understands the need for participation of the NomCom annually in the planning processes to ensure adequate resourcing for the NomCom. However, the Council believes that the Standing Committee and/or the NomCom has no role in other areas of the budget and this should be clarified. Build the institutional memory of the NomCom - In collaboration with ICANN org NomCom support staff, the NomCom Standing Committee will be responsible for reviewing, assessing, and providing input on the website and systems used for maintaining a historical archive for processes and procedures used by the NomCom. The ccNSO Council supports such a role for the Standing Committee. The NomCom Standing Committee engagement with ICANNorg - In fulfilling its purpose and responsibilities with ICANN org NomCom support staff, especially with regard to the review of each NomCom cycle, the NomCom Standing Committee will work in consultation with ICANN org NomCom support staff to help assess the previous NomCom cycle. To the extent this activity enhances processes, and alleviates the work of the NomCom and reduces the time pressure, the ccNSO Council is supportive. However, again it is noted that some elements under this activity are open for interpretation, particularly the work items under d) and e). The NomCom Standing Committee Role with Respect to Bodies That Appoint Delegates to the NomCom - In fulfilling its purpose and responsibilities, the NomCom Standing Committee will be available to provide information/guidance to bodies appointing delegates to the NomCom regarding the diversity needs, in line with the ICANN community agreed upon definitions and goals for diversity considerations. It is the understanding of the Council that to date the ICANN community definitions and goals for diversity considerations, have not been defined, nor been agreed upon. In addition, it is our understanding that – although important - diversity criteria are not included as a requirement for bodies appointing delegates to the NomCom. Therefore the ccNSO Council does not understand the need to include this already in the charter. Finally this Standing Committee should have a more explicit name to avoid confusion with the Nominating Committee itself, for example: NomCom’s Improvement & Continuity Standing Committee.

2 1

The May 2023 edition of the ccNSO monthly newsletter is out now.
by Joke Braeken May 26, 2023

May 26, 2023

Hello All, The May 2023 edition of the ccNSO monthly newsletter<https://community.icann.org/x/UgirBQ> is out now. You will be able to find this month's edition, the ccNSO Newsletter Archive and instructions on how to subscribe to the newsletter here: https://community.icann.org/x/UgirBQ Highlights from this month's edition: * ccNSO adopts review mechanism policy for ccTLDs * Keep informed about the work of the ccNSO * The ICANN77 Policy Outlook Report is out now * The .ec ccTLD manager joins the ccNSO * ICANN77 & ccNSO: what to expect? * Session highlights: ccTLD registration trends, ccTLD News, Cyber Security legislation affecting ccTLDs * DASC shares second set of survey results at ICANN77 * DASC launches its repository for ccTLDs. You too can contribute! * Council highlights Happy reading! Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> = = = ICANN77 links to bookmark now * ccNSO Schedule https://community.icann.org/x/IQM5Dg * ccNSO Session Highlights https://community.icann.org/x/RgI5Dg * Tech Day https://community.icann.org/x/MAM5Dg

2 1

Decision to adopt report voting on ccNSO PDP3 Review Mechanism
by Bart Boswinkel May 26, 2023

May 26, 2023

Dear all, Please find included the Joke’s report on the PDPRM voting. To formally close the voting process and include it as a reference in the Board Report, you are kindly asked to adopt the report. To date we have not received any questions on the report itself. If you have any questions, or object, please use the list. Closure of this item is Tuesday 30 May 23.59 UTC. Kind regards, Bart Draft Resolution Decision The ccNSO Council adopts the report of the voting manager ccPDP3 Review Manager, dated 23 May 2023. With the adoption the voting on the PDP RM is formally closed. The ccNSO Council notes the following result of the voting: At the closure of the vote, 105 Emissaries out of 173 (60%) casted their votes. Out of the 105 casted votes, 101 supported the ccNSO Council's recommendation to adopt the proposed policy, 2 voters did not support the recommendation, and 2 voters voted without selecting any of the options. The ccNSO Council concludes that the ccNSO Council's recommendation to adopt the proposed policy is supported by the ccNSO membership. The ccNSO Council thanks Joke Braeken, the Regional Organisations (AFTLD, APTLD, CENTR and LACTLD) to make this happen. This resolution becomes effective up publication.

6 5

FOR REVIEW: ccNSO Council workshop and ICANN77 prep call agenda | 1 June at 20:00 UTC
by Kimberly Carlson May 25, 2023

May 25, 2023

Dear Council, In preparation for the workshop and prep call scheduled on Thursday, 1 June at 20:00 UTC, Council leadership request you review the “Roles and Responsibilities” document prior to the call: https://docs.google.com/spreadsheets/d/1fmToQ3l3nrj78jgwy8RpFGLF4qfq7jrW/ed… Agenda: 1. Welcome and roll call 2. Discussion roles and responsibilities * Recap Council workshop ICANN76 * During the session discussion of the skill set/requirement per role * Agree on overview of roles * Councilors are requested to look at the various roles and indicate, either online or during the meeting, which role they are interested in 1. ccNSO portfolio of activities 2024-2025 * Continue introduction from Council meeting 195 * Detailed overview of work items 1. Prep ICANN77: sessions of interest and assigning rapporteurs 2. AOB 3. Adjourn Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/97059507892?pwd=eVpmd2FlUzN3ekVEcXFxZ2ZDeGc2QT09 Meeting ID: 970 5950 7892 Passcode: ccNS0-prep

1 0