NOTES | UAC | 19 February 2025 at 14 UTC
1. Welcome
Welcome by chair Abdalmonem
2. Admin matters
a. SoI updates
None. please contact secretariat, if any
3. ICANN82 planning
a. Prep week
5 min. Update
Encourage all to join the session on drivers
Abdalmomen: action now
b. Session on drivers
i. Confirm presenters
UNESCO confirmed. They are enthusiastic about contributing to the session. They will deliver the keynote
We just learned that Sabrina will not be able to present. Apologies regarding the misunderstanding. She is not in a position to present
the importance of supporting language communities.
Bart: Masha, are you still available to present?
Masha: yes. Depends on how deep i need to go into this. Currently only russian alphabet. There are plans to introduce cyrilic elements
used more broadly in the russian federation
I will join remotely.
Bart: unesco will participate remotely as well.
We need to confirm today a replacement for Sabrina, ideally in person
Masha: i suggest Qing Cai, .cn
They have a good gvt report on UA acceptance
Bart: is this possible?
Qing Cai: i will be remote only
Regina: strong language communities behind .cat, .fo etc at CENTR. Why did the launch not go as expected
Abdalmonem: or India. Nitin Walia will attend. He could attend.
Bart: 2 alternatives. Through Regina.
The person needs to be there
Masha: it will be 02:30 in Moscow. But will do it
Joke: .fo will attend in person
Sami: I will not attend in person
Masha: Could we ask Indian colleagues to talk about the current status of their e-Gov service based on EAI addresses provided to every
citizen
Or Armenia
Anna: i have no visa. I cannot attend in person
Bart: the ccTLDs who run IDNs are the obvious candidates
Anna: we run IDNs since 2016.
Bart: the idea is to have one testimonial from a ccTLD who is involved. And one who does not run an IDN ccTLD. The contrast makes it
interesting.
The need to support local language communities in Canada, the first nations.
Hence the proposal by Regina, to invite .fo or Joke’s proposal regarding .ke could be a good option. Not have an “obvious” testimonial.
An out-of-ordinary testimonial might be more interesting.
Regina: i agree that Kenya would be a good example. If the format of the session is successful. We can do a similar one in Prague, with
EU testimonials
Bart: regional diversity in this group. More interesting to have both the story of an obvious candidate, but also a not so obvious ccTLD.
Maybe have .fo as a back-up plan.
Action item #1
Joke/Abdalmomen to reach out to Andrew (.ke), and invite him to present during ICANN82 (UAC session on drivers).
Deadline to confirm: Monday, noon UTC. If Andrew is not available, Joke to reach out to Gudrun
Abdalmomen: or Malysia.
They have a ccTLD, and support for UA
Bart: but since they have IDNs, they are again an obvious candidate
ii. Proposals mentimeter questions
Bart: ask which of the drivers are relevant to ccTLDs.
Suggestion: select 3 out of the 7 drivers
Masha: we provide the list. We do not ask the audience for own suggestions?
Bart: no
Masha: we could also ask for … are we sure the list is complete and correct?
Bart: we do not
Keynote: 15 min
Testimonials: slightly shorter
3 questions at the start of the session
That ensures a lot of feedback
Abdalmonen: having “none” as an option would not be good.
Replace it with “other”
Qing Cai: We can do an open question in the servey: please write down the IDN domain name you know. because on the one hand to promote
the audience's thinking, on the other hand to collect the domain name atlas can be used for later display
Masha: The 3 Q is challenging... we won't know who is answering
Joke: We need to check if Mentimeter allows that kind of restriction (max 3 options
Bart: at the end, 2 options:
Abdalmomen: are there other driver options?
Bart: you can go different directions
Regina: almost same questions, see there is a change
Bart: ok. Force people to make a choice
Anna: problem with one-way translations. 5 specific letters. This could also be a driver. Have writing in the Armenian language. Prevent
phishing
Bart: important to mention. We build on earlier work. That is part of the session intro
iii. Prep meeting next week
Not a full group meeting. Have a prep just for those with an active role in the session.
Bart: we will invite unesco as well.
Action item #2
Secretariat to schedule prep meeting for next week, Wed 26 Feb, 13:30 UTC
c. Working session
i. Topic: blockers for UA and
prep for ICANN83 session
Bart: additionally, finalising the presentation. Maybe not relevant for broader public
Action #3
Secretariat to share again the list of drivers and blockers
4. AOB
5. Closure and proposed meetings post ICANN82
a. Wed, 26 March 2025 (13 UTC? DST)
b. Meetings continue up to ICANN83, every second week
At most 4 meetings between ICANN82 and ICANN83
Limited time. Suggestion is to start discussing already at icann82, to prep for icann83