Dear all,
Please find included, version 2 of the agenda for upcoming Thursday.
Changes are:
Finally, One resolution on adoption of the Guideline is included,
Kind regards,
Bart
Draft Agenda ccNSO Council Meeting
17 October 2019
12.00 UTC
Minutes
Minutes of the September 2019 meeting have been circulated on [to be inserted].
Action items
Action Item 155-01:
Council to prepare a formal notification from the ccNSO, approved by the ccNSO Council, showing support for recent Bylaw change.
Related, Circulate part of the Bylaws referencing the Community Action Forum (whether or not its optional). Completed
Included in background material item 6 Agenda
Action Item 155-02:
The Secretariat to inform relevant staff of ICANN Org and the ccNSO appointed IFRT members of the appointment of Frederico Neves as co-chair. Completed
Action Item 155-03:
Chair to inform the ICANN Board of Directors accordingly in response to ICANN Board resolutions ICANN Board resolutions 2017.11.02.10 and 2017.11.02.11.
To-do: Secretariat to compile list of actionable recommendations from the Emoji study draft report – for circulation and consideration. Draft completed
Action Item 155-04:
Recommendation for the Review Working Party to review the template and recommendations and come up with a final assessment and implementation plan.
Completed RWP to meet 16 October to discuss recommendations.
Action Item 155-05:
Council to comment on the Montreal workshop Google Doc. Completed see agenda item 10.
For information
For Decision
In March 2019, Councillors were requested to provide feed-back and input on latest version (version 3) of the Guideline: ccNSO Approval Action Process. No additional comments were received. The Guideline is now submitted for adoption by Council.
Draft Resolution
Background
The Guideline: ccNSO Procedure for the Exercise of the Empowered Community’s Rights to Approve Specified Actions was submitted by the GRC to the Council in February 2019 to seek their comments and input. No comments were received.
Decision
The ccNSO Council adopts the The Guideline: ccNSO Procedure for the Exercise of the Empowered Community’s Rights to Approve Specified Actions version 9, as submitted for this Council meeting. The Guideline will become effective 7 days after publication on the ccNSO Website. For avoidance of doubt, the Guideline, once effective shall not apply to the currently running Approval Action Procedure to amend section 18.7 of the ICANN Bylaws.
For information & discussion: Timing of Council decision, Draft Council statement supporting change of Fundamental Bylaw ( Section 18. 7 ICANN Bylaws)
For discussion
Background material: Note on: Bylaw requirements on need for Approval Action Community Forum, Timing of approval decision and proposed text Resolution
Background: The ccNSO CSC Selection Process Committee has confirmed Alejandra Reynoso (.gt) as selected by the ccNSO Councillors eligible to vote and approved the full slate of the CSC membership.
The GNSO Council has approved the full slate on 14 October 2019.
Update & Closure
Informational
8 a. Update Board Selection Procedure Board Seat 11
8 b. Update Council Election Procedure
Informational
See Google doc: https://docs.google.com/document/d/1uFr2vNhzUowueD2kAp_YSrCoyIwy0aoZ/edit [docs.google.com]
For decision
1. Finalisation of topics Council Workshop and
For discussion
2. Agree on working method and teams to prepare and facilitate the topics.
i. Prep meeting
ii. Council meeting
iii. Joint meeting with GNSO Council ( Monday 4 November 2019, lunch)
Topics:
iv. Joint meeting with ALAC
i. Tentative agenda members meeting
ii. Plenary topics
Topics for discussion as submitted by the ccNSO:
Question 1
The ccNSO and GNSO Councils are working together to define a procedure for launching a Specific IANA Function Review (SIFR) after the Customer Standing Committee (CSC) has determined that a persistent and systemic PTI performance Issue exists and all three escalation steps - including the escalation to the ICANN Board - have failed to correct the issue (for more information see CSC Remedial Actions Procedures or RAP). When looking at the overall processes from RAP to SFIR to Separation process, the ccNSO Council notices that the timelines to deal with the unlikely - but highly impactful - situations are prohibitive and affecting the stability of the DNS negatively. What is the Board’s procedure to deal with issues raised by the CSC in a timely and efficient manner?
All together we have created procedural monsters which, due to their timelines, unknown and/or non-transparent processes do not allow for quick resolution of serious and potentially damaging issues. An IANA Naming Function service performance issue as described above is a very good example. What activities does the Board plan to make its own processes more efficient? What would the Board suggest to the Community to make sure that we can resolve issues efficiently?
Question 2
We have read with interest the recent blog post from ICANN CEO on the President & CEO’s FY20 priorities. Could the Board clarify how the priorities highlighted in the blog fit into the ICANN approved and published Strategic Plan?
Question 3
What, in the Board's view, is ICANN’s role regarding DNS Abuse? How could the ccNSO support ICANN in the fight against DNS abuse given that ccTLDs’ policy development is outside ICANN’s remit?
If we receive a response to our letter regarding ccNSO PDP 2 by Montreal, then it will be irrelevant but, if not, we would like to ask a quick question: When can the ccNSO expect a response on its 4 September 2019 proposal to end the evolution of the Fast Track Process and mutually agree to close ccNSO PDP 2 (the overall IDN ccTLD policy proposals)?
Once a response / indication of the response is received, the ccNSO Council intends to take further steps: preferably launching ccPDP 4 and requesting a change to Article 10 of the Bylaws to allow IDN ccTLD to become members of the ccNSO.
Topic suggested by the Board
“Community, Board and ICANN org readiness to implement the following three critical plans that will shape ICANN’s future. : (1) Strategic Plan FY 21-25, (2) Operating & Financial Plan FY 21-25, and (3) Work Plan to improve the effectiveness of ICANN’s multistakeholder model.”
The Strategic Plan [icann.org] has been adopted by the Board last June at ICANN 65 in Marrakech. The two other plans will be completed and posted for public comment in December 2019.
At ICANN 64 in Kobe, the Board asked each constituency to provide three suggestions, one for the Board, one for ICANN org and one for the Community of things/aspects that should be done/improved in order to implement these plans successfully, starting 1 July 2020, as mandated by our Bylaws. In addition, the Board asked for one suggestion of something that could be done externally to improve trust and with our partners and alliances (eg. IETF) so that they collaborate effectively with ICANN on some of our strategic objectives (eg. DNS security).
Based on the input received in Kobe, we are compiling a list of suggested actions for the community, Board and ICANN org which we would like to share and discuss with you in Montreal. We will send you that list in advance of our meeting in Montreal on or before 11 October 2019.