- Tsg-alternative-names-project-community-group

in-person workshop 2
by Andrew Sullivan June 8, 2026

June 8, 2026

Hi everyone, We had more than one suggestion to set up workshop 2 around the IETF meeting in Vienna in July of 2026. I'd initially floated the weekend after (i.e. 25-26) as the dates, but more than one of you replied you could not make those dates, but that you could make the weekend before (i.e. 18-19). I can see an obvious disadvantage of 18-19 in that it's only a little over 3 weeks before our prior workshop, but the whole effort is pretty short so that doesn't seem like a powerful objection. So, I'd like to ask these questions, please: 1. Is 18-19 July in Vienna possible for you? If you will have a partial conflict due to other obligations during the IETF pre-weekend, please say "partly". 2. Are 18-19 and 25-26 equally ok? If you have a strong or weak preference for one of the other, please indicate with [18-19], [25-26], both, neither. 3. If the meeting were held the following week instead of the weekend after the IETF meeting (so, eg,, 27-28) does that help? Thanks, A -- Andrew Sullivan contractor, ICANN <andrew.sullivan(a)icann.org> non-ICANN mail: <ajs(a)anvilwalrusden.com>

2 1

Charter
by Andrew Sullivan June 5, 2026

June 5, 2026

Hi all, One of our responsibilities is to ensure we've worked out the charter for ourselves along with ICANN. The current draft is up at https://docs.google.com/document/d/1Qw8q4G71G7EwuOoC_cFWJFPLwJgZp8qcrUr3evw…. I think there were some permission problems before, such that comments might not have been recorded, so if you think you made some comments before just check to make sure that those were recorded and are reflected in this version. Thanks! A -- Andrew Sullivan contractor, ICANN <andrew.sullivan(a)icann.org> non-ICANN mail: <ajs(a)anvilwalrusden.com>

1 0

In-person workshop 1
by Andrew Sullivan June 5, 2026

June 5, 2026

Hi everyone, You have probably seen already an invitation to the first in-person workshop. Given the responses we've had, it appears that a majority of people _can_ make a workshop on 24 and 25 June in LA at the ICANN offices. As a practical matter given the time, there isn't really another option anyway. So we've decided to go ahead and organize that, recognizing that there are people who can't make those dates, or who can't travel there for some reason. We will ensure that remote participation is also possible, recognizing that remote participation will not be able to be supported during more informal discussions (e.g. over a meal or drink). Last I heard, this is not _officially_ approved: there are some more steps within the ICANN staff that need doing. We should nevertheless begin preparation on this basis, and start making travel plans. We'll get travel support details to the list quickly. I'll send a separate note about the second f2f meeting. Best regards, A -- Andrew Sullivan contractor, ICANN <andrew.sullivan(a)icann.org> non-ICANN mail: <ajs(a)anvilwalrusden.com>

1 0

Regular meeting times redux
by Andrew Sullivan June 5, 2026

June 5, 2026

Hi all, We currently have a practical problem. Given the constraints people mailed me, using the language of "I can make" vs. "I prefer," we have meeting times that end on a Thursday no later than 13:00 UTC. But for people in California, that is an ending at 06:00 AM, which would mean a start time of 04:30, which is obviously not so good. So I've started over with a "when available" calendar broken down in 30 minute increments between Tuedays and Thursdays. I thin I have arranged this on the following principles: 1. Where people's normal home TZ is, they should never have to attend a meeting starting any earlier than 05:30 (arguably, that alone is worthy of criminal prosecution, but the California-EU times problem is well-known). 2. Where people's normal home TX is, they should never have to be in a meeting after 19:30. The when available calendar is at https://whenavailable.com/invite/0kWuUfcN6XOLFJhD2h5G. Please fill this urgently (it says it closes on Tuesday but, obviously, it'll be much easier to set a meeting time with more advance time). If you can't make a given slot next week but you _normally_ could, please just mark it as available and we can work out regrets for the specific meeting later. I think this illustrates part of the problem we are going to face, so I'm going to adopt the traditional IETF rule governing meeting decisions: decisions might be taken at a meeting, but they are formally approved on the mailing list. Thanks, A -- Andrew Sullivan contractor, ICANN <andrew.sullivan(a)icann.org> non-ICANN mail: <ajs(a)anvilwalrusden.com>

1 0

Meeting logistics and follow-up after today's working session
by Andrew Sullivan June 4, 2026

June 4, 2026

Hi everyone, This is the reminder email to let us know what are good times for you between Tuesday and and Thursday for a 90 minute slot. If we converge rapidly then we'll do that. Otherwise, once we have a little bit of a range we'll run a doodle. Similarly, please send any objections or support for the first face to face workshop being at the ICANN (LA) offices the week of the 22d June. Finally on meeting logistics, please send objections or support for the 2nd face to face workshop being held either (1) after the IETF in Vienna, on 25-26 July, or (2) week of 13 July (likely mid-week) at the ICANN offices in LA or (3) week of 27 July, also at the ICANN offices in LA. Apparently, I made an error about Slack. ICANN cannot offer a Slack license to members of the TSG. My apologies. This means we are not waiting for that item to be ready, but also that we won't have to consider time on Slack as part of our record. This helps us to maintain transparency by having fewer ways someone interested must follow the work. Finally, I neglected to mention that, when the announcement goes up about the project, so will get shipped and celebrated likely on 4 June. Best regards, A -- Andrew Sullivan contractor, ICANN <andrew.sullivan(a)icann.org> non-ICANN mail: <ajs(a)anvilwalrusden.com>

4 3