NOTES | ccNSO UA Committee (#4) | 15 November 2023 (13:00 UTC) 1. Welcome and roll call Attendance via Zoom Welcome by Adbalmonem 2. Admin matters, if any a. Action items, if any Reminder about the last meeting, prior to ICANN78 (12 October). 2 main topics: * Repository * Email list Preference to start with repository first. There is nothing solid to share yet on the mailing list. Also, we need sufficient time to prepare the e-mail list Action items: * #1: Staff to share details regarding repository with UAC mailing list * #2: Staff to invite colleagues from DASC to share experiences DASC is our role model, preferring to use the same model. Bart: We did invite DASC, but they were unable to join today’s meeting. So let’s check after today, if it is still relevant. Asks Kim whether information was shared. Kim: draft was not yet circulated. Was hoping to have some feedback first, before sending anything out. Will show it later. Would still be worthwhile to invite DASC. Bart: at the end of the meeting, after we discussed the proposal, let’s revisit this action item. Next meeting is in 2 weeks. Abdalmomen: explore whether to invite Sarmad and Pitinan. And explore how the UAC fits into the UASG. Bart: inviting them to join conversations regarding scope of UAC and participate in the napkin pitches. Invite them for the 22nd Action item #1: staff to invite ICANN org IDN staff as observers Anna: can we also invite Maria Kolesnikova. Chair regional group, and she has a lot of experience Masha: Would be good. She has a lot of experience. Anna: Igor M. said he received the invite to join today’s meeting Joke: sent link to UAC mailing list with notes document Anna: confusion with other UAC meeting Bart: before we start to invite everybody, let’s check what we want to receive. The more people, the easier it is to loose focus. But indeed good to invite ICANN staff. Abdalmonem: ask Sarmad what ccTLDs need to do to promote Bart: let’s first brainstorm to set the work activities (napkins next week). Good opportunity to network. First develop the direction, and then start working along the path you want to take. b. Introducing Statement of Interest procedure https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-procedure-general-soi-coi-21sep23-en.pdf<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-procedure-general-soi-coi-21sep23-en.pdf__;!!PtGJab4!6zASBBghh0MLZA5ZbusN8x2Kfkj786H8H6omt7mymjuuAJVV1XdeNQOcGLaF64_bPaGjAfA5zYhxaZyKithpIiyDwSkQlvgcU7v1$> Bart: Statement of Interest (SOI) procedure was adopted by Council in July. SOI is new for the ccNSO. Council agreed that the procedure would be effective since 1 November, following implementation. Aim is to increase the transparency of WG/C and Council. SOI form: https://forms.gle/79Jw4wSnNhn5W4Z46 This is a ccNSO SOI. May differ from other SOI used by other SO/ACs at ICANN. Please complete the form, if you feel like it. Voluntary for existing WG/C. Abdalmonem: please share link to wiki in footer of every email. Kimberly: each meeting has an own page on wiki Abdalmomen: I need the main page, and then I can click to the meeting i am looking for Kim: can send individual page and main page, both. Bart: post ICANN78 admin matters Information on the DASC mailing list and contact list: https://community.icann.org/x/BJJME Bart: DASC launched an email list regarding DNS Abuse at ICANN78 If you are interested in DNS abuse, please subscribe. It will be used to discuss DNS abuse repository related matters. For people within the ccTLD community. Makes it easy to reach out to colleagues that deal with the topic within other ccTLD registries. Also open to non ccNSO members. TO SUBSCRIBE: DASC-mailing-contacts-subscribe@icann.org<mailto:DASC-mailing-contacts-subscribe@icann.org> Please add the IANA admin-c in copy. This is also a contact list. Updated quarterly. Digest. Jiankang: UAC to have a similar list Bart: that is the intention. See agenda items 4 and 5 later today 3. What happened during ICANN78 re UA? Abdalmonem. 2 highlights * Strategic plan. FY25. moving from awareness to adoption. Governments are going for digital inclusion * Planning UA day in 2024. Global, regional, national, local etc. The global one is the most important one. Different stakeholders discuss UA. Previous one was in India, and was a great success. Main contact point: Masha. Serbia as proposed host. Qing Cai to add anything? Nothing at the moment. Anna: if the global UA day is being held in Europe, it will raise interest since UA is currently not so well promoted Abdelmonem: Global one is important. Different actors discussing at the same table. Thought it would be in Serbia. Kim: is there a global calendar? We can add to wiki. Abdalmonem and Joke: https://uasg.tech/ua-day/ Joke: https://www.icann.org/ua-day-en Abdalmomen: ccTLD involvement Bart: see outcome of the napkin pitches Qing Cai: Maria applied. No decision yet by UASG. deadline 15 December 4. Design UA library for ccTLDs Use DNS Abuse frame as starting point and adjust for purposes of UA. Kim: changes in google doc. Red-line. How to proceed. Bart: before we start talking about the edits, please explain the content of the doc Kim: this is an overview. Why to consider? Includes info from the DASC library. Could look totally different. Why is it there? What is its mandate? Content advisory board: what happens when there are submissions? Have different sections, categories. E.g. announcements (example: UA Day) Questions regarding how to deal with submissions. E.g. AI submissions. What if there are objections to the submissions? Bart: not up to staff to decide what is in the repository. Hence the editorial board Secondly, it would be good to group the information in a relevant way. E.g. tools, events …. Up to UAC to decide what those relevant categories would be. Core things to decide: purpose, categories and the role of the editorial board Kim: will prepare a red-line, to see comparison with what DASC did. Will there be a small editorial board? Or a sub-team? Some green marks for sub-team option. Bart: who volunteers? Action item #2 Staff to share call for volunteers on UAC mailing list: offer UAC full group members the opportunity to join the UAC Repository editorial board. Bart: In 2 weeks, call with subgroup and inform full group on the 13th. 5. Design email list charted dedicated email list Use charter DSN Abuse email list as starting point and adjust for purposes of UA Bart: Deferred to a later date. Sub-group that will work on repository will also work on the email list, as per the DASC example. First focus on the library. Abdalmomen: agree. No objections from UAC Kim: waiting a bit allows us to use the lessons learned from the launch of the DASC mailing list. 6. Next meetings a. 22 November 2023: Napkin pitch: detailing the work items i.liaising with other groups ii.Information sharing, sessions etc. b. 29 November 2023: Discussion UA Library & Email list c. 6 December 2023: Discussion roadmap UA d. 13 December 2023: Continue Discussion UA Library & Email list Abdalmomen: show our existence and progress at ICANN79 Bart: Summary of the meeting today. we will share the SOI procedure again and repeat it next week. UA day was high on agenda during ICANN78. Suggestion to include link in library. We briefly discussed the library. Priority number 1 to develop. The sub-grup will meet on the 29th. We will adjust the agenda accordingly. Staff will share the call for volunteers. And Kim will share doc with small team, which will report back to full team on 13 December. Email list activities were deferred to later. Next week we will discuss how to liaise with other groups, and how/which sessions to organise. UA will present its progress to date at ICANN79 7. AOB none 8. Adjourn Thank you all. See you next week. Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org>