NOTES | Council Prep | Tuesday, 1 March 2022 (21 UTC)
Since this is a prep meeting, it will not be recorded.
Green ticks in zoom.
Questions:
When to issue the statement? Asap
Irina: I should refrain from discussing/voting on this I believe
Javier: agrees with neutrality. Is it appropriate to add that this is the official position of Council, and not necessarily the opinion of personal councillors
Alejandra: yes, statement ccNSO, of its Council. Any personal opinions remain personal. Whether it should be added to the statement? Not sure.
Chris: is fine with the statement. Will review the actual text. Understands it needs to be carefully phrased, not to be misinterpreted
Every ccTLD is sovereign. Decisions by ccTLD managers remain their decisions.
Tatiana: agrees with Chris. Important that the statement goes out. Cannot be misinterpreted that certain councillors diminish the human tragedy. It should not
look like we ignore what happens. We do not. We fulfill our function.
Alejandra: understood. We will circulate in a google doc. Please comment. The statement should be sent Friday.
Jordan: difficult issue. This is the right approach for us to take as a group.
Action item:
Secretariat to create google doc. Deadline to comment: Thursday, 3 March (end of day)
Draft fiinal version to be shared with Council for final comments
Alejandra: we could be contacted regarding this and other matters
Please refrain from speaking on behalf of the ccNSO. Before you do that, the matter needs to be discussed with Council.
Bart: reminder about .su
Alejandra: Recent article where the suggestion to remove .su from the zone is raised. individual case. The ccNSO has no opinion on individual cases.
Stephen: spoke with .su representative in Dubai last week. We should stay away from this. Not for us to decide. Maintenance agency ISO
Bart: In case you have not seen this article:
https://domainincite.com/27553-maybe-nows-the-time-for-icann-to-start-dismantling-the-soviet-union
2.
ICANN 73 relevant sessions
ccNSO bilateral meetings:
2.
Joint session: ccNSO and GAC
| 1300-1400 UTC | Block 1
·
PDP updates (ccPDP RM and IDN ccPDP)
·
DNS Abuse
Joint session ccNSO-GAC link to public schedule:
https://73.schedule.icann.org/meetings/RGsyFbNRyJjPpiDNh
Bart shares a high-level overview of the main message that will be conveyed during the joint meeting with the GAC. general progress update about
the ccPDP3 and ccPDP4 progress. Also status update on what ccNSO has been doing in terms of DNS abuse, stressing open communication channels, and invite to those interested to join the ccNSO MM session on DNS Abuse, held after the joint meeting
3.
ccNSO and ccTLD-related/interested ICANN Board
| 1300-1400 UTC | Block 1
a.
What are your key priorities for ICANN work in 2022, how do these priorities help achieve ICANN’s common objectives as expressed in the FY 2021-2025
Strategic Plan, and how do you see Community, Board and org moving forward together on a way to achieve these?
b.
If any, what suggestions would you have to enhance ICANN’s effectiveness and efficiency with regards to the process of implementation after adoption
of a PDP or Review recommendations?
Chris: I have some thoughts on B. Do you want them in writing?
Alejandra: now
Chris: b does not make much sense for the ccNSO. ccNSO input from reviews, some recommendations are not for the Board. Purpose
of reviews? Not binding on ccNSO. Board has a process for refusing. Not getting recommendations that are not actable on. As a review Team, or as a PDP, this is what your recommendations need to be. Recommendations outside of the Board will be ignored. Simple
useful input we could provide.
Stephen: Why is the board surprised our policy recommendations were submitted?
Alejandra: not a surprise
Chris: agrees. The key point is that we will get the standard response. This is all about prioritisation. A useful question would
be: what can we do to help you to speed up the birth of the prioritsation framework, so that the work we dealt with can be treated in an appropriate timeframe
Jordan: process engineering problem. Shortening the cycle. Board needs a lot of time. It is not just a prioritisation thing.
Refers to session 5 years ago about icann prioritization.
Alejandra: suggest to icann meeting committee to do a plenary again on that topic?
Stephen: response time to requests from WGs. WG asked a question 5 months ago. No response yet. If we need ICANN legal’s opinion,
and we do not get it, this blocks the community.
Alejandra: not the first time we have the time issue
We said to Board Ops that we will not have a joint meeting with the full Board, but we will have the Q&A instead. We will address
the questions they directed at all SO/ACs, including to ccNSO.
Chris: yes, will speak to this. Reminder is appreciated.
Kim: will send calendar invites.
Alejandra lists key priorities for the ccNSO.
Bart: council started discussion UASG. Although not applicable to all ccTLDs, it is very relevant for some. We will start to
explore the role of the ccNSO in addition to what is happening locally and regionally.
Irina: does it make sense to mention the exercise regarding our prioritisaiton workshop?
Jordan: yes, thanks. If we mention it. Our ducks in a row to do our own prioritisaiton better, and being clear about the role
of the ccNSO helps us
Bart: make explicit that you consider revisiting the plenary session from 5 years ago, on who sets icann priorities. 5 years
later, what have we learned?
Alejandra: yes, if we plan to do so, good to give a heads up
Should we make those plans more concrete, and plan such a session at ICANN74?
Council agrees
Bart:
https://icann59johannesburg2017.sched.com/event/B3p4/who-sets-icanns-priorities
4.
ccNSO Council Meeting
| 1430-1600 UTC
a.
5 min. NomCom presentation
b.
Leadership election
c.
Roles & responsibilities
d.
Potential approval of ToR for the DASC
e.
Session reports
Stephen: AOB
ccTLD relevant sessions:
2.
ccTLD News #2 – Thu, 3 March 2022 (09:00 UTC)
Topic: & Capacity building efforts by ccTLDs.
Alejandra warmly welcome all Councillors to participate. Useful info if you feedback for MPC. There will be a networking opportunity at the end
of the session
3.
Tech Day – Monday 7 March 2022
Part 1,
Part 2 and
Part 3 | 1300-1400, 1430-1600, 1630-1800 UTC | Blocks 1, 2, 3
>>>> Rapporteur to debrief Council: Stephen Deerhake
Alejandra: they will have a panel on DNS Abuse. That panel would be good to report on
Kim offers to remind Stephen about his role, as per his request
4.
ccNSO Session on DNS Abuse
| 1430-1600 UTC
>>>> Rapporteur to debrief Council: Jordan Carter
Bart: recap of where we are and next steps. To date we have shared the Roadmap doc and the ToR of the DASC. this will be discussed at the meeting.
If the proposals are supported by those who attend, will be on Council agenda for adoption. Small committee that prepared the roadmap will talk about specific aspects of the roadmap. E.g. messaging, creating DASC, metrics, enhanced information sharing.
Seek feedback from the community on the various aspects, and then assess the input for the Council meeting.
Alejandra: will chair the session. Someone who is not involved to report back please
5.
ccNSO Governance Session
| 1630-1800 UTC
a.
Rules of the ccNSO (short intro and heads up about the vote)
b.
Conflict of Interest: 2 presentations, one by Chris and Marika, who have proposals with do’s and don’ts. Sean will share this session. Idea is to start
the conversation. Not the only opportunity for input by the community.
>>>> Rapporteur to debrief Council: Javier Rua
Plenary & other cross-community session(s)
>>>> Rapporteur to debrief Council: Jordan Carter
2.
Plenary session 2: Evolving the DNS Abuse Conversation: Maliciously Registered versus Compromised Domains
>>>> Rapporteur to debrief Council: Irina Danelia
3.
ICANN org: Overview legislative initiatives with potential impact on DNS.
>>>> Rapporteur to debrief Council: Tatiana Tropina
Will report on mailing list, since the session is held after our Council meeting
2:30 AST (UTC-4), 10 March 2022
16:30 UTC, 10 March 2022
3. Roles and Responsibilities
Bart: reminder to nominate a Chair and Vice Chair. Deadline for doing so is Friday, 4 March 2022 (23:59)
a.
Review of sign-up sheet roles and responsibilities: to be adopted at the upcoming Council call
Please fill in column G, by Monday, 7 March latest
Overview roles and responsibilities ccNSO Council
b.
Review of external appointments
For your information
4.
AOB
Sean: dear friend Dotty Sparc-le-Blanc passed away. A memorial moment at Council meeting.
Alejandra: expresses she is sorry for the loss. How should we approach the memorial moment?
Sean: yes, people sharing experiences. Booklet is currently being put together.
Chris: yes, virtually at ICANN73, but also have a function or a celebration when we meet at ICANN74, if we meet in person.
Sean: ccNSO cocktail. good opportunity to share the virgin islands drink with everyone.
Bart: we will touch-base with Sean and Stephen in the course of the week on how to approach this.
Alejandra: let us know if you want to be involved.
Irina: regarding the meeting with the ccTLD-related ICANN Board members. 2 questions they ask us, as the ccNSO. Do we have questions for them too?
Alejandra: yes, collected from mailing list. Prep meeting with Katrina, Patricio and you.
Jordan: Nick suggested some (end January - early February, see council mailing list)
Alejandra: legislative developments in EU and their impact on ccNSO and ICANN
Secretariat to follow up with scheduling a prep meeting, and listing all topics
Javier: Difficult call today. Proud of this group
Alejandra: Thank you all. See you soon
Joke Braeken
joke.braeken@icann.org