- Ccnso-council - lists.icann.org

Notice start rejection action petition period FY 22 Operating Plan and Budget
by Bart Boswinkel May 21, 2021

May 21, 2021

Dear ccTLD Community, First of all apologies for cross-posting. I am writing to you on behalf of Nick Wenban-Smith, ccNSO Rejection Action Process Manager, to inform you that on 12 May 2021, the ICANN Board of Directors has adopted ICANN’s FY 22 Operating Plan and Budget(see https://www.icann.org/resources/board-material/resolutions-2021-05-12-en#2.a ), which can be viewed at: https://www.icann.org/en/system/files/files/budget-fy22-2021-en.pdf On 21 May 2021, the ccNSO as a Decisional Participant received a notice from the ICANN Secretary pursuant to Section 22.5(a)(v) of the ICANN Bylaws. The adopted FY 22 Operating Plan and Budget is subject to Rejection Action Petitions from the community. If you are interested in submitting a Rejection Action Petition to the ccNSO Council, with respect to the approved FY22 Operating Plan and Budget, please consult Section 2 of Annex D for the requirements, which must be met (https://www.icann.org/resources/pages/governance/bylaws-en/#annexD ). Please be advised that per Annex D Section 2.2(a)(i)(A) the Rejection Action Petition must be: “…based on one or more significant issues that were specifically raised in the applicable public comment period(s) relating to perceived inconsistencies with the Mission, purpose and role set forth in ICANN's Articles of Incorporation and Bylaws, the global public interest, the needs of ICANN's stakeholders, financial stability, or other matter of concern to the community.” Please see also our internal Guideline: ccNSO Procedure for the Exercise of the Empowered Community's rights to Reject Specified Actions (https://ccnso.icann.org/about/guideline-rejection-actions-procedure-24may18… ). According to the Guideline, the ccNSO will consider a Rejection Action Petition from the following constituents: * ccTLD managers, * Individual(s) directly related to a ccTLD manager, * ccNSO working groups or committees mandated to submit such a pe//on, * Regional ccTLD organisations (as defined in sec/on 10.5 of the ICANN Bylaws), * the ccNSO Council. The deadline for submission of Rejection Action Petition(s) to the ccNSO role account (ccnso-petions(a)icann.org) by 1 June 2021 at 23:59 UTC. All relevant information will be published at: https://community.icann.org/x/8tDRAw Kind Regards, On behalf of Nick Wenban-Smith, ccNSO Rejection Action Process Manager, Bart Boswinkel, ccNSO Secretariat

1 0

Fwd: [ECAdmin] Secretary's Notice
by Alejandra Reynoso May 21, 2021

May 21, 2021

Dear Councillors I received the Secretary’s Notice to Empowered Community of Board Approval of FY22-26 Five Year Operating and Financial Plan. You can find it in the following attachment. Nick, as our Rejection Action Process Manager, will notify the ccTLD community shortly. 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 ---------- Forwarded message --------- From: Peg Rettino via ECAdmin <ecadmin(a)icann.org> Date: Fri, May 21, 2021 at 10:43 AM Subject: [ECAdmin] Secretary's Notice To: ecadmin(a)icann.org <ecadmin(a)icann.org> Cc: maarten.botterman(a)board.icann.org <maarten.botterman(a)board.icann.org>, Goran Marby <goran.marby(a)icann.org> Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of FY22-26 Five Year Operating and Financial Plan sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org Slack: peg.rettino Direct: 310-301-3868 _______________________________________________ ECAdmin mailing list ECAdmin(a)icann.org https://mm.icann.org/mailman/listinfo/ecadmin _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Fwd: [ECAdmin] Secretary's Notice
by Alejandra Reynoso May 21, 2021

May 21, 2021

Dear Councillors I received the Secretary’s Notice to Empowered Community of Board Approval of FY22 Operating Plan and Budget. You can find it in the following attachment. Nick, as our Rejection Action Process Manager, will notify the ccTLD community shortly. 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 ---------- Forwarded message --------- From: Peg Rettino via ECAdmin <ecadmin(a)icann.org> Date: Fri, May 21, 2021 at 10:42 AM Subject: [ECAdmin] Secretary's Notice To: ecadmin(a)icann.org <ecadmin(a)icann.org> Cc: maarten.botterman(a)board.icann.org <maarten.botterman(a)board.icann.org>, Goran Marby <goran.marby(a)icann.org> Greetings, Attached please find the Secretary’s Notice to Empowered Community of Board Approval of FY22 Operating Plan and Budget sent on behalf of John Jeffrey. Best, Peg -- Peg Rettino Project Specialist & Executive Assistant to John Jeffrey General Counsel and Secretary ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 peg.rettino(a)icann.org Slack: peg.rettino Direct: 310-301-3868 _______________________________________________ ECAdmin mailing list ECAdmin(a)icann.org https://mm.icann.org/mailman/listinfo/ecadmin _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Alejandra's question during today's tele-conference regarding the supplemental funding request submitted by the Technical Information Gathering/Sharing Working Group
by Stephen Deerhake ＠ ASNIC May 21, 2021

May 21, 2021

Greetings, Subsequent to the question raised by Alejandra’s question presented to me during today’s tele-conference, I have researched and answered her question, as I promised I would on the call. Please see the attached for the specifics. Please do not hesitate to reach out to me with any questions you might have. Have a great weekend! Best Regards, /Stephen

2 1

DEADLINE EXTENDED | Call for Expressions of Interest: Customer Standing Committee (CSC)
by Joke Braeken May 21, 2021

May 21, 2021

Dear All, The deadline for the expression of interest for one member of the Customer Standing Committee has been extended. New Deadline: 4 June 2021 (23:59 UTC). Further details about the call for expressions of interest and the CSC in general are included below. Apply here: https://forms.gle/tS9FWEi3z84uAf2j8 Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org 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: Thursday, 20 May 2021 at 13:44 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] FINAL REMINDER | Call for Expressions of Interest: Customer Standing Committee (CSC) Dear All, This is a final reminder. The Customer Standing Committee (CSC) has been established to ensure the satisfactory performance of the Internet Assigned Numbers Authority (IANA) naming function. In April 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. The ccNSO is now seeking a candidate from either the African, Asia-Pacific, Latin American And Carribean or North African region, who wishes to become a member of the Customer Standing Committee (CSC) for the remainder of Alejandra’s term (ending 30 September 2021 at 23.59 UTC). For an overview of the current members and liaisons, go to https://www.icann.org/en/csc/members-liaisons How to apply If you are interested, please submit by Friday, 21 May 2021 (23:59 UTC): 1. An Expression of Interest (application form: https://forms.gle/tS9FWEi3z84uAf2j8 ) 2. Your resume, curriculum vitae, or biography and 3. A letter of support from your employer, if applicable, with respect to the required time commitment to participate actively in the CSC The application form is located on https://forms.gle/tS9FWEi3z84uAf2j8 [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/tS9FWEi3z84uAf2j8__;!!PtGJab4!…> . Please complete by Friday, 21 May 2021 (23:59 UTC). Materials listed under 2 and 3 should be sent to Joke Braeken (joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> ), by Friday, 21 May 2021 (23:59 UTC). By submitting your personal data, you agree that your personal data will be processed in accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy)and agree to abide by the website Terms of Service (https://www.icann.org/privacy/tos) Candidate Qualification Requirements The Customer Standing Committee (CSC) is comprised of representatives with direct experience and knowledge of IANA naming functions. Please refer to the CSC Candidates Qualification Requirements<https://www.icann.org/en/system/files/files/csc-skill-set-matrix-members-li…> for details about candidate selection or the CSC Charter<https://www.icann.org/en/system/files/files/csc-charter-amended-27jun18-en.…> for the full text of the CSC scope and responsibilities. About the Customer Standing Committee (CSC) The CSC ensures the satisfactory performance of the Internet Assigned Numbers Authority (IANA) naming function. The CSC is responsible for monitoring Public Technical Identifier’s (PTI) performance of the IANA naming function against the service level expectations in the IANA Naming Function Contract. The CSC analyzes performance reports provided by PTI and publishes its findings. The CSC is authorized to undertake remedial action to address poor performance of the IANA naming function, and if performance issues are not remedied, may escalate the issues to the ccNSO and GNSO. Follow the CSC discussions at http://mm.icann.org/pipermail/icann-csc<https://mm.icann.org/pipermail/icann-csc>. The CSC can be contacted at icann-csc(a)icann.org<mailto:icann-csc@icann.org>. If you'd like to be informed of upcoming meetings, receive CSC reports, etc., you may subscribe at https://mm.icann.org/mailman/listinfo/csc-announce Wiki Space: https://community.icann.org/x/rKbRAw Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

Extension can for Expression of Interest to apply for member CSC
by Bart Boswinkel May 21, 2021

May 21, 2021

Dear all, On behalf of the Chair of the ccNSO Council, I want to inform you that today 21 May 2021, the call for Expression of Interest as members of the CSC (Alejandra’s replacement) will close at 23.59 UTC . To date (a few hours before closing of the Call for Expression of Interest) no expressions have been received. After informing the Council yesterday and in accordance with section 9.2 of the Guideline: ccNSO Appointment Procedures (version 1, 25 March 2021), the Alejandra as Chair of the ccNSO Council decided to extend the Call for Expression of Interest with 2 weeks until: 4 June 2021, 23.59 UTC. Kind regards, Bart Section 9.2 of the Guideline: ccNSO Appointment Procedures (version 1, 25 March 2021) reads: 9.2 Omission in or Unreasonable Impact of the procedure In the event the Procedure does not provide guidance and/or the impact is unreasonable to conduct the business of the ccNSO, the ccNSO Council or the Chair of the ccNSO Council will decide.

1 0

Draft resolution: launch call for volunteers to appoint one (1) ccTLD-related delegate to the 2022 Nominating Committee
by Joke Braeken May 21, 2021

May 21, 2021

Dear Councillors, Please find included below and enclosed a request from ICANN org to appoint a ccNSO delegate to the 2022 Nominating Committee. If you have any questions or comments regarding the draft resolution below, please send an email to the ccNSO Council mailing list by Tuesday, 25 May 2021 (23:59 UTC).Unless there are concerns or objections by the aforementioned deadline, the resolution included below is considered to be accepted. Draft Resolution Background Following the request by ICANN org for the ccNSO to appoint one (1) ccTLD-related delegate to the 2022 Nominating Committee, the ccNSO Council launches a call for volunteers, according to the timeline below. * Start call for nominations: Wed, 26 May 2021 * Close call for nominations: Monday, 8 June 2021 (23:59 UTC) * Start Selection process (The ccNSO Council evaluates the application of all the candidates according to the applicable Selection Criteria as set in the call for expression of Interest.): Tuesday, 9 June * Close Selection Process: Tuesday, 15 June 2021 (23:59 UTC) Latest by 18 June 2021 (23:59 UTC), the ccNSO Council chair with the assistance of the ccNSO Secretariat will inform NomCom Operations Staff about the name of the ccNSO appointed delegate to the 2020 NomCom. Decision The ccNSO Council seeks one (1) volunteer, associated to a ccTLD Manager, to fill the position on the 2022 ICANN Nominating Committee as ccNSO appointed delegate. The ccNSO Council requests the Secretariat to launch a call for volunteers as soon as feasible. The call for expressions of interest as well as the selection process and all other related aspects should be in accordance with the Guideline: ccNSO Appointment Procedures<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…> and should meet the deadline and at least the criteria as outlined by the Nominating Committee of ICANN. Kind regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of ccnso-council <ccnso-council(a)icann.org> Reply to: Alejandra Reynoso <alejandra.reynoso(a)cctld.gt> Date: Thursday, 20 May 2021 at 15:22 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Fwd: PLEASE READ: Delegate to join the 2022 Nominating Committee Dear Councillors We have received the following request for the ccNSO to select a delegate to join the 2022 Nominating Committee. Best regards, Alejandra -- [Image removed by sender. Photograph] Alejandra Reynoso Investigación & Desarrollo | Dominios .gt P: +502 23688565 E: alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt> 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt [gt]<https://urldefense.com/v3/__http:/www.gt/__;!!PtGJab4!p6zJcL2ELK0PzNfDhjKpk…> ---------- Forwarded message --------- From: NomCom Operations Team <nomcom-ops-team(a)icann.org<mailto:nomcom-ops-team@icann.org>> Date: Wed, May 19, 2021 at 3:47 PM Subject: PLEASE READ: Delegate to join the 2022 Nominating Committee To: alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt> <alejandra.reynoso(a)cctld.gt<mailto:alejandra.reynoso@cctld.gt>> Cc: Teresa Elias <teresa.elias(a)icann.org<mailto:teresa.elias@icann.org>>, Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Dear Alejandra, This email is a request for the Country Code Names Supporting Organization(ccNSO) to select a delegate to join the 2022 Nominating Committee. Specific criteria and requirements regarding the NomCom composition and NomCom delegates are outlined in the ICANN Bylaws in Article 8, Sections 8.2 and 8.4 (https://www.icann.org/resources/pages/governance/bylaws-en/#article8) Attached is the job description for NomCom delegates. Additionally, please note the following as you select and appoint your delegate to the 2022 NomCom: * The ICANN community is diverse and the composition of the NomCom should reflect this in order to fulfill its mission. * NomCom delegates should have a high-level network of contacts essential to candidate recruitment. * Eligibility Exception - Current ICANN employees or paid ICANN consultants (including Ombudsman) are excluded from consideration for eligibility as described in Article 8, Section 8.2 of ICANN’s Bylaws (https://www.icann.org/resources/pages/governance/bylaws-en/#article8) * The delegate should be able to join monthly teleconferences. Note that the NomCom's workload will increase significantly during the candidate assessment process. Conference calls are held more frequently during this time as well (typically weekly and the duration of the calls may last up to three hours). * All NomCom delegates should have the ability travel to and participate in ICANN Public meetings and NomCom meetings when requested (travel and hotel accommodations will be provided for all meetings). If travel is restricted, then NomCom delegates will meet virtually. The NomCom has a procedures<https://www.icann.org/resources/pages/nomcom2021-operating-procedures-2021-…> document that provides additional information about the work of the NomCom. The 2022 NomCom will be selecting people to fill the following positions: * Three members of the ICANN Board of Directors. * One member of the PTI Board of Directors. * Two regional representatives to the At-Large Advisory Committee (ALAC) – one from the European region and one from the North American region. * One member of the Generic Names Supporting Organization (GNSO) Council. * One member of the Country Code Names Supporting Organization (ccNSO) Council. We would appreciate that you acknowledge receipt of this message, and please send the name of the Country Code Names Supporting Organization(ccNSO) delegate no later than Friday, 18 June 2021 to NomCom Operations Staff at nomcom-ops-team(a)icann.org<mailto:nomcom-ops-team@icann.org>. Please reach out to us if you have any questions. Sincerely, Nominating Committee Operations Team cc: bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>

1 0

NOTES ccNSO COUNCIL 173 | 20 May 2021 (18.00 UTC)
by Joke Braeken May 20, 2021

May 20, 2021

Hello everyone, Please find included below some notes from today’s ccNSO Council meeting. Best regards, Joke 1. Welcome and roll call Welcome by Chair Alejandra Reynoso. Reminder to add “ccNSO Council” to your name in the zoom room. Wiki with documents for the call: https://community.icann.org/display/ccNSOCWS/20+May+2021+%7C+18%3A00+UTC We are quorate. Laura sent her apologies. Nick might join a bit later. 2. Minutes & Action Items All action items completed. Minutes of the previous meeting have been circulated. CSC: no applications received to date. 3. Intermeeting Decisions (since 22 April 2021) All completed 4. ccPDP3 a. Part 1 Retirement – Update Presentation by Alejandra. Final phase of ccPDP3 on retirement Important milestone. No decisions to date, but a heads up on the things to do next: 1. Formally separate part 1 from part 2. Council online voting. (28 May - 4 June). This decision does not require a vote by the ccNSO members. Explicit vote, since we do this for the first time. Agree, Abstain, Object. Response via email. 7 days to allow ccnso members to veto the decision. 2. Recommendation on proposed policy (part 1) Members report circulated to Council. Decision at icann71. We need consensus. (14 in favour) 3. Approve members report Timeline was circulated with the agenda. Aim: start the members vote on 6 July until 27 July. if we do not meet the 50% threshold, 30 days for the next round. Proposal: start in September. Stephen: in favour of this timeline. Available to answer questions. To do: * Start email decision on 28 may * Councillors to start engaging the community regarding the upcoming members vote. Task for all to be aware of the upcoming vote Bart: why separation? Document has been circulated on the mailing list. It includes an executive summary. Also includes a rationale for the proposed decision. Include a bit on the impact of the decision, explaining why it is not part of the PDP itself. Hence no members vote. Background of the decision making, and the relevant section from the issue report in the annexes. Council decision on combining part 1 and part 2. Will be re-circulated tomorrow. The call for your decision will include the executive summary. Bart: Final Report This was a deliberate draft. Why circulated? It provides the background. Will be recirculated after the separation decision has been made. This allows you to prepare for the deliberations and final recommendation in June. The final report: the policy itself is included in attachment A. Section 1 to 5 is the process as proposed by the WG, which went through 2 consecutive consultation rounds. Other sections around the stress test, responses to public comment. Also a glossary included. b. Part 2 Review Mechanism – Update Group met yesterday. Robust discussion on how binding the review mechanism could be. IRP is laborious, expensive, and time-consuming. Not trying to repeat that. Another consultation with ICANN legal to be expected a couple of meetings after ICANN71. An informational policy session will be held during ICANN71, together with ccPDP4. Alejandra: do councillors have a role in that policy session? Stephen: informational session. Staff will work on a slide set. Jordan: how binding this review mechanism is. What is meant here? Stephen: conflict between ccTLD community’s wishes, and others. Binding for IFO and ICANN Board, vs their fiduciary responsibilities. The board and IANA and the contractual relation between the 2. Bart: discussion IRP in WS1. Result of the discussion between the law firms engaged by the WG and ICANN legal and their lawyers. ICANN legal mentioned that fiduciary duties would prevent an external decision to be binding, which is as important as for instance a delegation. Jordan: this sets off alarms 5. IDN ccPDP4: Update Written update by Ai-Chin shared on the mailing list Alejandra: What is happening at the policy session? Bart: group has agreement on the processes and procedures and main criteria. At ICANN71, during the policy session, 45 min will be dedicated to this group. The ccPDP4 WG seeks the feedback and comments from the participants during the session. Intention is to share the principles with the audience, and check whether they agree. 6. Initial discussion workplan ccNSO, changing role of Triage Committee Presentation by Alejandra. Purpose and value of the ccNSO Triage and OISC provide a balance between what needs to be done. Help to Council. Proposal for GRC to be more involved in the continuous organisational improvement. a. Baseline overview work items May 2021- May 2023 b. Updating the work plan – changing role of Triage Committee Bart prepared a GANTT chart. There are some areas which come naturally: role of the ccNSO as decisional participant and supporting organisation. This type of overview provides the broader community, triage committee, and council, to look at progress made against the plan. Check if there are issues, and monitor what is happening. Informing the community about potential delays for instance. Work items which are currently in the pipeline. What you can anticipate in the next 2 years. There is a clear need to start managing work items and to see what should be included. If necessary, start prioritising work items. Not spend too much time on trivial matters. Work plan will be on the agenda for the next council meeting. Councillors invited to carefully read, to be ready for the adoption at the next meeting. c. Quarterly reporting on progress completion work items Jordan: proposing priorities. Triage Committee to have a meeting each quarter. See after a year, if that is the right frequency. Establish the priorities at the start of the year. New work for the triage committee. At the next meeting there will be more info available. 7. Council Election 2021 This is a heads up. Proposed timeline being displayed. No action needed right now. Biyi, Jordan, Nick, Demi and Pablo’s current term ends at the conclusion of the March 2022 meeting. Timeline to be adopted latest by the July Council meeting. 8. ICANN71 Planning a. ccTLD Managers related events i. ccTLD news sessions ii. Newcomer’s session iii. Tech Day iv. Members meeting All are invited to promote the upcoming ccTLD News Session. May edition of the Newsletter: https://conta.cc/3f1YzPb or on the workspace Links to bookmark now: ccNSO Schedule & Remote Participation Hub https://community.icann.org/x/WIG1CQ ccNSO Members Meeting, including sessions held prior to ICANN71, including the ccTLD News Session and the upcoming ccNSO newcomer webinar. https://community.icann.org/x/UYG1CQ Tech Day https://community.icann.org/x/a4G1CQ b. Council related meetings i. Wednesday, 9 June | 18:00 UTC (Council prep call for ICANN71) ii. Thursday, 10 June | 20:00 UTC (joint gNSO & ccNSO Councils) Joint meeting ccNSO & GNSO Councils: Maarten: Topics from last meeting: no relevant progress compared to the previous meeting. No new topics of interest either. Suggestion or proposal to skip the ICANN71 session, and to meet at ICANN72 instead. Alejandra: do councilors have any topics as a suggestion? We can indeed defer to the next meeting, if none, but i have one suggestion (see CSC update later today) ICANN71 public schedule: https://71.schedule.icann.org/ Block schedule shared in the zoom room and in the May edition of the Newsletter: https://conta.cc/3f1YzPb @ Maarten and Sebastien: The GNSO and ccNSO need to agree on CSC effectiveness Review. Starting 1 october 9. Update ECA & CSC a. ECA (Informational) Tomorrow a meeting to prepare the process in case of rejection action petition. Stephen: formal notification regarding board’s notification of the adoption of the 2 items on the ECa mailing list. Surprised you did not get a notification b. CSC (Informational) There is a call for EoI for a replacement for Alejandra on CSC. but there is also an annual selection, for term start in october. Hopefully the person that replaces Alejandra intends to stay onboard. Full slate needs to be approved by ccNSO and GNSO Councils. Candidate should not be from Europe, to meet the diversity requirements. 1 meeting per month. 30 min prep, max 45 min meeting per month. Limited time commitment. Monitoring the performance of the IANA naming services. Read more here about the CSC expressions of Interest: https://ccnso.icann.org/en/announcements/announcement-07may21-en.htm 10. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat None 11. Update WGs Written updates posted on the wiki for this meeting https://community.icann.org/display/ccNSOCWS/20+May+2021+%7C+18%3A00+UTC Please have a look at the forward by Alejandra, regarding a suggestion by the GRC. Alejandra suggests OISC to have a look. Response preferably latest by the July meeting. Sean on a transition period, to take over Katrina’s role as chair on the GRC. had conversations with various people. Scope of the GRC is different. Next GRC meeting, adjusted scope. Proposal to be presented for the council soon. Triage committee is visioning. The GRC is policy, the OISC is having a communications role. Find a way for these groups to work fluently together. OISC met earlier today. Continued exercise on the scope of the OISC. which activities? Ongoing effort. 45 items to be discussed, hopefully to conclude this process by next meeting. Pablo referred to 5 action items from today’s meeting. See tracker and agenda for today’s OISC meeting here: https://community.icann.org/display/ccnsowkspc/20+May+2021+%7C+16+UTC Alejandra: what about the Additional budget request from the Technical WG? ccNSO Request: https://community.icann.org/display/projfinadhocws/ccNSO+-+FY22+Additional+… Stephen: will look it up. Alejandra: did they consult with anyone? Stephen; wish to get outside of the ccNSO silo, and have a more cross-community nature. Stephen: will send info to the mailing list Alejandra: request was denied. Tech Day goes beyond the ccNSO in terms of audience, but the group is a ccNSO WG. anything which is WG-related is part of the ccNSO. The Tech WG is not a group that can make these requests, but the ccNSO does. Was tagged as a ccNSO request therefor by the Board The charter does not allow or give the TEch WG this authority to ask for a budget. Also, the charter is very outdated. Kindly ask the Tech WG to review the charter, and to send the council and updated version. Stephen: i did not know about this. Will talk to Eberhard and David Conrad and will respond back to the council mailing list. a. SOPC b. IGLC c. GRC d. OISC e. TLD-OPS f. Technical WG g. MPC Ali: not sure if my written update arrived on the council mailing list, therefore oral update today. No recent meetings for the TLD-OPS Committee. Email exchange with the TLD OPS and the leadership team. Last meeting was in December 2020. To make sure the actions of TLD-OPS are followed up. 22 responses were received. That is not much. Invite the ccnso council to invite the ccTLD community to respond. TLD OPS will share the link to the TLD OPS engagement form. 12. Update liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update to follow) 13. Meetings Next Council Meetings: Wednesday, 9 June | 18:00 UTC (Council prep call for ICANN71) Thursday, 10 June | 20:00 UTC (joint gNSO & ccNSO Councils) TBC Thursday, 17 June | 12:30 UTC (Council meeting at ICANN71) July 22 -12:00 UTC September 16 – 20:00 UTC October @ ICANN72 (23-28 October) November 18 – 12:00 UTC December 17 – 18:00 UTC ● 14. AOB Irina : quick question to other councillors. Invite from Sebastien Bacholet to attend an EURALO event. Short update about the ccNSO and its role. 3 min update. Include a call for action for at large audience. Any suggestions? Will follow up on the mailing list Ali: the Africa Engagement Forum took place today. Good opportunity to share updates from the ccNSO. Thanks to the secretariat to help prepare the update. Stephen: proposed Jordan to make him an observer to the ccPDP3-RM Jordan accepted. Alejandra: we receive a letter from Avri Doria regarding the second ccNSO organisational review. Dashboard of the recommendations and their implementation has been updated. DASHBOARD - Implementation ccNSO review & WS2 Recommendations https://community.icann.org/pages/viewpage.action?pageId=164628289 Alejandra: we received a request from NomCom to appoint a delegate. Online decision to launch a call for volunteers. 15. Closure Thank you all for today. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

Thursday, 20 May 2021
by ICANN Community Leadership Digest May 20, 2021

May 20, 2021

Thursday, 20 May 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: ICANN71 Prep Week Schedule Now Available TRANSLATION DEADLINE TOMORROW: ICANN71 Publication Support DEADLINE TOMORROW: Participate in "ICANN Community Groups: An Introduction for Newcomers" REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment CLOSES TOMORROW: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration Maximal Starting Repertoire Version 5 (MSR-5) NEW: Draft North America Engagement Plan FY21-25 Information Sharing NEW: ICANN71 Prep Week Schedule Now Available ICANN announced the ICANN71 Prep Week schedule of ten sessions to prepare the ICANN community for the ICANN71 Virtual Policy Forum taking place 14-17 June. ICANN71 Prep Week will be 1-3 June. Read more. TRANSLATION DEADLINE TOMORROW: ICANN71 Publication Support Translation-only Deadline For translation of a publication for ICANN71, please provide the final material(s) by Friday, 21 May 2021. This ensures that there is enough time to translate the publication. If the publication requires design assistance, please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Please work directly with your support team to submit these requests to evin.erdogdu(a)icann.org and liana.teo(a)icann.org. DEADLINE ON MONDAY: Participate in "ICANN Community Groups: An Introduction for Newcomers" The Public Responsibility Support team seeks speakers from ICANN communities to participate in an introductory session for newcomers. Each speaker will have five minutes to provide an overview of their ICANN community group. The session will take place Wednesday, 2 June 2021, 13:00-14:30 UTC. Sign up by Monday, 24 May 2021. Please contact deborah.escalera(a)icann.org with any questions. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN71, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 28 May 2021 at 23:59 UTC. The goal of this program is to facilitate participation in ICANN Public Meetings during this pandemic. It offers ICANN community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Public Comment CLOSES TOMORROW: GNSO Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Phase 1 Final Recommendations for ICANN Board Consideration Close Date: Friday, 21 May 2021 GNSO New gTLD Subsequent Procedures Final Outputs for ICANN Board Consideration Close Date: Tuesday, 1 June 2021 Maximal Starting Repertoire Version 5 (MSR-5) Close Date: Tuesday, 8 June 2021 NEW: Draft North America Engagement Plan FY21-25 Close Date: Friday, 2 July 2021 Volume 3, Issue 38 | Archive | Next Issue: Monday, 24 May 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

Re: [ccnso-council] Draft Agenda meeting 173, 20 May 2021, 20.00 UTC
by Joke Braeken May 20, 2021

May 20, 2021

Hello everyone. Notes during today’s ccNSO Council meeting will be taken here: https://docs.google.com/document/d/14e6_MdNPRdQYhYLGbr4ymM1UKLCngp2nhB3ANRU… Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of ccnso-council <ccNSO-Council(a)icann.org> Reply to: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Thursday, 13 May 2021 at 10:48 To: ccnso-council <ccNSO-Council(a)icann.org> Subject: [ccnso-council] Draft Agenda meeting 173, 20 May 2021, 20.00 UTC Dear all, Please find included the draft agenda for the upcoming Council meeting. Background material will follow. Kind regards, Bart Draft Agenda ccNSO Council Meeting 173 20 May 2021 18.00 UTC 1. Welcome and roll call 1. Minutes & Action Items * Minutes Meeting 172, circulated 10 May 2021 * Action items and To-do’s, if any 172-01: The Secretariat is requested to inform the OISC membership and list Pablo as such on the OISC webpage accordingly. Completed 172-02: - Chair to send letter to relevant executive staff regarding translation of ccNSO Course on ICANN Learn Completed - Secretariat to update the ccNSO Review Recommendation Dashboard accordingly. Completed 172-03: Chair to inform ICANN Secretary and ECA of appointment Alejandra Reynoso to ECA. Completed 172-04: Launch call for Expression of Interest CSC for duration of term Alejandra Reynoso. Completed 1. Intermeeting Decisions (since 22 April 2021) * Appointment Ellen Strickland (.nz) as member of IGLC * Term of Appointment for the initially appointed OISC members. * Adoption Roles and Responsibilities of Council * Adoption of recommendations to enhance and improve effectiveness and efficiency of the ccNSO Council 1. ccPDP 3 * Part 1 Retirement – Update Informational & Next Steps Anticipated timeline 1. Final Report, Issue Manager, 18 May 2021 to be submitted to the Council and published on website 2. Chair actions upon receipt of report: a. Circulate report to Council b. Call for Council meeting working towards recommendation to the Board c. Ask GAC opinion or advise 3. Proposed date Council discussion and vote 17 June 2021 4. Compile Members report (Final Report + minutes of the meeting + recommendation of the Council to the Board) 5. 1st round of Members vote start 6 July 2021(21 days) and closing on 27 July 2021 6. 2nd round of Members Vote to start 3 September (at least 30 days between 1st and 2nd round of voting. If 1st round is not quorate – at least 50 % of membership). 2nd round closes 24 September 2021. 7. Upon adoption by Members (after 1sr or 2nd round of voting)prepare Board Report to be approved by Council. 8. Submission of Board Report to ICANN Board of Directors * Part 2 Review Mechanism –Update Informational 1. IDN ccPDP4: Update Informational For discussion 1. Initial discussion workplan ccNSO, changing role of Triage Committee Informational & for discussion * Baseline overview work items May 2021- May 2023 * Updating the work plan – changing role of Triage Committee * Quarterly reporting on progress completion work items 1. Council Election 2021 Informational Initial timeline and required actions 1. ICANN71 Planning * ccTLD Managers related events i. ccTLD news sessions ii. Newcomer’s session iii. Tech Day iv. Members meeting * Council related meetings i. Wednesday, 9 June | 18:00 UTC (Council prep call for ICANN71) ii. Thursday, 10 June | 20:00 UTC (joint gNSO & ccNSO Councils) 1. Update ECA & CSC * ECA (Informational) * CSC (Informational) 1. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 1. Update WGs * SOPC * IGLC * GRC * OISC * TLD-OPS * Technical WG * MPC 1. Update liaisons * Update ALAC Liaison (written update) * Update GNSO Liaison (written update to follow) 1. Meetings * Next Council Meetings: * Wednesday, 9 June | 18:00 UTC (Council prep call for ICANN71) * Thursday, 10 June | 20:00 UTC (joint gNSO & ccNSO Councils) * Thursday, 17 June | 12:30 UTC (Council meeting at ICANN71) ● May 20 – 18:00 UTC 1. AOB 1. Closure

1 0