3,197
edits
Changes
Jump to navigation
Jump to search
Line 40:
Line 40: + + + + + + − − ====Name Collision==== − * The [[SSAC]] presented on the progress of the [[Name Collision Analysis Project]].<ref name="ncap">[https://74.schedule.icann.org/meetings/wcin8eB2MQNNRwWP6 ICANN 74 Archive - NCAP Status Update], June 14, 2022</ref> Due to a small meeting room, seats for the presentation were fully reserved before the commencement of the meeting. The discussion group presented on the workflow for name collision analysis and evaluation, as well as the current state of the project. NCAP project members also held working group meetings during the conference, which were also open to the public.<ref>[https://74.schedule.icann.org/meetings/th2nNfvvn5mGPoj3e ICANN 74 Archive - NCAP Discussion Group], June 14, 2022</ref> Line 55:
Line 58: +
→Policy Forum
** Commenters noted that [[Contractual Compliance]] was not necessarily calling for more tools to combat abuse through the [[Registrar Accreditation Agreement]] or [[Registry Agreement]].
** Commenters noted that [[Contractual Compliance]] was not necessarily calling for more tools to combat abuse through the [[Registrar Accreditation Agreement]] or [[Registry Agreement]].
** The second half of the session was devoted to the continued work of the small team on specific issues or recommendations. In particular, the small team focused on the conversation that began at [[ICANN 73]] regarding malicious registration versus compromised websites.
** The second half of the session was devoted to the continued work of the small team on specific issues or recommendations. In particular, the small team focused on the conversation that began at [[ICANN 73]] regarding malicious registration versus compromised websites.
====External Forces: Governments, International Agreements, & Emergencies====
* [[EURALO]] hosted a policy session on issues facing ICANN and other Internet Governance bodies in time of emergency.<ref>[https://74.schedule.icann.org/meetings/khmnpDKfTLdvkpCCm ICANN 74 Archive - At-Large EURALO Policy: Internet Governance and Multistakeholderism in Times of Emergency], June 16, 2022</ref>
====Name Collision====
* The [[SSAC]] presented on the progress of the [[Name Collision Analysis Project]].<ref name="ncap">[https://74.schedule.icann.org/meetings/wcin8eB2MQNNRwWP6 ICANN 74 Archive - NCAP Status Update], June 14, 2022</ref> Due to a small meeting room, seats for the presentation were fully reserved before the commencement of the meeting. The discussion group presented on the workflow for name collision analysis and evaluation, as well as the current state of the project. NCAP project members also held working group meetings during the conference, which were also open to the public.<ref>[https://74.schedule.icann.org/meetings/th2nNfvvn5mGPoj3e ICANN 74 Archive - NCAP Discussion Group], June 14, 2022</ref>
====Prioritization====
====Prioritization====
* The [[Prioritization Framework]] was featured in a broader plenary session on priority-setting.<ref>[https://74.schedule.icann.org/meetings/ZP3ZHC242wXKnWRdP ICANN 74 Archive - Plenary Session: Who Sets ICANN's Priorities?], June 14, 2022</ref> The briefing paper for the session provided some background on the ongoing struggles with ICANN board, org, and community workloads, and the enduring call for prioritization.<ref name="prbrief">[https://cdn.filestackcontent.com/content=t:attachment,f:%22Who%20Sets%20ICANN's%20Priorities_ICANN74%20Plenary%20Session%20Briefing%20Paper.pdf%22/v9Y65TZSCqr7ydRGjf0o ICANN 74 Archive - Briefing Paper: Who Sets ICANN's Priorities?], June 2022</ref> The paper noted that a similar plenary session was held at [[ICANN 59]]:
* The [[Prioritization Framework]] was featured in a broader plenary session on priority-setting.<ref>[https://74.schedule.icann.org/meetings/ZP3ZHC242wXKnWRdP ICANN 74 Archive - Plenary Session: Who Sets ICANN's Priorities?], June 14, 2022</ref> The briefing paper for the session provided some background on the ongoing struggles with ICANN board, org, and community workloads, and the enduring call for prioritization.<ref name="prbrief">[https://cdn.filestackcontent.com/content=t:attachment,f:%22Who%20Sets%20ICANN's%20Priorities_ICANN74%20Plenary%20Session%20Briefing%20Paper.pdf%22/v9Y65TZSCqr7ydRGjf0o ICANN 74 Archive - Briefing Paper: Who Sets ICANN's Priorities?], June 2022</ref> The paper noted that a similar plenary session was held at [[ICANN 59]]:
<blockquote>While ICANN community discussions with the ICANN Board and ICANN org were ongoing, there was a perceived risk that various ICANN community groups were asserting different priorities with different interpretations.<br /> The ICANN Strategic and Operating Planning Framework provided an initial shared understanding about prioritization, but further work was needed on how to prioritize projects related to the strategic plan and how to meet evolving needs. The plenary session explored the likely benefits from future discussions about how to set priorities.<ref name="prbrief" /></blockquote>
<blockquote>While ICANN community discussions with the ICANN Board and ICANN org were ongoing, there was a perceived risk that various ICANN community groups were asserting different priorities with different interpretations.<br /> The ICANN Strategic and Operating Planning Framework provided an initial shared understanding about prioritization, but further work was needed on how to prioritize projects related to the strategic plan and how to meet evolving needs. The plenary session explored the likely benefits from future discussions about how to set priorities.<ref name="prbrief" /></blockquote>
====Subsequent Procedures for new gTLDs====
====Subsequent Procedures for new gTLDs====
====[[Policy Development Process to Review the Transfer Policy|Transfer Policy Review]]====
====[[Policy Development Process to Review the Transfer Policy|Transfer Policy Review]]====
* The working group initiated work on Phase 1(b) of the Transfer Policy Review PDP.<ref>[https://74.schedule.icann.org/meetings/exSok5N3N9WTCM4LH ICANN 74 Archive - GNSO Transfer Policy Review PDP Working Group], June 13, 2022</ref>
* The working group initiated work on Phase 1(b) of the Transfer Policy Review PDP.<ref>[https://74.schedule.icann.org/meetings/exSok5N3N9WTCM4LH ICANN 74 Archive - GNSO Transfer Policy Review PDP Working Group], June 13, 2022</ref>
====SSAD and Alternative Tool Options====
====SSAD and Alternative Tool Options====
* The [[GNSO]] held a session on [[Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data#EPDP Phase 2|Phase 2]] of the EPDP on the Temporary Specification for gTLD Registration Data, whose recommendations focused on creating a Standardized System of Access/Disclosure of registration data ([[SSAD]]).<ref name="ssad">[https://74.schedule.icann.org/meetings/EsEMmLrkif6b52rJB ICANN 74 Archive - GNSO: EPDP Phase 2 (SSAD)], June 13, 2022</ref> Correspondence and analysis before ICANN 74 had resulted in the opinion of GNSO Council that a "[[SSAD#Simple Ticketing System (aka SSAD Light)|SSAD Light]]" option might be more feasible and cost-effective. The session therefore focused on options and tools for a SSAD Light system.<ref name="ssad" /> [[Goran Marby]] introduced [[Ashwin Rangan]]'s presentation on a "WHOIS Disclosure System," a technical solution for the reporting of registration data. Rangan then proceeded to describe how ICANN org might be able to leverage existing technologies to create a solution for the needs of accurate access and disclosure of registration data.<ref name="ssad" /> The proposal was to utilize the ICANN Account authorization system to allow users to request registration information through ICANN's [[Naming Services Portal]], which is built with SalesForce. This would create a ticket capture method, and would allow each request to be handled in a pre-existing service system. The WHOIS Disclosure System would then be an application that would allow retrieval of encrypted registration data. The proposal would balance the need to access registration data with the requirements of GDPR and other data privacy regulations. It would also sidestep the requester authentication process that rendered SSAD too expensive in the eyes of ICANN org.<ref name="ssad" /> During Q &A, Marby emphasized that the technical aspects of the proposal were designed to avoid complications with GDPR.
* The [[GNSO]] held a session on [[Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data#EPDP Phase 2|Phase 2]] of the EPDP on the Temporary Specification for gTLD Registration Data, whose recommendations focused on creating a Standardized System of Access/Disclosure of registration data ([[SSAD]]).<ref name="ssad">[https://74.schedule.icann.org/meetings/EsEMmLrkif6b52rJB ICANN 74 Archive - GNSO: EPDP Phase 2 (SSAD)], June 13, 2022</ref> Correspondence and analysis before ICANN 74 had resulted in the opinion of GNSO Council that a "[[SSAD#Simple Ticketing System (aka SSAD Light)|SSAD Light]]" option might be more feasible and cost-effective. The session therefore focused on options and tools for a SSAD Light system.<ref name="ssad" /> [[Goran Marby]] introduced [[Ashwin Rangan]]'s presentation on a "WHOIS Disclosure System," a technical solution for the reporting of registration data. Rangan then proceeded to describe how ICANN org might be able to leverage existing technologies to create a solution for the needs of accurate access and disclosure of registration data.<ref name="ssad" /> The proposal was to utilize the ICANN Account authorization system to allow users to request registration information through ICANN's [[Naming Services Portal]], which is built with SalesForce. This would create a ticket capture method, and would allow each request to be handled in a pre-existing service system. The WHOIS Disclosure System would then be an application that would allow retrieval of encrypted registration data. The proposal would balance the need to access registration data with the requirements of GDPR and other data privacy regulations. It would also sidestep the requester authentication process that rendered SSAD too expensive in the eyes of ICANN org.<ref name="ssad" /> During Q &A, Marby emphasized that the technical aspects of the proposal were designed to avoid complications with GDPR.