[[-- Translated text (en -> es) --]] Hola, Envío esta importante nota a la lista LACRALO en inglés ya que contiene contactos originados en inglés. Esto es extremadamente importante informe del SSAC (pregunte si necesita más información al respecto), sobre colisiones de nombres de dominio. No he enviado la publicación original del SSAC sino la comente sobre su proceso, que luego incluye la publicación original del SSAC. Usuarios finales en pequeñas organizaciones e individuos, como afirma LACRALO. representar y cuyos intereses LACRALO se representa a sí mismo como administrador, son particularmente propensos a sufrir daños por colisiones de nombres de dominio, porque algunos de estas colisiones involucran nombres frecuentemente utilizados en la gestión de redes de área local o pequeños ISP, donde no hay disponibilidad de la tipo de personal técnico y experiencia, o la capacidad de contratar a terceros servicios o consultores, para configurar las cosas adecuadamente. Cada ALS de LACRALO debe recibir asesoramiento técnico ya sea de su propia miembros y personal o de vecinos, amigos y aliados, y su servicio proveedores, para poder participar en este desarrollo y prevenir desarrollo de políticas que puedan provocar mayores daños. Este es un importante aportes y restricciones sobre los nuevos gTLD. Alejandro Pisanty ---------- Mensaje reenviado --------- De: Andrey Kolesnikov vía At-Large<at-large@atlarge-lists.icann.org> Fecha: martes 7 de mayo de 2024 a las 9:40 a.m. Asunto: Re: [At-Large] El SSAC ha publicado el SAC124 Para: Matías M. Hudobnik<matthias@hudobnik.at> , At-Large en todo el mundo < at-large@atlarge-lists.icann.org> ¡Gracias Matías! Vale la pena señalar que la implementación del proyecto duró muchos años con numerosos días y horas invertidos por el grupo de trabajo del SSAC bajo el guía de Suzanne y Matt. El proyecto también requirió una participación activa de la organización de la ICANN y de muchas otras partes interesadas de la ICANN. Este documento constituye un testimonio de un trabajo meticuloso, innumerables discusiones, debates y compromisos. ¡Gran trabajo! --andrei El martes 7 de mayo de 2024 a las 12:20 p. m. Matthias M. Hudobnik a través de At-Large < at-large@atlarge-lists.icann.org> escribió:
Hi colleagues, the SSAC has published SAC124.
*### SSAC Advice on Name Collision Analysis (SAC124):*
The SSAC provides its advice on name collision analysis based on the NCAP Study Two report. The SSAC fully endorses the findings and recommendations presented in the report and recommends the ICANN Board adopt and implement these recommendations.
The SSAC supports the centralized and coordinated approach proposed by Study Two. This approach is essential for implementing effective measures to mitigate the two data-access-related risks associated with name collisions:
· Delegation Risk: Privacy and risks to users and end systems from name collisions associated with the delegation of a TLD.
· Assessment Risk: Privacy risks associated with the execution of data collection methods in the proposed Name Collision Risk Assessment Framework.
While acknowledging ICANN org's privacy concerns around the proposed data collection methods, the SSAC offers three considerations:
· Privacy risks are inherent in managing name collision risk due to ICANN's role in coordinating gTLD allocation and assignment.
· Avoiding data collection does not resolve delegation privacy risks, but rather transfers these risks to third parties, potentially amplifying harm.
· Effective management of security, stability and resiliency risks requires a proactive approach to name collision identification and mitigation.
Based on these, the SSAC recommends prioritizing solutions that allow sufficient data collection and analysis to properly inform name collision mitigation strategies. Failing to mitigate delegation risks due to assessment risk concerns would threaten DNS security/stability and end-user privacy.
The SSAC's recommendations are:
· Adopt and implement all recommendations in NCAP Study Two.
· Prioritize finding appropriate solutions within the proposed framework that enable sufficient data collection and analysis for mitigation.
· The SSAC welcomes engagement from ICANN org and offers its expertise.
The SSAC acknowledges more work is needed on privacy aspects and looks forward to collaborating with ICANN org and privacy experts.
Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee....
Have a nice day!
Best,
Matthias
______________________________
Ing. Mag. Matthias M. Hudobnik
FIP • CIPP/E • CIPT • DPO • CIS LA
matthias@hudobnik.at
@mhudobnik _______________________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large
At-Large Official Site: http://atlarge.icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-- Andrei Kolesnikov IOTAS.RU con robot de calendario ________________________________ At-Large mailing list At-Large@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/at-large At-Large Official Site: http://atlarge.icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . .