NOTES | ccNSO Council Meeting 179 | 27 January 2022, noon UTC

1. Welcome and roll call

https://community.icann.org/display/ccNSOCWS/27+January+2022+-+12%3A00+UTC

Welcome by Chair Alejandra

Slight changes in the order. topic of universal acceptance is less urgent at this stage, if needed, we will defer to the following next meeting

we are quorate, 1 apology from Jennifer.

2. Relevant Correspondence (https://ccnso.icann.org/en/about/statements.htm)

3. Minutes & Action Items

a. Minutes Meeting 178: circulated and published 18 January 2022

b. Action items and To-do’s, if any 

All actions completed. 

Alejandra asked all WG/C chairs to review their charters. 

Tech WG should be included in the package. Hopes to have feedback by the February meeting. 

PDPs do not need to be reviewed: that would require review of the issue report 

4. Intermeeting Decisions (since meeting 178, December 2021) 

only 1. Margarita and Javier appointed to community excellence award panel

Item 5-9 Updates and Q&A

written updates. 

5. Update ECA & CSC(written updates)

6. Update WGs taken (written updates)

a. IGLC

b. SOPC

a. GRC

b. OISC

c. TLD-OPS

d. Technical WG

e. MPC

Triage: see item 13

7. Updates ccPDPs (written updates)

a. Update ccPDP3- Retirement

b. Update ccPDP3 - Review Mechanism

c. Update IDN ccPDP4

8. Update liaisons (written updates)

a. Update ALAC Liaison 

b. Update GNSO Liaison

9. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat

Alejandra: reports on the catch up call with Pablo, Jordan and Goeran Marby. Topics: 

• DNS Abuse
• ccnso website
• developments legal and regulatory global events. see plenary session at icann73
• ICANN74: hope for a hybrid meeting. time will tell
• report on 2021 by Alejandra: fits in WS2 recommendation on accountability. 
• Trend exercise. We have been invited. similar exercises in the past. see doodle poll in your inbox and zoom chat. please respond

Item 10 - 20 for discussion or decision during the meeting

10. Appointment GAC-Liaison.

Giovanni stepped down from his ccNSO work, including his liaison role. Biyi volunteered to replace Giovanni. 

Move? Pablo

Second? Irina

Comments or questions? none

abstain? none

against? none

All in favour.

11. Appointment Mentor Fellowship

Jenifer agreed to serve another term

Ali: What is the status of the fellowship programme, now that all is online?

Alejandra: saw in previous rounds that they are doing their best. fellows are still motivated, they meet with SO/AC leaders, make regular calls with their mentors, trying to involve them in the work of icann. mix of long standing community members and newer ones. entirely remote is not as effective as in person, but still valuable. 

Move? Javier

Second? Pablo

comments or questions? none

abstain? none

against? none

all in favour

12. Appointment of Internet Governance Liaison Committee (IGLC) Vice-Chairs

Pierre announced he will step down in the middle of the year. To allow a smooth transition, the IGLC proposes to have 2 Vice Chairs. IGLC is working on an update of the ToR, since that is currently not foreseen in the charter.  

Move? Pablo

Second? Ali

no comments or questions 

abstain? none

against? none

all in favour

13. Update Triage Committee - preparation of February Council Workshop

Alejandra: We appreciate your input here.

Council decided that the role of the Triage Committee would expand. It was among others tasked with developing a ccNSO internal Prioritization Model and re-define is own role. As part of the process to develop a prioritization model it suggested a model based on assessment of impact/benefit for the ccNSO or ccTLDs versus effort it would take to achieve the expected results. In November we agreed that the Triage Committee would prepare a workshop to further discuss the model and its role. After the workshop we would start applying this for the 2022-2024 rolling work plan.

Jordan: 45 min slot at the next Council meeting. getting clear about the long-term goals for the ccNSO and the top priorities. assess the impact relatively easily. We aim for a light strategy, 3 to 5 years. The Triage committee will come up with a draft. We will test and refine it during the workshop, depending on the input received then. 

Alejandra: Do you think we need a follow-up, in between febr council meeting and ICANN73?

Jordan: depends on feedback, but hopes for a sign off in March at the Council meeting

14. Update CSC Effectiveness Review/ Appointment new member

As per requirement of the Bylaws the ccNSO and GNSO have initiated the 2nd CSC Effectiveness Review. The group started on the basis of the method of the first review, looking at the tasks the CSC is supposed to undertake  as described in the CSC charter and assess whether they are performed satisfactorily.  In addition the CSC RT has identified a few items that may need further discussion: frequency of meetings, attracting qualified members and liaisons.  The RT has met with CSC and will conduct further meetings. The RT is also expected to consult the ccTLDs and gTLD operators. Most likely this will happen at a webinar when they will introduce their Initial Findings as well. This is expected to happen post ICANN73.

Jens (.is) needs to step down from the RT. Council needs to appoint a new member asap. Response to previous calls for volunteers was very low. Suggestion to appoint someone without a call for volunteers. See also the email sent by Bart to the mailing list.  

against? none

Alejandra suggests appointing a councillor to the CSC Review Team, Any volunteers?

Not eligible: Alejandra, Nick, Demi (Brett is there on behalf of .uk and a colleague from .br too). 

Sean: available, but am I qualified?

Bart: elected and selected by Council. as long as Council feels comfortable, no further issues. need to be aware of the importance of the iana function. 

Sean confirms availability. 

Bart: provides support to CSC and CSC RT together with Claudia. will inform them, and subscribe you asap to mailing list.

15. Change the Rules of the ccNSO: next steps and what can Council expect? 

GRC subgroup worked on a new set of rules, to replace the 2004 rules.

David McAuley, Chair of the GRC rules subgroup. He shares a slide deck.  Topics:

• Why do we need an update?
• new rules are a result of extensive discussions and consultations with ccnso members
• Scope: what is not included in the proposed rules? empowered community, decisional participation
• Scope: what is included? introduction as context: why do the rules exist? ccnso decision making, voting, review of the rules, changing the rules, glossary
• What needs to happen to replace the rules?
• proposed timeline for the membership vote. The rules subgroup will forward the new draft to the council, with the recommendation to support adoption of the new rules. member vote to begin in March. Rules subgroup will co-chair the governance session at ICANN73. 
• GRC subgroup members. Participants have been thoughtful and generous with their comments. thanks to staff support.

Thanks to David for leading the subgroup. 

Irina: When are there holidays in April?

Alejandra: 15-18 April

Irina: ok. matches the timeline

Alejandra: questions or comments?

none

Alejandra: long timeline for the vote. best case scenario: 37 days. worst case scenario, we need a second voting round. makes it 60 days. please socialise the draft of the new rules. and seek active participation from all ccnso members. we need 50% of the members to vote, as a minimum (86 members currently). 66% of the voting members need to be in agreement, to adopt the new rules

Rules SG and Secretariat should prepare an outreach plan. In February, Joke to be appointed as voting process manager and proposed a timeline to be adopted too. 

16. ccNSO and DNS Abuse: what should the ccNSO do? Next steps.

Roadmap is the result of extensive discussions: during ICANN72, the ccTLD webinar on the topic, and the small ad-hoc group. Today that small group seeks your feed-back to refine their proposals. Once finalized they will be presented to the community during ICANN73.

Tatiana: gives a presentation on behalf of the small team (Ad Hoc Group)

• Ad Hoc Group: tasks
• 4 pillars identified during icann72 and the november workshop

• enhance sharing info
• messaging
• create DNS Abuse Oversight Committee
• metrix
• Phases: 4. phase 1 starts now, leading up to ICANN73 and in the aftermath. if council adopts the roadmap, the oversight committee can be created post ICANN73
• roadmap has concrete steps, vision of how it is going to work, ongoing effort. 
• next steps:
  • DNS Abuse Session at ICANN73: proposal to community, we seek feedback
  • adoption of the roadmap by council at its ICANN73 meeting
• list of Ad Hoc Group members

Ai-chin: What's the difference of function between TLD-OPS and DOAC this two committees. Do you consider enlarge the function of TLD-OPS or form the subgroup under TLD-OPS

Nick: conscious that is not a policy creation exercise. not to tell people what to do, but to allow for a safe environment to discuss and share best practices. 

Tatiana: tld-ops as a model. the DAOC would be a different group. The model has proven to be efficient. this is a community effort, we are suggesting something, but up to community on what to do with it

Alejandra: Indeed, separate groups. tld ops focuses on security. focus is different.  

Ai-Chin: Thank you.

Ali: tld-ops is indeed focused on security. TLDs can ask ccTLDs for help. dns abuse is a different mission. Did you reflect on how you will increase the community to be part of this approach? That was a difficulty for TLD-OPS, to ensure all TLDs are involved. Language challenges etc and other barriers are a reality.

Tatiana: outreach is indeed important. The committee will reflect on how to do outreach. how to get ccTLDs engaged? nuances. how to inform people about DAAR? but DNS abuse is much broader. the new committee will be tasked to 

Ali: answers my question, thanks

David: The challenge for the group as a resource, not a policy, will be to assemble information that is useful - a resource that is compelling by what it presents to members to consider in this area of high concern

Alejandra: will there be a draft ToR prior to ICANN73?

Bart: yes, the subgroup will present the ToR prior to ICANN73. 

Alejandra: topic to be included for the February council meeting

Hadia: I was just going to ask about the engagement of this group with the entire ICANN community - thanks again for this great work

Tatiana: yes, part of the plan. liaisons 

17. Coordination group to implement specific WS2 Accountability Recommendations

Alejandra circulated the latest proposal to you on the Coordination group to implement specific WS2 Accountability Recommendations. This would be a group that could assist us and the GRC in proposals to implement some of the WS 2 recommendations. We have discussed this before, and given the limited scope, and potential added value, Alejandra proposes that we support this ICANN org Initiative.

Abstain? none

Against? none

all in favour

Alejandra asks the GRC to nominate someone to the coordination group. 

Sean: ok. will take it up on Monday, when the GRC meets next

Jordan: I’m happy to support anyone appointed from GRC, as someone who was a co-chair of the WS2, but am not volunteering to be the rep on the group - can be a contact point if needed 

Abstain? none

Against? none

All in favour

Alejandra will inform other SO/AC chairs that we agree with the coordination of the group, and will inform GRC about the need to appoint someone.

18. ICANN73 Meetings

only 2 weeks between Febr and March meetings

when to have prep meeting? I don’t mind which day, but since the time slots are awful in this region for the ICANN meet the next week, including the Council, I encourage the prep to not be in the (almost) same 12UTC time slot

a. ccNSO Council

i.Council meeting: 

Topics:

• election chair and vice chair
• roles and responsibilities for councilors
• adoption roadmap dns abuse

b. Bilateral Council meetings

i.No joint ccNSO – GNSO meeting 

As per the suggestion of the 2 liaisons, Maarten and Sebastien

ii. ccNSO Joint session with ccNSO related Board members. 

Should we continue with the Q&A? different format?

Katrina: Any format is fine. let us know. Have you already thought about topics? perhaps ccPDP, budget, strategic plans… a hot topic? Patricio and I are flexible 

Alejandra: format. informal meeting with ccTLD-related board members. Jordan has been chair of these sessions. any comments?

Jordan: growing numbers of ccTLD-related board members. hard to fit in questions for all. board members seem to enjoy it, happy to continue. 

Alejandra: same format then.

any suggested topics?

Irina: PDP retirement might be of interest. 

Alejandra: yes

Chris: maybe an on list call for topics? I will probably have some thoughts but hard to think right now 

Pablo: the legal and regulatory topics regarding UN, EC and how that would affect icann and ccTLDs. 

Alejandra: ok. there will be a plenary session on this topic too.

Tatiana: board question to every SO/AC was hinting to these developments. ultimately boils down to the legislative developments. what affects the DNS? seconds pablo’s suggestion

Alejandra: any other topics? please use the mailing list?

c. ccTLD relevant sessions

i.ccNSO webinar for newcomers: Date and time TBC

ii. ccTLD news sessions

1. ccTLD News #1 - ICANN73 ccTLD News | Wed, 2 March 2022 (13 UTC) topics: Meet the members providing a platform for newer ccTLD community members & Capacity building efforts by ccTLDs

2. ccTLD News #2 – Thu, 3 March 2022 (07:00 UTC)

iii. Tech Day – Monday 7 March 2022

iv. ccNSO Members meetings

1. Governance session: 

Opportunity to interest people in voting for the new Rules!

Introduction of conflict of interest issues.

Other upcoming GRC projects.

2. ccNSO & DNS Abuse Session 

Presentation of roadmap and terms or reference for the committee.

Seek feedback from ccTLD community.

v. Plenary & other cross-community session(s)

1. Plenary session 1: Evolving the DNS Abuse Conversation: Maliciously Registered versus Compromised Domains

2. Plenary session 2:  Moving Forward with the Global Public Interest Framework

3. ICANN org: Overview legislative initiatives with potential impact on DNS 

19. ccNSO & Universal Acceptance 

Deferred to the next Council meeting. please reflect on this, so we can discuss next time.

20. Next Council Meetings 

· Meeting 180, February 24 – 21.00 UTC, includes workshop on Strategy/Prioritization

· Meeting 181, March 5-10 – ICANN73 TBD, includes tentatively decision on ccNSO & DNS Abuse Roadmap, Chair and Vice-Chair election and assigning roles and responsibilities to Councillors

· Meeting 182, April 21 – 12:00 UTC 

· Meeting 183, May 19 – 18:00 UTC 

· Meeting 184, June 13-16 – ICANN74 TBD

· Meeting 185 July 21 – 12:00 UTC

· Meeting 186, August 18 – 21:00 UTC 

· Meeting 187, September 17-22 – ICANN75 TBD

· Meeting 188, October 20 – 12:00 UTC 

· Meeting 189, November 17 - 18:00 UTC 

· Meeting 190, December 15 – 12:00 UTC

21. AOB

22. Closure 

Thank you. bye all

Joke Braeken

joke.braeken@icann.org