At-Large Session Reports
Resources:
- ICANN80 Schedule
- At-Large ICANN80 workspace
- At-Large ICANN80 Talking Points
- At-Large Wrap-Up session Zoom Info (Thursday)
Objective is to keep these reports brief and focused on what At-Large should do in terms of next steps. Reports to be presented during the Thursday At-Large Wrap-Up session.
Report format:
What happened?
-
- Item 1
- Item 2
What are the At-Large specific takeaways from this session?
-
- Item 1
- Item 2
What are the At-Large specific action items (next steps)?
-
- Item 1
- Item 2
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
Example Title | Date/Time | @example name | Use template: What happened? Example: This session discussed.... What are the At-Large specific takeaways from this session? Example: At-Large is interested in... What are the At-Large specific action items (next steps)? Example: At-Large needs to... |
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
GNSO: CPH DNS Abuse Community Outreach |
Sunday, 3 March at 16:15 | What happened? This session focused on the new DNS Abuse requirements in the RA and RAA contracts that go into effect on April 5th, 2024. There was a panel that included representatives from the CPH as well folks from IPC and NCUC. The CPH participants focused on the the speed with which an agreement was reached and the effort to get it voted on by a majority of the CPH and expressed high hopes for a positive impact on taking down "bad actors." Elliot Noss made a rare appearance to emphasize the expectation that ICANN Contract Compliance now has the tools it has been asking for and hope to see real results. The IP and business interests suggested it was a good start and the NCUC rep expressed concern that it might trample due process. What are the At-Large specific takeaways from this session? the At-Large perspective is that we've been looking for similar changes to the contracts for many years and welcome them. We have no desire to see due process suffer as a result. Ideally, these ammendments do NOT change the behavior of "good actors" but allow ICANN to punish bad ones, there by splitting the difference between the fears of the NCUC and the expectations of the business community. What are the At-Large specific action items (next steps)? Justine has suggested that we perhaps begin holding a series of plenaries on how these ammendments are working out, starting at ICANN 80 so that there are continuous updates. |
||
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
GNSO: CPH DNS Abuse Community Outreach |
Sunday, 3 March at 16:15 | Jonathan Zuck | What happened? This session focused on the new DNS Abuse requirements in the RA and RAA contracts that go into effect on April 5th, 2024. There was a panel that included representatives from the CPH as well folks from IPC and NCUC. The CPH participants focused on the the speed with which an agreement was reached and the effort to get it voted on by a majority of the CPH and expressed high hopes for a positive impact on taking down "bad actors." Elliot Noss made a rare appearance to emphasize the expectation that ICANN Contract Compliance now has the tools it has been asking for and hope to see real results. The IP and business interests suggested it was a good start and the NCUC rep expressed concern that it might trample due process. What are the At-Large specific takeaways from this session? the At-Large perspective is that we've been looking for similar changes to the contracts for many years and welcome them. We have no desire to see due process suffer as a result. Ideally, these ammendments do NOT change the behavior of "good actors" but allow ICANN to punish bad ones, there by splitting the difference between the fears of the NCUC and the expectations of the business community. What are the At-Large specific action items (next steps)? Justine has suggested that we perhaps begin holding a series of plenaries on how these ammendments are working out, starting at ICANN 80 so that there are continuous updates. |
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
ASO AC Work Session (1 of 12) |
Monday, 4 March at 10:30 | What happened? What are the At-Large specific takeaways from this session? What are the At-Large specific action items (next steps)? At-Large can participate at the level of the RIR. At-Large need to be ready to answer consultation from ASO-AC about IPC-2 |
||
GDS: Subpro IRT Work Session (2 of 3) |
Monday, 4 March at 16:15 | What happened? ICANN org provided an update on:
What are the At-Large specific takeaways from this session? At-Large should follow progress of IRT work, paying particular attention to topics of importance to us. What are the At-Large specific action items (next steps)? At-Large should participate in the public comments as needed, and note that there will be no extensions for any of the public comment proceedings. |
||
GAC Discussion on DNS Abuse Mitigation |
Monday, 4 March at 16:15 | What happened?
What are the At-Large specific takeaways from this session?
What are the At-Large specific action items (next steps)?
|
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
Reviews Program Session with the Community on ATRT4 Deferral and Pilot Holistic Review |
Tuesday, 5 March at 9:00 | Sebastien Bachollet | What happened? This session provided updates on the timing for the Fourth Accountability and Transparency Review and the status of the Pilot Holistic Review. The group also discussed the CIP. What are the At-Large specific takeaways? ATRT4 must be done in a not to distant futur. CIP can be started "officially" the 1st of July 2024 (start of the FY25). What are the At-Large specific action items (next steps)? At-Large needs to answer the letter received by the ALAC Chair from Theresa S. (ICANN Org) regarding ATRT4. |
|
UASG Governance and Plans Working Session |
Tuesday, 5 March at 10:30 | Satish Babu | What happened? The UASG Leadership interacted with the community and presented the 5-year Work Plan for UASG from FY25 to FY29 for UASG as a whole, as well as for each of the four Working Groups (Measurement, Tech, EAI, and Comms). In addition, the UASG Leadership also presented suggested changes to the Governance Processes to enhance the transparency and accountability of UASG. What are the At-Large specific takeaways? Since UASG and At-Large work in close relation, particularly for initiatives such as the UA Day, At-Large needs to track the strategic plan as well as governance initiatives within the UASG. Specific Governance Changes Proposed Pls see the full report here. |
|
New gTLD Program Next Round: Planning for String Similarity Review Work Session |
Tuesday, 5 March at 15:00 | Bill Jouris | What happened? The IDN project presented the String Similarity Review Guidelines ( https://itp.cdn.icann.org/en/files/strategic-initiatives/string-similarity-review-guidelines-07-02-2024-en.pdf ) which are currently up for Public Comment. The IDN Project has recognized that there are lots of pairs of symbols which, while they are not classed as variants, are sufficiently similar to cause confusion. They have identified some of these, and developed a process to automate the initial evaluation of proposed TLDs. The proposed automation will basically eliminate those TLDs which are clearly NOT similar to any other TLD (current or proposed), thus keeping the number requiring manual review to a manageable number. The only significant oversight appears to be in the matter of variations under the basic character which would be obscured by the underlining which major browsers and word process software packages automatically generate for domain names. What are the At-Large specific takeaways? This is a huge improvement over where the IDN project appeared to be a couple of years ago, and it should be commended for that. ALAC may also wish to produce a Public Comment (deadline 27 March) on the matter of underlining, and a couple of other more technical details. (NOTE: This is an interim document, with several unwritten sections still visible. So there will be opportunities for further comment later. This is an opportunity to get some things included while the situation is still somewhat fluid.) What are the At-Large specific action items (next steps)? CPWG to draft a Public Comment for ALAC. |
Informes de la sesión de At-Large de ICANN79
Formato del informe:
¿Qué sucedió?
- Tema 1
- Tema 2
¿Cuáles son las conclusiones clave específicas de At-Large de esta sesión?
- Tema 1
- Tema 2
¿Cuáles son los puntos de acción específicos de At-Large (próximos pasos)?
- Tema 1
- Tema 2
Sesión |
Fecha y hora (local) |
Relator |
Informe |
Fotos (opcional) |
¿Qué sucedió? Ejemplo: Esta sesión debatió... ¿Cuáles son las conclusiones clave específicas de At-Large de esta sesión? Ejemplo: At-Large está interesado en... ¿Cuáles son los puntos de acción específicos de At-Large (próximos pasos)? Ejemplo: At-Large necesita... |
||||
Rapports de séance d’At-Large de l’ICANN79
Format du rapport :
Que s’est-il passé ?
- Item 1
- Item 2
Quels sont les principaux points à retenir de cette séance ?
- Item 1
- Item 2
Quelles sont les mesures spécifiques à prendre (étapes suivantes) ?
- Item 1
- Item 2
Séance |
Date/heure (locale) |
Rapporteur |
Rapport |
Photos (facultatif) |
Que s’est-il passé ? Exemple : Lors de cette séance, la discussion a porté sur... Quels sont les principaux points à retenir de cette séance ? Exemple : At-large s’intéresse à... Quelles sont les mesures spécifiques à prendre (étapes suivantes) ? Exemple : At-Large a besoin de... |
||||