NOTES | UAC | 14 January 2026 (8 UTC) 1. Welcome Welcome by Abdalmonem Happy New Year Apologies received: Jiankang Yao 2. Administrative matters a. Any SOI updates? None b. Action items Completed. See discussion later today c. Update UA Day Sami: We evaluated all proposals. A few queries were done. We have not heard back from ICANN staff on next steps Abdalmomen: i heard from colleagues that applied that they received their success report. Will be from march to may. Successful applications are announced. It focuses on adoption, not awareness. There are not a big number of EU region applicants. More details regarding countries and other matters, i defer to Seda Bart; we can check with her Anna: Armenia received the confirmation. No other EU region proposals, even though we are APAC country, we are listed as EU. regional conference. Andrew: happy new year. Kenya also received confirmation we get support. First time for our country. We are excited. I will soon share some thoughts with this committee on how we can get the right agenda. Bart: UAC or selection committee? Andrew: i welcome guidance Bart: please use mailing list. If needed, we can put it on the agenda. Rest of the group will appreciate this d. Update Expert Group Sami: We had a meeting yesterday. We included 10 items considered the issues highlighted for discussion by the group. Last issue was discussed yesterday. By mid Feb, the guidelines will be finalised, and presented at ICANN meeting. It will be open for comments. Bart: what are the 10 work items? There might be a link with the joint session. This might be a platform for involving the technical audience. Sami: they want us to collect UAC perspective. Ok if i make a summary by monday/tuesday? That might be an update from UAC to the Expert group, and other way around First 5 items are technical ones. (e.g. system admin platforms) the other ones are more engagement and capacity building related. Engagement with Tech Day and Tech WG will be useful. Bart: regarding presenters, please start thinking about it. One or 3 presentations, followed by a discussion. Where do we take all those new developments Sami: yes, discussing with others as well. Bart: we have a more detailed discussion under number 3 Abdalmomen: the 10th one is most important i think. It is related to the work done by the community. GAC, ALAC, ccNSO …. Important to consider these updates. Have an explanation about the scope of the work Sami: we can invite the co-chairs. Edmun Chung, Sarmad Bart: Eberhard provides the platform. Think about the audience, and bringing the threads together. Inform the broader community about the ongoing work, and see where you may need assistance Abdalmonem: GAC UA IDN WG has a session as well. Think on day 1. Invite for UAC to join the session as a panellist. Bart: saturday? Abdalmomen: yes Bart: important to avoid overlap. And tech day is always open to all. Maria: could UAC spread the word about the events? Bart: ccnso members mailing list. You can use it to alert people. Maria: we can prep announcement and share ourselves? Bart: yes. If needed we can publish something on the ccNSO website. Regina: Seda and theme are now reaching out to successful candidates. Questions to be clarified, regarding the adoption plan. Once published, we can pick it up, and highlight the ccTLD initiatives. But the process is not yet over. Bart: yes. Once list is public, closer to UA day 3. Joint session ICANN85: suggestions for format and presenters Bart: i circulated an email yesterday. Tech Day is a platform with successful discussions in Dublin on abuse. In Dublin it was about tools on abuse. Eberhard hoped for more discussions. As Maria already mentioned, keep the audience in mind. This is about technical and operational developments. New perspectives, what needs to happen? Link with Expert Group. From the discussions with Eberhard, he would like to invite the local host. NIXI might be an interesting part of the speakers panel. But I do not know what they do. Maybe discuss for 20 min. Abdalmomen: sessions on saturday, and Monday. Bart: saturday is a UAC working session, focus on the workplan. Bart: regarding the format * Presentation from NIXI * Presentation on latest developments UA readiness from a technical perspective (for Expert Group?) * Discussion between UAC and Expert Group Maria: this is not the project of NIXI. Xgen plus launched the project with local gvt in Rajastan. https://xgenplus.com/ They provided citizens with email addresses to work with the gvt services. It would be interesting to have an update on this project. NIXI could get this info from their partners and provide? Would be interesting. This project is well known. I added info in chat. Interesting for the session? A new Request for Comments is now available in online RFC libraries. RFC 9873 Title: Additional Email Address Extension for the Extensible Provisioning Protocol (EPP) Author: D. Belyavsky, J. Gould, S. Hollenbeck Status: Standards Track Stream: IETF Date: October 2025 Mailbox: beldmit@gmail.com<mailto:beldmit@gmail.com>, jgould@verisign.com<mailto:jgould@verisign.com>, shollenbeck@verisign.com<mailto:shollenbeck@verisign.com> Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-regext-epp-eai-27.txt URL: https://www.rfc-editor.org/info/rfc9873 DOI: 10.17487/RFC9873 The Extensible Provisioning Protocol (EPP) does not inherently support internationalized email addresses because the specifications for these addresses did not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP contact object. That additional email address can be either an internationalized email address or an ASCII-only address. Maria: Arnt Guldbrandsen makes project with open source community on UA. we could ask him to give a general overview of the current situation for ccTLDS. Bart: Could you drop an email to the list? probably we can invite one of the authors of this RFC to speak about it Action item #1 Maria to share her proposal in response to yesterday’s e-mail from Joke Maria: We could share our experiences. We launched the support for EAI addresses for all our systems some years ago. If useful, we can share our experiences. Vadim: i could share our experiences. But what do we want to say? Level of technical details? Just an overview of the different solutions in our environment? Or do we want to make a deep dive in the details. Model? Library? Infrastructure element? What level of abstraction do we want to use? Bart: good point. Any comments? Abdalmomen: different models for ccTLDs to be UA ready. Have a presentation on this. Some overlap between the sessions on saturday, and the session for GAC. Bart: separate discussion, the saturday Qing Cai: i agree with Maria. I want to see the discussions. UA development of system. Arnt is an expert. We can let him talk about the EAI. Maria: Who can make presentation on how to make UA ready registry? Regina: and UA ready registrars Abdalmomen: Arnt is icann staff. He is an expert. Arnt to speak, and someone else. Qing Cai: open source. With microsoft and other tech companies. Maybe he can make deeper recommendations for us. Vadim: i do not understand what we do about my question? I have additional thoughts. What we can provide from our side: we can give high level points of usage infrastructure and UA ready elements. If we need to explore this in depth, we would need to invite our partners that made some elements for us. If we decide NIXI - because they are the host - is the headliner of our session, we should ask them what they will speak about. We can pick up on this, and proceed along the same level of details. Bart: we can reach out to Arnt. he is icann staff. Bart, coming back to the Format: * 2 or 3 presentations * Discussion 5 min. Introduction by session chair 15 min. Presentation 1 15 min. Presentation 2 20 min. Roundtable: Arnt, members Expert Group, members UAC (Vadim?) 5 min. Wrap up by session chair Abdalmomen: https://www.icann.org/en/system/files/files/ua-roadmap-registry-registrar-sy... Michael Bauland usually attends ccNSO sessions. Would be good to have him Maria: i am in favour of more presentations. The ccTLD community is not that much involved yet. It would be good to show practical examples of people who do something. The roundtable needs to be very focused. What exactly do we want to discuss? We should choose speakers. Bart: issues you encounter, and where you need help. Tech Day is looking for the discussions Abdalmomen: author for the doc I shared. Michael Bauland. We could ask him to share info about the doc. Bart: we have only 60 min. Be careful regarding death by powerpoint. If Arnt could provide an high-level overview, that would be interesting for the audience Vadim: maybe Arnt, or someone else, can give some other view of what has been done regarding ICANN systems of UA. A lot of work happened there. Experience of the work? How can it help ccTLDs to make them UA ready? That might be useful, for the audience, form a technical point of view. Bart: what Abdalmonem said can be embedded in such a presentation. This is about triggering interest. Maria: 4 speakers for 7-8 min each? Bart: that just allows for a soundbite. Suggest to give 10 to 15 min. Maria: if we have 3 speakers max, we should find ICANN staff to present the UA Roadmap. Also someone should give a general overview of what happens in Big Tech, plus open source community. In that case, we do not have time to go into deep tech details. Vadim: My experience that it's common practice it Tech day presentation shorter than 10 minutes). During DS automation and Multisigner sessions Abdalmomen: 2 or 3 presenters. I support that Bart: we need to finalise this asap. Start to invite people by end January. To make it successful, you need to prep properly. Make sure people are aware about the expectations. Finalise this in 2 weeks. 4. Workplan https://docs.google.com/document/d/1o3tPVX9DeIRrEQOw0S--zN8tRT8kzNB_/edit We defer to the next meeting 5. Next meetings: 28 January | 13:00 UTC 11 February | 08:00 UTC 25 February | 13:00 UTC ICANN85 – 7-12 March 6. AOB 7. Adjourn Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org>