NOTES | UAC | 11 October 2023 (13:00 UTC)
Welcome by Chair Abdalmonem
2.
Administrative matters
All unanimously appointed by Council. New chair and vice chair
Informal meeting at ICANN78, exploring future work items.
All action items completed
Abdalmonem: pleased to take on role of Chair, thanks to Regina for agreeing to take on role as Vice Chair
3.
Defined work items UAC
a.
How could repository look like
Kim talks about what the ccNSO DNS Abuse committee (DASC) did in terms of creating a repository library, regarding DNS abuse. As inspiration for what the
UAC could explore. Based on a concept paper, and Terms of Reference. Various categories of information, for instance:
This list is vetted. The editorial Board meets on a quarterly basis.
Bart: consider it a framework. Replace “DNS Abuse” with “Universal Acceptance”. Template for you to look at. Build a repository, if you feel this is a good
way forward. The reason for including an editorial board is to ensure the info remains relevant to ccTLDs. This is for and by ccTLDs, this is not staff-driven.
UAC is in favour of creating a repository
Action item #1:
Staff to share proposal (concept paper) ahead of the next meeting
b.
Creating an email list: what does it take?
Kim shares experiences from DASC, who will launch the mailing list at ICANN78 (session on Wednesday afternoon). Based on experiences from TLD-OPS. It all
started with a concept paper, moved into a procedural document. Digest modeled after TLD-OPS. They also send out a monthly contact list. Concerns regarding Personal Identifiable Information (PII).
Up to the group to decide whom to subscribe.
Jiankang: We need to have several subscribers. Not just one person per ccTLD. Invite more people, more users, also from providers, open source providers
and internet users.
Bart: the charter of this list determines all those choices. If - and only if - the UAC decides to create such a list. Reminder to avoid overlap efforts
elsewhere. You do not want to overlap with UASG for instance. First, carefully think about what you want to achieve. The language is fairly formal. Do not mix it up with the ccNSO rules or bylaws. Ultimately up to the ccTLDs and what the UAC decides. This
is not set in stone. There are many variables. The starting point is: what is the purpose of this mailing list?
Kim: mailing list and contact repository. Should this be done in parallel (note by Joke: with repository)? Suggestion is not to do so.
Bart: make sure to attend the DASC session on wednesday afternoon at ICANN78. The first 20 min will talk about DASC repository and mailing list. As inspiration
for the UAC efforts.
UAC is in favour of creating a mailing list
Method of working?
First repository, then focus on the mailing list. Abdalmonem initially did not agree.
Regina: going step by step seems to be a good approach. DASC experience has shown this. We could propose a concept to ccTLDs and get their input.
Bart: indeed. Presenting results to date as an update to the community during ICANN79. Consult and check whether it makes sense.
Regina: broader group needed?
Bart: not yet. The list we are talking about is to reach out to all ccTLDs. ccNSO has 176 members currently. Over 200 ccTLDs are subscribed to the TLD-OPS
mailing list. People that deal with operations and security on a daily basis that are subscribed.
Mirjana: good to first have a product. Mailing list could be used to show what we are doing to the broader community. Does not make sense to first have
the mailing list, and then the repository. Focus on repository first.
Vadim: not clear what we are going to share, if we do not have the repository yet?
Bart: please consider whether an email list adds value.
Kim will share basic doc regarding the repository. Perhaps ask the question to the DASC during the session about their experience, whether it made sense
for DASC to start with list or a repository first? Do not underestimate the governance aspects for the mailing list. It took the DASC about 8 months to come as far as where they are today (shortly before the launch in ICANN78)
Qing Cai: will this list be limited? We could encourage people to subscribe with a EAI mailing address
Bart: this list is for the broader community.
Abdalmonem: i will change my opinion. Repository first seems like the better approach.
Bart: proposal to invite DASC as a gues speaker, to help you and inform you about their role. We shared our perspective as staff, but this would be from
your peers to inform you.
Action item #2:
Staff to invite DASC community member to share experiences regarding creating the repository and mailing list.
4.
Exploring UAC work items
Bart: time check. Let’s defer the napkins to the 8 november meeting. Let’s also reconsider whether we work in future with subgroups, or meet perhaps every
week. For discussion on 8 November.
a.
UAC as liaison committee
b.
UA readiness and practices session
5.
Next meetings
a.
Informal meeting ICANN78
Abdalmonem: Will Sarmad be there?
Kim: no observers subscribed yet
Action item #3
Kim to subscribe Sarmad and Pitinan
Abdalmonem: check with them how to cooperate in future.
Bart: see item 4a
b.
8 november | 13 UTC (90 min.)
Proposed agenda for the meeting on 8 november:
Materials will be shared by staff prior to the meeting. Abdalmomen welcomes input on the mailing list.
c.
22 november | 13 UTC
6.
AOB
Regina: Thanks to staff for sharing experiences and insights
Regarding the informal meeting, what are the next steps?
Bart: we will share a proposal regarding time/day. Our availability is limited at ICANN78.
7.
Adjournment
Thank you.
Joke Braeken
ICANN78: Links to bookmark now
ccNSO Schedule
https://community.icann.org/x/doDxDg
ccNSO Session Highlights
https://community.icann.org/x/K4LxDg