At-Large Session Reports
Resources:
- ICANN79 Schedule
- At-Large ICANN79 workspace
- At-Large ICANN79 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: IDN EPDP Working Session |
Saturday, 2 March at 09:00 | This session discussed two outstanding issues from the Charter Questions from Phase 2 of the EPDP on IDNs. These were:
Full report available here: At-Large ICANN79 Documents |
||
GDS: Subpro IRT Work Session (1 of 3) |
Saturday, 2 March at 10:30 | Use template |
||
GNSO: Transfer Policy Review PDP Working Group (1 of 2) |
Saturday, 2 March at 13:15 | Use template |
||
ccNSO: DNS Abuse Standing Committee Community Update |
Saturday, 2 March at 15:00 | Aris Ignacio | Use template |
|
GNSO: Transfer Policy Review PDP Working Group (2 of 2) |
Saturday, 2 March at 15:00 | Shah Zahidur Rahman | Use template |
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
|
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 | Use template |
|
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. |
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
UA Day 2024 Overview Work Session |
Wednesday, 6 March at 9:00 | Laura Margolis | Use template |
|
Continuous Improvement Program Community Coordination Group (CIP-CCG) Meeting Agenda: https://community.icann.org/pages/viewpage.action?pageId=295043305 |
Wednesday, 6 March at 10:30 | What happened? The CIPCC held its monthly meeting #4 during ICANN79. They let the community know the focus of their work, their objectives, and their progress. They discussed the Assigned Task among the CIP volunteers on the creation of the Draft Principles and Criteria for the framework of the Continuous Improvement Program. What are the At-Large specific takeaways from this session? Atlarge would be interested in answering questions about the effectiveness and efficiency of the work of your AC/SO and NomCom and if you feel that you are doing your job well, then what processes could you improve further? Atlarge would be interested in organizations and members of their structure being informed of these criteria exercises to make bottom-up contributions that enrich the construction of a framework that will define the continuous improvement process for AC/SO and NomCom in the future. What are the At-Large specific action items (next steps)? After ICANN79, CIP volunteers must coordinate with the leadership of their home groups to locate a recurring space in which they can update their organization and request contributions for the discussion and construction that takes place in CIPCC. From our monthly ALAC meetings, we can report whether these updates are being made periodically as needed for the work of the CIPCC. |
||
GNSO SubPro Supplemental Recommendations Community Consultation |
Wednesday, 6 March at 10:30 | Tijani Ben Jemaa | Use template |
|
GNSO: Registrars and ICANN: Validation, Verification, and Accuracy - Oh My! |
Wednesday, 6 March at 10:30 | Eduardo Diaz | What happened? This session discussed the practices and experiences of gTLD registrars relating to the validation and verification of domain name registration data. Key topics included the onboarding process for ICANN-accredited registrars, RrSG membership benefits, and the importance of data accuracy. The meeting featured presentations, discussions, and a Q&A session, highlighting the challenges and costs associated with validation and verification processes. A significant portion of the discussion focused on the need for a trustworthy registration process, the use of digital ID for verification in certain jurisdictions, and the potential for collaborative efforts among registrars to streamline and reduce the costs of these processes. What are the At-Large specific takeaways from this session? At-Large is interested in the implications of these practices for the broader community, especially in ensuring a safe and secure domain name system while balancing the operational and financial burdens on registrars. The discussions around digital ID and the potential for collaborative verification efforts are particularly relevant, as they could lead to more inclusive and efficient practices that benefit all stakeholders. Additionally, the emphasis on the importance of data accuracy and the challenges associated with achieving it resonate with At-Large's commitment to user trust and the integrity of the domain name system. What are the At-Large specific action items (next steps)? At-Large needs to engage with ICANN and other stakeholders to explore further the feasibility and implications of implementing a system where verification performed by one registrar can be utilized by another, potentially reducing costs and administrative burdens. At-Large should advocate for the development of guidelines that support the use of digital IDs for domain registration verification, especially in regions where such systems are already in place. This would streamline the verification process without compromising security or privacy. At-Large could facilitate discussions among its members to gather insights and feedback on the current challenges registrars face in validating and verifying domain registration data. This could inform At-Large's contributions to policy discussions and its advocacy efforts. At-Large may consider organizing a workshop or session at a future ICANN meeting to discuss the potential for collaborative efforts among registrars and other stakeholders to address the challenges of validation and verification, including the exploration of new technologies and methodologies. At-Large should monitor developments related to NIS2 and other relevant legislation to ensure that the interests and concerns of the broader Internet user community are considered in discussions about domain registration data accuracy and verification. |
|
FY26-30 Strategic Plan Development Community Consultation |
Wednesday, 6 March at 10:30 | Claire Craig | What happened?
What are the At-Large specific takeaways from this session?
What are the At-Large specific action items (next steps)?
|
|
IFR2 Team Meeting and Work Session |
Wednesday, 6 March at 13:15 |
|
Use template |
|
ICANN Grant Program |
Wednesday, 6 March at 15:00 | Use template |
||
GDS: Subpro IRT Work Session (3 of 3) Agenda: https://community.icann.org/x/doAvEQ |
Wednesday, 6 March at 16:15 | Use template |
Session |
Date/Time (local) | Rapporteur | Report | Photos (Optional) |
GNSO Council Small Team Plus - SubPro Supplemental Recommendations Work Session |
Thursday, 7 March at 9:00 | Tijani Ben Jemaa | Use template |
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... |
||||