Sunday, 12 March 2019 | 12:15-13:30
Action item #1:
Council members are invited to email to the council mailing list possible answers to the Board’s questions
Action item #2:
Future Council workshops
Should we have another workshop at ICANN65?
Pablo and Giovanni agree. Specially to address the fears and hopes.
Target: come up with solutions for the issues identified.
ccNSO Council meeting at ICANN64
The Wednesday council meeting on Wednesday will be in room Emerald, starting at 17 pm
Council elections at the very end of the meeting. Katrina will step down, Debbie will take over. There will be a call for nominations. Secret vote if there are 2 or more candidates. Otherwise there will be
a regular vote (abstentions, objections)
Annual workplan: pdp timeline adjustment for the april agenda
Board questions
Giovanni: Is there consistency in what has been done for the past 5 years? That is crucial in a long-term partnership.
Are we talking about ICANN, ICANNorg, the Board? What is meant by the 2nd question?
Peter suggests having a look at what Fadi did, informing icann the community regarding the action items to follow to achieve the goals.
Katrina: Risks from outside that could impact icann and how to remediate them?
Jordan: stay clear from UN
Giovanni: we should be consistent
Young-eum: inform community what is going on. E.g. ITU. The community itself is working.
Peter: is law enforcement part of this community, or rather external?
Katrina: Icann community being on the same page with partners, if even within icann we are not on the same page? Let’s ask them for clarification.
Byron: comment period is still open for a few weeks. Their published plan = THE plan. That is how it is being presented.
Peter: ICANN can go out and talk about the icann model. However, representing the community’s interest in for instance the GDPR discussions in Brussels is not appropriate.
Stephen: would it be appropriate for us to reach to our 2 board reps what these questions mean. Katrina: it is too late for that. We should have done our homework earlier.
Jordan: the Board should focus on the strategic goals and not on other distractions
Strategic plan implementation. Previously SOPC was told that the goals were set and could not be changed during the 5-year term. With all the knowledge they should have, they should be able to anticipate
certain industry developments (e.g. market saturation) Goals and targets to be flexible
Action item #1:
Council members are invited to email to the council mailing list possible answers to the Board’s questions
Joint meeting with GAC
Peter Vergote is an outgoing councilor. He was liaising with the GAC regarding the agenda setting for our joint meetings. Somebody needs to be replace him. Councillors are invited to volunteer, if interested
Scheduling joint meetings between ccNSO & GAC: GAC meets with SO/ACs on Sunday here at icann64. For us they made an exception, to have the meeting during the members meeting
Action item #2:
Fundamental bylaw changes
Chris asked ICANN legal how to make those changes (changes related to IFRT, definition of ccTLDs)
Fundamental bylaw changes will require an approval action. ccNSO needs to seek support. We need to write to ICANN Board, they send it to ICANN org, legal needs to propose the wording. A public comment process
is needed. The whole process might take 6 to 9 months, at least 4 months. Other SO/ACs also need changes to the bylaws. Idea was to bundle them
Action item #3:
Let others know if something comes up that needs to be addressed during the ccNSO council meeting on Wednesday
GAC decommissioned its independent secretariat
Increasing need for policy support.
We rely on volunteers when it comes to WT5. Since CENTR stopped following the GNSO tracks.
Volunteer fatigue
Peter Van Roste asks to look into an independent policy secretariat. GAC members and ccTLDs wish to contribute to that solution.
Joke Braeken
ccNSO Policy Advisor
Follow @ccNSO on Twitter: https://twitter.com/ccNSO
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/