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 | What happened? This session discussed two outstanding issues from the Charter Questions from Phase 2 of the EPDP on IDNs. These were: (a) Whether or not the EPDP should make a recommendation on the need for registries to evolve their own systems for IDN Table Harmonization; and (b) If the information returned by RDDS should include information on the variant set, noting that RDDS does not currently provide for information on variants. What are the At-Large specific takeaways from this session? IDN Table Harmonization is important for end-users amongst other stakeholders as harmonization ensures that there is a consistent and predictable way second-level labels behave at the second level. However, registries have difficulties in accepting any binding recommendation on how harmonization should be done. End-users and registrants need a single source of information regarding variants, particularly delegated variants. Although RDDS doesn't currently provide information on variants, it is not difficult for registries to provide information on delegated variants. What are the At-Large specific action items? On the RDDS search output, registrants and end-users should be able to access authoritative information on variants, especially the delegated variants of a primary label. Next Steps On RDDS, EPDP team needs to discuss further how to make information on variants accessible to everyone that requires it. |
||
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: Universal Acceptance Committee Work Session |
Saturday, 2 March at 13:15 | Laura Margolis | 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) |
GDS: Subpro IRT Work Session (2 of 3) |
Monday, 4 March at 16:15 | Use template |
||
GAC Discussion on DNS Abuse Mitigation |
Monday, 4 March at 16:15 | Use template |
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 |
|
New gTLD Program Next Round: Planning for String Similarity Review Work Session |
Tuesday, 5 March at 15:00 | Bill Jouris | Use template |
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 |
Wednesday, 6 March at 10:30 | Sebastien Bachollet | Use template |
|
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 | Use template |
|
FY26-30 Strategic Plan Development Community Consultation |
Wednesday, 6 March at 10:30 | Claire Craig | Use template |
|
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... |
||||